This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 81%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
I have another thread regarding his migration here. It was though I should ask this in a separate thread.
Basically I will need to migrate the file server portion of the old 2012 standard server to the new, 2019 server.
My plan was, once I got the new server in place and set up as a member server on the domain, not a DC yet, I would robocopy all the data to it, preserving the rights.
robocopy.exe "\MainDC\Companyshare" "C:\CompanyShare" /COPYALL /SECFIX /E /XO /R:1 /W:1 /nfl /ndl /LOG+:"C:\Temp\companyshare.log"
Then go through with the rest of the migration and finally run that same robocopy job one more time before removing the old DC from the network.
Sound like a plan?
Sure, using robocopy should be fine to do.
--please don't forget to upvote and Accept as answer if the reply is helpful--
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
As a work-around and assuming other domain controllers you could demote this one, then as a member server a local user account would be possible.
--please don't forget to upvote and Accept as answer if the reply is helpful--
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
OK, maybe we're going down the wrong road here with the users. My (sort of) plan at this point is to get the new (2019) server on-site and install AD on it then promote it to a DC. This will pull all the users in as well as security groups, etc.
Once this is done I will need to them pull over the one company share (C:\companyshare) which, at first, your pointer to the "Windows Server Manager" was perfect. It's always amazing to me how we, or at least I, get into ways of doing things and don't look at alternatives. That was a great suggestion on your part... until it looks like the migration service doesn't work with Server 2012 standard:
"Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2"
But I will continue to look at it. I'd like to leave this thread open for the time being until I see if I'm missing something.
Dave,
Sorry, been away. So, here is what I tried. I loaded the Windows Admin Center (WAC) on a client system connected to the domain. This is great, thanks for the pointer.
Anyway, when I brought up the 2012 server the "Storage Migration Service" was not available. Seems it won't be on a 2012. Then I remembered we have "dev" server that is running 2019 and is just a member server. So I connected to that one and found the SMS feature. I figured it doesn't matter if I push or pull the files to the new server (not here yet) so I created a job and let it scan the 2012 server, not to move/copy anything, but to see what the scan turned up. I ended up with a list of all the shares, some marked "Succeeded", some "Skipped" and some "Couldn't inventory some devices". Of course, the one share I want/need was in the last category. Double clicking produced this:
I made sure all updates were applied and rebooted the servers, Ran the Scan, same thing. I'm researching this now but wanted to give you an update.
Now, to be clear, there is one share "Company" that I want with ~300gb of files. Would using Robocopy to copy them to the new server, preserving security, be such a bad thing?
The command I would use is:
"\SERVER\CompanyShare" "C:\CompanyShare" /COPYALL /SECFIX /E /XO /R:1 /W:1 /nfl /ndl /LOG+:"C:\Temp\companyshare.log"
Thanks again
As always, thanks for sharing the wisdom.
You're quite welcome.
You could follow along here.
https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/migrate-data
--please don't forget to upvote and Accept as answer if the reply is helpful--
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
Dave,
Thank you, this looks promising. I did a very cursory look at this and installed admin center on a Windows 11 client. Poking around in this I got:
Local users and groups
This tool cannot be used when connected to a domain controller
I got this when I clicked on my secondary DC. So, when I am doing this I will have my 2012 box, which is the current DC and File server, that I need to migrate to my new, 2019 server. But is this saying that I can't even use my old computer because it is a DC? The new one won't be a problem as I can keep it as a member server and promote it after. I really like the sound of this, but does it only work on member servers?
Again, this was just a quick look, but I thought I would ask about this before I spend more time looking into it, if I can't use it on a DC then it will be of no value.
May make sense since there are no local users on a domain controller.
--please don't forget to upvote and Accept as answer if the reply is helpful--