Ask a question


How can we help you today?

Ask Question
Manage notifications
Subscribe to this question
Andy Sharpe

Windows 2012 r2 to 2019 Essentials migration and AD Domain Name change

Hi, we are looking to migrate from a Windows 2012 r2 server running AD and is our only DC, to a new Windows 2019 Essentials server, transferring all the existing roles.

  • The Windows Server 2012 Migration Kit DIY looks to be the product to guide us through the exercise?
  • What form of backup for disaster recovery should be employed or is this covered in the guide?
  • We also have a need the change the AD domain name, when is it advisable to do this, pre-migration, during or post migration?
Thanks
asked11/29/2023 14:30
36 views
Add Comment
Last Activity 02/02/2024 11:02

2 Answer(s)

  • Mariette Knap

    Hello Andy,

    Yes, our migration kits can do what you want and you can also ask me for help. We have kits without support but also with support, see https://server-essentials.com/store/windows-server-2012-migration-kits. If you buy a DIY kit and need support you can always purchase that after.

    1. Not sure what you ask for. You should have a proper backup plan already in place, that should not depend on a migration. In the kit we ask you to make one SystemState backup just in case something goes very wrong which has never happened in the 25 years I do this work.
    2. Changing the local domain name can be done but this is NOT part of any migration kit I have written. A comprehensive free guid for renaming a local AD domain name can be found here How to rename an Active Directory domain name of a Windows Server 2012 R2 with the Essentials Experience role installed
    I am wondering why you want to change the name of your local domain?
    answered 11/29/2023 14:42
    Add Comment
    Andy Sharpe

    Hello Mariette,

    Thank you for the fast response.

    • For the backup, I think we have that covered, but I take your point on the SystemState backup beforehand.
    • The reason for the domain name change is much the same as as your 2012 example, company name change.
    Thanks.
     
    Mariette Knap

    Hello Andy,

    Remember that procedure can only be done without Exchange Server in your network or any connection to Azure/Office365 has to be removed before you do the rename. And last but not least, it is not part of any migration kit and NOT supported by me.

    replied 11/30/2023 16:55
    Reply
    replied 11/30/2023 16:45
  • Andy Sharpe

    Hello Mariette,

    I am pleased to say that we have successfully migrated to Windows 2019, using your guide, our network is stable with no dramas.

    We now need the change the AD Domain Name and I am using your " How to rename an Active Directory domain name of a Windows Server 2012 R2 with the Essential Experience role installed" as a guide. We do not have an Exchange Server installed and have no 365 or Azure integration and we currently have a single DC.

    For carrying out the renaming task on 2019 Essentials:

    1. Can we simply skip step 1 in its entirety?
    2. There is obviously no need to carry out step 8, but will there be a need to run the Connect software on our client computers?
    3. Finally, will the "Users" directories on the client computers be unaffected by the name change?

    Thanking you

    Best Regards,
    Andy

    answered 02/02/2024 10:35
    Add Comment
    Mariette Knap

    Hello Andy,

    Thank you! It is always nice to hear that your project went well. The tech note your are referring to is How to rename an Active Directory domain name of a Windows Server 2012 R2 with the Essentials Experience role installed.

    1. Windows Server Essentials 2019 does not include the Essentials Experience part. But if you have migrated the CA to the new DC you must create a backup of the configuration and all certificates BEFORE renaming the domain name and then uninstall the CA completely. You may want to reconsider if you really need the CA on your new DC? If it was only used for the Essentials Experience role on the old 2012R2 server you probably don't need that at all but you must make the backup as described in the migration kit so that we can restore if needed. BTW, as far as I know a domain name change makes it impossible to restore the CA but I am not 100% sure on this issue.
    2. Yes, we cannot install the Essentials Experience role as it is not part of Windows Server 2019. The Connector software on clients should be removed also, there is more information and a script in the kit.
    3. If the users directory on client computers contains information with domain.old.local the a new directory will probably be created as soon as you have rebooted the client 3 times.
    Andy, make sure you make a full image of your DC before you start this. I hope your DC is virtualized because restoring that will be so much easier. If it is virtualized and you have the OS on a separate virtual disk the easiest way to make a backup is to shutdown the DC and copy the virtual disk with the OS on it.
    Reply
    replied 02/02/2024 11:01
Add an Answer