<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How to Sysprep Windows Server 2008</title>
	<atom:link href="http://jameskovacs.com/2008/10/15/how-to-sysprep-windows-server-2008/feed/" rel="self" type="application/rss+xml" />
	<link>http://jameskovacs.com/2008/10/15/how-to-sysprep-windows-server-2008/</link>
	<description></description>
	<lastBuildDate>Wed, 01 Feb 2012 20:51:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: Nathan Boyd</title>
		<link>http://jameskovacs.com/2008/10/15/how-to-sysprep-windows-server-2008/comment-page-1/#comment-30007</link>
		<dc:creator>Nathan Boyd</dc:creator>
		<pubDate>Mon, 19 Dec 2011 14:41:53 +0000</pubDate>
		<guid isPermaLink="false">http://jameskovacs.com/2008/10/15/How+To+Sysprep+Windows+Server+2008#comment-30007</guid>
		<description>Thanks James, for the nice concise explanation!

@Hayden:  That&#039;s by design.  Sysprep returns the installation to the &quot;first reboot after installation&quot; but with the whatever updates installed.  Typically any customizations and/or settings will be wiped during sysprep.  If you want customization after Sysprep, then look for the link to Brian Madden&#039;s blog above.</description>
		<content:encoded><![CDATA[<p>Thanks James, for the nice concise explanation!</p>
<p>@Hayden:  That&#8217;s by design.  Sysprep returns the installation to the &#8220;first reboot after installation&#8221; but with the whatever updates installed.  Typically any customizations and/or settings will be wiped during sysprep.  If you want customization after Sysprep, then look for the link to Brian Madden&#8217;s blog above.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Nilson</title>
		<link>http://jameskovacs.com/2008/10/15/how-to-sysprep-windows-server-2008/comment-page-1/#comment-26397</link>
		<dc:creator>David Nilson</dc:creator>
		<pubDate>Wed, 16 Nov 2011 23:23:32 +0000</pubDate>
		<guid isPermaLink="false">http://jameskovacs.com/2008/10/15/How+To+Sysprep+Windows+Server+2008#comment-26397</guid>
		<description>@Hayden Hancock
That is the EXPECTED behaviour of Sysprep .  Read &quot;What is Sysprep&quot; at:
http://technet.microsoft.com/en-us/library/cc783215(WS.10).aspx</description>
		<content:encoded><![CDATA[<p>@Hayden Hancock<br />
That is the EXPECTED behaviour of Sysprep .  Read &#8220;What is Sysprep&#8221; at:<br />
<a href="http://technet.microsoft.com/en-us/library/cc783215(WS.10).aspx" rel="nofollow">http://technet.microsoft.com/en-us/library/cc783215(WS.10).aspx</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Nilson</title>
		<link>http://jameskovacs.com/2008/10/15/how-to-sysprep-windows-server-2008/comment-page-1/#comment-26396</link>
		<dc:creator>David Nilson</dc:creator>
		<pubDate>Wed, 16 Nov 2011 23:20:33 +0000</pubDate>
		<guid isPermaLink="false">http://jameskovacs.com/2008/10/15/How+To+Sysprep+Windows+Server+2008#comment-26396</guid>
		<description>@NoCertsJustLife
You are correct that duplite WSUS SIds will cause one and only one of the machines with duplicates to show up in WSUS at one time.
But thats a different SID and is easily solved by deleting the WSUS SID fro mthe registry, it will auto-create on next boot.
Try this in a .CMD file on an effected machine or in logon scripts:

net stop wuauserv


REM -- Clear out history and downloaded updates - start Fresh
cd %windir%\SoftwareDistribution
del DataStore /q
rmdir Download /S /Q


REM - Normal
:SUS_normal
Reg DELETE &quot;HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update&quot; /v LastWaitTimeout /f
Reg DELETE &quot;HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update&quot; /v DetectionStartTime /f
Reg Delete &quot;HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update&quot; /v NextDetectionTime /f


REM - d.a.n.   To regenerate SUSclientID
reg delete &quot;HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate&quot; /v SusClientId /f

net start wuauserv

:SUS_end
wuauclt /resetauthorization /detectnow /reportnow

:SUS_End2</description>
		<content:encoded><![CDATA[<p>@NoCertsJustLife<br />
You are correct that duplite WSUS SIds will cause one and only one of the machines with duplicates to show up in WSUS at one time.<br />
But thats a different SID and is easily solved by deleting the WSUS SID fro mthe registry, it will auto-create on next boot.<br />
Try this in a .CMD file on an effected machine or in logon scripts:</p>
<p>net stop wuauserv</p>
<p>REM &#8212; Clear out history and downloaded updates &#8211; start Fresh<br />
cd %windir%\SoftwareDistribution<br />
del DataStore /q<br />
rmdir Download /S /Q</p>
<p>REM &#8211; Normal<br />
:SUS_normal<br />
Reg DELETE &#8220;HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update&#8221; /v LastWaitTimeout /f<br />
Reg DELETE &#8220;HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update&#8221; /v DetectionStartTime /f<br />
Reg Delete &#8220;HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update&#8221; /v NextDetectionTime /f</p>
<p>REM &#8211; d.a.n.   To regenerate SUSclientID<br />
reg delete &#8220;HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate&#8221; /v SusClientId /f</p>
<p>net start wuauserv</p>
<p>:SUS_end<br />
wuauclt /resetauthorization /detectnow /reportnow</p>
<p>:SUS_End2</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hayden Hancock</title>
		<link>http://jameskovacs.com/2008/10/15/how-to-sysprep-windows-server-2008/comment-page-1/#comment-24055</link>
		<dc:creator>Hayden Hancock</dc:creator>
		<pubDate>Mon, 24 Oct 2011 19:19:17 +0000</pubDate>
		<guid isPermaLink="false">http://jameskovacs.com/2008/10/15/How+To+Sysprep+Windows+Server+2008#comment-24055</guid>
		<description>I&#039;ve tried performing this method in a virtual environment (VirtualBox). Everything seems to work fine except that my VHD changes what I had in my domain. For instance, I used company.com as my domain but after sysprep, it put that into the WORKGOUP field.

Any suggestions on what I am doing wrong? Thanks!</description>
		<content:encoded><![CDATA[<p>I&#8217;ve tried performing this method in a virtual environment (VirtualBox). Everything seems to work fine except that my VHD changes what I had in my domain. For instance, I used company.com as my domain but after sysprep, it put that into the WORKGOUP field.</p>
<p>Any suggestions on what I am doing wrong? Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NoCertsJustLife</title>
		<link>http://jameskovacs.com/2008/10/15/how-to-sysprep-windows-server-2008/comment-page-1/#comment-21324</link>
		<dc:creator>NoCertsJustLife</dc:creator>
		<pubDate>Wed, 05 Oct 2011 12:10:27 +0000</pubDate>
		<guid isPermaLink="false">http://jameskovacs.com/2008/10/15/How+To+Sysprep+Windows+Server+2008#comment-21324</guid>
		<description>A note to the cloners - Failure to change the SID, although not required, will make a WSUS database fail.  Near as I can tell WSUS (Windows Server Update Services) has a SQL database that is key&#039;ed on the machine SID and it ignors domain SID.

If you clone server &quot;A&quot; to make &quot;B&quot;, &quot;C&quot;, etc., you may only find server &quot;A&quot; in your WSUS database.  If you group your servers in WSUS to allow/deny selected updates, you may be selecting all type &quot;A&quot; servers by selecting just &quot;A&quot;.  Always &quot;Generalize&quot; your clone source, or find and use NewSID.

And oh, by the way, if your source computer is already joined to a domain, remove it from the domain (make it a workgroup computer) before SYSPREP.  This is another source of pain.</description>
		<content:encoded><![CDATA[<p>A note to the cloners &#8211; Failure to change the SID, although not required, will make a WSUS database fail.  Near as I can tell WSUS (Windows Server Update Services) has a SQL database that is key&#8217;ed on the machine SID and it ignors domain SID.</p>
<p>If you clone server &#8220;A&#8221; to make &#8220;B&#8221;, &#8220;C&#8221;, etc., you may only find server &#8220;A&#8221; in your WSUS database.  If you group your servers in WSUS to allow/deny selected updates, you may be selecting all type &#8220;A&#8221; servers by selecting just &#8220;A&#8221;.  Always &#8220;Generalize&#8221; your clone source, or find and use NewSID.</p>
<p>And oh, by the way, if your source computer is already joined to a domain, remove it from the domain (make it a workgroup computer) before SYSPREP.  This is another source of pain.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph</title>
		<link>http://jameskovacs.com/2008/10/15/how-to-sysprep-windows-server-2008/comment-page-1/#comment-20123</link>
		<dc:creator>Joseph</dc:creator>
		<pubDate>Sat, 17 Sep 2011 00:04:48 +0000</pubDate>
		<guid isPermaLink="false">http://jameskovacs.com/2008/10/15/How+To+Sysprep+Windows+Server+2008#comment-20123</guid>
		<description>Hi James,

i did a sysprep using the sysprep in windows 2008 R2 sysprep.exe in the system32 folder. I clicked (OOBE) and shutdown option i selected &quot;Quit&quot; and i rebooted my machine manually . It prompted me to change password when i entered my old password it said &quot;Access Denied&quot; . What exactly happened ? i am lost , and i did not clone the syspred image from that machine as i was afriad it would happen to all my machines if i cloned it. Would you advise me ? Thanks.</description>
		<content:encoded><![CDATA[<p>Hi James,</p>
<p>i did a sysprep using the sysprep in windows 2008 R2 sysprep.exe in the system32 folder. I clicked (OOBE) and shutdown option i selected &#8220;Quit&#8221; and i rebooted my machine manually . It prompted me to change password when i entered my old password it said &#8220;Access Denied&#8221; . What exactly happened ? i am lost , and i did not clone the syspred image from that machine as i was afriad it would happen to all my machines if i cloned it. Would you advise me ? Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William Hatten</title>
		<link>http://jameskovacs.com/2008/10/15/how-to-sysprep-windows-server-2008/comment-page-1/#comment-19509</link>
		<dc:creator>William Hatten</dc:creator>
		<pubDate>Wed, 07 Sep 2011 18:39:03 +0000</pubDate>
		<guid isPermaLink="false">http://jameskovacs.com/2008/10/15/How+To+Sysprep+Windows+Server+2008#comment-19509</guid>
		<description>I trying to sysprep a 2008 server and use Imagex to get the image file but it keeps failing as it does not find the image file. Could you please help with that process.</description>
		<content:encoded><![CDATA[<p>I trying to sysprep a 2008 server and use Imagex to get the image file but it keeps failing as it does not find the image file. Could you please help with that process.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://jameskovacs.com/2008/10/15/how-to-sysprep-windows-server-2008/comment-page-1/#comment-13931</link>
		<dc:creator>James</dc:creator>
		<pubDate>Thu, 30 Jun 2011 14:46:42 +0000</pubDate>
		<guid isPermaLink="false">http://jameskovacs.com/2008/10/15/How+To+Sysprep+Windows+Server+2008#comment-13931</guid>
		<description>You set up the initial server, run sysprep to re-seal the OS, and then transfer it to another server. Note that the servers need to have identical hardware (or close to it) otherwise the sysprepped image won&#039;t boot.</description>
		<content:encoded><![CDATA[<p>You set up the initial server, run sysprep to re-seal the OS, and then transfer it to another server. Note that the servers need to have identical hardware (or close to it) otherwise the sysprepped image won&#8217;t boot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://jameskovacs.com/2008/10/15/how-to-sysprep-windows-server-2008/comment-page-1/#comment-10258</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Mon, 11 Apr 2011 20:38:44 +0000</pubDate>
		<guid isPermaLink="false">http://jameskovacs.com/2008/10/15/How+To+Sysprep+Windows+Server+2008#comment-10258</guid>
		<description>I&#039;m a little confused since this is the first time I&#039;m trying to use sysprep.  I hope you can clarify how to use the sysprep tool for cloning an OS.  I want to take an image of a Windows Server 2008 and copy it onto other servers.  I have already created the image of the server.  Do I load the image onto another server and then once loaded and installed, I run sysprep to change SIDs, computer name, activation code, etc.?

Or do I run through sysprep steps first on the host I want to clone, then create an image, then copy the image to a server and the sysprep will guide me through the first time booting up?</description>
		<content:encoded><![CDATA[<p>I&#8217;m a little confused since this is the first time I&#8217;m trying to use sysprep.  I hope you can clarify how to use the sysprep tool for cloning an OS.  I want to take an image of a Windows Server 2008 and copy it onto other servers.  I have already created the image of the server.  Do I load the image onto another server and then once loaded and installed, I run sysprep to change SIDs, computer name, activation code, etc.?</p>
<p>Or do I run through sysprep steps first on the host I want to clone, then create an image, then copy the image to a server and the sysprep will guide me through the first time booting up?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shery</title>
		<link>http://jameskovacs.com/2008/10/15/how-to-sysprep-windows-server-2008/comment-page-1/#comment-9931</link>
		<dc:creator>Shery</dc:creator>
		<pubDate>Thu, 31 Mar 2011 08:11:04 +0000</pubDate>
		<guid isPermaLink="false">http://jameskovacs.com/2008/10/15/How+To+Sysprep+Windows+Server+2008#comment-9931</guid>
		<description>Thanks Jack,
That helped.
-- Shery</description>
		<content:encoded><![CDATA[<p>Thanks Jack,<br />
That helped.<br />
&#8211; Shery</p>
]]></content:encoded>
	</item>
</channel>
</rss>

