Sysprep 3 Execution Limit



petesa
07-10-2005, 03:15 AM
Our Windows build has reached the 3 execution Sysprep limit, and I am
urgently searching for workaround procedures that will allow me to make
a critical utility update (install application) and then complete the
Sysprep -reseal function on it. See
http://support.microsoft.com/Default.aspx?kbid=308554

I need to update a highly complex 'Windows XP' SP2 image that has
had Sysprep -reseal run on it 3 times already. Recreating a new Windows
build, from scratch, to get around this problem is would be nearly
impossible at this point.

Legally we are ready to go: we have the valid Volume License media
('Windows XP' Professional SP2 Select CD) and employ valid Volume
Licensing.

To avoid this issue in the future a "Pre-Sysprep'ed" image will
be maintained. For now I need a workaround or a way to travel back in
time...

As far as I can tell the Sysprep 3 run limit is primarily related to an
"artificial" Sysprep count in the registry or in the "Windows
Product Activation" database. This Sysprep limit may be in place to
dissuade the use of to many different master build workstations and any
ensuing PnP play or registry "pruning" issues. We did not change
the model of the master build workstation.

Any help would greatly appreciated. Thank you

WM
07-10-2005, 03:15 AM
You aren't using Volume Licensing media if you are hitting the limit - the
limit applies only to Retail and OEM media versions of Windows. There is no
way around the limit once it is hit. However, all it means is that any
systems deployed with that image will have to be immediately activated upon
installation.


"petesa" <pmsaragosa@gmail.com> wrote in message
news:1115968882.140368.291570@g43g2000cwa.googlegroups.com...
> Our Windows build has reached the 3 execution Sysprep limit, and I am
> urgently searching for workaround procedures that will allow me to make
> a critical utility update (install application) and then complete the
> Sysprep -reseal function on it. See
> http://support.microsoft.com/Default.aspx?kbid=308554
>
> I need to update a highly complex 'Windows XP' SP2 image that has
> had Sysprep -reseal run on it 3 times already. Recreating a new Windows
> build, from scratch, to get around this problem is would be nearly
> impossible at this point.
>
> Legally we are ready to go: we have the valid Volume License media
> ('Windows XP' Professional SP2 Select CD) and employ valid Volume
> Licensing.
>
> To avoid this issue in the future a "Pre-Sysprep'ed" image will
> be maintained. For now I need a workaround or a way to travel back in
> time...
>
> As far as I can tell the Sysprep 3 run limit is primarily related to an
> "artificial" Sysprep count in the registry or in the "Windows
> Product Activation" database. This Sysprep limit may be in place to
> dissuade the use of to many different master build workstations and any
> ensuing PnP play or registry "pruning" issues. We did not change
> the model of the master build workstation.
>
> Any help would greatly appreciated. Thank you
>

petesa
07-10-2005, 03:16 AM
Thank you for your reply, this Sysprep limit issue is very frustrating.

As I understand it the 3 Sysprep Limit and Product Activation are two
entirely separate functions.

"all it means is that any systems deployed with that image will have to
be immediately activated upon installation."

Unfortunately we can't even get to the deployment stage, the problem
that we are encountering is that we can not Sysprep the image using the
Sysprep -reseal. Sysprep will not run a fourth time. Microsoft has
apparently put an artificial limit into the Sysprep 2.0, and this is
unacceptable (with legal Volume Media and Volume License) since there
is no technical reason that if Sysprep has run 3 times on the same
exact hardware it can't run 4 times on the exact same hardware. We
have not changed the model of the master build workstation or any
hardware at all; the update that was made was made was to the MS Office
installation that was on the build.

So are you saying that the "Microsoft Select Windows XP" CD that we
received as part of our Microsoft Select Subscription is NOT Volume
Licensing media?

In my opinion Microsoft should provide a work around for this Sysprep
oversight/issue (again not product activation), since there are huge
implications to its corporate customers who are the primary users of
Sysprep. Starting a Windows build over from scratch is a ludicrous
solution, in my opinion.

....still looking for a workaround procedure to the 3 run Sysprep limit.


Sysprep 3 Execution Limit