Reset policy

[X-13]

I've been given the, in my opinion, vague advice to "do a restore after a policy reset"

 

But I've got no clue as the WHAT policy I'm supposed to be resetting. [Or if I can even do it...]

 

It's to do with drivers not being installed during the build process.

 

Server is 2003, clients are WinXP:SP3. All on CC3.

 

If it helps the drivers are for the audio and video.

[webman]

I'm not sure what policy is being hinted at either.

 

Are the drivers related to Realtek HD Audio? Do you have a relevant HSP installed? What about logs/events etc - are there any other indicators than "sound not working" to say that they haven't installed correctly?

[X-13]

I'm sure they're realtek audio HD. If I manually install it, it changes from [unknown device on HD audio bus] to Realtek HD audio.

 

I've built, rebuilt and restored before and all the drivers have gone on fine. I've even [shred -vfz -n 10 /dev/hda], installed Ubuntu 10.10 and then used a USB build disk to re-install XP on CC3 without a problem.

[CHR1S]

My memory of CC3 is hazy at best, is this a custom build disk with the drivers for the audio? Or am I not getting the issue right?

[X-13]

My memory of CC3 is hazy at best, is this a custom build disk with the drivers for the audio? Or am I not getting the issue right?

 

Nah, it's a standard build disk made from RM Build disk manager.

 

All it had on it are the network card drivers, and during the XP install phase it SHOULD get the audio drivers from the server.

[CHR1S]

Yes your right, same as CC4.

 

If the driver isnt imported correctly or runs in GUI mode during the build they will never install (I have had this exact problem, albeit under CC4).

 

You have to reimport the driver not the exe or msi (CC4 has the exe import option, not sure on CC3) and try again. You could sit and watch the build and wait for the driver to install with the GUI to confirm.

[webman]

Ah Do you have such a thing as MS update KB888111? IIRC, that first makes the audio bus visible to Windows, which then allows the driver to successfully install. It's usually part of the driver package in some random folder, and is (should be) mentioned as a pre-requisite in the README. I can't remember if it's part of SP3 or not though.

 

We had a similar problem. Couldn't get machines to build with the driver built-in, so I created a CC3 package that silently installed MS KB888111 and then force-installed the drivers.

 

We're on CC4 now, so the problem is a distant memory. I may still be able to lay my hands on the package though and will post back. Watch this space.

[X-13]

Ah Do you have such a thing as MS update KB888111? IIRC, that first makes the audio bus visible to Windows, which then allows the driver to successfully install. It's usually part of the driver package in some random folder, and is (should be) mentioned as a pre-requisite in the README. I can't remember if it's part of SP3 or not though.

 

We had a similar problem. Couldn't get machines to build with the driver built-in, so I created a CC3 package that silently installed MS KB888111 and then force-installed the drivers.

 

We're on CC4 now, so the problem is a distant memory. I may still be able to lay my hands on the package though and will post back. Watch this space.

 

 

It worked before so I'm assuming it's there. I'll check tomorrow when I get in. If this is the problem, I'm going to rage so hard...

[X-13]

Just had a look, no KB888111 that I can see.

 

But, from what I remember, that's for SP2.

 

I've one set of drivers to my build disk. I was presented with about 13 .inf files, I've taken a guess at which one it is.