 |
|
|
|
|
|
||
      |
|
||
 |
 |
|
|
|
|||
 |
| Infrastructure Services GROUP |
| IRT Information |
If you are going to migrate a server into the domain during while you are migrating users desktop's, the best time to do this is during the window that you are migrating the users.
This means that the users will be unable to access the resources on the server untill the user has been completly migrated.
The following types of servers cannot be migrated into the domain, NT4.0 servers, Domain Controllers, and Exchange servers. Each of these types need to either have there resources migrated to a server that it already in the domain, or to rebuild them server using Win2k Server, or Win2003 Server (preferred). For Exchange server's, you will need to work very closely with the ITSS Windows group to complete the migration successfully.
If the server that is being migrated is a fileserver there are many things that need to be considered before the migration begins.
Scenario 1: old domain, extra server. Data not on domain controller.
If there is an old domain, the old domain will not be able to migrate into the new domain, but the data can.
Either a new server will need to be built, or if the data is not on the domain controller, the server can be added into the domain.
When the users are being migrated the data will be migrated at the same time, to the new server, or standalone server to be added into the domain.
All users will not have access until their desktop has been migrated completly. Folder structure and permissions on the new file server will be mapped out before hand.
Scenario 2: old domain, no extra servers. Or Data on domain controller.
If there is an old domain, the old domain will not be able to migrate into the new domain, the server will have to be rebuilt, in order to go into the domain.
In this scenario, the users that use the data will have to change there share mappings in order to map to the new server.
When the users are being migrated the server that the data is on will be added in to the domain at that time, the users will not have access until there desktop has been migrated completly, and the server has been put into the domain with the correct user and permission mappings on the server.
For each scenario, either way you do it the users will not have access to the data until they have been migrated, there are a couple of things that can be done to ease this problem.
1. have the users take ownership of the files they need to work on during the migration period, and have them copy the files off the fileserver to there local hd's. Once there in the new domain, they can re-upload the file if they have made changes to it. There has to be some co-ordination, to make sure not more then one person takes ownership of a file.
2. If you are using scenario #1, you can have data on both servers, in the old domain, and the new domain, this only works well for "read" only files.
3. IRT has space on a file server that we can either provide temp access to for your files during the migration, or for permenant storage space(there might be a fee for space). Or if you have a small amount of data, you can use a desktop machine running win2k, winxp, or win2003 to share the data out. You can use the desktop in Scenario #2
