I'm receiving this error when attempting to publish my Topology with Lync 2010 Enterprise Edition:

http://dl.dropbox.com/u/2210630/Topology%20Failure.txt

My Current setup is the following:

-Root Domain Controller (Where Lync AD Prep/Forest was ran) Windows Server 2008 R2 Standard x64

--Primary Domain Controller (Where the Domain Admin I'm using to install Lync sits) Windows Server 2003 Standard x64

---LyncFE (Front End Server, on the Primary Domain, location of Topology push)

---LyncBE (Back End Server, on the Primary Domain)

---LyncMA (Archiving/Monitoring Server, on the Primary Domain)

I'm wondering if this is part of the issue...should I be seeing the Lync security groups in the primary domain as well as the root?  Currently they're only in the Root...also within the Root domain I gave my domain admin from my primary domain the following permissions:

Primary Domain Admin Credentials:

CSAdministrator (Root Domain)

RTCUniversalServerAdmins (Root Domain)

I also gave the computer account which I'm installing/pushing the topology from (LyncFE) permissions to the following groups which all sit in the Root Domain:

RTCHSUniversalServices
RTCComponentUniversalServices
RTCUniversalConfigReplicator
RTCUniversalServerAdmins
RTCUniversalUserAdmins

A little more information:

On this test network there was a previous install of Lync 2010 Trial Version.  I did my best to remove all the previously installed components but the Forest/Domain Prep changes remains.  I did however remove the reference to the old configuration store location...this gave me trouble initially.

Any help is greatly appreciated!  I'm at a total stand still with deploying this =/.

The groups should be created in the domain you specidied when you ran forest prep.  They should not exist in multiple domains typically they exist in the root domain.

I see you gave some permissions to a user but I don't see what account you are installing as.  Your installer account should have local admin rights to the server you are installing on, the SQL server, SQL Server permissions db_owner as well as CSAdministrator.  Make sure you log off after your grant yourself appropriate rights. 

also - you dont need to add the computer account to any of those groups - I recommend removing any changes to security you made.

Mark

Hi,EmbraceDarko,

The permission requirement for publishing a topology are Domain Group membership in one of the following groups:

• Domain Admins Group
• RTCUniversalServerAdmins Group

• For Enterprise Edition, the SQL Server-based Back End Server must be joined to the domain in which you are deploying the servers, online, and remotely accessible by means of defining firewall rules on the SQL Server-based server.
• Except for Edge Servers, the computers referenced in the topology must be joined to the domain and in Active Directory Domain Services (AD DS), but do not need to be online when you publish the topology (except for the SQL Server-based Back End Server, as described in the previous bullet). Standard Edition server has a collocated database that will accept the publish configuration. You must first run “Prepare first Standard Edition server” in the Lync Server Deployment Wizard.
• The file share must be created and accessible by the user account used to publish the topology.
• The SQL Server 2005 backward compatibility components (SQLServer2005_BC.msi, which is included on the installation media) must be installed on the server on which you are using Topology Builder to publish the topology. This should be installed automatically by Setup when running the Lync Server Deployment Wizard.
• A member of the Domain Admins group can follow Setup Delegation steps to delegate this task to other users or groups. For details, see Delegate Setup Permissions. Following the successful delegation of permissions, the specified user objects will be able to run the Publish-CsTopology and Enable-CsTopology cmdlets, in addition to other commands related to setup and publishing).

So please check the account has permission to remote access your back-end databaser server and have permission to access the file share.

And that you mentioned there has installed a trail verison of Lync server 2010 and you have removed the reference,was there any error or warning message when you prep forest/domain for the new deployment?Could you also check the event viewer to see if there are any error or warning messages?

Regards,

Sharon

• Proposed as answer by Sharon.ShenMicrosoft contingent staff, Moderator Wednesday, July 20, 2011 6:54 AM
• Marked as answer by Sharon.ShenMicrosoft contingent staff, Moderator Friday, July 22, 2011 2:46 AM

