This task simply involves checking the Administrative tool to confi rm that no users are still
homed to an old LCS 2005 server. The process is as follows:
1. While logged in as an administrator and in the LCS 2005 Administrative tool,
expand the console tree and expand the tree for each front-end server.
SOME INDEPENDENT ADVICE
If you properly inserted a new OCS 2007 front-end server and all communications
are now fl owing in and out of the new OCS 2007 environment, you can drop
the old LCS 2005 front-end server(s) at any time because the old server(s)
aren??™t doing anything on the network. However, to be extra safe and conservative,
you can leave one of the old LCS 2005 front-end servers still running for a few
days, and in case you have problems, you can reconfi gure to communicate
back to the old LCS 2005 system.
Although this is a nice fallback option, it is highly recommended that you
pick a date to bite the bullet and drop LCS 2005 from the environment, typically
within 10 days of installing OCS 2007. The longer you wait to remove LCS 2005
from your environment, the further it is in your mind to do so. I??™ve seen
organizations that have stray servers in their networks two or three years
later and when asked why they have the old systems, they say no one in the
IT department was around when the new configuration was put in, and no
one wants to fiddle with removing the old system because they do not know
what might happen. So, clean up your network and get rid of LCS 2005 within
a week to 10 days of OCS 2007 taking over user communications.
Pages:
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382