I have a single pool that consists of a single Lync 2010 Enterprise server.  I recently added a new sip domain.  After configuring the additional meet url for this new domain, i attempted to run local setup and got the error below:

=====

The given key was not present in the dictionary.
   at System.ThrowHelper.ThrowKeyNotFoundException()
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.Rtc.Management.Deployment.Core.MsiFeatureFactory.GetFeature(String featureName)
   at Microsoft.Rtc.Internal.Tools.Bootstrapper.BootstrapperTask.RemoveUnusedFeatures(Boolean scorch)
   at Microsoft.Rtc.Management.Internal.Utilities.LogWriter.InvokeAndLog[T](Action`1 action, T arg)
   at Microsoft.Rtc.Internal.Tools.Bootstrapper.BootstrapperTask.Action()
   at Microsoft.Rtc.Management.Internal.Utilities.LogWriter.InvokeAndLog(Action action)
   at Microsoft.Rtc.Management.Internal.Utilities.LoggableAction.InvokeAction()
   at Microsoft.Rtc.Internal.Tools.Bootstrapper.Bootstrapper.Action()
   at Microsoft.Rtc.Management.Internal.Utilities.LogWriter.InvokeAndLog(Action action)
   at Microsoft.Rtc.Management.Internal.Utilities.LoggableAction.InvokeAction()
   at Microsoft.Rtc.Internal.Tools.Deploy.BootstrapCmdInfo.RunBootstrapper(Object obj)
=====

I did re-key the SSL certificate so it has the additional SAN for the new sip domain.

Hi Slotted Spoon,

Did you follow these steps ?

1. Add the new SIP domain(s) to the Topology and publish the Topology.

2. Create DNS records for the new simple URLs, both internal and external.

     meet.domain.com (external and internal)

     sip.domain.com (external and internal)

     SRV _sipinternaltls._tcp.domain.com 5061-> sip.domain.com (internal)

     SRV _sip._tls.domain.com 443-> sip.domain.com (external)

     SRV _sipfederationtls._tcp.domain.com 5061-> sip.domain.com (external)

3. Request new certificates for the following:

     Front End Server Certificate (internal)

     Edge Server Certificate (external)

     Reverse Proxy Certificate (external)

4. Run Enable-CSComputer on each pool member and director Server. This will re-configure IIS to accept the new simple URLs.

Best regards,

Eric

Any other errors you can post? I wouldn't think certs would stop this process.

Topology all up to date?