A
Abhishek Samal
Hi All
In our environment, we are activating Windows Servers via KMS. The server is a clone copy of other production instances.
Troubleshooting Steps done till now:
1. Removed from domain and re-added.
2. The engineer who worked on cloning had ran sysprep. Even still to be sure, I again ran sysprep.
3. We are able to telnet on the port 1688 without any issues.
4. Then I followed some of the blogs and ran couple of commands like manually setting up the KMS using command:
slmgr /skms <KMS Server IP>:1688
slmgr.vbs /ato
It returned the errr 0x80072EE2
6. Even tried setting the key directly by:
slmgr /ipk %key%
Please help in further troubleshooting as I followed other blogs but nothing helped much.
Regards
Abhishek
Continue reading...
In our environment, we are activating Windows Servers via KMS. The server is a clone copy of other production instances.
Troubleshooting Steps done till now:
1. Removed from domain and re-added.
2. The engineer who worked on cloning had ran sysprep. Even still to be sure, I again ran sysprep.
3. We are able to telnet on the port 1688 without any issues.
4. Then I followed some of the blogs and ran couple of commands like manually setting up the KMS using command:
slmgr /skms <KMS Server IP>:1688
slmgr.vbs /ato
It returned the errr 0x80072EE2
6. Even tried setting the key directly by:
slmgr /ipk %key%
Please help in further troubleshooting as I followed other blogs but nothing helped much.
Regards
Abhishek
Continue reading...