Log in



Tags » ‘OCS’

OCS/LCS and Windows 2008 R2 Active Directory

April 6th, 2010 by Scott

If you’re thinking about upgrading your existing Active Directory Forest and Domain to Windows 2008 R2 you need to consider what applications you currently have running.  There have been a number of issues relating to deploying Windows 2008 R2 Domains Controllers. 

I was looking over on MS Support and noticed that OCS 2007, OCS 2007 R2 and LCS are now supported on Windows 2008 R2 Domains.  The trick of it though is if you already have OCS deployed you will need to rerun the forest prep utility.  For some reason when deploying the R2 schema and promoting to a DC the OCS schema information gets removed.

How odd but at least the fix is simple.  So in the event you have OCS or LCS deployed and decide to move to Windows 2008 R2 AD keep in mind that you will need to rerun the the forestprep for OCS or use the Lcscmd command “Lcscmd.exe /forest /action:ForestPrep”  which will work for LCS or OCS.

For more information see the following articles: 

Office Communications Server 2007 R2, OCS 2007 or LCS 2005 does not work correctly after you upgrade to Windows Server 2008 R2
and
Supportability is available for Office Communications Server 2007 R2 member server role on a Windows Server 2008 R2 operating system

 

Microsoft Office Communicator cannot Sync Address book

October 16th, 2009 by Scott

I recently deployed OCS 2007 R2 for a client that involved a front end server and a edge sync server. A few days after deploying OCS we noticed that MOC had an error “Cannot synchronize with the corporate address book. This may be because the proxy server settings in your web browser does not allow access to the address book. If the problem persists, contact your system administration” Upon doing some investigation I noticed an error in the event logs, Event ID: 5021 Source WAS. The error was “The identity of application pool LSGroupExpAppPool is invalid. The user name or password that is specified for the identity may be incorrect, or the user may not have batch logon rights. If the identity is not corrected, the application pool will be disabled when the application pool receives its first request. If batch logon rights are causing the problem, the identity in the IIS configuration store must be changed after rights have been granted before Windows Process Activation Service (WAS) can retry the logon. If the identity remains invalid after the first request for the application pool is processed, the application pool will be disabled. The data field contains the error number.” Upon checking the batch logon rights under Security Settings> Local Policies>User Right Assignment I noticed that the service account was not permitted. This was a result of Group Policy over-writing the local security policy and in essence disabling the application pool.

The fix? We had to add the service account to the GPO, did a gpupdate /force and then restarted MOC. All is well again!

KB974571 Breaks Office Communication Server!

October 15th, 2009 by Scott

This morning when I went to log into Microsoft Office Communicator from a client I failed to sign in.  Given that this worked yesterday without any problem I couldn’t figure out what was going on so I pinged our local admin to let him know OCS was not working.  Long story short it appears that KB974571, which our Front End and Edge Server Downloaded last night kills OCS.  Our System Admin had to remove the update and everything went back to working…..

So, be wary of the KB974571.  More info can be found here: http://support.microsoft.com/kb/974571 and it looks like MS is already aware of the situation. 

 

 

CUCI-MOC

October 14th, 2009 by Scott

Recently I have been working on getting an integration of Cisco UC Integration for Microsoft Office Communicator. Well, it turns out there is an issue with Windows 7 and the version of CUCI we are using with is 7.1.2. When trying to dial a number I am receiving an error that states “Phone Error.  Could not place call because you have no audio device or sound card.  This error is being generated directly from CUCI. Cisco is aware of the problem and plans to have it resolved in CUCI version 8.0 which is due out some time in Q4 or Q1.