Migrating Workstations |
Post Reply |
Author | |
nicolas
Newbie Joined: 31 Jan 2010 Status: Offline Points: 5 |
Post Options
Thanks(0)
Posted: 31 Jan 2010 at 7:54pm |
hi
we are in the process of evaluating the "User Profile wizard" software. However we are in the unique situation that we wish to migrate to a new domain BUT with the same domain name that is residing on a different segment as we want to keep the same naming identification. Does your software comply to such a requirement? If not can you point us to another direction
ie the steps that we assume need to be taken are:
1. workstation to disjoin the current domain (domainname1)
2. change IP address to new segment
3. join new domain (domainname1) which has the same name
4. restart workstation
much appreciated
regards
|
|
Support
Moderator Group Joined: 09 Nov 2006 Location: United Kingdom Status: Offline Points: 1844 |
Post Options
Thanks(0)
|
Hi,
User Profile Wizard does handle this requirement. There are two points to keep in mind:
1. Do not disjoin the workstation from the current domain. If you do this, the existing domain account information will no longer be cached locally and User Profile Wizard will not be able to resolve the existing domain account names. (The old domain no longer being on the wire.) The Wizard will handle unjoining/joining the domain for you any way.
2. Because you are using the same domain name, you will need to force the Wizard to join the new domain. Set <ForceJoin> to True in the Profwiz.config file and/or make sure there is a tick in the "Join domain" checkbox on the "User Account Information" page of the GUI.
Many Thanks.
|
|
nicolas
Newbie Joined: 31 Jan 2010 Status: Offline Points: 5 |
Post Options
Thanks(0)
|
Sorry but I am getting a little confused with your response. Are you saying that if do not disjoin the workstation from the current domain, this current domain which is the old domain should no longer be on the wire, and if so how is it possible to propagate the script throug GP from the old domain. Also if this old domain is not on the wire, how is authentication taking place?
|
|
Support
Moderator Group Joined: 09 Nov 2006 Location: United Kingdom Status: Offline Points: 1844 |
Post Options
Thanks(0)
|
Hi, Sorry for any misunderstanding. You cannot have two domains with the same name on the network at the same time. Therefore if you want to join a machine to a new domain which has the same name as the current domain, the current domain has to be out of the way. I'm assuming that this is why you said you need to "change IP address to new segment" in step 2 above. Unfortunately, because you cannot have the two domains up at the same time, it will be very difficult to run a script from the old domain GP. Are you planning on scripting the the switching of the IP address? How are you going to do that? If you are changing segments, doesn't that involve either a physical connection change or a router configuration change? In any event, do not disjoin the computer from the existing domain. If the existing domain is not in place, the user logon will be authenticated with locally cached credentials. |
|
nicolas
Newbie Joined: 31 Jan 2010 Status: Offline Points: 5 |
Post Options
Thanks(0)
|
hello again.
as you can understand we are at a loss as to how we are going to manage this operation. If possible can you please suggest the right approach with the right tools step by step - and how much it will cost to putchase the corporate solution if neccessary
thanks
|
|
Support
Moderator Group Joined: 09 Nov 2006 Location: United Kingdom Status: Offline Points: 1844 |
Post Options
Thanks(0)
|
Hi,
How you approach this is really down to how many machines you need to migrate and what resources you have available. If you are only migrating a small number of machines you might just want to consider migrating them by visiting each machine. In this scenario you could create the migration script and copy it and the migration files (Profwiz.exe and Profwiz.config) to a flash drive. You could then visit each machine once it has been put on the new network segment (or once the old domain is off the network) and run the script. Remember, the workstation still needs to be joined to the old domain when you do this. If you have a lot of machines to migrate and the process must be automated, there are a number of options. One would be to have a script run when the user is still logging on to the old domain that copies the necessary migration files to the machine, but which does not run the migration at that point. The migration itself could then be triggered to run either after a specific time or, for example, if the machine's IP address is from a specific range. We would be happy to help with the scripting. Another option would be to migrate the machines remotely. However, this is likely to be more disruptive to your users if you have a lot of machines to migrate in a short time. |
|
nicolas
Newbie Joined: 31 Jan 2010 Status: Offline Points: 5 |
Post Options
Thanks(0)
|
thanks for your prompt reply and suggestions. We definitely have a sufficiently large number of workstations that are also dispersed geographically over a number of states in Australia. We would therefore require an automated procedure to take care of the migration.
|
|
nicolas
Newbie Joined: 31 Jan 2010 Status: Offline Points: 5 |
Post Options
Thanks(0)
|
so may I ask what you need so that w can proceed with this task as we need to commit to this migration asap
regards
nicolas
|
|
Support
Moderator Group Joined: 09 Nov 2006 Location: United Kingdom Status: Offline Points: 1844 |
Post Options
Thanks(0)
|
Please contact support@ForensiT.com
|
|
Post Reply | |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |