Ok a little background. Our company has been rolling out "beta" deployments of Windows 7 to select users for testing, about 35-40 clients in all. We have been using our MAK key for now, but we are moving to KMS. I got KMS up and running on Server 2003 SP2 with a B key, all was well. I decided to try to activate myself first to test it. So I ran slmgr.vbs and updated my key to a KMS client key (-ipk), and ran slmgr.vbs /ato to activate myself and ping the KMS host. I can see my activation in the event log on the KMS host, so I know it works and everything talks and processes.
Here's my problem. KMS clients will not activate until count:25 is reached. Right now I'm at count:1 (me). After running /ato my system obviously got back <25 for the count and thus is not activated. The problem is now it says my copy of Win7 Enterprise is not genuine even though it is. I need to get about 24 more people activated, and they are all end users. Is there a way to avoid this behavior until I ht the 25 count mark? I ran slmgr.vbs /rearm and rebooted, and that was okay (got rid of the not genuine message), but every time I reboot now I'm still prompted to activate even though my grace period has been reset.
So I'm trying to find out the best way to migrate 20 or so more users with the least bit of interruption and prompting to activate until we hit 25. Has anyone run into this?