OCS 2007 R1 server with Communicator 2007 R2 clients
We have OCS 2007 R1 with Communicator 2007 R1 clients. Everything worked fine until I upgraded us to Exchange 2010, and I now get Integration errors where Communicator can't connect to the Exchange EWS site properly to get OOO and calendar data. I spent a lot of time trying to figure that one out, and even after applying the latest update to Communicator and a few other ideas, no dice. In speaking with Microsoft they told me to see if using Communicator 2007 R2 client would help, and it does now work with the R2 client. So this brings up some questions for me.
1. Is it a good idea to update all my clients to Communicator 2007 R2 while I leave my OCS 2007 server at R1? It seems to work fine for me, but I thought I'd ask.
2. If #1 is okay, what is my best option for upgrading all my end user clients from Communicator 2007 R1 to R2?
1. Is it a good idea to update all my clients to Communicator 2007 R2 while I leave my OCS 2007 server at R1? It seems to work fine for me, but I thought I'd ask.
2. If #1 is okay, what is my best option for upgrading all my end user clients from Communicator 2007 R1 to R2?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You have 2 main options...
1. Export user info using DBIMPEXP, deactivate OCS 2007, install OCS 2007 R2, enable users, then run DBIMPEXP /IMPORT to import all of the user contacts.
2. (preferred) Setup OCS 2007 R2 next to the R1, rt click, move users over... then update the clients.
1. Export user info using DBIMPEXP, deactivate OCS 2007, install OCS 2007 R2, enable users, then run DBIMPEXP /IMPORT to import all of the user contacts.
2. (preferred) Setup OCS 2007 R2 next to the R1, rt click, move users over... then update the clients.
ASKER
I was actually referring to just updating the Communicator clients from R1 to R2 and leaving the OCS server at R1 for the time being.
ASKER
I'm not familiar with installing packages via group policy, but I'd like to try to install Communicator that way. The things I want to accomplish are:
1. Uninstall the current Office Communicator 2007 R1 client
2. Install the Office Communicator 2007 R2 client
3. Install the add-ons for Live Meeting
3. Install the Update for Office Communicator 2007 R2 client
Can anyone suggest the best way of going about this?
1. Uninstall the current Office Communicator 2007 R1 client
2. Install the Office Communicator 2007 R2 client
3. Install the add-ons for Live Meeting
3. Install the Update for Office Communicator 2007 R2 client
Can anyone suggest the best way of going about this?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hello.
We are moving from Exchange 2007 to Exchange 2010. We have OCS 2007 R1 Server and we are running Office Communicator R2 clients. How did this work out?
We are moving from Exchange 2007 to Exchange 2010. We have OCS 2007 R1 Server and we are running Office Communicator R2 clients. How did this work out?
ASKER
Looks like you already are on Communicator R2 so you should be fine. We had to upgrade our clients to R2 in order to get rid of the integration error once we moved to Exchange 2010. We were on Exchange 2003 before though.
Thank you for the information. We want to hang on to the OCS R1 server for the time being.
ASKER