Windows AD 2019 compatibility

Questions about using Windows AD service.
Post Reply
tribunal3117
Starting out
Posts: 37
Joined: Thu Jul 31, 2014 8:40 am

Windows AD 2019 compatibility

Post by tribunal3117 » Thu Feb 06, 2020 4:55 am

I'm migrating from a Windows Server 2008 R2 AD domain to a Windows 2019 AD Domain. The latest documentation doesn't explicitly state that QTS can join a Windows 2019 AD Domain. That said, I stood up a 2019 server, joined it to my 2008 R2 AD domain, and then went through the manual join process again in QTS, and it seems to have worked. I also transferred FSMO roles and powered down the old 2008 R2 server, but before I run DCPROMO to remove it from the AD domain, I'm going to let it sit for a week or so. However, once I finish removing the old 2008 R2 DC, I plan to raise the domain level to Windows 2016 (the current max), but I also know that 2019 raised the schema version above that of windows 2016. So I figured I would ask if anyone has had any issues with the QNAP NAS interacting with a 2019 AD?

Also I'm running QTS 4.3.4. I've been planning to upgrade to either 4.3.6 or 4.4.1. I've seen some posts of others having issues with AD on recent versions of both of those. Can anyone comment on that?

dolbyman
Guru
Posts: 17024
Joined: Sat Feb 12, 2011 2:11 am
Location: Vancouver BC , Canada

Re: Windows AD 2019 compatibility

Post by dolbyman » Thu Feb 06, 2020 5:01 am

I can tell you in a couple of weeks, upgrading a domain from SBS 2011 (Effectively 2008 R2) to Server 2019. A QNAP is domain joined to sync group permissions etc.

tribunal3117
Starting out
Posts: 37
Joined: Thu Jul 31, 2014 8:40 am

Re: Windows AD 2019 compatibility

Post by tribunal3117 » Thu Feb 06, 2020 9:59 pm

Just an update, but I did a full shutdown of all the VMs (except the 2008 R2 DC) and then the NAS last night. I then brought them back up, and all systems were working with the NAS still accessing the new 2019 domain correctly (pulling back AD users/groups, ACLs from Windows clients still working properly). In case anyone else is in the boat of upgrading a DC, I found this article very helpful.

https://techcommunity.microsoft.com/t5/ ... a-p/538377

Fortunately I was already using DFSR replication, so I didn't have to go through the chore of migrating to that method.

I'll run DCPROMO in a few weeks and see if everything keeps working. In the meantime, does anyone have any thoughts on the version of QTS to which I should upgrade to maintain to avoid AD issues (I've seen mentions of AD integration being broken in certain builds)? Should I stay with 4.3 or move up to 4.4?

tribunal3117
Starting out
Posts: 37
Joined: Thu Jul 31, 2014 8:40 am

Re: Windows AD 2019 compatibility

Post by tribunal3117 » Wed Feb 19, 2020 5:30 am

Last update. I demoted the old DC, and then promoted both the domain and forest levels to Windows 2016. I tested the NAS rejoining the domain, and it succeeded. Other tests for authentication and communication from the the NAS to the 2019 DC worked as well.

Also, I went with 4.3.6.1070 as opposed to 4.4.1. It seemed safer to not jump an entire version upwards for the NAS firmware while all these other changes were going on.

Post Reply

Return to “Windows Domain & Active Directory”