• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Need Windows 11 Migration Help in Server environment

les_garten

Gawd
2FA
Joined
Dec 12, 2007
Messages
532
I have an office that needs to migrate 12 Workstations from 10 to 11 in 1 2019 Server Domain Controller network.

In the end the new PC needs to have the name as the old PC. I need ao install a bunch of SW needed for Surgical procedures and don't want to lost it with a name change anywhere.

I need local accounts and Domain accounts to be available for anytime the DC may hiccup.

How do you install Win 11 now without creating a MS account? Is that possible?

How does that work with MS Office serial numbers?
 
If you are on a domain, you should be using Windows 10/11 Pro or Enterprise.

When you install Windows, you just say "sign in aother way" and choose Domain.

Also, if a computer already exists with a name, do an inplace upgrade?

You can not have 2 computers with the same name domain joined.. you must either delete one, or inplace upgrade it.
 
If you are on a domain, you should be using Windows 10/11 Pro or Enterprise.

When you install Windows, you just say "sign in aother way" and choose Domain.

Also, if a computer already exists with a name, do an inplace upgrade?

You can not have 2 computers with the same name domain joined.. you must either delete one, or inplace upgrade it.


All will be 11 Pro, and REQUIRE new hardware. Sorry, forgot to mention those two points.

Can I give them temp names, decomission the orig names and rename new PCs to original names?
 
transfer drives to new hardware, get them up and running.
upgrade to 11.
yes your last post would work too.
 
Why wouldn't you just clone the drives from the old W10 to the new and then do in place upgrade to W11? Or in place upgrade the old W10 machines to W11 then clone drive to new machines.
 
Why wouldn't you just clone the drives from the old W10 to the new and then do in place upgrade to W11? Or in place upgrade the old W10 machines to W11 then clone drive to new machines.
Thanks guys. Hadn't thought of some of these. Cannot do in place upgrades because of TPM. But cloning and upgrading in place might work. If the machines will boot.
 
If the machines will boot.
remove the chipset drivers before you shutdown to move the drive(or clone it over) to the new hardware. let windows fire up and do its reboot dance (3-6 reboots) and it then should load up fine*. install new chipset drivers. upgrade to 11.
*as long as these systems have all their efi info on the boot drive....
 
remove the chipset drivers before you shutdown to move the drive(or clone it over) to the new hardware. let windows fire up and do its reboot dance (3-6 reboots) and it then should load up fine*. install new chipset drivers. upgrade to 11.
*as long as these systems have all their efi info on the boot drive....

These will be new Dell workstations with most likely some version of Core Ultra. The old are around 10th gen i7 and i5 vintage
 
Ya, cloning can work, Windows is pretty flexible now moving between hardware and so long as the new Dell systems come with Windows, they should activate fine also.

Redoing company apps can be a pain, and a clean install is always best...

Now you do note Surgical procedures, so these sound very critical, so, make sure you properly test on a single system first.
 
Ya, cloning can work, Windows is pretty flexible now moving between hardware and so long as the new Dell systems come with Windows, they should activate fine also.

Redoing company apps can be a pain, and a clean install is always best...

Now you do note Surgical procedures, so these sound very critical, so, make sure you properly test on a single system first.

I'm thinking of just doing what I originally thought, total clean install. I don't want to drag around old problems.

So just call the new accounting pc >> accounting2, get it setup, then decommission accounting and rename accounting 2 >> accounting?

Any gotchas to watch out for?
 
Build the new machines, configure, etc, if your existing machines are 'OFFICEPC01' use a temp name on the new machine of 'OFFICEPC01R'
Before you shut down the old machine, rename it to OFFICEPC01X, shut down, then when the new one powers up, rename and remove the R
(this is a backup situation and lets you put the old one in place if the new ones encounter some hiccup)
 
Build the new machines, configure, etc, if your existing machines are 'OFFICEPC01' use a temp name on the new machine of 'OFFICEPC01R'
Before you shut down the old machine, rename it to OFFICEPC01X, shut down, then when the new one powers up, rename and remove the R
(this is a backup situation and lets you put the old one in place if the new ones encounter some hiccup)
Thanks!
 
Do you use DHCP reservations, does everything work over DNS? Or does anything use IP's also, as you would need to add the new MAC addresses of the new machines to get the same IP also.
 
Back
Top