<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: AD: Active Directory Users and Computers Slow to Initialize</title>
	<link>http://blog.netnerds.net/2006/12/ad-active-directory-users-and-computers-slow-to-initialize/</link>
	<description>ls /usr/lolcat</description>
	<pubDate>Sun, 12 Oct 2008 10:56:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Wim</title>
		<link>http://blog.netnerds.net/2006/12/ad-active-directory-users-and-computers-slow-to-initialize/#comment-512</link>
		<dc:creator>Wim</dc:creator>
		<pubDate>Wed, 09 May 2007 05:56:47 +0000</pubDate>
		<guid>http://blog.netnerds.net/2006/12/ad-active-directory-users-and-computers-slow-to-initialize/#comment-512</guid>
		<description>With your script I figured out the probleme here wasn't on the LDAP layer. My collegue noticed when he closed the AD mmc the mmc.exe process did not stop. In face it took 100% of system resources..

The probleem seems to be known to microsoft though they have not yet come up with a solution and the kb seems to be about win2k instead of the Win2k3 R2 we're using...

http://support.microsoft.com/kb/300036</description>
		<content:encoded><![CDATA[<p>With your script I figured out the probleme here wasn't on the LDAP layer. My collegue noticed when he closed the AD mmc the mmc.exe process did not stop. In face it took 100% of system resources..</p>
<p>The probleem seems to be known to microsoft though they have not yet come up with a solution and the kb seems to be about win2k instead of the Win2k3 R2 we're using...</p>
<p><a href="http://support.microsoft.com/kb/300036" rel="nofollow">http://support.microsoft.com/kb/300036</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wim</title>
		<link>http://blog.netnerds.net/2006/12/ad-active-directory-users-and-computers-slow-to-initialize/#comment-511</link>
		<dc:creator>Wim</dc:creator>
		<pubDate>Wed, 09 May 2007 02:51:40 +0000</pubDate>
		<guid>http://blog.netnerds.net/2006/12/ad-active-directory-users-and-computers-slow-to-initialize/#comment-511</guid>
		<description>thanks a MILLION! Really wouldn't have come up with that solution by myself!</description>
		<content:encoded><![CDATA[<p>thanks a MILLION! Really wouldn't have come up with that solution by myself!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vikrant</title>
		<link>http://blog.netnerds.net/2006/12/ad-active-directory-users-and-computers-slow-to-initialize/#comment-510</link>
		<dc:creator>vikrant</dc:creator>
		<pubDate>Wed, 14 Mar 2007 05:01:58 +0000</pubDate>
		<guid>http://blog.netnerds.net/2006/12/ad-active-directory-users-and-computers-slow-to-initialize/#comment-510</guid>
		<description>I am facing a similar problem.I have 2 sites geografically seperated by 1000 miles. I have 512 kbps lease line between the sites.
Now whenever I launch ADC.msc, it loads the remote site ADC.
How can I make it load the ADC where I belong. I have added my subnet address in the ADsite and services then also I am facing the same problem.
Please help....
regards Vikrant</description>
		<content:encoded><![CDATA[<p>I am facing a similar problem.I have 2 sites geografically seperated by 1000 miles. I have 512 kbps lease line between the sites.<br />
Now whenever I launch ADC.msc, it loads the remote site ADC.<br />
How can I make it load the ADC where I belong. I have added my subnet address in the ADsite and services then also I am facing the same problem.<br />
Please help....<br />
regards Vikrant</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chrissy</title>
		<link>http://blog.netnerds.net/2006/12/ad-active-directory-users-and-computers-slow-to-initialize/#comment-509</link>
		<dc:creator>Chrissy</dc:creator>
		<pubDate>Mon, 05 Feb 2007 22:40:06 +0000</pubDate>
		<guid>http://blog.netnerds.net/2006/12/ad-active-directory-users-and-computers-slow-to-initialize/#comment-509</guid>
		<description>Hey DK,
Yep, that's exactly what it was. He wasn't assigned an IP address under DHCP and set his own. His subnet was not defined under Sites and Services. Once that was added, it worked great.

Thanks for commenting!

Chrissy</description>
		<content:encoded><![CDATA[<p>Hey DK,<br />
Yep, that's exactly what it was. He wasn't assigned an IP address under DHCP and set his own. His subnet was not defined under Sites and Services. Once that was added, it worked great.</p>
<p>Thanks for commenting!</p>
<p>Chrissy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DK</title>
		<link>http://blog.netnerds.net/2006/12/ad-active-directory-users-and-computers-slow-to-initialize/#comment-508</link>
		<dc:creator>DK</dc:creator>
		<pubDate>Sat, 03 Feb 2007 15:14:23 +0000</pubDate>
		<guid>http://blog.netnerds.net/2006/12/ad-active-directory-users-and-computers-slow-to-initialize/#comment-508</guid>
		<description>Have you checked AD Sites and Services to see which site his Workstation/Client IP address is a member of? Is it covered by a subnet, if not, create a subnet and assign it to the site where his local DC is located.</description>
		<content:encoded><![CDATA[<p>Have you checked AD Sites and Services to see which site his Workstation/Client IP address is a member of? Is it covered by a subnet, if not, create a subnet and assign it to the site where his local DC is located.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chrissy</title>
		<link>http://blog.netnerds.net/2006/12/ad-active-directory-users-and-computers-slow-to-initialize/#comment-507</link>
		<dc:creator>Chrissy</dc:creator>
		<pubDate>Wed, 10 Jan 2007 03:43:15 +0000</pubDate>
		<guid>http://blog.netnerds.net/2006/12/ad-active-directory-users-and-computers-slow-to-initialize/#comment-507</guid>
		<description>Cyril,
AD should automatically be finding it for you. The above workaround is really a hack. Check your Active Directory Sites and Services to ensure that you've got sites setup and working properly.</description>
		<content:encoded><![CDATA[<p>Cyril,<br />
AD should automatically be finding it for you. The above workaround is really a hack. Check your Active Directory Sites and Services to ensure that you've got sites setup and working properly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cyril Edwards</title>
		<link>http://blog.netnerds.net/2006/12/ad-active-directory-users-and-computers-slow-to-initialize/#comment-506</link>
		<dc:creator>Cyril Edwards</dc:creator>
		<pubDate>Mon, 08 Jan 2007 20:46:05 +0000</pubDate>
		<guid>http://blog.netnerds.net/2006/12/ad-active-directory-users-and-computers-slow-to-initialize/#comment-506</guid>
		<description>Hi

i found that using the ip address fixed the problem however what about fault tolerance and redundancy? what if that server is busy or down?</description>
		<content:encoded><![CDATA[<p>Hi</p>
<p>i found that using the ip address fixed the problem however what about fault tolerance and redundancy? what if that server is busy or down?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
