ADMT migration from 2000 or 2003 sbs to 2003 sbs
Here is the situation. The last two Domains that we have tried to migrate with the ADMT have been nightmares. Mainly client side failures. I have searched through MS sites and read their manuals. Basically I have little to no problems on the server side of the migration. User accounts and all normally go just fine. The problem that we keep running into is the client machines.
Question: What are the prereqs on the client machines. I think we are leaving something out there.
These are the things that we have done in the past on 2003 SBS to 2003 SBS.
1) RPC enabled
2) File and print sharing enabled.
3) Firewall off
4) Antivirus off.
5) Cross DNS on the servers. Basically made each server a secondary to the other.
We spent most of the day fooling with the client machines and we could have just rejoined them by hand then do a profile copy. Then be done with it. This ADMT tool seems to be very picky.
Standard edition is no biggie. It is a DCPROMO away then swap.
Any help is appreciated.
Thanks
Casey
Question: What are the prereqs on the client machines. I think we are leaving something out there.
These are the things that we have done in the past on 2003 SBS to 2003 SBS.
1) RPC enabled
2) File and print sharing enabled.
3) Firewall off
4) Antivirus off.
5) Cross DNS on the servers. Basically made each server a secondary to the other.
We spent most of the day fooling with the client machines and we could have just rejoined them by hand then do a profile copy. Then be done with it. This ADMT tool seems to be very picky.
Standard edition is no biggie. It is a DCPROMO away then swap.
Any help is appreciated.
Thanks
Casey
ASKER
Ended up figuring out that ADMT tool shut down some services on the clients. So we made a script that enabled them and it works now.
this is what we implemented for the fix for a one time script.
net stop sharedaccess # Stop Windows Firewall
sc config sharedaccess start= disabled # Set Firewall service to disabled
sc config RpcSs start= auto # Set RPC Service to Automatic
net start RpcSs # Start RPC Service
sc config DNSCache start= auto # Set DNS Client Service to Automatic
net start DNSCache # Start DNS Client Service
sc config LMHosts start= auto # Set NetBIOS Helper Service to Automatic
net start LMHosts # Start NetBIOS Helper Service
Casey
this is what we implemented for the fix for a one time script.
net stop sharedaccess # Stop Windows Firewall
sc config sharedaccess start= disabled # Set Firewall service to disabled
sc config RpcSs start= auto # Set RPC Service to Automatic
net start RpcSs # Start RPC Service
sc config DNSCache start= auto # Set DNS Client Service to Automatic
net start DNSCache # Start DNS Client Service
sc config LMHosts start= auto # Set NetBIOS Helper Service to Automatic
net start LMHosts # Start NetBIOS Helper Service
Casey
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Oh... FYI, even if you do rejoin workstations by hand, you don't do a profile copy. ConnectComputer migrates profiles automatically.
What you need to do is stop trying to migrate SBS networks with an Enterprise server mentality. Leave all of that experience at the door and if you do things the "SBS way" you'll be much happier!
Jeff
TechSoEasy
What you need to do is stop trying to migrate SBS networks with an Enterprise server mentality. Leave all of that experience at the door and if you do things the "SBS way" you'll be much happier!
Jeff
TechSoEasy
For SBS 2003 to SBS 2003 there are FOUR options available which I've detailed in this Question: http:Q_22008948.html#17640511
If you do a fair amount of migrations then I would definitely recommend that you use the SwingIT method described in that Q. Full info on it is available at www.sbsmigration.com
Jeff
TechSoEasy