SP2 SysPrep Imaging Problem: Lost Model Independence

[Guest]

I am a professional PC Systems Administrator who has prepared more than 100
Windows images that have been successfully deployed to thousands of PCs. I
have a problem that started with the new SysPrep for XP SP2 that I have not
seen described here:

Starting with an XP SP1 image that worked fine on several closely related
models of computers, I upgrade to SP2 (and other new software) using a
slipstreamed VL copy of XP SP2. I then run the new SysPrep -mini - reseal
and upload the image to our server. (I happen to use Symantec Ghost 8.0 and
8.2, but the problem appears independent of how the image is transferred.)

When I download that image to the exact same model of computer and reboot,
it works fine. However, when I download that image to a closely related
computer model and reboot, it always immediately bluescreens, then reboots
offering me Safe Mode/Last Known Good, none of which ever works. I have
found nothing that works at this point in my testing, no repair or Recovery
Console. I have found no different SysPrep.exe switches or SysPrep.inf
settings that have any affect in preventing this problem. After about 100
hours of testing, I'm out of ideas of what else to try.

Let me emphasize that this process of using one image for 2-3 closely
related models has worked fine from Windows 2000 through Windows XP SP1. I
maintain a dozen images that have always worked like this, and they cover
about 20 different models of Compaq, Dell, Gateway, and IBM computers. I'm
not trying to use one image for everything; just one image for 2-3
indistinguishable computer models by one manufacturer. This problem occurs
on every image I have upgraded, not just some. I even tested an image I
didn't create: I took a brand new computer that came with XPSP2, ran SysPrep,
downloaded it to a closely related model, and got the same problem.

Why would this process break with SP2's SysPrep? What can I do to fix it?
I cannot maintain 20 different images, one for each slight variation in each
model line. (I can hardly maintain the dozen I have.) Is there anything I
can do to troubleshoot this problem? Does anyone from Microsoft have
_anything_ I can try? I'm willing to open a support incident, if that's what
it takes. Would reverting to SP2 SysPrep improve matters or make them worse?


You experts out there, this one's for you -- Please Help!
Sande

 

[Michael Niehaus [MS]]

This sounds like a mass storage controller issue (STOP 0x0000007B). Do you
have the PnP IDs in the Sysprep.inf for the mass storage adapter of the
problematic machine? Do you have the "BuildMassStorageSection=Yes"
directive in the Sysprep.inf (if you haven't manually added the PnP ID)?
What make and model is this new machine? Are you still building the image
on the same machine that you used to use for XP SP1?

-Michael Niehaus
Senior Consultant
MCS US Centers of Excellence - Deployment AOS
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Guest]

I agree with Michael. Sounds like the wrong HD Controller is being installed.
Also check the type of Hal you are using. For example, Dell GX260s and
GX270s may seem similar but the GX270s use hyperthreading and it uses a Hal
driver for a multi-processor system. This could cause issues on Images.

Michaels answer should do the trick though...

 

[Guest]

This sounds like a mass storage controller issue (STOP 0x0000007B). Do you
have the PnP IDs in the Sysprep.inf for the mass storage adapter of the
problematic machine? Do you have the "BuildMassStorageSection=Yes"
directive in the Sysprep.inf (if you haven't manually added the PnP ID)?

Thank you both for your quick replies. I have not added the mass storage
section to Sysprep.inf, because I never had to before. Why would this work
with XP SP1 Sysprep but break with SP2 Sysprep?

I do plan to test this (adding the mas storage section), but I don't think
it's the problem. For example, I have two SP1 images that cover 6
closely-related Gateway E-series computers. There are two images rather than
one because the oldest three variations do use a different IDE card than the
newest three. However, the newest three use exactly the same HDC, as far as
I can tell. And with the oldest three, I can pull out the HDC and examine
it, and they are all the same.

Seeing other information in this newsgroup about HAL differences, I checked
that today. But all 6 of these Gateways use the same ACPI HAL, the specific
HAL that *is* recommended for compatibility.

What make and model is this new machine? Are you still building the image
on the same machine that you used to use for XP SP1?

Keep in mind that this is happening in all of my images: in the two Gateway
images, in the Dell image, in a ThinkPad image. And yes, I always build all
my images on "rack PCs" I have in my office that I don't swap out.

Any other ideas, anyone?

Or, for a different angle, what are the implications of using the SP1
Sysprep on SP2 images? I saw several contributors who are doing this, but
I'm reluctant because I've seen subtle Sysprep errors appear long after
imaging. Sande

 

[Guest]

Michael, I apologize for doubting your suggestion; you were absolutely
correct. The [SysprepMassStorage] section of Sysprep.inf, which I never
needed before SP2, is now apparently required. (Would it be so hard to say
that in the documentation?) Adding this section fixed the problem in one of
my Gateway images, and I'll bet it will fix the other images too. Maybe it
will even let me have fewer images!

I should mention some other advice I found, that may be necessary on newer
computers. (This was not necessary on the Gateway image.) Apparently, some
of the new hyperthreading Pentium 4 CPUs can introduce a problem of what HAL
driver is used in an image. The article here, though it predates SP2,
describes the problem and a solution: http://www.jnux.net/community/hal/

I'm not endorsing that diagnosis or solution; I just thought I should
mention it here, for completeness.

Thanks again to Michael and William for their sound advice.
Sande