Yet Another Reason the Front end services will not start on Lync 2013 Pool. Child Domains beware of event ID 41029 and 30009.

Yet Another Reason the Front end services will not start on Lync 2013 Pool.  Child Domains beware of event ID 41029 and 30009.

In an instance where you had tried to run the Lync Installation Wizard and  failed to install the Schema and Forrest updates, you may have looked at the  DigitalBamboo web site to find instructions on how to manually prepare the  Schema and Forrest.

https://digitalbamboo.wordpress.com/2013/11/13/prepare-lync-2013-forrest-where-a-null-root-domain-exist/

img2

Everything is going fine until you try to start the Front end service. I must  say, I had an install very similar where there was no issues. This was because  there was no other child domains to scan when the front end service starts. The odd thing about this is no users can even be created for lync at this time.  We have uncovered a prerequisite for the Front end service that we did not know was there. This prerequisite is the User Replicator naming context for the  forest. The default should not be set. The global setting is default,  the domain in the forest is  scanned and the service will start; unless you have multiple child domains, and you install Lync 2013 in one of those children… And you had prepared a null Root Domain. Yes this is a mind blower.

In this unusual circumstance, Lets say there are 5 child domains. you only  install Lync in one domain. So the behavior of the Front End Service is to look  for the user replicator naming contexts. In other words there front end service  will not start if there are child domains that are not domain prepped for Lync.  you have 2 choices, prepare all child domains for lync. or narrow the scope of  the naming context. Really? wow. once you administer one of the following your  front end service should start

The default value should be NULL. This will check all domains in the forrest.  If you need to narrow or control the scope of the variable look at this KB gg398540 and commands:

Set-CsUserReplicatorConfiguration -Identity global -ADDomainNamingContextList  @{Add=”dc=domain,dc=com”}
Set-CsUserReplicatorConfiguration -Identity global -ADDomainNamingContextList  @{Remove=”dc=domain,dc=com”}
Run this to set to null. It clears the Domain Naming Context property
Set-CsUserReplicatorConfiguration -Identity global -ADDomainNamingContextList  $Null

Once you set the proper target for the domain where you want the Front end  service to start, well it will start. I hope this is helpful to some person who  is in need

Advertisements

One thought on “Yet Another Reason the Front end services will not start on Lync 2013 Pool. Child Domains beware of event ID 41029 and 30009.

  1. Alex says:

    Thank you so much! Been fighting for the last few hours and this just saved me from going insane!

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s