Stale OCS objects showing up in Lync BPA

Recently I ecountered a problem within the Lync Server 2010, Best Practices Analyzer where it found an error for the old OCS 2007 R2 EDGE server.

Problem

  • Lync Server 2010, Best Practices Analyzer returned an error stating the following
    • Error: A trusted service with the type “MRAS” and the fully qualified domain name (FQDN) “” was found for empty or unmatched Globally Routable User Agent URI (GRUU)
  • Searching this up in ADSI edit showed the object present under Trusted Services and aslo under Global Objects container
    • Full path: CN=RTC Service,CN=Services,CN=Configuration,DC=Contoso,DC=com

  • Notice in the picture the yellow highlight that the GRUUID is in capital letters. It turns out that OCS objects are in capital letters and Lync object are in small letters. This is confirmed by Microsoft
  • It is safe to remove these stale objects and OCS objects are easy to identitfy

Solution

  • Delete the stale objects from TrustedServices and Global Objects, containing references to the old EDGE server
  • When running Test-CsTopology again, wich also returned the error code, we got error messages on EDGE server having a missing GRUUID
  • Did rerun Publish-CsTopology
  • The missing objects got recreated
  • Test-CsTopology went through fine
  • Lync Server 2010, Best Practices Analyzer returned a healthy deployment

Conclusion

  • When uninstalling the OCS 2007 R2 services and serves we forgot to remove the OCS 2007 R2 EDGE from the OCS Configuration
    • These settings can be found under Global Properties->EDGE Servers in the OCS GUI
  • The OCS objects should be uninstalled when doing a proper removing of services and features
  • It is safe to remove stale OCS objects that is in capital letters
  • Publish Topology will recreate objects that are missing

NOTE: When you install OCS or OCS R2, the SIP Domain object in the Global Settings container is created as a Version 4 (legacy) object. Be careful not to accidentally delete your SIP Domain object, as it will appear as a legacy object in ADSI edit.

2 thoughts on “Stale OCS objects showing up in Lync BPA

  1. I am trying to install lync 2010. I had some issues and had to reinstall it fresh. I keep getting these errors when I attempto to publish the topology. Please help!
    Error: A trusted server with the fully qualified domain name (FQDN) “msilync.ad.mosys” was found for unmatched Globally Routable User Agent URI (GRUU).
    ▼ Details
    └ Type: DeploymentException
    └ ▼ Stack Trace
    └ at Microsoft.Rtc.Management.Deployment.Core.CompatTrustedServer.Create()
    at Microsoft.Rtc.Management.Deployment.Roles.Registrar.CreateTrustedServerEntry(RegistrarService registrar, Fqdn hostFqdn)
    at Microsoft.Rtc.Management.Deployment.Roles.Registrar.GlobalActivate(IService service)
    at Microsoft.Rtc.Management.Deployment.Core.Service.GlobalActivate()
    at Microsoft.Rtc.Management.Internal.Utilities.LogWriter.InvokeAndLog(Action action)

    6/3/2011 2:54:18 PM Error

    └ Error: A trusted server with the fully qualified domain name (FQDN) “msilync.ad.mosys” was found for unmatched Globally Routable User Agent URI (GRUU).

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