Migrate Server 2003 to Server 2016

[mdownes]

Hi all,

A customer (a school) has one tower server running Server 2003 (against advice) with the following:

Server 2003 Standard with SP2
DC
DNS
(DHCP handled by router)
Fileserver
100 user accounts with folder redirection (to share on same server)

So finally, they're getting a much more powerful box on which I'll install Server 2016. So I've a migration on my hands, which I've never done. In order to quote them for labour, with at least some degree of accuracy, what's are the minimum and maximum amounts of hours this is likely to take (ballpark)?

I have googled, but there's not much info on 2003 > 2016 migrations, so if anyone happens to know of any, that'd be very helpful.

Thanks!

 

[kwest]

$4,000

1500 for the job
2500 for not upgrading along the way. Just in case you run into issues.

 

[mdownes]

$4,000

1500 for the job
2500 for not upgrading along the way. Just in case you run into issues.

I like your thinkin'. But I'm in a different jurisdiction, so I'm after a rough idea of the hours I should budget ploughing into this.

 

[Markverhyden]

What are they actually using the DC for? I've seen way to many sites where they were sold a M$ Server solution that was way overkill when compared to their requirements.

Are they using groups?
How is the file sharing secured?
Do they have statutory (legal) requirements such as logging access, activity, etc?
100 users - are these 100 different workstations or 100 different domain logins and X workstations?

A big part of the price is how many workstations are being used.

 

[marley1]

This is a easy task
Install new server
D.C. promo
Migrate files
Update gpo

I would bill for 15 hours

 

[marley1]

Would try to get em on a vm and bill more as well as backup

 

[kwest]

This is a easy task
Install new server
D.C. promo
Migrate files
Update gpo

I would bill for 15 hours

There isn't D.C. Promo in 2016.

 

[kwest]

I like your thinkin'. But I'm in a different jurisdiction, so I'm after a rough idea of the hours I should budget ploughing into this.

I would pad your hours just in case an issue comes up. Should take 10 but I would charge 20

 

[YeOldeStonecat]

So nothing more than the folder redirections?

I'd want to separate that. What licensing do they have? I'd consider utilizing licensing to skin the new bare metal with Hyper-V..and then install a small DC as the first guest, and then install a second guest as their file/print share server.

Why is DHCP on the router? Should be on the server.

Depending on certain conditions and the history of the 2003 server, you may need to stand up a temporary 2008 R2 server....DCPROMO that and move the FSMO roles over to that...catalog, replicate, check things. Change DHCP so clients use that as their DNS, have 'em all log into that to ensure computer accounts are updated, At some point after checking and things look good, triple check all things services are transferred over. DCPROMO down the 2k3 server. Bump up domain functionality level...and then install the 2016 box, DCPROMO up that...transfer the FSMO roles over, ensure catalog too, change DHCP so clients are getting the 2016 box as their one and only DNS, replicate, have clients all log in....lastly retire the temporary 2k8 DC via proper steps.

When at the point of the DC duties being on the 2k8r2 box, I'd introduce the second VM guest, the file server. 2k8 will have the good GPOs for folder redirection, where you can activate that and during reboots of clients, have the GPO change over the location.. Or manually relocate them...may have to do that approach since you likely won't have all students user accounts.
Sure it's actually folder redirection? Not just mapped the old fashioned way to a students folder? Schools usually do simple folders for students...used to be usually on a NAS, but over recent years they've all moved to Google Apps for storage.

I've run into issues doing such a large leap from 2000 or 2003 to 2012, so with 2016 you may run into the same. Sometimes it's fine, other times...you'll run into issues with the DCPROMO where when you Google the error you;'ll find the fix was to put in a middle man (2k8) server temporarily. (just trial mode license is fine since it's only for a few days at the most).

I'd be well over 2 grand for this if not over 3.

 

[mdownes]

What are they actually using the DC for? I've seen way to many sites where they were sold a M$ Server solution that was way overkill when compared to their requirements.

Are they using groups?
How is the file sharing secured?
Do they have statutory (legal) requirements such as logging access, activity, etc?
100 users - are these 100 different workstations or 100 different domain logins and X workstations?

A big part of the price is how many workstations are being used.

Yes, they've different groups for staff and the various classrooms. File sharing is secured using the usual file permissions - no user can access the data of another. It's actually 100 (approx) endpoints and about 500 user accounts

 

[mdownes]

Thanks for all the advice - very helpful, although the mixture of prices and estimated durations suggests my rates could stand some upward adjustment.

 

[Markverhyden]

100 end points? This will not be cheap, especially if you have to deal with data on each machine. As mentioned there is no DC promo from '03 to '16. People have used swing servers to cover large gaps. But given the difference you'd be better off just starting from scratch.

Dealing with each end point will be very expensive. If you can get them to deal with the data on each will help. And give them written instructions on how to join the new domain. Create a tiered price structure. Starting price would be server setup, data transfer, etc. Then a per workstation charge for each one you have to deal with.

 

[YeOldeStonecat]

I still call it DCPROMO...it's just in the GUI now, but it invokes the same processes in the background (and automates more for you). Install as member server, make a DC (the steps you do in the GUI right here basically hand-hold you through the DCPROMO steps without having to do the command line method), move the fizzy roles, demote old server, remove old server.

This part here is all the easiest..it's the redirected folders that will take you the longest....by a far far far mile.

 

[marley1]

Yes dcpromo is what I call it. I know the steps but for those doing this long time dcpromo is in our hearts