Archive

Posts Tagged ‘Office Communications Server’

Office Communications Server update complete

December 20th, 2010 No comments

I realized it’s been a while since I posted anything about OCS here, but it’s (mostly) done. Everyone was moved to the new environment and the old servers were decomissioned.

I’m now working on a Communicator Web Access server and desktop sharing environment. I’ve got it working internally, and, using this excellent article here (and this one), I have it set up to work externally as well. Unfortunately I have to wait for the firewall to get updated before it will work on the outside.

I also have it in the hands of our desktop people to update everyone’s Communicator client to v3.5.6907.206 (Communicator R2 with the July 2010 update), then I also need to go around and patch all the servers (FE, Edge, Archive/Monitor, SQL and CWA) with the November 2010 update.

In the mean time I’m also starting to plan out the MS Lync 2010 environment, probably for a whole, new domain.

Office Communications Server 2007 R2 almost there

August 30th, 2010 No comments

I’ve got a full OCS 2007 R2 environment built, just waiting for the big switch this weekend to the new environment. It’s been quite a learning experience.

Setting up a new OCS pool is not exactly a double-click-next-next-finish type of install. Lots of planning has to go in to it, even for an updated environment where we’ve already done all the legwork in DNS, certificates and firewalls. This was also a transition to a 64-bit OS environment from a 32-bit one, and trying to preserve all the connectivity at the same time.

I learned, for instance, that you can do all the configuration-moving and schema updates, and bring up a new front-end server for a new pool in the same domain as your old OCS pool, and everyone is none the wiser. No impact until you actually start migrating people.

However, if you bring up a new Edge server, and configure that in your new pool, it becomes an Edge server not only for your old environment, but for your new one as well. I had to unconfigure that real quick. The server is still up and running, but I’ll need to manually add it to the new pool and remove the old one at the same time that I migrate all 5,000 of our users.

So, I’ll have to remember this: Edge servers (and, I’m guessing, CWA servers as well) are forest-level resources. They are not limited to the pool in which you created them, even though the docs say that a R1 Front End can’t communicate with an R2 Edge server, and an R2 FE can’t communicate with an R1 Edge server.

For a brief time, though, I found I could connect from the outside through the R1 Edge server to the R2 pool when I was a member of that pool. In retrospect, though, Federation was probably not working.

How do larger companies do this, I wonder, since as near as I can tell, there’s no command-line tool for migrating users to the new environment?

Anyway, the big switch will take place hopefully this Sunday night when all the US and Canadian branches are on holiday.

After that I need to set up backups, archiving, and eventally the Communicator Web Access server our last environment didn’t have.