Shep’s Pondering’s

Dial Plans and Location profiles. These can be the bain of your existence; you try to give them meaningful names so they remind you of what they do. The one thing you need to remember if you are tying enterprise voice to the unified messaging system is that they have to have the same name. Therefore, it must contain no more than 256 alphanumeric characters and must not contain spaces or special characters other than hyphens (-) or periods (.).

The other big gotcha in or environment is that we are in a slightly disjoined named space. This made it necessary to modify the ExchUCUtil.psl file. By default it will go to a Global Catalog server in the domain that the universal groups are defined in. This in our environment is not the same domain that the Exchange servers are deployed in.

To fix this issue I made the change to point the cmdlet to a specific GC by changing these lines.

•  $globalCatalog = $entry.psbase.Properties["rootDomainNamingContext"].Value;
   $entry.psbase.Path = “GC://” + $globalCatalog
   write-host Using Global Catalog: $entry.psbase.Path
  

   Put a # at the beginning of the second line and add a new line to point directly to a GC that exists on your domain1.com.
  

   For example:
  

   $globalCatalog = $entry.psbase.Properties["rootDomainNamingContext"].Value;
  # $entry.psbase.Path = “GC://” + $globalCatalog
  

  $entry.psbase.Path = “GC://myServer01.domain1.com”
  

  write-host Using Global Catalog: $entry.psbase.Path
  

   This assumes you have a GC called myServer01.domain1.com. Save the file, and run Get-UCPool.ps1
  

  Once this was changed the command ran appropriately. Creating the appropriate Access lists needed to connect the servers.
  

  (found this at Technet forums thanks Ray Fong for this answer.)
  

   

  After creating aN Auto attendant to answer the calls, we now have unified Messaging answering Voicemail through Office Communications Server.