bradsorensen
asked on
Update RIS image on server 2003 r2
Im running Server 2003 R2, Ive used riprep to create a ris image on my server. The server is working fine.
Question: How do I update or slipstream windows updates/patches/software/d
FYI: My project requires that the server is not connected to the internet (no network)
Question: How do I update or slipstream windows updates/patches/software/d
FYI: My project requires that the server is not connected to the internet (no network)
RIS is replaced with windows deployment service in SP2 and it is capable of updating the source with patches and service packs.
http://technet.microsoft.com/en-us/windowsserver/bb294403.aspx
http://technet.microsoft.com/en-us/windowsserver/bb294403.aspx
Not so in Mixed or Legacy mode. You're still dealing with RIPREP and a flat file source in WDS Legacy. You can't run Legacy and Native WDS.
ASKER
Ok I still have my master system intact... on the shelf schewww.
What your saying is If I install service pack 2 for server 2003 r2 Ill have to start using WDS, is RIS gone at this point on the server? I understand that my RIS images cannot be updated but WDS images can but I can keep both.
Ive never used WDS what is the procedure for creating an image and deploying an image for WDS, remember Ive only used RIS.
Also what is the process for updating a WDS image?
Whitepapers step by step guides are apprecieated if you have them for all this...
What your saying is If I install service pack 2 for server 2003 r2 Ill have to start using WDS, is RIS gone at this point on the server? I understand that my RIS images cannot be updated but WDS images can but I can keep both.
Ive never used WDS what is the procedure for creating an image and deploying an image for WDS, remember Ive only used RIS.
Also what is the process for updating a WDS image?
Whitepapers step by step guides are apprecieated if you have them for all this...
WDS (natively) supports WIM image formats. You would use BDD2007 to create them.
You can't have your images and the new format together.
Once you install SP2 - DO NOT - open the snap in for Windows Deployment Services - only the one with (Legacy) in the name. If the server gets added to the new Native snap in then it isn't always possible to remove it. Once it's added the old functionality stops so PXE doesn't respond to clients.
All the docs you need are on www.microsoft.com/wsus.
You can't have your images and the new format together.
Once you install SP2 - DO NOT - open the snap in for Windows Deployment Services - only the one with (Legacy) in the name. If the server gets added to the new Native snap in then it isn't always possible to remove it. Once it's added the old functionality stops so PXE doesn't respond to clients.
All the docs you need are on www.microsoft.com/wsus.
ASKER
Couldn't I use a similar process as described below when Ris cant detect your network card?
See process below...
Creating an installation image with RIPrep to upload to RIS server
If RIS complains about the network card follow this process putting a driver into a RIS image
To do this copy the raw driver files into a directory that's part of the image and then update
the DevicePath accordingly. As the driver directory belongs to the image, it will be copied to
the machine's hard disk. When the machine reboots after the image is installed, Windows
should (re-)detect PNP hardware it doesn't have a driver for and look up possible driver
locations from DevicePath. This time Windows will find the driver and install it.
a. On the RIS server create the driver name directory in the image's local files -
\\SERVER\\REMINST\Setup\La
(In this step WinXP_SP2 is the RIS image you are trying to deploy to target machines).
Remember that " DellDrivers" signifies your hardware. This name is just an example and you will
need to adjust it to suit your requirements.
b. Copy the driver files into the newly created directory.
c. On the server (or your personal workstation), load regedit.
d. Load the Software registry hive of the image by selecting HKEY_LOCAL_MACHINE and
clicking "File" then "Load Hive". Navigate to
\\SERVER\REMINST\Setup\Lan
and pick the Software file.
e. Type RIS Image as the temporary name of the hive.
f. In the registry tree, navigate to
g. HKEY_LOCAL_MACHINE\RIS Image\Microsoft\Windows\Cu
pane double click the DevicePath value.
h. Add ;%SystemDrive%\Drivers\Del
i. Unload the hive by navigating to HKEY_LOCAL_MACHINE\RIS Image and selecting Unload
Hive on the File menu. Don't forget this step because otherwise the hive will not be saved
until you reboot your personal workstation.
j. Install the RIS image on a test machine as your network card drivers will be installed.
end.
See process below...
Creating an installation image with RIPrep to upload to RIS server
If RIS complains about the network card follow this process putting a driver into a RIS image
To do this copy the raw driver files into a directory that's part of the image and then update
the DevicePath accordingly. As the driver directory belongs to the image, it will be copied to
the machine's hard disk. When the machine reboots after the image is installed, Windows
should (re-)detect PNP hardware it doesn't have a driver for and look up possible driver
locations from DevicePath. This time Windows will find the driver and install it.
a. On the RIS server create the driver name directory in the image's local files -
\\SERVER\\REMINST\Setup\La
(In this step WinXP_SP2 is the RIS image you are trying to deploy to target machines).
Remember that " DellDrivers" signifies your hardware. This name is just an example and you will
need to adjust it to suit your requirements.
b. Copy the driver files into the newly created directory.
c. On the server (or your personal workstation), load regedit.
d. Load the Software registry hive of the image by selecting HKEY_LOCAL_MACHINE and
clicking "File" then "Load Hive". Navigate to
\\SERVER\REMINST\Setup\Lan
and pick the Software file.
e. Type RIS Image as the temporary name of the hive.
f. In the registry tree, navigate to
g. HKEY_LOCAL_MACHINE\RIS Image\Microsoft\Windows\Cu
pane double click the DevicePath value.
h. Add ;%SystemDrive%\Drivers\Del
i. Unload the hive by navigating to HKEY_LOCAL_MACHINE\RIS Image and selecting Unload
Hive on the File menu. Don't forget this step because otherwise the hive will not be saved
until you reboot your personal workstation.
j. Install the RIS image on a test machine as your network card drivers will be installed.
end.
That's really a lot of work to get drivers in.
It's much simpler than that.
Your patches are a little different as they replace existing files and should add a few registry keys.
You may have some luck checking out methods for integrating patches using www.msfn.org and looking at the unattended XP section.
Since a RIPREP image is pretty much the same as a ghost image making changes to it are not always possible. Honestly, you're probably best to update your reference machine and re-RIPREP it. I don't see any time savings trying to figure out how to slipstream them with unpredictable results.
It's much simpler than that.
Your patches are a little different as they replace existing files and should add a few registry keys.
You may have some luck checking out methods for integrating patches using www.msfn.org and looking at the unattended XP section.
Since a RIPREP image is pretty much the same as a ghost image making changes to it are not always possible. Honestly, you're probably best to update your reference machine and re-RIPREP it. I don't see any time savings trying to figure out how to slipstream them with unpredictable results.
ASKER
Yeah not the perfect solution but it will do... Ill keep the master system myself update it monthly when Microsoft releases its patch blitz and re Riprep it to the server.
Also the good part about that is once Longhorn and XImage is out Ill have my master system to create an XImage and not have to deal with legacy.
Also the good part about that is once Longhorn and XImage is out Ill have my master system to create an XImage and not have to deal with legacy.
Yes, as time progresses the ability to keep things current will get easier.
One of the downfalss of RIS was this inability. Hopefully, WDS with WIM and XImage will help there somewhat.
One of the downfalss of RIS was this inability. Hopefully, WDS with WIM and XImage will help there somewhat.
ASKER
Ok what do I do to give you the points?
What is the normal point scale for questions like this?
Would I get and answer for no points, I saw an option for this? I'm hoping this option would be good for asking questions that are low priority where I don't need an answer for a week.
Sorry Im new to this and want to give credit where credit is do but I also don't want to give to few or to many point for questions if you know what I mean.
What is the normal point scale for questions like this?
Would I get and answer for no points, I saw an option for this? I'm hoping this option would be good for asking questions that are low priority where I don't need an answer for a week.
Sorry Im new to this and want to give credit where credit is do but I also don't want to give to few or to many point for questions if you know what I mean.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You update the master reference machine, then RIPREP it again.
You can only update the flat file source for new, unattended installs - not a riprep'd image.