asked on

PowerShell: Error provisoning a user for Office Communicator 2007 R2 (Using SET-QADUser)

I'm getting the following error when I attempt to use Quest SET-QADUser to provision a user for OCS 2007 R2 support.

I get that the SET-QADUser is in the example below is modifying the user account attributes directly, but I'm confused as to why the command is failing.

The server I'm pointing to is the Office Communicator 2007 R2 server...

Set-QADUser : A constraint violation occurred.

At \\<network path erased>\NewUserCreationV1_1.ps1:530 char:13

+ set-qaduser <<<< -identity $strSamAccountName -oa @{'msRTCSIP-UserEnabled'=$true;'msRTCSIP-PrimaryHomeServer'='CN=OCServer1,CN=Live Communicator,CN=Member Servers,CN=Servers,DC=humpty,DC=dumpty,DC=com';'msRTCSIP-PrimaryUserAddress'=("sip:" + $strMailAddress );'msRTCSIP-OptionFlags'=256;'msRTCSIP-InternetAccessEnabled'=$true}

+ CategoryInfo : NotSpecified: (:) [Set-QADUser], DirectoryServicesCOMException

+ FullyQualifiedErrorId : System.DirectoryServices.DirectoryServicesCOMException,Quest.Act
iveRoles.ArsPowerShellSnapIn.Powershell.Cmdlets.SetUserCmdlet

Any thoughts?

I don't see any options on Experts Exchange for OCS 2007 (or any OCS / Lync platform for that matter), so I'm placing this in PowerShell and AD.

GB

Chris Dent

They both sit until LCS (Live Communications Server), which is a tad out of date these days.

Anyway, I think this is the problem:

msRTCSIP-PrimaryHomeServer

I believe this should be a reference to the Pool under the Configuration Naming Context, not the server itself in the Domain context.

Chris

Chris Dent

And just for reference, the topic area path is:

OS / Microsoft OS / MS Server OS / Microsoft LCS

Chris

gerhardub

ASKER

You rock... searching just did not find OCS, Lync, or LCS...

A pool eh? Humph... I just not really familiar with LCS to know what to look for in AD... (Assuming I look in AD for the pool? ...or is it the container were the OCS server resides?, etc.)

GB

ASKER CERTIFIED SOLUTION

Chris Dent

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

gerhardub

ASKER

Ok,

So this is what I needed to do to get it to work, and it did work:

set-qaduser -identity $strSamAccountName -oa @{'msRTCSIP-UserEnabled'=$true;'msRTCSIP-primaryHomeServer'='CN=LC Services,CN=Microsoft,CN=<LCS Server>,CN=Pools,CN=RTC Service,CN=Microsoft,CN=System,DC=<company>,DC=com';'msRTCSIP-PrimaryUserAddress'=("sip:" + $strMailAddress );'msRTCSIP-OptionFlags'=256;'msRTCSIP-InternetAccessEnabled'=$true}

What I find confusing is that none of the contructs are visible in AD as OUs. E.g. pools.RTC Service.Microsoft.System... etc.

Using the format above causes everything to work without issue... the only configuration difference I need to fix is that the "Allow Remote Access" attribute is set to $true.

But the code about will provision an OCS account and it does work!

GB

Chris Dent

> What I find confusing is that none of the contructs are visible in AD as OUs. E.g. pools.RTC Service.Microsoft.System... etc.

They are, just not in AD Users and Computers. If you fire up ADSI Edit you can access the Configuration naming context, it's an entirely separate partition of AD.

Chris

gerhardub

ASKER

Roger... thanks!