<?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: Security descriptor error during Exchange Server 2007 schema extension</title>
	<atom:link href="http://exchangeserverpro.com/security-descriptor-error-during-exchange-server-2007-schema-extension/feed" rel="self" type="application/rss+xml" />
	<link>http://exchangeserverpro.com/security-descriptor-error-during-exchange-server-2007-schema-extension</link>
	<description>Microsoft Exchange Server News - Tips - Tutorials</description>
	<lastBuildDate>Fri, 10 Feb 2012 02:36:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Ganesh</title>
		<link>http://exchangeserverpro.com/security-descriptor-error-during-exchange-server-2007-schema-extension#comment-1131</link>
		<dc:creator>Ganesh</dc:creator>
		<pubDate>Wed, 04 Nov 2009 09:41:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.capslockassassin.com/2008/09/09/security-descriptor-error-during-exchange-server-2007-schema-extension/#comment-1131</guid>
		<description>Thanks for this followup</description>
		<content:encoded><![CDATA[<p>Thanks for this followup</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CrashtheMachine</title>
		<link>http://exchangeserverpro.com/security-descriptor-error-during-exchange-server-2007-schema-extension#comment-1118</link>
		<dc:creator>CrashtheMachine</dc:creator>
		<pubDate>Tue, 20 Oct 2009 19:04:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.capslockassassin.com/2008/09/09/security-descriptor-error-during-exchange-server-2007-schema-extension/#comment-1118</guid>
		<description>Ganesh, that workaround is just plain dumb but it works.  Why would that ever make a difference.  Thanks for the simple solution.  I like those.</description>
		<content:encoded><![CDATA[<p>Ganesh, that workaround is just plain dumb but it works.  Why would that ever make a difference.  Thanks for the simple solution.  I like those.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Qwantum</title>
		<link>http://exchangeserverpro.com/security-descriptor-error-during-exchange-server-2007-schema-extension#comment-1116</link>
		<dc:creator>Qwantum</dc:creator>
		<pubDate>Fri, 16 Oct 2009 17:00:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.capslockassassin.com/2008/09/09/security-descriptor-error-during-exchange-server-2007-schema-extension/#comment-1116</guid>
		<description>Ganesh workaround worked perfectly for me. Changing the CD drive letter to E: (instead of D:) resolved the &#039;Organization Preparation&#039; step issue where I could not read the &#039;Security Descriptor&#039; on &quot;CN=Deleted O
bjects,CN=Configuration,DC=domain,DC=local&quot;.

Damn Micro$oft and their &quot;never-working-out-of-the-box-that-need-thousands-of-workaround-and-fixes&quot; applications...

Thanks Ganesh !</description>
		<content:encoded><![CDATA[<p>Ganesh workaround worked perfectly for me. Changing the CD drive letter to E: (instead of D:) resolved the &#8216;Organization Preparation&#8217; step issue where I could not read the &#8216;Security Descriptor&#8217; on &#8220;CN=Deleted O<br />
bjects,CN=Configuration,DC=domain,DC=local&#8221;.</p>
<p>Damn Micro$oft and their &#8220;never-working-out-of-the-box-that-need-thousands-of-workaround-and-fixes&#8221; applications&#8230;</p>
<p>Thanks Ganesh !</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ganesh</title>
		<link>http://exchangeserverpro.com/security-descriptor-error-during-exchange-server-2007-schema-extension#comment-749</link>
		<dc:creator>Ganesh</dc:creator>
		<pubDate>Wed, 18 Feb 2009 13:47:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.capslockassassin.com/2008/09/09/security-descriptor-error-during-exchange-server-2007-schema-extension/#comment-749</guid>
		<description>Hello,
During exchange 2007 sp1 setup the same error accured 
You do not have permissions to read the security descriptor on CN=Deleted O
bjects,CN=Configuration,DC=domain,DC=com,DC=au.

FOR RESOLVE THE PROBLEM

CHANGE YOUR CD DRIVE LETTER TO E:\

And Run the exchange setup again.</description>
		<content:encoded><![CDATA[<p>Hello,<br />
During exchange 2007 sp1 setup the same error accured<br />
You do not have permissions to read the security descriptor on CN=Deleted O<br />
bjects,CN=Configuration,DC=domain,DC=com,DC=au.</p>
<p>FOR RESOLVE THE PROBLEM</p>
<p>CHANGE YOUR CD DRIVE LETTER TO E:\</p>
<p>And Run the exchange setup again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://exchangeserverpro.com/security-descriptor-error-during-exchange-server-2007-schema-extension#comment-709</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Tue, 06 Jan 2009 22:57:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.capslockassassin.com/2008/09/09/security-descriptor-error-during-exchange-server-2007-schema-extension/#comment-709</guid>
		<description>Update: Kay and I took this discussion to email and identified the issue.  To summarise:

dsacls &quot;CN=Deleted Objects,DC=domain,DC=com&quot; /takeownership

1) Make sure you include the space in Deleted Objects
2) Make sure you enclose the LDAP string in quotes
3) Make sure you replace &quot;dc=domain,dc=com&quot; with the right values for your domain name

Glad the problem is solved Kay!</description>
		<content:encoded><![CDATA[<p>Update: Kay and I took this discussion to email and identified the issue.  To summarise:</p>
<p>dsacls &#8220;CN=Deleted Objects,DC=domain,DC=com&#8221; /takeownership</p>
<p>1) Make sure you include the space in Deleted Objects<br />
2) Make sure you enclose the LDAP string in quotes<br />
3) Make sure you replace &#8220;dc=domain,dc=com&#8221; with the right values for your domain name</p>
<p>Glad the problem is solved Kay!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kay Malm</title>
		<link>http://exchangeserverpro.com/security-descriptor-error-during-exchange-server-2007-schema-extension#comment-704</link>
		<dc:creator>Kay Malm</dc:creator>
		<pubDate>Fri, 02 Jan 2009 20:37:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.capslockassassin.com/2008/09/09/security-descriptor-error-during-exchange-server-2007-schema-extension/#comment-704</guid>
		<description>I tried running the command and there is no Object.</description>
		<content:encoded><![CDATA[<p>I tried running the command and there is no Object.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://exchangeserverpro.com/security-descriptor-error-during-exchange-server-2007-schema-extension#comment-702</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Thu, 01 Jan 2009 03:20:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.capslockassassin.com/2008/09/09/security-descriptor-error-during-exchange-server-2007-schema-extension/#comment-702</guid>
		<description>According to the article the version of DSACLS.exe that ships with ADAM is required for the fix.

The syntax for the deleted objects container is as follows:

&quot;CN=Deleted Objects,DC=domain,DC=com,dc=au&quot;

In that example there the domain is &quot;domain.com.au&quot;.  So you just need to change that part of the string to match your domain, eg:

business.net would be &quot;dc=business,dc=net&quot;
microsoft.com would be &quot;dc=microsoft,dc=com&quot;</description>
		<content:encoded><![CDATA[<p>According to the article the version of DSACLS.exe that ships with ADAM is required for the fix.</p>
<p>The syntax for the deleted objects container is as follows:</p>
<p>&#8220;CN=Deleted Objects,DC=domain,DC=com,dc=au&#8221;</p>
<p>In that example there the domain is &#8220;domain.com.au&#8221;.  So you just need to change that part of the string to match your domain, eg:</p>
<p>business.net would be &#8220;dc=business,dc=net&#8221;<br />
microsoft.com would be &#8220;dc=microsoft,dc=com&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kay Malm</title>
		<link>http://exchangeserverpro.com/security-descriptor-error-during-exchange-server-2007-schema-extension#comment-701</link>
		<dc:creator>Kay Malm</dc:creator>
		<pubDate>Wed, 31 Dec 2008 16:56:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.capslockassassin.com/2008/09/09/security-descriptor-error-during-exchange-server-2007-schema-extension/#comment-701</guid>
		<description>If I don&#039;t have ADAM installed, how do I use the tools?  I do not know the correct syntax for my deleted objects or CN,DC portions of command.  Where do I find this?</description>
		<content:encoded><![CDATA[<p>If I don&#8217;t have ADAM installed, how do I use the tools?  I do not know the correct syntax for my deleted objects or CN,DC portions of command.  Where do I find this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://exchangeserverpro.com/security-descriptor-error-during-exchange-server-2007-schema-extension#comment-699</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Tue, 30 Dec 2008 21:26:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.capslockassassin.com/2008/09/09/security-descriptor-error-during-exchange-server-2007-schema-extension/#comment-699</guid>
		<description>Kay, I&#039;m not saying install ADAM, I&#039;m saying once you&#039;ve got ADLDS installed on the server and you&#039;ve run the DSACLS command try also following the final step in that article I linked to.

Also, you could try installing ADAM on a Windows Server 2003 server in your environment instead.

I don&#039;t have any further suggestions right now because my experience has always been that the steps I wrote about in the blog post fix the problem.</description>
		<content:encoded><![CDATA[<p>Kay, I&#8217;m not saying install ADAM, I&#8217;m saying once you&#8217;ve got ADLDS installed on the server and you&#8217;ve run the DSACLS command try also following the final step in that article I linked to.</p>
<p>Also, you could try installing ADAM on a Windows Server 2003 server in your environment instead.</p>
<p>I don&#8217;t have any further suggestions right now because my experience has always been that the steps I wrote about in the blog post fix the problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kay Malm</title>
		<link>http://exchangeserverpro.com/security-descriptor-error-during-exchange-server-2007-schema-extension#comment-698</link>
		<dc:creator>Kay Malm</dc:creator>
		<pubDate>Tue, 30 Dec 2008 15:40:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.capslockassassin.com/2008/09/09/security-descriptor-error-during-exchange-server-2007-schema-extension/#comment-698</guid>
		<description>Please refer back to original request.  ADAM fails to install - error &quot;Not enough storage is available to process this command.&quot;  I have available 249 GB of space available.  I am already a member of the Domain Administrators Group.  Exchange fails to install because as Administrator I do not have permission to read the security description.  Why are we back to doing what I have already tried?</description>
		<content:encoded><![CDATA[<p>Please refer back to original request.  ADAM fails to install &#8211; error &#8220;Not enough storage is available to process this command.&#8221;  I have available 249 GB of space available.  I am already a member of the Domain Administrators Group.  Exchange fails to install because as Administrator I do not have permission to read the security description.  Why are we back to doing what I have already tried?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

