Archive

Archive for the ‘OCS 2007 R2’ Category

Powershell Command to find component version for Lync and OCS

August 10, 2011 Leave a comment

 

Came via my Twitter feed;

 

http://blogs.technet.com/b/premal/archive/2011/06/07/powershell-command-to-find-the-version-of-lync-server-installed-components.aspx

 

Handy Smile

Advertisements

Error Activating/Deactivating OCS 2007 R2 Server after rename

March 18, 2011 Leave a comment

 

Accidentally activated an OCS Edge recently, and then renamed it.

 

Whoops.

 

Server was marked as un-activated, and when I attempted activation I got the following;

 

ERROR (0xC3EC794B): Specified role doesn’t match the installed product ID.

 

Answer was simple – rename the machine back to its prior name, and deactivate the Edge service and uninstall the binaries.

Unable to send IM to OCS 2007 R2 user

February 22, 2011 3 comments

 

Recently had a client who were unable to send IM’s after a LCS to OCS 2007 R2 upgrade.

 

users got “Joe Bloggs could not be reached and this message was not delivered” when starting a new IM conversation with certain users, although if that user started a conversation with them they were able to converse.

 

After installing the 2007 Resource kit and running a trace on “SIPStack” I saw the following error message;

 

"The application specified an invalid static forwarding url"

 

A Google (oh our trusty friend) showed up the following post;

 

http://theucguy.wordpress.com/2009/03/23/a-sip-request-made-by-communicator-failed-in-an-unexpected-manner-status-code-80ef01f4/

 

In short this was right, only the “other” value was indeed a blank value. After I removed this (and waited for AD to replicate to the DC that OCS was looking at), IM’s worked.

 

Client has asked me to write a script to check AD users for this, so if I do I will post up here 🙂

 

UPDATE:

 

After a user comment on this I decided to investigate more via ADSI edit.

If I add a “blank” (or space) value to the Other IP phone to a user via ADSI edit, it looks like this;

 

image

This doesn’t look too bad – however if I expand the property I can select the “first line” like such;

 

image

And sure enough, in the AD Users and Computers counterpart I can do the  same;

 

image

Removing this value (either via ADSI edit or AD UC) means I can no longer select this value whatsoever.

It also leaves the ADSI value as <not set> as can be seen below;

 

image

 

In short, if you are having this problem – make sure that the attribute is listed as <not set> in ADSI edit – anything other than this and it should be cleared down 🙂

 

Hope that helps! 🙂

Error when upgrading the Schema for OCS 2007 R2 when LCS is deployed

February 9, 2011 Leave a comment

Got this error when going to run the Schema upgrade for OCS 2007 R2 in an LCS environment;

“You are about to upgrade a forest that is storing its Office Communications Server data in the system container in the root domain.  It is recommended that the data be moved to the configuration partition before upgrading the schema to ensure that network connectivity issues to the root domain does not affect system performance.  Once the schema has been upgraded to R2 it will not be possible to move the data.  Please see the deployment documentation for additional details.”

image

Use the tool/instructions found here;

 

http://technet.microsoft.com/en-us/library/dd441370(office.13).aspx

 

You can download the tool referenced from;

 

http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyID=23236784-508e-44c9-809d-30ff245928d8&displaylang=en

 

NOTE: Lync needs to be fully shut down on ALL servers before proceeding with this

OCS 2007 R2 Bug

September 10, 2010 Leave a comment

There is a known bug in OCS 2007 R2 (and I presume 2007) whilst using the Remote Screen feature.

If you try to run an elevated process under Vista/Windows 7 and have UAC enabled the Accept box for UAC (the Yes/No prompt) is ran in the “Secure Desktop” and therefore inaccessible to the user.

This is also the case if it prompts for a username/password.

From what I can see the only way around this is to DISABLE UAC – not recommended obviously.

Categories: Microsoft, OCS 2007 R2