P
petesa
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
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