<?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: Event ID 2095 and The USN Rollback Adventure</title>
	<atom:link href="http://exchangeserverpro.com/event-id-2095-and-the-usn-rollback-adventure/feed" rel="self" type="application/rss+xml" />
	<link>http://exchangeserverpro.com/event-id-2095-and-the-usn-rollback-adventure</link>
	<description>Microsoft Exchange Server news, tips, tricks and tutorials</description>
	<lastBuildDate>Tue, 09 Mar 2010 11:56:05 +1000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Steven</title>
		<link>http://exchangeserverpro.com/event-id-2095-and-the-usn-rollback-adventure/comment-page-1#comment-1157</link>
		<dc:creator>Steven</dc:creator>
		<pubDate>Fri, 04 Dec 2009 02:00:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.capslockassassin.com/2007/06/02/event-id-2095-and-the-usn-rollback-adventure/#comment-1157</guid>
		<description>How people can have this happen and windows is still considered ready for production use I will never understand.

Thanks for the info, hopefully I can fix this then we can migrate to something less brittle.</description>
		<content:encoded><![CDATA[<p>How people can have this happen and windows is still considered ready for production use I will never understand.</p>
<p>Thanks for the info, hopefully I can fix this then we can migrate to something less brittle.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hary</title>
		<link>http://exchangeserverpro.com/event-id-2095-and-the-usn-rollback-adventure/comment-page-1#comment-720</link>
		<dc:creator>Hary</dc:creator>
		<pubDate>Tue, 20 Jan 2009 16:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.capslockassassin.com/2007/06/02/event-id-2095-and-the-usn-rollback-adventure/#comment-720</guid>
		<description>You saved my Life!!! I was searching for many day to solve this Problem. Thanks for that wonderfull Hint!!!!! Sorry for my english :-) Thanks so much from Vienna/Austria! My situation was as following: 2 virtual DC´s (one w2k3 R2 one w2k8), i demotet the 2k3 and used the &quot;Patch&quot; on the w2k8, after reboot everething was working angain.</description>
		<content:encoded><![CDATA[<p>You saved my Life!!! I was searching for many day to solve this Problem. Thanks for that wonderfull Hint!!!!! Sorry for my english <img src='http://exchangeserverpro.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  Thanks so much from Vienna/Austria! My situation was as following: 2 virtual DC´s (one w2k3 R2 one w2k8), i demotet the 2k3 and used the &#8220;Patch&#8221; on the w2k8, after reboot everething was working angain.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: idgara</title>
		<link>http://exchangeserverpro.com/event-id-2095-and-the-usn-rollback-adventure/comment-page-1#comment-711</link>
		<dc:creator>idgara</dc:creator>
		<pubDate>Sat, 10 Jan 2009 05:52:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.capslockassassin.com/2007/06/02/event-id-2095-and-the-usn-rollback-adventure/#comment-711</guid>
		<description>I&#039;m in the same scenario as Erik as we had a hardware failure and the DR restore resulted in Event ID 2095.

We&#039;re not keen on demoting the Exchange server (restored) either so will try demoting the DC2 and clearing the registry key...I think I&#039;ll try it in a virtual environment first.

Erik - did it work for you?</description>
		<content:encoded><![CDATA[<p>I&#8217;m in the same scenario as Erik as we had a hardware failure and the DR restore resulted in Event ID 2095.</p>
<p>We&#8217;re not keen on demoting the Exchange server (restored) either so will try demoting the DC2 and clearing the registry key&#8230;I think I&#8217;ll try it in a virtual environment first.</p>
<p>Erik &#8211; did it work for you?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik</title>
		<link>http://exchangeserverpro.com/event-id-2095-and-the-usn-rollback-adventure/comment-page-1#comment-570</link>
		<dc:creator>Erik</dc:creator>
		<pubDate>Fri, 12 Sep 2008 04:05:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.capslockassassin.com/2007/06/02/event-id-2095-and-the-usn-rollback-adventure/#comment-570</guid>
		<description>Just to clarify the steps everyone is taking here...

DC1 with Exchange = USN 100
DC2 without exchange = USN 10

You are demoting DC2 along with cleaning the metabase since you cannot demote DC1 because of exchange and then editing the registry on DC1 with the information supplied by Rob...right?

This then fixes the netlogon pausing problem when starting up DC1

Thanks for everyone for contributing!</description>
		<content:encoded><![CDATA[<p>Just to clarify the steps everyone is taking here&#8230;</p>
<p>DC1 with Exchange = USN 100<br />
DC2 without exchange = USN 10</p>
<p>You are demoting DC2 along with cleaning the metabase since you cannot demote DC1 because of exchange and then editing the registry on DC1 with the information supplied by Rob&#8230;right?</p>
<p>This then fixes the netlogon pausing problem when starting up DC1</p>
<p>Thanks for everyone for contributing!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Is Cuil off to a good start? - Crane Factory</title>
		<link>http://exchangeserverpro.com/event-id-2095-and-the-usn-rollback-adventure/comment-page-1#comment-499</link>
		<dc:creator>Is Cuil off to a good start? - Crane Factory</dc:creator>
		<pubDate>Wed, 30 Jul 2008 12:48:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.capslockassassin.com/2007/06/02/event-id-2095-and-the-usn-rollback-adventure/#comment-499</guid>
		<description>[...] time ago I wrote a post titled &#8220;Event ID 2095 and the USN Rollback Adventure&#8220;, which is one of my highest trafficked posts and ranks on Google for &#8220;Event ID [...]</description>
		<content:encoded><![CDATA[<p>[...] time ago I wrote a post titled &#8220;Event ID 2095 and the USN Rollback Adventure&#8220;, which is one of my highest trafficked posts and ranks on Google for &#8220;Event ID [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Rutkowski</title>
		<link>http://exchangeserverpro.com/event-id-2095-and-the-usn-rollback-adventure/comment-page-1#comment-475</link>
		<dc:creator>John Rutkowski</dc:creator>
		<pubDate>Thu, 26 Jun 2008 03:42:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.capslockassassin.com/2007/06/02/event-id-2095-and-the-usn-rollback-adventure/#comment-475</guid>
		<description>We restored an SBS2003 server for a client and the System state restored caused the USN symptomswith NETLOGON paused. Tried removing the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters “Dsa Not Writable”=dword:00000004″

And it worked! Saved me many hours of frustration! I was getting ready to camp on the MS line. Never gotten anything solved in less than 4 hours with them.

What we all really need is a supported way from Microsoft to restore a windows server to radically different hardware. Disasters happen and you can&#039;t always restore to like system.

Moving Novell Netware to new hardware is a piece of cake. And NDS is more robust.

SBS complicates things becasue EVERYTHING is on one server, DC, PDC, DNS, etc.</description>
		<content:encoded><![CDATA[<p>We restored an SBS2003 server for a client and the System state restored caused the USN symptomswith NETLOGON paused. Tried removing the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters “Dsa Not Writable”=dword:00000004″</p>
<p>And it worked! Saved me many hours of frustration! I was getting ready to camp on the MS line. Never gotten anything solved in less than 4 hours with them.</p>
<p>What we all really need is a supported way from Microsoft to restore a windows server to radically different hardware. Disasters happen and you can&#8217;t always restore to like system.</p>
<p>Moving Novell Netware to new hardware is a piece of cake. And NDS is more robust.</p>
<p>SBS complicates things becasue EVERYTHING is on one server, DC, PDC, DNS, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken</title>
		<link>http://exchangeserverpro.com/event-id-2095-and-the-usn-rollback-adventure/comment-page-1#comment-471</link>
		<dc:creator>Ken</dc:creator>
		<pubDate>Fri, 06 Jun 2008 18:14:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.capslockassassin.com/2007/06/02/event-id-2095-and-the-usn-rollback-adventure/#comment-471</guid>
		<description>&quot;Anyway, to stop the server from “thinking” it’s messed up, you need to remove the following from the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters “Dsa Not Writable”=dword:00000004&quot;

My situation was similar: my sole DC thought it was suffering a USN rollback after an episode of hardware failures trying to promote another server.

I&#039;d noticed this page back in January and then again today and gave it a try.

This totally fixed the problem - many thanks for sharing!</description>
		<content:encoded><![CDATA[<p>&#8220;Anyway, to stop the server from “thinking” it’s messed up, you need to remove the following from the registry:<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters “Dsa Not Writable”=dword:00000004&#8243;</p>
<p>My situation was similar: my sole DC thought it was suffering a USN rollback after an episode of hardware failures trying to promote another server.</p>
<p>I&#8217;d noticed this page back in January and then again today and gave it a try.</p>
<p>This totally fixed the problem &#8211; many thanks for sharing!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jarrod</title>
		<link>http://exchangeserverpro.com/event-id-2095-and-the-usn-rollback-adventure/comment-page-1#comment-452</link>
		<dc:creator>Jarrod</dc:creator>
		<pubDate>Sun, 11 May 2008 04:15:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.capslockassassin.com/2007/06/02/event-id-2095-and-the-usn-rollback-adventure/#comment-452</guid>
		<description>Been struggling with this for a while thanks for the info :-)

Deleting the &quot;DSA Not Writable&quot; registry key is as effetive as it is simple, many thanks...</description>
		<content:encoded><![CDATA[<p>Been struggling with this for a while thanks for the info <img src='http://exchangeserverpro.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Deleting the &#8220;DSA Not Writable&#8221; registry key is as effetive as it is simple, many thanks&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob P</title>
		<link>http://exchangeserverpro.com/event-id-2095-and-the-usn-rollback-adventure/comment-page-1#comment-408</link>
		<dc:creator>Rob P</dc:creator>
		<pubDate>Thu, 20 Mar 2008 23:54:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.capslockassassin.com/2007/06/02/event-id-2095-and-the-usn-rollback-adventure/#comment-408</guid>
		<description>I know how alone a person can feel when faced with a situation not yet documented.  I can&#039;t count the number of  times I have been helped by a forum like this one.

It&#039;s good to have helped someone else for a change...</description>
		<content:encoded><![CDATA[<p>I know how alone a person can feel when faced with a situation not yet documented.  I can&#8217;t count the number of  times I have been helped by a forum like this one.</p>
<p>It&#8217;s good to have helped someone else for a change&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://exchangeserverpro.com/event-id-2095-and-the-usn-rollback-adventure/comment-page-1#comment-384</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Thu, 06 Mar 2008 03:03:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.capslockassassin.com/2007/06/02/event-id-2095-and-the-usn-rollback-adventure/#comment-384</guid>
		<description>Thanks again for sharing the solution Rob.</description>
		<content:encoded><![CDATA[<p>Thanks again for sharing the solution Rob.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
