Migrate existing server 2022 with WSEE to new server 2022
I have an existing installation of Windows Server 2022 with WSEE running on very old hardware. It is time to upgrade, so I bought new hardware, Windows Server 2022 standard, work folders, and WSEE. I have read the instructions for moving the domain controller and have completed the following steps, but I am reluctant to continue without knowing how to get WSEE working seamlessly.
- installed the software on the new server and joined it to the domain
- verified the domain state on the existing server
- installed the DNS, DHCP, and domain roles on the new server
The next step looks like promoting the new server to DC, but before I do that I want to know when I should install WSEE and how I migrate the existing environment so that I retain all the existing computers.
- Jeff Drew asked 2 months ago
- last edited 2 months ago
- You must log in to post comments.
I don’t do domain migrations and so I can’t really help you out any further on that topic other than what I’ve already posted about it within my main WSEE article (which it appears that you’ve already read and are following).
As far as when to install WSEE… I’d simply make sure that your migration has completed successfully and that the server is up and running just as you want/expect it to be (as far as the migrated domain users, domain computers, Group Policy, etc. goes). Once it is, then I assume that you can then go ahead and run the WSEE Installer on it at that time. The WSEE Installer will install all of the required WSEE files, etc. for you and then launch Microsoft’s Windows Server Essentials Configuration wizard. The wizard “should” then recognize your existing (migrated) domain and configure Essentials onto the existing domain accordingly.
That being said… I’d make sure that you have a working backup of your server before attempting to install WSEE onto it (as a just in case).
Personally, I always strongly suggest that folks start out with a brand new/clean installation of Windows Server 2019/2022/2025 to ensure success, but I understand that some folks can’t (or don’t want to) do that.
Best of luck.
- Mike answered 2 months ago
- last edited 2 months ago
- You must log in to post comments.
I promoted the new server to DC and have migrated all the roles. The next step appeared to be installing WSEE, but I am stuck. The WSEE installation doesn’t seem to recognize the existing domain. When I try to configure the Company Information it says Cannot validate user entries on this page. I have entered the information as I did for the creation of the domain in the first place and consistent with the current configuration for the server. Any ideas on how to get past this?
thanks
- jeffdrew answered 2 months ago
- I looked in the event log and found that there appears to be an issue with the license. It thinks I am already using it. Is that because I still have the other server running?
- You must log in to post comments.
The WSEE Installer license is “single server only” and so if you’re running it on more than one server then it will indeed become invalid (on one of the servers). If you’ve finished the domain migration and are installing WSEE on the newly migrated server, then the license will be activated on the new server (when you run the WSEE Installer) and deactivated on the old server (just as you’d expect). Thus, there shouldn’t be an issue (with the license on the new server) unless you try to reactivate the WSEE Installer license on the old server again.
If you’re having an issue with the WSEE Installer license becoming invalid on the new server, then it’s best to shut down the older server before attempting to install WSEE on the new server (so that the licenses on the two servers don’t clash). If needed, you can contact us (via our email support page) with the “Registration Key” from your WSEE Installer license (or with the “User Name” from the license of your purchased product) and we can reset the license for you.
That being said… I did not write the Windows Server Essentials Configuration wizard (Microsoft did) and so if it’s not recognizing your migrated domain, then I’m not exactly sure what would be causing that. However, the wizard not recognizing your existing domain would have nothing whatsoever to do with the validity of your WSEE Installer license, and as far as I’m aware, it would have nothing to do with the validity of your Windows Server license either. You might want to try rebooting the server and then running the config wizard again just to see if it recognizes your existing domain that way. I definitely wouldn’t proceed with the wizard if it doesn’t recognize the existing domain though (as doing that would just cause you all kinds of grief).
Lastly, you might want to take a look though the WSEE documentation that talks about deploying Essentials in an existing active directory environment:
Deploy Windows Server Essentials in an existing Active Directory environment
Install and Configure Windows Server Essentials or Windows Server Essentials Experience
- Mike answered 2 months ago
- You must log in to post comments.
Everything works now thanks to Mike. The domain has been preserved. It appears the correct order to do things in is as follows:
- install server software and join the domain
- promote the new server
- migrate all the server roles to the new server
- demote the old server
- let the environment sit for a bit to ensure nothing is using the old server
- remove the WSEE software
- turn off the old server
- install the WSEE software on the new server
- answer the questions with the existing information – server name, domain name, etc.
- reconnect the clients
- jeffdrew answered 2 months ago
- You must log in to post comments.
