?
Solved

ADMT migration from 2000 or 2003 sbs to 2003 sbs

Posted on 2007-07-22
4
Medium Priority
?
758 Views
Last Modified: 2008-06-06
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
0
Comment
Question by:Casey Herman
  • 3
4 Comments
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 19544052
Well, there's more to that because you have Exchange involved, which makes this a much more complex migration.

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
0
 
LVL 10

Author Comment

by:Casey Herman
ID: 19580227
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
0
 
LVL 74

Accepted Solution

by:
Jeffrey Kane - TechSoEasy earned 500 total points
ID: 19582812
You don't need to do that for an SBS2003 to SBS2003 migration because when the workstations were first joined to the network using the ConnectComputer wizard, all of those items (and a lot more) would have been set properly.  So, if the workstations weren't originally joined to the domain properly, that should be corrected before beginning the migration.

Then, are you following all of the recommendations in http://sbsurl.com/migrate?  Or are you just running ADMT?  Because with SBS there are many more considerations to make.

Also, I noticed your step, "Cross DNS on the servers.  Basically made each server a secondary to the other".  Usually on an SBS network you don't need or want more than one DNS server... that being the SBS.

Jeff
TechSoEasy
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 19582818
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
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP,  Windows Server…
Despite its rising prevalence in the business world, "the cloud" is still misunderstood. Some companies still believe common misconceptions about lack of security in cloud solutions and many misuses of cloud storage options still occur every day. …
Screencast - Getting to Know the Pipeline

840 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question