Saturday, July 07, 2012 8:46 PM
Say I have a Windows 7 machine which has activated against our KMS server with 1 rearm remaining. If I was to run "slmgr.vbs /rearm", reboot, login again and run slmgr.vbs /dlv what would you expect the output to look like?
Saturday, July 07, 2012 9:18 PMOn Sat, 7 Jul 2012 20:46:38 +0000, J. Wall wrote:Software licensing service version: 6.1.7601.17514Name: Windows(R) 7, Enterprise editionDescription: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENTchannelActivation ID: ae2ee509-1b34-41c0-acb7-6d4650168915Application ID: 55c92734-d682-4d71-983e-d6ec3f16059fExtended PID: 00392-00170-918-500000-03-1033-7601.0000-1892012Installation ID:006021896741368713188395245745167615940656976723547251Partial Product Key: HVTHHLicense Status: Grace PeriodTime remaining: 42540 minute(s) (29 day(s)) RemainingWindows rearm count: 0Trusted time: 2012-07-07(sorry - couldn't resist it <g>)
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
Saturday, July 07, 2012 9:40 PMThat is what I'd expect as well but... the machine went to back to initial grace with 2 rearms remaining. I think I am losing it.
Saturday, July 07, 2012 10:03 PM
The only way I know to increase the number of rearms available is to install the Service Pack - I haven't tested to see if uninstalling it decrements it.
Sh&t happens - and sometimes in to our benefit :)
- Marked As Answer by J. Wall Saturday, July 07, 2012 10:31 PM
Saturday, July 07, 2012 10:27 PM
What I was afraid of is getting myself into a hole where I can no longer update my thick image because I've ran out of rearms, preventing sysprep /generalize from running.
From what I've read and my testing this afternoon though, as long as we have a kms server and I have a non-sysprepped image go to back to each time I need to update, I can restore this non-sysprepped image, activate it, and this will give me a rearm back, allowing me to run sysprep /generalize and capture a new image to be deployed to the rest of the machines.
I'd really like to move the whole image creation procedure to an MDT tasks sequence but we have lots of legacy apps that do not support silent / unattended installs. I could probably automate these using some sort of scripting but I think that'll take more time than I have right now. To furthur complicate things some of these legacy apps need to be launched and have options configured.