{"id":337,"date":"2011-04-19T17:40:22","date_gmt":"2011-04-20T01:40:22","guid":{"rendered":"http:\/\/systemsolver.com\/StatlerBlog\/?p=337"},"modified":"2011-04-19T17:40:22","modified_gmt":"2011-04-20T01:40:22","slug":"win7-sysprep-nightmare","status":"publish","type":"post","link":"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/2011\/04\/19\/win7-sysprep-nightmare\/","title":{"rendered":"Win7 Sysprep nightmare!"},"content":{"rendered":"<p>Well, it was a nightmare trying to figure out how to use Win7 Sysprep. The documentation is poor and the interface for creating the automated answer file (in xml) is horrible. I would have prefered the old text document version of an answer file and can&#8217;t for the life of me understand why they used xml.\u00a0 But they did, and the bull-dog in me wouldn&#8217;t let go of the fight to figure it out, even though it was not possible to charge my client for the effort beyond the first few hours. So I&#8217;m putting what I figured out here. I hope to keep this as simple as possible, but it&#8217;s such a mess that simple is going to be unobtainable I fear.<\/p>\n<p>The main value of using sysprep on a machine is that it can produce an install file with answers to basic questions and it can do more than just the basic install\u00a0 of Windows. A syspreped machine will allow not only additional software to be installed but also drivers and settings.<\/p>\n<p>For instance, we might want to have various utilities (defrag, maybe ccleaner, etc) and Office 2010 installed at the same time. A sysprep setup can install automatically with the right answer file<\/p>\n<p><strong>This is a work in process, so if you&#8217;re viewing this statement know that it&#8217;s not done. I published it anyway just so I&#8217;d have easier access to it.<\/strong> I hope to have links and even a sample to copy, but it will take a few days to finish this article.<\/p>\n<p>There are 11 steps to the creation of a custom unattended Windows7 install in it&#8217;s most basic form.<\/p>\n<ol>\n<li>Copy the Win7 CD files to a networked drive custom folder.<\/li>\n<li>Create or modify an answer file (unattend.xml or a variation of that name).<\/li>\n<li>Copy the answer file to root of the networked drive custom Win7 CD files folder (same location as setup.exe).<\/li>\n<li>Create a Win7PE boot disk ???with imagex added???.<\/li>\n<li>Create a base-install machine (load the programs and files you want replicated in future installs, do not join a domain).<\/li>\n<li>Make an image of your base install machine for safety reasons (probably to the same networked drive but in a different folder from the Win7 CD files) &#8212; make sure you have a boot disk for the image program.<\/li>\n<li>Sysprep the base-install machine (not using audit mode, but saving drivers).<\/li>\n<li>??? Boot from a WinPE disk and ??? run imagex to create an image of the sysprep&#8217;ed base-install machine (imagex will create a install.wim file).<\/li>\n<li>Copy the sysprep-created install.wim file from the base-install machine to the \/sources sub-folder of your  custom Win7 files on the network (you&#8217;ll be replacing the \/sources\/install.wim file).<\/li>\n<li>Test the install by mapping to the networked drive, changing to the Win7 folder created in step 1 and running, on the base-install machine, &lt;setup.exe \/unattend:unattend.xml&gt; without the &lt;&gt; and all one line.<\/li>\n<li>Log in, reboot with ???oob??? and give the computer a name.<\/li>\n<\/ol>\n<p>Thereafter, booting with Win7PE CD and running steps 10 and 11 is all that&#8217;s necessary to do a clean install on any other machine. If it all fails, there&#8217;s always that image you created in step 6 &#8212; you did create the image didn&#8217;t you? If it didn&#8217;t work then there was a failure in either the answer file or the sysprep stage.<\/p>\n<p style=\"page-break-before: always\">\nNow for the details:<\/p>\n<p>Gather:<br \/>\nInstall disk for Windows version to be installed (need install.wim from \\source folder)<br \/>\nSample &#8230;install.xml file for the Windows version?<br \/>\nWindows Automated Installation Kit (WAIK) DVD<br \/>\nWindows PE boot disk<br \/>\nTechnician computer (for WAIK)<br \/>\nModel computer (to install programs)<\/p>\n<p>Create Technician&#8217;s computer by installing WAIK<br \/>\nCopy &#8220;install.wim&#8221; to root folder on Technician&#8217;s computer<br \/>\nOpen WAIK Management window<br \/>\nRight click in &#8230; window and direct to the install.wim file<br \/>\nAccept the creation of a catalogue of the install.wim file<br \/>\nWait 10 minutes for completion<br \/>\nOpen Walk-through file<br \/>\nFollow directions to create a new install.xml file<br \/>\nNote: there are two places for license keys. The first place<br \/>\nis for normal keys, the second place is for MAK keys. Don&#8217;t put<br \/>\nany in the first if you will be using a MAK key.<br \/>\n&#8230;..more about MAK key&#8230;.<\/p>\n<p>Alternatively, if you are just making a slightly different xml file, just copy the existing model and make changes directly with notepad. For instance, you might want to just change the product key or add\/change default user\/password.<\/p>\n<p><strong>Install on new machine:<\/strong><\/p>\n<p>Boot new computer with Win7PE<br \/>\nMap network drive where Win7 CD files folder exists<br \/>\nClear and format the hard drive if you want\n<\/p>\n<p style=\"padding-left: 30px;\">diskpart<br \/>\nselect disk 0<br \/>\nclean<br \/>\ncreate partition primary<br \/>\nselect partition 1<br \/>\nformat fs=ntfs label=&#8221;system&#8221;<br \/>\nassign letter=C<br \/>\nactive<br \/>\nexit<\/p>\n<p>Change drive to mapped network location of Win7 CD files folder<br \/>\nChange directory to Win7 CD files folder<br \/>\nRun &lt;setup.exe \/unattend:unattend.xml&gt; or use whatever unattend file you created.<br \/>\nReboot<br \/>\nLogin<br \/>\nWindow appears &#8212; select OK to reboot to Out-of-box experience<br \/>\nAnswer a few questions, give computer a name<br \/>\nIf you are joining a Win2008 domain then open IE and type into address bar &lt;connect&gt; without the &lt;&gt; and follow those directions.<\/p>\n<p>End<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Well, it was a nightmare trying to figure out how to use Win7 Sysprep. The documentation is poor and the interface for creating the automated answer file (in xml) is horrible. I would have prefered the old text document version of an answer file and can&#8217;t for the life of me understand why they used [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-337","post","type-post","status-publish","format-standard","hentry","category-general"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-json\/wp\/v2\/posts\/337","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-json\/wp\/v2\/comments?post=337"}],"version-history":[{"count":0,"href":"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-json\/wp\/v2\/posts\/337\/revisions"}],"wp:attachment":[{"href":"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-json\/wp\/v2\/media?parent=337"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-json\/wp\/v2\/categories?post=337"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-json\/wp\/v2\/tags?post=337"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}