Hi,EmbraceDarko,

The permission requirement for publishing a topology are Domain Group membership in one of the following groups:

• Domain Admins Group
• RTCUniversalServerAdmins Group

• For Enterprise Edition, the SQL Server-based Back End Server must be joined to the domain in which you are deploying the servers, online, and remotely accessible by means of defining firewall rules on the SQL Server-based server.
• Except for Edge Servers, the computers referenced in the topology must be joined to the domain and in Active Directory Domain Services (AD DS), but do not need to be online when you publish the topology (except for the SQL Server-based Back End Server, as described in the previous bullet). Standard Edition server has a collocated database that will accept the publish configuration. You must first run “Prepare first Standard Edition server” in the Lync Server Deployment Wizard.
• The file share must be created and accessible by the user account used to publish the topology.
• The SQL Server 2005 backward compatibility components (SQLServer2005_BC.msi, which is included on the installation media) must be installed on the server on which you are using Topology Builder to publish the topology. This should be installed automatically by Setup when running the Lync Server Deployment Wizard.
• A member of the Domain Admins group can follow Setup Delegation steps to delegate this task to other users or groups. For details, see Delegate Setup Permissions. Following the successful delegation of permissions, the specified user objects will be able to run the Publish-CsTopology and Enable-CsTopology cmdlets, in addition to other commands related to setup and publishing).

So please check the account has permission to remote access your back-end databaser server and have permission to access the file share.

And that you mentioned there has installed a trail verison of Lync server 2010 and you have removed the reference,was there any error or warning message when you prep forest/domain for the new deployment?Could you also check the event viewer to see if there are any error or warning messages?

Regards,

Sharon

• Proposed as answer by Sharon.ShenMicrosoft contingent staff, Moderator Wednesday, July 20, 2011 6:54 AM
• Marked as answer by Sharon.ShenMicrosoft contingent staff, Moderator Friday, July 22, 2011 2:46 AM

Hi,EmbraceDarko,

The permission requirement for publishing a topology are Domain Group membership in one of the following groups:

• Domain Admins Group
• RTCUniversalServerAdmins Group

• For Enterprise Edition, the SQL Server-based Back End Server must be joined to the domain in which you are deploying the servers, online, and remotely accessible by means of defining firewall rules on the SQL Server-based server.
• Except for Edge Servers, the computers referenced in the topology must be joined to the domain and in Active Directory Domain Services (AD DS), but do not need to be online when you publish the topology (except for the SQL Server-based Back End Server, as described in the previous bullet). Standard Edition server has a collocated database that will accept the publish configuration. You must first run “Prepare first Standard Edition server” in the Lync Server Deployment Wizard.
• The file share must be created and accessible by the user account used to publish the topology.
• The SQL Server 2005 backward compatibility components (SQLServer2005_BC.msi, which is included on the installation media) must be installed on the server on which you are using Topology Builder to publish the topology. This should be installed automatically by Setup when running the Lync Server Deployment Wizard.
• A member of the Domain Admins group can follow Setup Delegation steps to delegate this task to other users or groups. For details, see Delegate Setup Permissions. Following the successful delegation of permissions, the specified user objects will be able to run the Publish-CsTopology and Enable-CsTopology cmdlets, in addition to other commands related to setup and publishing).

So please check the account has permission to remote access your back-end databaser server and have permission to access the file share.

And that you mentioned there has installed a trail verison of Lync server 2010 and you have removed the reference,was there any error or warning message when you prep forest/domain for the new deployment?Could you also check the event viewer to see if there are any error or warning messages?

Regards,

Sharon

• Proposed as answer by Sharon.ShenMicrosoft contingent staff, Moderator Wednesday, July 20, 2011 6:54 AM
• Marked as answer by Sharon.ShenMicrosoft contingent staff, Moderator Friday, July 22, 2011 2:46 AM

