Help with implimentation plan... Big points and its only advice I'm after!

Hi All,


I have a client currently running a single Win 2003 Server (2.6ghz, 1gb, 160gb), on this they have all files / folders, a workgroup email system called Tobit (which I hate) and Sage Line 100 (when I say this is running on the server what I mean is the Sage folder is shared on the network and is run locally on each machine (its a DOS app).

Software RAID 1 on 2 IDE disks

This is running with a Servgate SG100 Firewall and ADSL modem for internet / VPN connectivity.

This network was also setup with a very common 192.168.1.* IP scheme (not my doing).

Currently running about 40ish users.

I have got the go ahead to install a Small Business Server 2003, a new server to run it, a much better Firewall / UTM Device (Servgate Edgeforce M30), new switches etc etc.

My plan is to have the new server running SBS 2003 (and so managing all file / print / email tasks) and rebuild the current server using new hard disks (software raid 1 as current) to run the Sage line 100 app (or basicaly share the folder) (far easier than messing around with the current install and a cleaner end result, also able to keep the old disks as back up if everything goes wrong).

I also want to change the IP scheme to something a bit more obscure so users will be able to VPN in easily without having to change router settings at the remote end.

Now I need some advice...

I'm trying to figure out the best way to migrate to the new setup, minamising downtime.

The users obviously don't want any down time, all sales / production / delivery is based around the Sage line 100 system so this must suffer as little downtime as possible.

I have no hope of exporting any data from the Tobit system so I am just leaving that and asking users to backup any important emails manualy (save as HTML).. hopefully this should not cause to many problems.

I'm willing to work the weekends but just the simple number of pcs means I will not be able to setup all of them before the next day starts!! (they start at 5am) lol

Sage downtime is my main concern.

Advice please... Basicaly I'm looking for help with my implimentation plan.
Who is Participating?
Jay_Jay70Connect With a Mentor Commented:
migrating servers pretty much guarrantees at least some downtime for some users, you cannot avoid it :)

for me, i would build the new domain and have it setup ready for migration. Then, after hours, I would move the sage data, and then start moving also depends on how the sage data is stored....leave the xp machines for last as far as formatting goes, get your users up and running and then at your own time you can rebuild machines.

I dont know enough on how Sage works to know the best solution is as far as migrating that program
Install and configure SBS. USe the migration tools ADMT from microsoft to migrate users. Create new shares as appropriate, Deffinitely change the IP scheme. Rebuild the old server, add it in. Join all the machines to the new domain and configure emails etc....

not much that i have given there but your implementation is fairly standard and not too hard at all
NetitudeAuthor Commented:

Thanks for your answer...

What I really want to know is how you would go about moving the sage data...

Down the server at the weekend, copy the data to the SBS box and get everyone runing like that... would mean sage was available almost straight away and I would have more time to re-install the sage box... but it also means alot of running around and almost doing the job twice...


Rebuild the old server over the weekend, add it to the domain setting up all clients as final installation...

Should have said I also want to wipe all the client PCs and reinstall (all XP SP2) as part of the migration (I will be much happier with a clean sheet, too many unknowns at the moment).
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

NetitudeAuthor Commented:
its not really th technical details (I know the end result I want).. it's just the order you would do it in.. and how much downtime you think would be reasonable for this kind of job.
NetitudeAuthor Commented:

That's all I needed, just a little reassurance, I think I'm on the right track...

Sage line 100 is a 4GL Based DOS app.. you just plonk it in a folder and share it, the client then runs a batch file from the share.


Move the data at the weekend and be on the case bright and early on monday bodging the urgent machines onto Sage... then make my way round re-installing all the other machines... and finding all the wonderful little things that have static IPs (print servers, clocking in machines, weather monitors etc)...

Woohaaa My weekends just ROCK!
i know that feeling my friend :)
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.