<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Active Directory Blog</title>
	<atom:link href="https://activedir.blogtown.co.nz/feed/" rel="self" type="application/rss+xml" />
	<link>https://activedir.blogtown.co.nz</link>
	<description>Stuart&#039;s Active Directory Blog</description>
	<lastBuildDate>Sun, 15 Jan 2006 08:48:55 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.6.1</generator>
	<item>
		<title>New links page</title>
		<link>https://activedir.blogtown.co.nz/2006/01/14/new-links-page/</link>
					<comments>https://activedir.blogtown.co.nz/2006/01/14/new-links-page/#comments</comments>
		
		<dc:creator><![CDATA[activedir]]></dc:creator>
		<pubDate>Sat, 14 Jan 2006 00:58:17 +0000</pubDate>
				<category><![CDATA[General]]></category>
		<guid isPermaLink="false">http://activedir.blogtown.co.nz/2006/01/14/new-links-page/</guid>

					<description><![CDATA[I&#8217;ve now added a page which lists all of the links that I&#8217;ll be collecting relating to Active Directory. You can find the page here: http://activedir.blogtown.co.nz/links/]]></description>
										<content:encoded><![CDATA[<p>I&#8217;ve now added a page which lists all of the links that I&#8217;ll be collecting relating to Active Directory.</p>
<p>You can find the page here: <a href="http://activedir.blogtown.co.nz/links/">http://activedir.blogtown.co.nz/links/</a></p>

<p><a href="https://activedir.blogtown.co.nz/2006/01/14/new-links-page/">Source</a></p>]]></content:encoded>
					
					<wfw:commentRss>https://activedir.blogtown.co.nz/2006/01/14/new-links-page/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>Remotely reboot a server into DSRM</title>
		<link>https://activedir.blogtown.co.nz/2006/01/12/remotely-reboot-a-server-into-dsrm/</link>
					<comments>https://activedir.blogtown.co.nz/2006/01/12/remotely-reboot-a-server-into-dsrm/#comments</comments>
		
		<dc:creator><![CDATA[activedir]]></dc:creator>
		<pubDate>Wed, 11 Jan 2006 03:32:39 +0000</pubDate>
				<category><![CDATA[HOWTO]]></category>
		<guid isPermaLink="false">http://activedir.blogtown.co.nz/2006/01/12/remotely-reboot-a-server-into-dsrm/</guid>

					<description><![CDATA[I thought I&#8217;d start off the blog with something that I learned recently that I will probably never use. However, it&#8217;s quite useful to know anyway and it highlights a couple of cool features that you may not have known about. The scenario is that you have a remote domain controller that you need to [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>   I thought I&#8217;d start off the blog with something that I learned recently that I   will probably never use. However, it&#8217;s quite useful to know anyway and it   highlights a couple of cool features that you may not have known about. </p>
<p>   The scenario is that you have a remote domain controller that you need to take   offline and reboot into Directory Services Restore Mode. There are a couple of   ways to do this but I am going to look at the most interesting&#8230; </p>
<p><span id="more-5"></span> </p>
<p>   The first thing we need to do is access the remote server&#8217;s boot.ini file and   add a new entry to boot into DSRM. The first way to do this would be to   connect to the server through remote desktop or terminal services and edit the   file in notepad, but that&#8217;s far too easy so we won&#8217;t worry about that. What   we&#8217;ll use is a tool called bootcfg which is included in Windows XP or 2003.   This little utility allows you to query and edit the boot.ini file on either   the local machine or a remote machine. The syntax is: </p>
<blockquote><p>C:\&gt;bootcfg /?</p>
<p> BOOTCFG /parameter [arguments]</p>
<p> Description:<br />     This command line tool can be used to configure, query, change or<br />     delete the boot entry settings in the BOOT.INI file.</p>
<p> Parameter List:<br />     /Copy       Makes a copy of an existing boot entry [operating<br />                 systems] section for which you can add OS options to.</p>
<p>     /Delete     Deletes an existing boot entry in the [operating<br />                 systems] section of the BOOT.INI file. You must specify<br />                 the entry# to delete.</p>
<p>     /Query      Displays the current boot entries and their settings.</p>
<p>     /Raw        Allows the user to specify any switch options to be<br />                 added for a specified boot entry.</p>
<p>     /Timeout    Allows the user to change the Timeout value.</p>
<p>     /Default    Allows the user to change the Default boot entry.</p>
<p>     /EMS        Allows the user to configure the /redirect switch<br />                 for headless support for a boot entry.</p>
<p>     /Debug      Allows the user to specify the port and baudrate for<br />                 remote debugging for a specified boot entry.</p>
<p>     /Addsw      Allows the user to add predefined switches for<br />                 a specific boot entry.</p>
<p>     /Rmsw       Allows the user to remove predefined switches for a<br />                 specific boot entry.</p>
<p>     /Dbg1394    Allows the user to configure 1394 port debugging<br />                 for a specified boot entry.</p>
<p>     /?          Displays this help/usage.</p>
<p> Examples:<br />     BOOTCFG /Copy /?<br />     BOOTCFG /Delete /?<br />     BOOTCFG /Query /?<br />     BOOTCFG /Raw /?<br />     BOOTCFG /Timeout /?<br />     BOOTCFG /EMS /?<br />     BOOTCFG /Debug /?<br />     BOOTCFG /Addsw /?<br />     BOOTCFG /Rmsw /?<br />     BOOTCFG /Dbg1394 /?<br />     BOOTCFG /Default /?<br />     BOOTCFG /? </p></blockquote>
<p>   The first option we&#8217;ll use is the query: </p>
<blockquote><p>C:\&gt;bootcfg /s dc-server /query</p>
<p> Boot Loader Settings<br /> &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;<br /> timeout:30<br /> default:multi(0)disk(0)rdisk(0)partition(1)\WINDOWS</p>
<p> Boot Entries<br /> &#8212;&#8212;&#8212;&#8212;<br /> Boot entry ID:    1<br /> OS Friendly Name: Windows Server 2003, Standard<br /> Path:             multi(0)disk(0)rdisk(0)partition(1)\WINDOWS<br /> OS Load Options:  /fastdetect /NoExecute=OptOut </p></blockquote>
<p>   The results above are typical of a new Windows Server 2003 build with no   special options. </p>
<p>   The next thing we need to do is create a copy of the fist entry so that we can   add the correct options to it. We do this by using the copy switch and   reference id 1 which is the fist entry as follows: </p>
<blockquote>
<p>   C:\&gt;bootcfg /s dc-server /copy   /id 1 /d &#8220;Directory Services Restore   Mode&#8221;<br />   SUCCESS: Made a copy of the boot entry   &#8220;1&#8221;. </p>
</blockquote>
<p>   Now when we run the query again, we can see that there are now two boot   entries in the boot.ini file: </p>
<blockquote>
<p>   C:\&gt;bootcfg /s dc-server   /query</p>
<p>   Boot Loader   Settings<br />   &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;<br />   timeout:30<br />   default:multi(0)disk(0)rdisk(0)partition(1)\WINDOWS</p>
<p>   Boot   Entries<br />   &#8212;&#8212;&#8212;&#8212;<br />   Boot entry ID:      1<br />   OS Friendly Name: Windows Server 2003,   Standard<br />   Path:               multi(0)disk(0)rdisk(0)partition(1)\WINDOWS<br />   OS Load Options:  /fastdetect   /NoExecute=OptOut</p>
<p>   Boot entry ID:      2<br />   OS Friendly Name: Directory Services   Restore Mode<br />   Path:               multi(0)disk(0)rdisk(0)partition(1)\WINDOWS<br />   OS Load Options:  /fastdetect   /NoExecute=OptOut </p>
</blockquote>
<p>   The boot.ini file now looks like this: </p>
<blockquote><p>[boot loader]<br /> timeout=30<br /> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS<br /> [operating systems]<br /> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=&#8221;Windows Server 2003, Standard&#8221; /fastdetect /NoExecute=OptOut<br /> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=&#8221;Directory Services Restore Mode&#8221; /fastdetect /NoExecute=OptOut </p></blockquote>
<p>   Now that we have the second boot entry we can add the option to boot into DSRM   by using the &#8220;/SAFEBOOT:DSREPAIR&#8221; option by using the raw switch: </p>
<blockquote><p>C:\&gt;bootcfg /s dc-server /raw &#8220;/SAFEBOOT:DSREPAIR&#8221; /a /id 2<br /> SUCCESS: Added the switch to OS entry for line &#8220;2&#8221; in the BOOT.INI file. </p></blockquote>
<p>The query now shows this:</p>
<blockquote><p>C:\&gt;bootcfg /s dc-server /query</p>
<p> Boot Loader Settings<br /> &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;<br /> timeout:30<br /> default:multi(0)disk(0)rdisk(0)partition(1)\WINDOWS</p>
<p> Boot Entries<br /> &#8212;&#8212;&#8212;&#8212;<br /> Boot entry ID:    1<br /> OS Friendly Name: Windows Server 2003, Standard<br /> Path:             multi(0)disk(0)rdisk(0)partition(1)\WINDOWS<br /> OS Load Options:  /fastdetect /NoExecute=OptOut</p>
<p> Boot entry ID:    2<br /> OS Friendly Name: Directory Services Restore Mode<br /> Path:             multi(0)disk(0)rdisk(0)partition(1)\WINDOWS<br /> OS Load Options:  /fastdetect /NoExecute=OptOut /safeboot:dsrepair </p></blockquote>
<p>   The only thing left to do now is to adjust the timeout period, otherwise   you&#8217;ll end up with a 30 second delay each time the server reboots. You can set   this to what you want, but I&#8217;ll set it to 5 seconds here: </p>
<blockquote><p>C:\&gt;bootcfg /s dc-server /timeout 5<br /> SUCCESS: Changed the timeout value in the BOOT.INI. </p></blockquote>
<p>   Now we have the boot.ini file completely prepared for the next step. Here&#8217;s   what the query looks like: </p>
<blockquote>
<p>   C:\&gt;bootcfg /s dc-server   /query</p>
<p>   Boot Loader   Settings<br />   &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;<br />   timeout:5<br />   default:multi(0)disk(0)rdisk(0)partition(1)\WINDOWS</p>
<p>   Boot   Entries<br />   &#8212;&#8212;&#8212;&#8212;<br />   Boot entry ID:      1<br />   OS Friendly Name: Windows Server 2003,   Standard<br />   Path:               multi(0)disk(0)rdisk(0)partition(1)\WINDOWS<br />   OS Load Options:  /fastdetect   /NoExecute=OptOut</p>
<p>   Boot entry ID:      2<br />   OS Friendly Name: Directory Services   Restore Mode<br />   Path:               multi(0)disk(0)rdisk(0)partition(1)\WINDOWS<br />   OS Load Options:  /fastdetect   /NoExecute=OptOut </p>
</blockquote>
<p>   And the boot.ini file looks like this: </p>
<blockquote><p>[boot loader]<br /> timeout=5<br /> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS<br /> [operating systems]<br /> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=&#8221;Windows Server 2003, Standard&#8221; /fastdetect /NoExecute=OptOut<br /> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=&#8221;Directory Services Restore Mode&#8221; /fastdetect /NoExecute=OptOut </p></blockquote>
<p>So back to our scenario&#8230; the remote server needs to be rebooted into DSRM. Although we know that the boot.ini file has been edited correctly, we&#8217;ll still run the query (bootcfg /s main-vm-server /query) and we&#8217;ll make a note that the option we want is boot entry id 2. What we want to do is change the order of the boot sequence so that ID 2 is now ID 1 and the server will boot into DSRM. This is done like this:</p>
</p>
<blockquote><p>C:\&gt;bootcfg /s dc-server /default /id 2<br /> SUCCESS: Changed the default OS entry in the BOOT.INI. </p></blockquote>
<p>And the query shows that the two boot entrues have swapped positions:</p>
</p>
<blockquote><p>C:\&gt;bootcfg /s dc-server /query</p>
<p> Boot Loader Settings<br /> &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;<br /> timeout:5<br /> default:multi(0)disk(0)rdisk(0)partition(1)\WINDOWS</p>
<p> Boot Entries<br /> &#8212;&#8212;&#8212;&#8212;<br /> Boot entry ID:    1<br /> OS Friendly Name: Directory Services Restore Mode<br /> Path:             multi(0)disk(0)rdisk(0)partition(1)\WINDOWS<br /> OS Load Options:  /fastdetect /NoExecute=OptOut</p>
<p> Boot entry ID:    2<br /> OS Friendly Name: Windows Server 2003, Standard<br /> Path:             multi(0)disk(0)rdisk(0)partition(1)\WINDOWS<br /> OS Load Options:  /fastdetect /NoExecute=OptOut </p></blockquote>
<p>Now all we have to is reboot the server using the shutdown.exe command:</p>
</p>
<blockquote><p>shutdown /m \\dc-server /r /t 10 /f </p></blockquote>
<p>Note that I&#8217;m using the /r to reboot the server, the /t to give myself 10 seconds to change my mind (if I do change my mind about rebooting the server I can use the /a switch to abort the reboot), and the /f to force any applications to close that aren&#8217;t behaving properly. When the server reboots, it will wait 5 seconds and then continue booting into DSRM. You can now connect to the server through remote desktop and continue restoring Active Directory as needed (more about that in a later article&#8230;)</p>
</p>
<p>Obviously, you need to remember to change the boot order back to how it was when you&#8217;re done otherwise you&#8217;ll be scratching your head wondering why the server isn&#8217;t booting properly! On the local machine you can use bootcfg without the /s switch and it will work locally by default. You just need to use the /query option to check the boot order, then the /default option to swap the order.</p>
</p>
<p>Hope this helps and (as always) comments &#8211; good/bad/ugly &#8211; are welcomed!</p>
<p>[Tags]Active Directory,Microsoft,bootcfg[/tags]</p>

<p><a href="https://activedir.blogtown.co.nz/2006/01/12/remotely-reboot-a-server-into-dsrm/">Source</a></p>]]></content:encoded>
					
					<wfw:commentRss>https://activedir.blogtown.co.nz/2006/01/12/remotely-reboot-a-server-into-dsrm/feed/</wfw:commentRss>
			<slash:comments>64</slash:comments>
		
		
			</item>
		<item>
		<title>My new Active Directory blog</title>
		<link>https://activedir.blogtown.co.nz/2006/01/10/my-new-active-directory-blog/</link>
					<comments>https://activedir.blogtown.co.nz/2006/01/10/my-new-active-directory-blog/#comments</comments>
		
		<dc:creator><![CDATA[activedir]]></dc:creator>
		<pubDate>Tue, 10 Jan 2006 06:55:20 +0000</pubDate>
				<category><![CDATA[General]]></category>
		<guid isPermaLink="false">http://activedir.blogtown.co.nz/2006/01/10/my-new-active-directory-blog/</guid>

					<description><![CDATA[I&#8217;ve decided to start up a new [tag]blog[/tag] where I&#8217;ll write posts relating to [tag]Microsoft[/tag]&#8217;s [tag]Active Directory[/tag]. This will probably include some tips and tricks, problems that I&#8217;ve run into in the past, solutions to common problems, perhaps some scripts that I&#8217;ve written to help manage to Active Directory, and any interesting links that I [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>I&#8217;ve decided to start up a new [tag]blog[/tag] where I&#8217;ll write posts relating to [tag]Microsoft[/tag]&#8217;s [tag]Active Directory[/tag]. This will probably include some tips and tricks, problems that I&#8217;ve run into in the past, solutions to common problems, perhaps some scripts that I&#8217;ve written to help manage to Active Directory, and any interesting links that I feel are important to keep handy.</p>
<p>Hope you enjoy this blog &#8211; I&#8217;ll keep the comments open so feel free to post your thoughts and ideas and I&#8217;ll always aim to respond as soon as I can.</p>

<p><a href="https://activedir.blogtown.co.nz/2006/01/10/my-new-active-directory-blog/">Source</a></p>]]></content:encoded>
					
					<wfw:commentRss>https://activedir.blogtown.co.nz/2006/01/10/my-new-active-directory-blog/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
	</channel>
</rss>
