Having an automated software distribution system will enable you to more quickly migrate
from MOC 2005 to MOC 2007 and ultimately will provide a more automated path to shift
users from LCS 2005 to OCS 2007 to take advantage of the new capabilities of OCS 2007.
Designing Your New OCS 2007 Environment
Armed with information about your existing LCS 2005 environment, you now need to design
your new OCS 2007 environment to include the replacement of old LCS 2005 server roles
with corresponding OCS 2007 server roles. And assuming that you will be taking advantage of
the new capabilities of OCS 2007, such as Web conferencing and VoIP telephony, the design
and architecture of the new OCS 2007 will likely include even more server roles, functions,
and features.
The design of OCS 2007 in a migration from LCS 2005 to OCS 2007 is similar to the
design of a brand-new installation of OCS 2007. For more information, refer to Chapter 2,
which covers the design of OCS 2007.
Choosing a ???Big Bang??? Migration
or a Phased Migration to OCS 2007
The last step when planning an LCS 2005 to OCS 2007 migration is to determine how quickly
you??™ll be migrating to OCS 2007. It is always preferable to keep the coexistence between LCS
2005 and OCS 2007 to a minimum. With some users on OCS 2007 and others not, those that
are on OCS 2007 cannot utilize its new capabilities until everyone in the organization has
been migrated to OCS 2007 and is using the MOC 2007 client. So, do what is necessary to
make the migration timeline as quick as possible!
An organization with one LCS 2005 server and 50 users can do a ???big bang??? migration
for the entire organization because the scope of the migration is limited to a single server
and a handful of users.
Pages:
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366