• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1636
  • Last Modified:

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
0
gerhardub
Asked:
gerhardub
  • 4
  • 3
1 Solution
 
Chris DentPowerShell DeveloperCommented:

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
0
 
Chris DentPowerShell DeveloperCommented:

And just for reference, the topic area path is:

OS / Microsoft OS / MS Server OS / Microsoft LCS

Chris
0
 
gerhardubAuthor Commented:
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
0
Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

 
Chris DentPowerShell DeveloperCommented:

Can you copy it from someone who is already activated on the system?

I forget exactly what it looks like for OCS (upgraded ours to Lync), but it will be named after the server for Standard Edition. And it'll be under this if I remember correctly:

CN=Pools,CN=RTC Service,CN=Services,CN=Configuration,DC=domain,DC=com

If not that, you might check that proxyAddresses already contains the SIP address, not sure if it validates that at all, or if it just figures itself out.

Upgrade to Lync, Enable-CsUser is easier :)

Chris
0
 
gerhardubAuthor Commented:
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
1
 
Chris DentPowerShell DeveloperCommented:

> 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
0
 
gerhardubAuthor Commented:
Roger... thanks!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improved Protection from Phishing Attacks

WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now