Comments on: Provisioning OCS From the Command Line

By: Enable existing email users for Communications Server « Заметки ИТ инженера

Enable existing email users for Communications Server « Заметки ИТ инженера — Thu, 13 Oct 2011 09:48:49 +0000

[...] – Provisioning OCS From the Command Line – Enable existing user for Communications Server – Provisioning OCS Users (and the AD [...]

By: Yps

Yps — Fri, 17 Dec 2010 15:32:01 +0000

I got ‘Get-WmiObject : Invalid class’ when I run it from Exchange Shell ? Anyone got a clue what´s wrong?

By: david

david — Mon, 17 May 2010 14:09:45 +0000

Hi Curtis,

I am a bit confused to what is generally referred to as ENABLING and PROVISIONING. Can a user be configured to use OCS by ONLY setting their AD attributes directly? Or do their AD attributes need to bet set, AND the WMI provider be used to provision them?

To understand this better I’m trying to see the link between the WMI MSFT_SIPESUserSetting class properties, and the AD attributes of the user. The only relation I see is that some of the MSFT_SIPESUserSetting class properties are synced to the msRTCSIP-OptionFlags AD Attribute.

My goal is basically to enable/provision OCS for users through C# code – which is done pretty easily by simple settings a few AD attributes. But the confusion is whether this is possible without using a WMI provider.

Thanks so much for your help, the your posts have been really useful.

David

By: AD Properties Required to Enable a User for OCS « Inside OCS

AD Properties Required to Enable a User for OCS « Inside OCS — Mon, 03 May 2010 21:03:30 +0000

[...] Properties Required to Enable a User for OCS As a follow-on to my popular post “Provisioning OCS From the Command Line”, several readers noted that they were in the situation where the OCS user had not been created [...]

By: Curtis Johnstone

Curtis Johnstone — Fri, 09 Apr 2010 20:06:23 +0000

Hi Saravanan,

The associated user AD object needs to be enabled for OCS before you can programmatically provision the user for OCS using the WMI provider (and WMI classes like MSFT_SIPESUSERSETTING). You can enable an AD user object for OCS by setting values for three AD attributes/properties: msRTCSIP-UserEnabled, msRTCSIP-PrimaryUserAddress, and msRTCSIP-PrimaryHomeServer. For the user to be able to logon with Communicator 2007 R2 with Enhanced Presence, you will also need to set msRTCSIP-OptionFlags to a value of 256 (or higher).

Many OCS user features can be provisioned in AD, these 3 properties are just the minimum to enable the OCS users.

To set those AD attributes, you have several choices: scripting (e.g. VBScript) if you want to write an automated process, or several of the AD tools that I highlight in Option #4 if you want to do a batch enable.

I will follow-up with a blog posting concerning this (several people are in this scenario).

Hope that helps,
Curtis

By: Saravanan

Saravanan — Tue, 06 Apr 2010 03:09:27 +0000

Hi,

Thanks for the post.

You have mentioned MSFT_SIPESUSERSETTING does not retrieve objects which were never been provisioned to OCS or LCS. Thats exactly the situation for me, where I need to retrieve user objects who are created new in the system (through some other automation) and enable them for using OCS. Since this WMI class does not return any users, am not able to provision OCS for them either.

Is there any prior step I need to perform?

Thanks,
Saravanan

By: Provisioning OCS Users (and the AD msRTCSIP-OptionFlags Attribute) « Inside OCS

Tue, 06 Oct 2009 20:11:41 +0000

[...] Because this is a bit-mask, becareful not to clobber any existing features. For example, if you are setting Enhanced Presence (bit 256), and want to preserve the ability for the user to have Public IM functionality, be sure to set the value to 257 (i.e. add a “1″ to set the enabled for PIC bit). A good way to approach this is to add the value of the bit representing the feature you want to add to the existing value. You can do this through several command line options outlined in my blog post “Provisioning OCS From the Command Line“). [...]