I am doing a SBS 4.5 to SBS 2003 migration and would like to know if anyone has any experience in this area.
Particulars:
-SBS 4.5 installation has small number of users, (10)
-Only 5 users use the exchange mailboxes to store mail, etc.. The other users keep data on local .pst files.
-There are no intranet (iis) websites which need migration.
-There are no SQL databases which need migration.
-The Public folders and other exchange data can be exported to .pst files.
-The Users Shared Folders can be copied off to a member server. (I can use Secure Copy)
-The Company Data Folders can be copied off to a member server. (ditto)
-Domain name will be same as before except for adding ".local" suffix. (XYZ to XYZ.local).
-All users are running WinXP Professional.
QUESTIONS:
-Is it easier and/or safer to configure the target server as a new installation and populate it with the data from the source server, or to use the migration tools?
-If the users are re-created manually on the target server, can the exchange data be exported to .pst files and then imported into the target exchange mailboxes and public folders?
-Can the Shared Folders be copied onto the target server and re-shared manually?
-Since the domain controller is being replaced and the domain name is changing, (to .local), how can the workstation's user profiles be preserved? (XP will want to generate a new default profile for the "new" domain user.)
-Can you select what items you want to migrate when using the tool, or does it just try to take everything and migrate it to the target server?
Thanks for any and all help.
Aloha
Scott
Particulars:
-SBS 4.5 installation has small number of users, (10)
-Only 5 users use the exchange mailboxes to store mail, etc.. The other users keep data on local .pst files.
-There are no intranet (iis) websites which need migration.
-There are no SQL databases which need migration.
-The Public folders and other exchange data can be exported to .pst files.
-The Users Shared Folders can be copied off to a member server. (I can use Secure Copy)
-The Company Data Folders can be copied off to a member server. (ditto)
-Domain name will be same as before except for adding ".local" suffix. (XYZ to XYZ.local).
-All users are running WinXP Professional.
QUESTIONS:
-Is it easier and/or safer to configure the target server as a new installation and populate it with the data from the source server, or to use the migration tools?
-If the users are re-created manually on the target server, can the exchange data be exported to .pst files and then imported into the target exchange mailboxes and public folders?
-Can the Shared Folders be copied onto the target server and re-shared manually?
-Since the domain controller is being replaced and the domain name is changing, (to .local), how can the workstation's user profiles be preserved? (XP will want to generate a new default profile for the "new" domain user.)
-Can you select what items you want to migrate when using the tool, or does it just try to take everything and migrate it to the target server?
Thanks for any and all help.
Aloha
Scott
