6. Write down the routing confi guration information for each access proxy server.
NOTE
The changes between LCS 2005 and OCS 2007 made it easier to set up fi rewall
rules for communications to OCS 2007 servers. Whereas LCS 2005 used a proprietary
port 5061 for communications, OCS 2007 uses port 443. Those confi guring
OCS 2007 will fi nd it much simpler to set it up for communications.
Understanding User
Distribution on Existing Servers
Now, with a good understanding of the front-end, internal, and perimeter server infrastructure
confi guration of LCS 2005, the next step is to understand the client side of LCS 2005. First
you need to determine which users are on which server in the LCS 2005 environment. When
you pick your pilot users to migrate from LCS 2005 to OCS 2007, you want to know where
to fi nd the users so that you can easily migrate them to OCS 2007. Likewise, if you are going
to be doing a phased migration from LCS 2005 to OCS 2007 and will be migrating users by
departments, workgroups, sites, or roles, you??™ll need to know where the users reside in LCS 2005
so that you can choose those users and migrate them to OCS 2007 in a logical manner.
Identifying users and their associated servers is easy because you will see the users when
you go into the LCS 2005 Administrative tool, and when you click on each server you will
see the users associated with each front-end server. The specifi c 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.
Pages:
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364