Once you have all of the materials you need for the slipstream original installation media, Service Pack 1 installation files and an installation of RT Server Customizer , you can launch the RT Server Customizer application to begin the process.
Though the instructions are quite similar, there are a few key differences. Each is performed separately. Bear in mind that though Microsoft released Standard, Enterprise, Datacenter and Web editions on a single ISO, this process will remove all but one edition. If you wish to slipstream multiple editions, you will have to perform these steps multiple times and create separate ISOs for each.
Fortunately, most of the same updates apply to all editions. NOTE: You will need to manually remove the source files you extracted in step 3 before continuing with the remaining updates.
This is to allow the expansion of the new media containing the Service Pack 1 files. To successfully build updated media, it is important to first define which patches are needed.
Use VirtualBox or another desktop virtualization product to build a base installation from the Windows media which contains Service Pack 1. Run through Windows updates until it can find no more updates. Once this is done, you can view the update history within that virtual machine to get a list of all of the patches that were installed.
In a pinch, you can do this on VMware or Microsoft Hyper-V remembering that this is a standalone test environment and should not yet be added to your domain. Microsoft has simplified the process of downloading patches for administrative installs by creating the Windows Update Catalog. Download them to a new folder on your local machine where they are easy to locate.
The download process will create a separate folder for each update under this directory location. You should now test your newly created image in your desktop virtualization application. Once you have the new image installed, you can go to Windows Update and verify that there are no further updates to perform. In rare cases, there will be only a handful of patches that need to be applied post install.
If you so desire, you can make a note of these patches, download them Microsoft and perform the slipstreaming task again to embed those into the image file. When you are ready to test your image for deployment, create a new virtual machine and use the new ISO as the default boot device. The system will appear to install as normal with one notable exception. After the initial install, there will be a period where the guest appears to be doing nothing.
This is due to the fact that the applications being installed Internet Explorer 9, Silverlight and DotNET Framework patches are all installing silently in the background.
Do not assume that the desktop did not load and reset the guest. Slipstreaming is not a difficult process but is time-consuming. The best answers are voted up and rise to the top.
Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 10 years, 6 months ago. Active 10 years, 6 months ago. Viewed 4k times. Improve this question. Add a comment. Active Oldest Votes. Notify me of new comments via email.
Notify me of new posts via email. Welcome To My Blog. Deployment Image Servicing and Management tool Version: 6. Share this: Twitter Facebook. Like this: Like Loading Comments 0 Leave a comment. Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in:. You'll need to install the software on Windows 7 or I've only tested on these 2. Next make sure you've got your installation media to hand, and launch a command prompt, be sure to run as Administrator otherwise later steps will fail 3.
The first step of slipstreaming is to mount the WIM file we wish to update, to do this run the following command : dism. Now we use dism. If you find this useful and would like to see a sample script let me know and I'll happily post one!
0コメント