3 times sysprep

  • Thread starter Thread starter Brian
  • Start date Start date
B

Brian

I have heard that i will only be able to deplay Vista 3 times. We have a
site license for Vista and we re-image over and over again. Is this true? or
what is the way for mass deplayment going to be?

Thanks
 
Well... if you're going to "deplay" Vista, then one might assume that your
install count will decrement. Otherwise, I have no idea what you're talking
about because you do not disclose what type of site license you have and
what exactly it is that you're doing...

Lang
 
Sorry for the spelling. "deploy" an image. We are a college and the
computers will be re-imaged each semester. As well staff computers are
re-imaged regularly. We have more than 5000 computers in this location. This
is the way we have done it with 98 and xp. I am not sure why my install
count will decrement.
 
Brian said:
Sorry for the spelling. "deploy" an image. We are a college and the
computers will be re-imaged each semester. As well staff computers are
re-imaged regularly. We have more than 5000 computers in this location.
This is the way we have done it with 98 and xp. I am not sure why my
install count will decrement.
Click to expand...

It is not true that you will only be able to deploy Vista three times.
With 5,000 machines you obviously must have a volume license. Contact
your Microsoft representative for details about handling your specific
situation (which is not unusual at all). There is no way that your
college doesn't have a support contract with Microsoft and a
representative with that many seats licensed.


Malke
 
We do.
Us techs are taking a vista training course and we are in clase now and this
is what this guy is telling us.
Thanks
 
Brian said:
I have heard that i will only be able to deplay Vista 3 times. We have a
site license for Vista and we re-image over and over again. Is this true? or
what is the way for mass deplayment going to be?

Thanks
Click to expand...


You need to put something like this in your unattend.xml file:

<settings pass="generalize">
<component name="Microsoft-Windows-Security-Licensing-SLC"
processorArchitecture="x86" publicKeyToken="31bf3856ad364e35"
language="neutral" versionScope="nonSxS"
xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SkipRearm>1</SkipRearm>
</component>
</settings>



Read up in the WAIK about "skiprearm" -- this will let you run sysprep
more than 3 times while you are testing your image out. Now, I leave
it for the reader to determine if they ever want to remove it -- it
probably depends on how you are doing your imaging.

IMO, if you are doing something like maintaining an image on a hard
disk that you manually update once a month (say patch Tuesday) and then
reburn your image with Ghost/Acronis -- then you'd leave this in there
and not really worry about the affect of the non-counting against the
KMS server, etc..

If you are using imageX and slipstreaming updates into your load set,
then maybe you don't need "skiprearm".



but I have yet to figure out any scenario where I'd actually want to
*remove* this code that's going to have any adverse affect on my
deployment.


I've probably run my unattend.xml file about 100+ times now with no
problems with this in it. Without it? Running sysprep 4 times will
hose your Vista load and you'll have to start all over. Really.

- Steve
 
Back
Top