• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 271
  • Last Modified:

Using multiple RIS images / changing the default flat image / changing flat image associated with a riprep image

Hi there,
I've got a situation where I successfully created and rolled out a RIPREP image to several dozen desktop HP computers (XP Pro SP2). I then had to add another image to my RIS server, to create images for a bunch of Dells (different HAL). In order to get this to work properly I ended up having to add a new risetup image (flat OS image) to the server from a retail XP Pro disc. It wouldn't work with my original HP flat OS image or the Dell OEM media.
And in both the above cases I had to slipstream NIC drivers into the images for deployment.
My problem is this.... since I added the new RISETUP image to the server, my HP RIPREP image is broken - it won't deploy at all, and I've got a bunch more HP clients that need deploying.
I know that when you add a new RISETUP image to the RIS server, it gets set as 'default' . I think the main cause of the problem is that the new risetup image has slipstreamed drivers that work for the Dell, but cause a BSOD during the HP RIS client install.. after the CIW (both systems have broadcom gigabit NICs, but different models).
So I still have the original HP flat image on the server, how do I tell the server to use that flat image for the HP RIPREP deployments, and the new flat image for the Dell deployments?
0
budchawla
Asked:
budchawla
  • 5
1 Solution
 
budchawlaAuthor Commented:
And how can I check what the envirnment variables %INSTALLPATH% %SYSPREPDRIVERS% and %SYSPREPPATH% point to?
0
 
budchawlaAuthor Commented:
OK I managed to get past the BSOD by modifying the riprep.sif for the HP image and removing all instances of environment variables and hard-coding the paths to the correct flat OS image folder. Since the default image on the ris server is the newer one, this was being pointed to instead of the old "correct" image.
Now I get another error: error 21 that image-folder\i386\halaacpi.dll could not be loaded.
Since there haven't been any responses, and the question title still holds, I won't start another question!
0
 
budchawlaAuthor Commented:
I tried getting a copy of the hal.dll file from the windows\system32 folder off an identical desktop and renaming it halaacpi.dll and putting it in the flat image\i386 folder, but that only BSOD'd again...
0
 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

 
budchawlaAuthor Commented:
Thanks for all the responses :-)

Solution: Use volume licence media to do a risetup -add and drop it into the same folder as the older flat OS image. Slipstream drivers, and away you go.
0
 
budchawlaAuthor Commented:
P.S. Using OEM media to carry out RIS installations is not a supported way of doing things, i.e. not the "Microsoft Way"
0
 
EE_AutoDeleterCommented:
budchawla,
Because you have presented a solution to your own problem which may be helpful to future searches, this question is now PAQed and your points have been refunded.

EE_AutoDeleter
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now