<?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: vCenter Server linked Mode. Error 28039. Setup cannot join vCenter Server to the linked mode group</title>
	<atom:link href="http://www.virtualizationteam.com/virtualization-vmware/vsphere-virtualization-vmware/vcenter-server-linked-mode-error-28039-setup-cannot-join-vcenter-server-to-the-linked-mode-group.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.virtualizationteam.com/virtualization-vmware/vsphere-virtualization-vmware/vcenter-server-linked-mode-error-28039-setup-cannot-join-vcenter-server-to-the-linked-mode-group.html</link>
	<description>Vmware ESX/ESXi - MS Hyper-V - ESX server; tutorials, how-to, video</description>
	<lastBuildDate>Wed, 25 Aug 2010 18:15:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Brian</title>
		<link>http://www.virtualizationteam.com/virtualization-vmware/vsphere-virtualization-vmware/vcenter-server-linked-mode-error-28039-setup-cannot-join-vcenter-server-to-the-linked-mode-group.html/comment-page-1#comment-1307</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Sun, 11 Oct 2009 11:06:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.virtualizationteam.com/?p=251#comment-1307</guid>
		<description>Hi There, Ive got this exact same problem but Ive been through all the things listed in your post and im still not able to configure linked mode.

The VC servers are virtual, but not cloned, they were new installs.
Time on systems is within 5 mins.
User account setup in AD and added to the local admin group on each vc server, also domain admin user also fails.
Both systems in same domain
DNS configured, all nslookups are 100% ok.

Im struggling to find the log files, any ideas ?</description>
		<content:encoded><![CDATA[<p>Hi There, Ive got this exact same problem but Ive been through all the things listed in your post and im still not able to configure linked mode.</p>
<p>The VC servers are virtual, but not cloned, they were new installs.<br />
Time on systems is within 5 mins.<br />
User account setup in AD and added to the local admin group on each vc server, also domain admin user also fails.<br />
Both systems in same domain<br />
DNS configured, all nslookups are 100% ok.</p>
<p>Im struggling to find the log files, any ideas ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eiad</title>
		<link>http://www.virtualizationteam.com/virtualization-vmware/vsphere-virtualization-vmware/vcenter-server-linked-mode-error-28039-setup-cannot-join-vcenter-server-to-the-linked-mode-group.html/comment-page-1#comment-840</link>
		<dc:creator>Eiad</dc:creator>
		<pubDate>Fri, 28 Aug 2009 18:53:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.virtualizationteam.com/?p=251#comment-840</guid>
		<description>Hi Mordock,

Thanks for your contribution, and sorry for the late reply. Though I am traveling abroad these days and don&#039;t get much of access to the net in here. I am glad you found the solution, and me restating the points in the manual with a bit extra on them was done as I found many people over looked them including me the first time I tried it in lab. Again thanks for your contribution &amp; sharing the solution with us.</description>
		<content:encoded><![CDATA[<p>Hi Mordock,</p>
<p>Thanks for your contribution, and sorry for the late reply. Though I am traveling abroad these days and don&#8217;t get much of access to the net in here. I am glad you found the solution, and me restating the points in the manual with a bit extra on them was done as I found many people over looked them including me the first time I tried it in lab. Again thanks for your contribution &#038; sharing the solution with us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mordock</title>
		<link>http://www.virtualizationteam.com/virtualization-vmware/vsphere-virtualization-vmware/vcenter-server-linked-mode-error-28039-setup-cannot-join-vcenter-server-to-the-linked-mode-group.html/comment-page-1#comment-838</link>
		<dc:creator>Mordock</dc:creator>
		<pubDate>Fri, 28 Aug 2009 14:54:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.virtualizationteam.com/?p=251#comment-838</guid>
		<description>I finally found the answer.  It has to do with the installation of ADAM and RPC. I found the following on another site:

&quot;On investigation we found that ADAM requires 2 more addtional ports  
(Port 135 &amp; a random port between 1025-65535) other than port 2000 to be opened at firewall. If I open those ports I replication happens without any Issues.&quot;

In simpler terms, turn off the firewall so that RPC can communicate, thus getting rid of the 0x800705ec error.
Error code: 0x800706ec
The list of RPC servers available for the binding of auto handles has been exhausted.</description>
		<content:encoded><![CDATA[<p>I finally found the answer.  It has to do with the installation of ADAM and RPC. I found the following on another site:</p>
<p>&#8220;On investigation we found that ADAM requires 2 more addtional ports<br />
(Port 135 &amp; a random port between 1025-65535) other than port 2000 to be opened at firewall. If I open those ports I replication happens without any Issues.&#8221;</p>
<p>In simpler terms, turn off the firewall so that RPC can communicate, thus getting rid of the 0&#215;800705ec error.<br />
Error code: 0&#215;800706ec<br />
The list of RPC servers available for the binding of auto handles has been exhausted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mordock</title>
		<link>http://www.virtualizationteam.com/virtualization-vmware/vsphere-virtualization-vmware/vcenter-server-linked-mode-error-28039-setup-cannot-join-vcenter-server-to-the-linked-mode-group.html/comment-page-1#comment-837</link>
		<dc:creator>Mordock</dc:creator>
		<pubDate>Fri, 28 Aug 2009 14:17:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.virtualizationteam.com/?p=251#comment-837</guid>
		<description>I can read the manual as well as you can.  This is not the solution to the problem.  There is something else that they are not telling us.  The following is in the log:

[2009-08-27 21:48:35 SEVERE] Operation &quot;Join instance VMwareVCMSDS&quot; failed: : Action: Join Instance
Action: Join Instance
Action: Create replica instance
Action: Create Instance
Problem: Creation of instance VMwareVCMSDS failed: Active Directory could not create the NTDS Settings object for this directory server CN=NTDS Settings,CN=VCENTER66$VMwareVCMSDS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,CN={1FAF683A-F763-45F5-9778-ADB023112C7B} on the remote directory server vCenter67.vi3.vm:389. Ensure the provided network credentials have sufficient permissions.
Error code: 0x800706ec

Notice that it is trying to make changes to active directory and that is what is failing.  Just what permissions does it need in AD??  There appears to be no stated requirement that it be an AD administrator account, yet it is making changes in AD.  I&#039;ve even tried it as Domain Admin, even as Enterprise Admin.</description>
		<content:encoded><![CDATA[<p>I can read the manual as well as you can.  This is not the solution to the problem.  There is something else that they are not telling us.  The following is in the log:</p>
<p>[2009-08-27 21:48:35 SEVERE] Operation &#8220;Join instance VMwareVCMSDS&#8221; failed: : Action: Join Instance<br />
Action: Join Instance<br />
Action: Create replica instance<br />
Action: Create Instance<br />
Problem: Creation of instance VMwareVCMSDS failed: Active Directory could not create the NTDS Settings object for this directory server CN=NTDS Settings,CN=VCENTER66$VMwareVCMSDS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,CN={1FAF683A-F763-45F5-9778-ADB023112C7B} on the remote directory server vCenter67.vi3.vm:389. Ensure the provided network credentials have sufficient permissions.<br />
Error code: 0&#215;800706ec</p>
<p>Notice that it is trying to make changes to active directory and that is what is failing.  Just what permissions does it need in AD??  There appears to be no stated requirement that it be an AD administrator account, yet it is making changes in AD.  I&#8217;ve even tried it as Domain Admin, even as Enterprise Admin.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
