Monthly Archives: April 2010
During a recent group chat server installation, the wizard failed with a very cryptic error message after specifying the Lookup Service account. We also got the same message for the Channel Account configuration.
The error message looked like this:
A Google search turned up nothing, and a quick query on the formicary hosted UC Community Group Chat Channel didn’t have any immediate answers. Bryan Childs was able to point me in the right direction looking for the log on as service permissions on the box.
The customer in question had PCI requirements where service accounts are denied the right to logon interactively, if not they had to change the passwords on those accounts during their regular intervals for user accounts. This setting was the culprit. Once removing the policy denying the service account interactive login rights we were able to proceed with installation. I did notice that during the installation it grants those accounts the log on as service rights on the local box, not sure how related these settings are.
Anyways, seems the group chat errors are pretty generic, this may not even be strictly for this issue, however wanted to get the information out there.
New batch of updates available for the server and client side for OCS 2007 R2.
So far so good, I will update this blog post over the weekend after I patch all of our servers.
Links below for Server and for Client. Biggest fix seems to be the annoyance with the CWA Dial In Conferencing Page and PIN number issues:
978373 The Dial-in Conferencing Settings page in Office Communicator Web Access 2007 R2 prompts you to enter a PIN that is at least 5 digits even if the PIN length policy is set to use a PIN that is less than 5 digits
Server Side Updates: http://support.microsoft.com/?kbid=968802
Communicator Client: http://support.microsoft.com/kb/978564
Just an update from running the updates over this past weekend. Everything seems to work just fine, your front end server may not prompt for a reboot, but I would advise rebooting. A couple people have reported some issues with group expansion. My fix was to cycle the application pool in IIS,however a reboot is suggested.