Inside OCS » LCS http://blog.insideocs.com Microsoft Office Communications Server - Tips, Tricks, and Insight Thu, 26 Jan 2012 20:13:04 +0000 http://wordpress.org/?v=2.8.3 en hourly 1 Provisioning OCS Users (and the AD msRTCSIP-OptionFlags Attribute) http://blog.insideocs.com/2008/12/19/provisioning-ocs-users-and-the-ad-msrtcsip-optionflags-attribute/ http://blog.insideocs.com/2008/12/19/provisioning-ocs-users-and-the-ad-msrtcsip-optionflags-attribute/#comments Fri, 19 Dec 2008 22:13:31 +0000 Curtis Johnstone http://blog.insideocs.com/?p=176 If you are deploying OCS 2007 or 2077 R2, and especially if you are migrating from LCS 2005, you will want to be careful about setting the OCS AD attribute msRTCSIP-OptionFlags.  This is an important AD attribute which is typically set by manually enabling/disabling specific user features in the OCS Administrative Console, or programmatically through [...]]]> If you are deploying OCS 2007 or 2077 R2, and especially if you are migrating from LCS 2005, you will want to be careful about setting the OCS AD attribute msRTCSIP-OptionFlags.  This is an important AD attribute which is typically set by manually enabling/disabling specific user features in the OCS Administrative Console, or programmatically through scripting (e.g. VBScript).

The underlying value is an integer bit-mask which controls whether the user is enabled or disabled for several specific features.  If you have an existing automated provisioning process (i.e. script) that sets this AD attribute, ensure that it is not inadvertently clobbering any OCS features that you are setting through the OCS Administrative Console. This can be an issue if there is an existing automated LCS 2005 provisioning script that is still being applied after users have been migrated to OCS 2007.

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 just add the value of the bit representing the feature you give to the user to the existing msRTCSIP-OptionFlags value. You can do this through several command line options outlined in my blog post “Provisioning OCS From the Command Line“).

The msRTCSIP-OptionFlags AD attribute is documented here: http://technet.microsoft.com/en-us/library/bb663647.aspx . If the user was migrated to OCS 2007 (or R2) from LCS 2005, the values 0 and 256 have significance. If bit 256 is set, the user is enabled for ‘Enhanced Presence’, and they will be able to log into OCS with Communicator 2007 or Communicator 2007 R2. After the first time they login with the newer client, they will NOT be able to login with the legacy Communicator 2005 client, so be careful to time the setting of Enhanced Presence with your client deployment.

Here are the values, what they mean, and where you can find the corresponding feature in the OCS Administrative Console.

Value

Setting / Meaning

OCS Admin Console Feature

0

Enabled for LCS (or Communicator 2005)

User Properties | Enable for Office Communications Server

1

Enabled for LCS with PIC

User Properties | Additional Properties (Configure…) | Enable public IM

16

Remote Call Control (RCC) Enabled

User Properties | Additional Properties (Configure…) | Enable Remote Call Control

64

AllowOrganizeMeeting

WithAnonymousParticipants

User Properties | Communications | Meetings | Allow anonymous participants

128

UCEnabled

User Properties | Additional Properties (Configure…) | Enable Enterprise Voice

256

EnabledForEnhancedPresence

User Properties | Enable Enhanced Presence

257

Enabled for OCS and PIC

User Properties | Enable Enhanced Presence

512

RemoteCallControlDualMode

User Properties | Additional Properties (Configure…) | Enable Enterprise Voice & PBX integration

1024

Enabled auto-attendant

R2 placeholder?
]]> http://blog.insideocs.com/2008/12/19/provisioning-ocs-users-and-the-ad-msrtcsip-optionflags-attribute/feed/ 4 Office Communicator Hotfixes http://blog.insideocs.com/2008/11/14/office-communicator-hotfixes/ http://blog.insideocs.com/2008/11/14/office-communicator-hotfixes/#comments Fri, 14 Nov 2008 16:54:25 +0000 Curtis Johnstone http://insideocs.wordpress.com/?p=145 Microsoft Office Communicator hotfixes are not part of Windows Update, so it is important to find and deploy them through other means.

If you are upgrading to OCS 2005 from LCS 2005, and will have Office Communicator 2005 and 2007 clients coexisting, you should deploy Microsoft Office Communicator 2005 Hotfix KB 945573 (http://support.microsoft.com/?kbid=942897). In addition to [...]]]> Microsoft Office Communicator hotfixes are not part of Windows Update, so it is important to find and deploy them through other means.

If you are upgrading to OCS 2005 from LCS 2005, and will have Office Communicator 2005 and 2007 clients coexisting, you should deploy Microsoft Office Communicator 2005 Hotfix KB 945573 (http://support.microsoft.com/?kbid=942897). In addition to addressing some OC 2005 specific functionality, it addresses several communication issues between OC 2007 and 2005 clients. See the knowledge base article for details.

Office Communicator 2007 also has a recent hotfix (http://support.microsoft.com/?kbid=957707) which addresses several issues and provides a rollup of previously released hotfixes.

]]> http://blog.insideocs.com/2008/11/14/office-communicator-hotfixes/feed/ 0 Windows Messenger 5.1 Support when Upgrading LCS 2005 http://blog.insideocs.com/2008/09/15/windows-messenger-51-support-when-upgrading-lcs-2005/ http://blog.insideocs.com/2008/09/15/windows-messenger-51-support-when-upgrading-lcs-2005/#comments Mon, 15 Sep 2008 18:51:43 +0000 Curtis Johnstone http://ocsbuzz.wordpress.com/?p=78 A quick post for anyone upgrading from LCS 2005 to OCS 2007. The first step in upgrading your LCS 2005 infrastructure to OCS 2007 is to replace the perimeter (e.g. replace your LCS Access Proxies with OCS 2007 Edge Access Servers). This will result in a mixed environment: OCS 2007 on the Edge and LCS [...]]]> A quick post for anyone upgrading from LCS 2005 to OCS 2007. The first step in upgrading your LCS 2005 infrastructure to OCS 2007 is to replace the perimeter (e.g. replace your LCS Access Proxies with OCS 2007 Edge Access Servers). This will result in a mixed environment: OCS 2007 on the Edge and LCS 2005 SP1 internally.

In this situation, Windows Messenger 5.1 and Microsoft Office Communicator Mobile 1.0 clients will not be able to log on to LCS 2005 through the OCS 2007 Edge.

For more details, see Microsoft Knowledge Base Article 94957 (http://support.microsoft.com/kb/949574/en-us).

]]> http://blog.insideocs.com/2008/09/15/windows-messenger-51-support-when-upgrading-lcs-2005/feed/ 0