Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 808
  • Last Modified:

XenApp 6.5 on PVS - change KMS server?

Hello,

I have migrated my KMS host environment over to a new Windows Server 2008 R2 server.  I have built out the temp servers needed to activate Windows Server 2008 R2 and Office 2010 Pro Plus past the grace period on the KMS host, and new servers are activating those products correctly.

I rebooted one of my XenApp 6.5 servers running from a PVS image.  Both the server OS and Office are showing up as activated.  However, if I run slmgr.vbs /dli from a cmd prompt, it is still showing the old KMS server in the "KMS machine name from DNS" line.  I have verified that the new KMS host is the only one listed in DNS.  

Do I need to reactivate the KMS keys on my PVS image in private mode to pick up the new KMS host info?  

Thank you,

wegis.
0
WEG_IS
Asked:
WEG_IS
1 Solution
 
amichaellCommented:
KMS clients typically use DNS to discover KMS hosts to activate against.  Ensure your old KMS host record is removed from DNS and the new one entered.  If you specified a particular KMS host to activate against you can remove it with the slmgr /ckms key.  See http://technet.microsoft.com/en-us/library/dn502540.aspx for more information.
0
 
Jayanta SarmahCommented:
As suggested above , KMS should be updated by DNS and I will suspect that the old server DNS entry still exist in DNS , please verify your DNS server/Servers , and I would not specify any specific KMS host to activate against , if you do may you would like to avoid that...
0
 
Ayman BakrSenior ConsultantCommented:
If you are sure that the old KMS doesn't exist in DNS, maybe you would require to issue the following command in private mode:

ipconfig /flushdns

Open in new window

0
 
Daniel BorgerCommented:
With Vdisk in Private mode

cscript.exe c:\windows\system32\slmgr.vbs /ipk YC6KT-GKW9T-YTKYR-T4X34-R7VHC  (Note – see link at the end of the email for the proper key to use here)

http://technet.microsoft.com/ru-ru/library/ff793421(en-us,printer).aspx


cscript c:\windows\system32\slmgr.vbs /skms 10.1.2.242:1688  (Note – this IP should be the KMS server )

cscript c:\windows\system32\slmgr.vbs /ato
0
 
amichaellCommented:
You don't want to activate the client while in private mode.  If you do so all target devices that use the vDisk will report the same CMID in KMS causing the KMS host count to not increment.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now