Archive for September, 2010

OCS 2007 R2 error: Trusted entry breaks FQDN, Port or Version uniqueness constraint.

September 25, 2010 Leave a comment

In my test environment I was my messing around with multiple OCS servers. While I was finishing the last steps of my Edge server installation on the Front-end were you need to configure the external access for users I ran into an unusual error:

Failure [0xC3F7584A] Trusted entry breaks FQDN, Port or Version uniqueness constraint.

At first sight this seems to be an DNS issue. First I verified everything in DNS but I could not found any misconfiguration, also on the Internet I could not find any info when searching on error “0xC3F7584A”. I spent some time searching through AD into the schema settings and there I discovered that my old pool name was still available. In my test environment was reinstalling everything but I didn’t follow the recommend uninstallation steps from Microsoft. I did not unprep my previous pool from the AD schema extensions. Normally you need to unprep your pool via the lcscmd command:

lcscmd.exe /Domain:poolname /Action:DomainUnPrep
lcscmd.exe /Forest:poolname /Action:ForestUnprep

I investigated via ADSIEDIT my AD schema. The poolname is normally located under: CN=Pools,CN=RTC Service,CN=Microsoft,CN=System.DC=test,DC=local
But my previous pool was already not present anymore, when I looked further into the other folders there were still multiple objects presents with attributes of the old pool name. So I played cowboy on my test environment and deleted all the old schema objects with references to the old pool name.

I deleted all the old objects in the underneath schema folders:

CN=Global Settings,CN=RTC Service,CN=Microsoft,CN=System.DC=test,DC=local
CN=MCU Factories,CN=RTC Service,CN=Microsoft,CN=System.DC=test,DC=local
CN=Trusted MCUs,CN=RTC Service,CN=Microsoft,CN=System.DC=test,DC=local
CN=Trusted Services,CN=RTC Service,CN=Microsoft,CN=System.DC=test,DC=local
CN=Trusted WebComponentsServers,CN=RTC Service,CN=Microsoft,CN=System.DC=test,DC=local

After these actions went the installation fine without the “Trusted entry breaks FQDN, Port or Version uniqueness constraint” error. It’s good to know that error 0xC3F7584A is related to an AD schema issue and that you always need to follow the Microsoft directions 😉

Categories: OCS 2007 / Lync 2010

OCS 2007 R2 error: “Cannot get presence for this contact”

September 6, 2010 Leave a comment

After I enabled the first users for OCS were the OCS users not able to view the presence information of other users nor able to chat with other contacts. After some research I found that this was an issue with the Address Book.  The Address Book only updates once within 24 hours, so if it has not ran since you have enabled the users, it can create this type of issue.

The solution is to initiate a new address book on the OCS frond end server and delete the local address book at the client side:

  • Start CMD and go to C:\Program Files\Microsoft Office Communications Server 2007 R2\Server\Core
  • Execute: abserver -syncnow
  • Delete the local address book “GalContacts.db” at the client side in:  C:\Documents and Settings\username\Local Settings\Application Data\Microsoft\Communicator\

Categories: OCS 2007 / Lync 2010

OCS 2007 R2 install Error: “The Windows Media Format Runtime is required”

September 5, 2010 3 comments

During the installation I forgot to install one of the required prerequisites and I received the following error:

“Error: The Windows Media Format Runtime is required in order to install this component. Installing the Windows Media Format Runtime may require a system restart to complete the installation. Click OK to continue with the installation.”

The solution to solve this problem is install the “Desktop Experience” Feature:

  • Start PowerShell as Administrator
  • Execute: Import-Module ServerManager
  • Execute: Add-WindowsFeature Desktop-Experience
  • Reboot the server

Why is this component necessary?

Conferencing Attendant and Conferencing Announcement Service use the Windows Media audio (WMA) file format to play prompts, music, and announcements. The WMA file format requires the Windows Media Format Runtime to run properly.

Found on Technet:

Categories: OCS 2007 / Lync 2010

NTFS Volume Mount Points & List folder permissions

September 4, 2010 2 comments

Last week I was troubleshooting NTFS permissions on mounted volumes.  Users were able to browse on a non-mounted directory but not on a  mounted Directory with the same permissions. So I was facing an issue with list folder permission on Mounted volumes.

Fore example:
Users1 is the non-mounted volume and users2 is the mounted volume.

With the command “mountvol” you can quickly view which volumes are mounted to folders like the example below.

Command mountvol example:

Permission overview Volumes & Folders:

Like you can see are all the permissions on the mounted volume and the non-mounted are volume the same! So why was a normal user not able to browse the mounted volumes? I figured out that the “list folder” was working on the mounted volumes when I selected “read attributes” on the volume itself. But why was this option required on mounted volumes?

I installed the tool “tweak file” to view all the folder Attributes and yes the “mounted folder users” had an special attribute REPARSE POINT which holds the mount point. Now I can conclude that “Read Attributes” is always required on mounted volumes to list the the contents in the “Mounted volume link folder”.

Attributes of a Normal Folder:

Attributes of a Mounted Volume Folder:

What happens with the permissions if you create a new volume? For example you create a new “volume mount point” Users3 under root volume E:/.

  1. Create an empty folder Users3 under the root folder.
  2. Initialize disk and format the volume in Disk Management.
  3. Mount the new Volume to the empty folder Users3.

In step one will the empty folder inherit permissions from the Root volume E:/ In step two will the volume receive the standard permissions from the OS like you create another volume and assign a drive letter. So the “mounted volume” itself will not receive the permissions from the root volume E:/. If we change permissions on the root volume E:/ it will not propagate across the underlying volumes but it will propagate to the underlying “Mounted volume link folders” like Users3.

It’s interesting to know that the permission “read attributes” is required on mounted volumes to list the folder contents. I could not find any info about this issue on the Internet. I would like to share my experience with permissions & Mounted volumes. Permissions on Root volume, mounted volume, mounted volume link folders could get confusing when you need to troubleshoot the permissions.

Read more…