Question on Migrations to new server

coffee

coffee

Well-Known Member
Reaction score
1,832
Location
United States
Im going to be doing my first migration from an old server running SBS and exchange to a newer server. However, I just have a question on how the local files are moved over once the new server takes over.

When I migrate to the new server Im thinking the first login to the new server from a workstation will present a fresh new desktop. I will have to migrate all the files over to the new desktop. Do I just run FABS before the migration and backup the workstations and then reinstall the data back after joining the new server?

I suppose I might just be able to copy the old desktop and files (documents, pics, ect..) to the new user folder but not sure.

My other thought is that since the domain will not change I might now have to do this but might have to correct some paths to programs they use from the new server. I m not sure.

The current server is SBS, Exchange, AD and is sd1.sd.local
The new server will be sd2.sd.local

Whats the most effective way to do this? This is my last hurdle before I set a date to do the migration :) As a first experience this is going to be quite fun really. I plan on posting about it in a separate thread as this will be very interesting. Yes, I will include pics ;)

Thanx,

coffee
 
Are roaming profiles being used or folder redirection?

For data on the shared drive, mapped as S for example, just copy data to the new server and change the S drive to point to the new server.
 
freedomit said:
Are roaming profiles being used or folder redirection?

For data on the shared drive, mapped as S for example, just copy data to the new server and change the S drive to point to the new server.
Click to expand...

They store everything on the local computer. Better put, All home directories are on the local computer they work on.
 
Why do I force these situations on myself? I learn all the intricate things and then miss the big picture? lol

I will be migrating this SBS / Exchange server to Centos/Icewarp. They have the software to do it and show you how. I dont have a problem there. But its just the pre-migration I guess I m wondering about.

This new server will be basically an Exchange/DHCPD/DNS/ Samba-AD. I know that I will just turn off most of the services before hooking into the current network. I think I do not even have to join the domain. Just have to get a IP address. Then run their software program on a workstation logged in as an admin account that is also on the old server. Then run their software program.

https://www.icewarp.com/download-premise/guides/

I have kept the same domain of course.

I have setup the server for testing in the shop and have everything loaded and running fine. Its pretty nice and I ve learned a lot from doing it. :)

You see I feel pretty stupid because Im asking questions that everyone probably things - "Stupid!". But I never seem to step back from the trees to see the forest is the best I can explain it. I also have some gaps in my knowledge because I have never had the opportunity to work on a SBS software wise. I have to say, I have been going almost non stop absorbing knowledge. I have come a long way. But still some gaps here. I have never done a migration and have to kinda piece it together and learn as I go. However, I am not going to install the server until I have a decent knowledge of how the basics work on a migration. Im getting there though :)

If I have to join the new server up to the domain then its going to be a bit sticky. However, I dont think so (at this point) as this is basically how it kinda maps out :

New server <-----------------------> Workstation <-----------------------> Old Server

The software for migration runs on the workstation. You supply credentials for the running Icewarp service and the Old Server. The workstation acts like a man in the middle to get the job done.

So, Thats where I am at.
 
Ok, I got it figured out.

Remembered that I had installed a wireless access point there a year ago. It got an ip right off. So, What you do is just hook up the new server to the existing network and get an ip. Then you run their software for the migration on a workstation logged in on a admin account (full access rights) and perform the migration. Their Desktops (files, folders shortcuts ect) do not change as long as the domain stays the same. Got it.

As for setting up AD, DNS, DHCPD ect.. I am no stranger to that and have everything ready now. Just will disable the services that would interfear with their existing network setup (i.e dhcpd) and have at it.
 
Ok. This would be an excellent example of using a VM environment to validate a plan.

I looked at doing the Samba AD thing several years ago but bagged it. M$ does too many things behind the scenes, of course never discussing it with anyone, that causes problems when clients are updated. A lot will depend on how much/what has been done on the AD/GP side. If there is next to nothing then it should be simple. If I remember correctly all *nix is doing is using ACL's to set GP via scripts.

If it was me I'd would absolutely make sure and image of the server and a couple of WS's. VM them and then give it a go.

Best of luck!!!
 
Before I got to heavily invested in this project I ran a couple of VMs : Winders 7 pro and CentOS7. I setup Samba-ad on the linux side and configured Icewarp on it with a 30 day license. I tinkered around with it for 30 days and then decided to pitch the idea to a client because they wanted to add a bunch of options - remote access, Getting rid of quotas on email from their email host ect... I did a lot of talking to the Icewarp company and finally decided to buy a server/drives and set it up in the shop and get it ready. Its been a great experience as I have no formal training with M$ and SBS. Everything that I have learned so far has been thru experience. I am now at the point of offering this as a package deal for replacement servers in small businesses. It costs the business less up front for licensing software and it improves my profit margin.

I really appreciate the warm reception from you. I remember the days that linux in general was frowned upon and I took a beating from others every time I mentioned it. Now, You see most techs use linux in some form in the shop and are quite interested. That is a great thing. I guess Iam just the "Black Sheep" of I.T.

I am running samba 4.6.7 and there was a new version released just the other day. Setting up the AD is really not hard at all. Just have to remember that all permissions and such are actually configured thru the windows side. Running Samba in AD mode means shares are not browsable. But that is not a problem really. On windows go to 'start/computer/ add a network drive' and put in the server name and hit browse. Then just make a shortcut on your desktop for the shares. Then go into the windows as an admin and set the permissions on the shares.
 
nlinecomputers said:
Not really trying to Snap. But I really don't know anything about such setups except that I've been called in to do away with a couple but that was back in the Windows Xp days. Maybe they are better now but I have my doubts.
Click to expand...

I appreciate that. I thought about it for some time today before posting. I kinda considered it a general question but after learning a bit more about how migrations are setup I realize not anyone here is going to be able to answer it.

Thanks.
 
If you keep the same Active Directory then local profiles will not be affected. Workstations will not notice the difference. As mentioned above - check for redirected desktops and roaming profiles as these will need moving and redirecting from old server to new server. If the workstations do miraculously get new profiles, you can use this previously recommended tool to assign their old domain profile to the new user account on the new domain: https://www.forensit.com/domain-migration.html
 
This morning while manual starting my brain with coffee I heard a mighty "CLick!". I got it. I understand now. I see how it all works.

Thank you everyone for the kind help.

If you have any question on how valid the Icewarp software is I did scrape this from their website:

icewarp-users.png


This coming weekend I will be setting up the new server on location and getting things going.

Thank you all again. Sometimes just a bit of info just makes things click when your learning things. :)
 
nlinecomputers said:
Not really trying to Snap. But I really don't know anything about such setups except that I've been called in to do away with a couple but that was back in the Windows Xp days. Maybe they are better now but I have my doubts.
Click to expand...

I think you misunderstood, in the UK ‘snap’ means ‘me as well’
 
You must log in or register to reply here.

Similar threads

JoelM
M365 to Google Workspace Migration
Replies
3
Views
242
Sky-Knight
Sky-Knight
thecomputerguy
Super small accounting client needs new server/workstation.
Replies
8
Views
224
YeOldeStonecat
YeOldeStonecat
C
VM Server reboot has a 169. address.
Replies
3
Views
692
YeOldeStonecat
YeOldeStonecat
autumn
Hyper V VM move to new hardware
Replies
6
Views
349
autumn
autumn
thecomputerguy
O365 Migration Question
Replies
1
Views
302
YeOldeStonecat
YeOldeStonecat
Back
Top