See how to enable scripts. Select Language:. English Japanese. A security issue has been identified in a Microsoft software product that could affect your system. Details Version:. File Name:. Date Published:. File Size:. System Requirements Supported Operating System. Install Instructions To start the download, click the Download button and then do one of the following, or select another language from Change Language and then click Change.
Needless to say that this saves me a lot of time in deployment and it provides a great deal of standardization. NOTE : These instructions were written for people in IT that need to duplicate computers within their organization, or possibly for home users to transfer their Windows installation to a different computer. SysPrep can also be used to distribute installations of Windows to customers of computer businesses. The difference is between " Factory " mode and " Reseal " mode and this guide focuses on how to reseal the computers, but they would also apply to factory installations.
If you have any questions, comments or suggestions then please let me know. Any feedback I receive from users will allow me to improve this guide, so you'll be helping others as well as yourself. Use the Contact page to send me a message.
There are a few terms that SysPrep uses and that I use and if you do not know them then they may confuse you. Users of Windows NT4 needed a way to properly duplicate installations of Windows and programs onto other computers. This was a task that would save time and reduce monotony for IT staff that needed to do such things as set up 30 identical computers in a computer lab. Programs existed at the time such as Binary Research's Ghost, which was later sold to Norton in July of , that could duplicate the exact software structure of one computer onto another.
But, in the case of Windows NT4 this created extreme driver problems that would either crash the replicate computer or impair specific devices, such as the network card. This was in contrast to Windows 95 or Windows 98 that when duplicated reacted in a much more manageable way, and basically this means they would go through a hardware redetection process.
Even worse, a Windows NT4 computer has a built-in security identifer SID that is generated only on the installation of the operating system.
This SID is used by domain controllers to internally identify workstations and servers, and if this code was duplicated then it would confuse domain servers since multiple computers would in effect have the same name.
Luckily Microsoft, for once, actually listened to the needs of its customers. And their response was the release of a free resource utility called the Microsoft System Preparation Tool versioned as 4. When you were ready to duplicate a computer you would run this program and it would follow rules defined in a script file answer file that you created.
And after duplication it would execute those rules while running through a short mini-setup that recreated the security identifer SID and forced a hardware remapping sequence. It still would not allow duplication across variable hardware, but it would make exact computer duplications a much easier task.
There are several versions of SysPrep and their options vary from Windows platform to Windows platform. Be sure that you use the latest version of SysPrep available to you or you will limiting what you can do a lot. You can check the version of your SysPrep executable by right clicking it and selecting properties. Then under the properties dialog view the Version tab. The website for the patch can be found here.
The original version fixed the problem of replicating software images onto exact, or near exact, hardware configurations. This version had several short comings. The most prominent was that it could not deploy using 3rd party mass storage controllers. So, if you had hard-drive controllers not natively supported by Windows then you would need to make different images for each. However, unlike the NT4 version this version would strip out hardware configurations and redetect hardware devices the first boot following the execution of SysPrep.
This version changed a few things but the most important was that it gave SysPrep the ability to use additional mass storage drivers, which was an awesome addition. This version was just as complete the Sysprep Update 1. You can download it from here. The differences between the SP2 SysPrep and the original SysPrep were that it supported scripted configuration of SP2 features, such as the firewall and Internet Explorer's pop-up blocker, and that it screwed up the profiles.
I should clarify the latter though, but it may be a bit technical for the time being so ignore it for now if you don't understand it. For as long as SysPrep has existed the concept was that you designed the "Default User" profile and then imaged the computer. So, the user accounts that were created after this point would use the settings from the "Default User" profile.
0コメント