Sysprep limitation to 4 uses

  • Thread starter Thread starter Eric Joy
  • Start date Start date
E

Eric Joy

Problem Description: We sell Windows XP on our systems
pre-loaded and pre-configured. We SYSPREP the "master" (a
system configured 'identical' to the customers system) in
order to make sure the customer does not have to (and it
is critical in order to make our software work
correctly). From time to time we have to update that
master image (driver changes, etc) and we have exceeded
our 4 time limit on SYSPREPing that system.

We need to be able to SYSPREP beyond the 4 time
limitation.

Can you tell us (1) If there is a way to bypass that
limit, (2) a better way to do what we are doing, or (3)
any other solution possibilities that you may see???

Eric Joy
Product Test Technician
AIS 800-441-4487 x1762
Problem Area: Setup
Frequency of problem: Always Happens
Operating system / version: Windows XP
 
If you always make your changes to the same image, you won't have a problem.

Here's an example:

You build the system fresh, Sysprep it, and take an image (Image A - 3 uses
left).

You now need to make some changes, so you install Image A on a computer,
make the changes, Sysprep it, and recapture the image (Image B - 2 uses
left).

You need to make another change. If you put Image B on the system and
Sysprep again, you'll only have 1 use left. If you put Image A on the
machine, you'll need to make all the changes that you made in Image B again,
but you'll still have 2 uses left, which really won't matter if you keep
reverting to Image A.

Also, Volume License copies of Windows don't have a limitation on the number
of uses, but I don't think that's really applicable in your situation.
 
Understood. One way we thought of doing it was to create
the system (load it as we would) then image it (Image A).

Sysprep, image (Image B) and then release.

When we go to make changes, we would load Image A and
then make all previous changes as well as the NEW changes
and then image it (Image C) and Sysprep that image and
release.

The only thing is since I reported this problem (and my
solution above) to my boss he decided to your answer is
the easiest.. so that is what we will do if Microsoft
does not answer the case.

Thank You
 
Back
Top