Answered by:
How do I manage Office Communications with my desktop

Question
-
With exchange 2003, all we needed was the adminpack.msi and the exchange 2003 management tools. Now things have changed. We're using exchange 2007 as part of a unified messaging solution which involves OCS. I can remote to the servers to create a new user, enable unified messaging... I eventually end up on the OCS server to make some settings in the Active Directory Users and Computers console on the communications tab (strange how this tab only shows up here).
I would like to be able to do all this on a workstation using an MMC console (runas /user
omain\admin_account) and not have to remote into any servers.
1. I'll still need the 2003 server adminpack.msi from the server disk. 2. I'll need to download and install the 32 bit version of the exchange 2007 management tools (reference http://support.microsoft.com/kb/555841). 3. What goes here? Are there any other management tools/packages required (i.e. OCS) and where are they located?
Thursday, September 4, 2008 9:56 PM
Answers
-
If you want the Communications Server tab to appear in Active Directory Users and Computers you should run the OCS Setup Wizard on that box and only install the Management Tools, similar to the way you would deploy the Exchange 2007 Manangement Tools.
Thursday, September 4, 2008 10:03 PMModerator
All replies
-
If you want the Communications Server tab to appear in Active Directory Users and Computers you should run the OCS Setup Wizard on that box and only install the Management Tools, similar to the way you would deploy the Exchange 2007 Manangement Tools.
Thursday, September 4, 2008 10:03 PMModerator -
Thursday, September 4, 2008 11:05 PM
-
Is it possible to add the Communications Tab to ADUC without installing the entire OCS admin pack ? I want to delegate the user administration but I don't want the LCSCMD tool deployed to these users.
Friday, November 7, 2008 2:43 PM -
It might be possible to extract just the required exe/dll files and register them on the computers manually, but it's not a supported installation. It's probably easier to install the Administration Tools and then simply delete the executable files that you don't want left on the workstations.
Friday, November 7, 2008 2:55 PMModerator -
How does one manage OCS2007 R2 (which is installed on 64bit Win2008 server) on our Win2003 DC's and my XP/Vista (x32) desktops?
The problem is that OCS2007 R2's CD is 64 bit only. Our DC's with Active Directory Users and Computers is 32 bit. We have the old "Communications" tab in ADUC, but get this error message, ""This user is enabled on a previous version of the product, and cannot be administered with this version of the Office Communications Server User Property Page. Please use the appropriate version of LCS MMC to administer the user. You may use the Office Communications Server Move User Wizard to move LCS 2005 SP1 users to Office Communications Server."
If I go to install the Console/Admin Tools I cannot because it's 64 bit. How do we manage OCS now, not on the OCS server?
thanks...
Peter A. Berger Jr.Thursday, June 11, 2009 1:27 PM -
nevermind -- I found it. Took a while of digging (it shouldn't be that hard):
0. Remove the "Microsoft Office Communications Server 2007 Administration Tools" (your OCS 2007 R1 Admin Tools) from the server.
Follow Microsoft's own directions found here: http://technet.microsoft.com/en-us/library/dd441247(office.13).aspx
To install the Office Communications Server 2007 R2 administrative tools on a computer running a 32-bit version of the operating system-
On the computer on which you want to install the Office Communications Server 2007 R2 administrative tools, log on using an account that is a member of the Administrators group (or an account with equivalent privileges) and the Domain Admins group.
-
On the Microsoft Office Communications Server CD or a network share containing the installation files, browse to the \support\i86 folder.
-
Run vcredist_x86.exe to start the Microsoft Visual C++ 2008 Redistributable Setup wizard. Take the appropriate action on each page of the wizard to complete the installation.
-
Run SQLServer2005_BC.msi to start the Microsoft SQL Server 2005 Backward Compatibility Setup Wizard. Take the appropriate action on each page of the wizard, including using the default for Feature Selection , to complete the installation.
-
Run sqlncli.msi to start the wizard for Microsoft SQL Server Native Client. Take the appropriate action on each page of the wizard, including using the default for Feature Selection, to complete the installation.
-
Run OCSCore.msi to start the Office Communications Server 2007 R2 Core Components Setup Wizard. Take the appropriate action on each page of the wizard to complete the installation.
-
Run AdminTools.msi to start the Office Communications Server 2007 R2 Administrative Tools Setup Wizard. Take the appropriate action on each page of the wizard to complete the installation.
Note:
Installing or removing the administrative tools on a computer running Windows Vista on which the Security Center service is running with the startup mode set to Automatic may result in the following error message: "Error stopping service since one or more dependent services failed to stop. Please try again." If you close the error message, the process should complete successfully.
Peter A. Berger Jr.Thursday, June 11, 2009 2:56 PM -
-
FYI, instructions are good for Vista desktop only. Never found a solution for XP. When you get as far as the OCSCore.msi install, here is the error message you get:
Setup cannot continue because the operating system on the computer is not supported. Please install Office Communication Server 2007 R2, Core Components on a computer that has one of the following operating systems: Windows Server 2008, Windows Vista SP1, or Windows Server 2003 SP3, The latest service packs for your operatin system are also recommended.
Tuesday, September 1, 2009 3:51 PM -
yeah..I tried it on my Win7 desktop and it fails too. Granted it's the RC version...still waiting for my RTM copy...but really...it's built on Vista codebase...tsk...tsk..
Peter A. Berger Jr.Tuesday, September 1, 2009 5:05 PM -
I'm having the same issue, I have 2 Windows XP Pro workstations, and a Windows 7 client workstation, none of which allow me to manage the OCS server. The issue is of particular concern from an accessibility perspective because I am blind, and use the Jaws screen reader
http://hj.com/jaws
which does not work well or at all with RDP sessions particularly if the machine is a VM.
It sounds like I will have to have yet another computer built either with Vista or Windows Server 2003/2008 solely to manage OCS.
I am surprised at these developments because on a 32 bit machine I am able to manage both AD and Exchange 2007 using 32 bit tools.Monday, September 28, 2009 3:42 PM