Hi,EmbraceDarko,

The permission requirement for publishing a topology are Domain Group membership in one of the following groups:

• Domain Admins Group
• RTCUniversalServerAdmins Group

• For Enterprise Edition, the SQL Server-based Back End Server must be joined to the domain in which you are deploying the servers, online, and remotely accessible by means of defining firewall rules on the SQL Server-based server.
• Except for Edge Servers, the computers referenced in the topology must be joined to the domain and in Active Directory Domain Services (AD DS), but do not need to be online when you publish the topology (except for the SQL Server-based Back End Server, as described in the previous bullet). Standard Edition server has a collocated database that will accept the publish configuration. You must first run “Prepare first Standard Edition server” in the Lync Server Deployment Wizard.
• The file share must be created and accessible by the user account used to publish the topology.
• The SQL Server 2005 backward compatibility components (SQLServer2005_BC.msi, which is included on the installation media) must be installed on the server on which you are using Topology Builder to publish the topology. This should be installed automatically by Setup when running the Lync Server Deployment Wizard.
• A member of the Domain Admins group can follow Setup Delegation steps to delegate this task to other users or groups. For details, see Delegate Setup Permissions. Following the successful delegation of permissions, the specified user objects will be able to run the Publish-CsTopology and Enable-CsTopology cmdlets, in addition to other commands related to setup and publishing).

So please check the account has permission to remote access your back-end databaser server and have permission to access the file share.

And that you mentioned there has installed a trail verison of Lync server 2010 and you have removed the reference,was there any error or warning message when you prep forest/domain for the new deployment?Could you also check the event viewer to see if there are any error or warning messages?

Regards,

Sharon

• Proposed as answer by Sharon.ShenMicrosoft contingent staff, Moderator Wednesday, July 20, 2011 6:54 AM
• Marked as answer by Sharon.ShenMicrosoft contingent staff, Moderator Friday, July 22, 2011 2:46 AM

Thanks for the suggestions guys.  As always these forums rock.  I actually just got off the phone with Microsoft and was able to correct it with resetting my configuration manager store location.  Apparently my previous install of Lync 2010 Standard Trial Edition was interfering with my new install.  The configuration store got pretty messed up and had to be manual set from my new Lync Front End server where I was publishing my topology from. 

We ran the following command and it worked allowing me to finish publishing my topology:

 set-csconfigurationstorelocation -sqlserverfqdn *Your FQDN Lync Back End Servername Here** -sqlinstancename Rtc -report c:\logs\storelocation.html

Hopefully this can help anyone else who had installed Lync 2010 Standard and then later the Enterprise version on the same domain.

• Marked as answer by EmbraceDarko Tuesday, August 02, 2011 7:07 PM

Thanks for the suggestions guys.  As always these forums rock.  I actually just got off the phone with Microsoft and was able to correct it with resetting my configuration manager store location.  Apparently my previous install of Lync 2010 Standard Trial Edition was interfering with my new install.  The configuration store got pretty messed up and had to be manual set from my new Lync Front End server where I was publishing my topology from. 

We ran the following command and it worked allowing me to finish publishing my topology:

 set-csconfigurationstorelocation -sqlserverfqdn *Your FQDN Lync Back End Servername Here** -sqlinstancename Rtc -report c:\logs\storelocation.html

Hopefully this can help anyone else who had installed Lync 2010 Standard and then later the Enterprise version on the same domain.

• Marked as answer by EmbraceDarko Tuesday, August 02, 2011 7:07 PM

Thanks for the suggestions guys.  As always these forums rock.  I actually just got off the phone with Microsoft and was able to correct it with resetting my configuration manager store location.  Apparently my previous install of Lync 2010 Standard Trial Edition was interfering with my new install.  The configuration store got pretty messed up and had to be manual set from my new Lync Front End server where I was publishing my topology from. 

