Several drawbacks that I can see.
1) Email routing. If you use exchange, since he external domain would
presumably be he same, getting the email routed to the proper internal
server will be downright tedious since it has to be done per user.
2) File access. Separate networks means the clients don't see both servers
and the servers don't see each other. If you use SBS as a file server *at
all* (and I'd be surprised if you don't, but I guess it is possible) then
how do clients on the different networks share files? Sneakernet?
Introducing a big chance of file-version creep with that one.
3) Sharepoint access. Same issue as above, but for sharepoint instead of
4) I'm also not a fan of introducing new OS's at the same time as a
file-server upgrade. Troubleshooting problems *really* becomes a nightmare.
Someone reports that they aren't getting some emails. IS that the server?
Is it a bug with outlook 200(x) on Win(Y)? ....just bad mojo.
In short? Do the client conversion first. I'd want to be 100% sure my
network is clean of malware *before* introducing a new server. Address any
OS/machine bizarreness and make sure your network is operating at peak
efficiency. THEN do the server migration, which you can now do without the
complication of upgrading clients and can thus do a planned phased migration
where both servers see each other and services are moved within the 21-day
grace period. Avoids all 4 of the hurdles I mention above.
"Jaredean" <shop@newsgroup> wrote in message
> I would like to setup a new server (SBS 2008) and bring clients over
> to it 2 at a time while the others are working on the old setup (SBS
> 2003) -- if i had them on separate networks (so the two didn't see
> each other) and they each had their own static IP for internet, what
> would the drawbacks be? That way i could bring our network up to the
> new server over a week instead of having downtime?
> The reason i want to do it slower is to convert each client computer
> to windows 7 (or back to XP for some) with clean installs since we
> had a nasty virus issue a bit ago and i don't believe it is completely