We ran the following command and it worked allowing me to finish publishing my topology:

 set-csconfigurationstorelocation -sqlserverfqdn *Your FQDN Lync Back End Servername Here** -sqlinstancename Rtc -report c:\logs\storelocation.html

Hopefully this can help anyone else who had installed Lync 2010 Standard and then later the Enterprise version on the same domain.

• Marked as answer by EmbraceDarko Tuesday, August 02, 2011 7:07 PM

Thanks for the suggestions guys.  As always these forums rock.  I actually just got off the phone with Microsoft and was able to correct it with resetting my configuration manager store location.  Apparently my previous install of Lync 2010 Standard Trial Edition was interfering with my new install.  The configuration store got pretty messed up and had to be manual set from my new Lync Front End server where I was publishing my topology from. 

We ran the following command and it worked allowing me to finish publishing my topology:

 set-csconfigurationstorelocation -sqlserverfqdn *Your FQDN Lync Back End Servername Here** -sqlinstancename Rtc -report c:\logs\storelocation.html

Hopefully this can help anyone else who had installed Lync 2010 Standard and then later the Enterprise version on the same domain.

• Marked as answer by EmbraceDarko Tuesday, August 02, 2011 7:07 PM

I kept getting this error:

"Cannot locate configuration store location container in the Active Directory global settings container"

I followed all the comments on here, but no luck.  However, when browsing ADSIedit - I noticed two "Topology Settings" objects in the: CN=RTC Service,CN=Microsoft,CN=System,DC=domain,DC=local container.  one was a CNF:XXX presumably from a replication error.  As soon as I removed the conflicted object, I was able to publish the topology.

• Proposed as answer by shototadumadze 11 hours 29 minutes ago

I kept getting this error:

"Cannot locate configuration store location container in the Active Directory global settings container"

I followed all the comments on here, but no luck.  However, when browsing ADSIedit - I noticed two "Topology Settings" objects in the: CN=RTC Service,CN=Microsoft,CN=System,DC=domain,DC=local container.  one was a CNF:XXX presumably from a replication error.  As soon as I removed the conflicted object, I was able to publish the topology.

• Proposed as answer by shototadumadze Sunday, April 05, 2015 7:54 PM

I kept getting this error:

"Cannot locate configuration store location container in the Active Directory global settings container"

I followed all the comments on here, but no luck.  However, when browsing ADSIedit - I noticed two "Topology Settings" objects in the: CN=RTC Service,CN=Microsoft,CN=System,DC=domain,DC=local container.  one was a CNF:XXX presumably from a replication error.  As soon as I removed the conflicted object, I was able to publish the topology.

• Proposed as answer by shototadumadze Sunday, April 05, 2015 7:54 PM

I kept getting this error:

"Cannot locate configuration store location container in the Active Directory global settings container"

I followed all the comments on here, but no luck.  However, when browsing ADSIedit - I noticed two "Topology Settings" objects in the: CN=RTC Service,CN=Microsoft,CN=System,DC=domain,DC=local container.  one was a CNF:XXX presumably from a replication error.  As soon as I removed the conflicted object, I was able to publish the topology.

• Proposed as answer by shototadumadze Sunday, April 05, 2015 7:54 PM

I kept getting this error:

"Cannot locate configuration store location container in the Active Directory global settings container"

I followed all the comments on here, but no luck.  However, when browsing ADSIedit - I noticed two "Topology Settings" objects in the: CN=RTC Service,CN=Microsoft,CN=System,DC=domain,DC=local container.  one was a CNF:XXX presumably from a replication error.  As soon as I removed the conflicted object, I was able to publish the topology.

• Proposed as answer by shototadumadze Sunday, April 05, 2015 7:54 PM

set-csconfigurationstorelocation -sqlserverfqdn *Your FQDN Lync Back End Servername Here** -sqlinstancename Rtc -report c:\logs\storelocation.html

should I point my SQL standard fqdn here OR EE Lync SQL instance ?