question

HORDZIEJEWICZAndrzej-1260 avatar image
0 Votes"
HORDZIEJEWICZAndrzej-1260 asked jiayaozhu-MSFT commented

failover clustering from w2016 for w2019 not working

hello, as in subject there is no possibility to add failover cluster windows 2019 standard or core in failover clustering manager located in DC/Win2016
the issue is constantly same that w2019 need to have clear-cluster method pushed but even doing it manually on w2019 in PS with success do not resolve this issue. ( see picture )
-Validation from DC/w2016 of that w2019 is successfull but creating it itsn not
-test-cluster from w2019 that is domain joined telling me info that cant validate active directory configuration
-did not find an organization Unit in AD
-could not get domain controller name from machine :localhostname
-please check connectivity of those nodes to domain controllers
all tests are done on brand new isntalled w2019 standard and 2019 hyper-v core - for both of them same errors BUT when i want join to cluster some other w2016 its working fine
i could not find anywhere this information but perhaps creating failover cluster for windows 2019 isnt supported from windows 2016 failover clustering manager ?
anyone had that problem before ? it will be fixed or i just messing something up ?

118637-image.png



windows-server-clustering
image.png (86.7 KiB)
· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,

Thanks for posting on our forum!

Based on your description, I assum that your issue may be more related with your AD configuration. In this case I need firstly to check some points to scope your issue:
1) "to add failover cluster windows 2019 standard or core in failover clustering manager located in DC/Win2016"
I guess in your environment, you were trying to add a 2019 server with Hyper-V role to your 2016-server cluster. What kind of your 2019 server, physical machine or VM. Do you put your 2019 server and 2016 server in the same domain? You can also try to ping between the 2016 server and your 2019 server.

2) "did not find an organization Unit in AD"
——Where did you find this error message? From validation report or failure report when you created your cluster?

Basically, 2016 server and 2019 server can be put into the same cluster, so we need to further investigate this issue. Hope to hear from your feedback!

Thanks for your support!

BR,
Joan

0 Votes 0 ·

hi
1) "to add failover cluster windows 2019 standard or core in failover clustering manager located in DC/Win2016"
I guess in your environment, you were trying to add a 2019 server with Hyper-V role to your 2016-server cluster. What kind of your 2019 server, physical machine or VM. Do you put your 2019 server and 2016 server in the same domain? You can also try to ping between the 2016 server and your 2019 server.
answer:
Windows are in same subnet in same switch so there is no even firewall block between them. ports are open same ping, all basic stuff i checked so no point to ask about ping.
on windows2016 AD/DC i open cluster manager and adding windows2019 by FQDN name. and error is clean-cluster as on picture i send.

2) "did not find an organization Unit in AD"
——Where did you find this error message? From validation report or failure report when you created your cluster?
answer:
when i want to do "test-cluster" command with parameter for DC FQDN in powershell ON windows2019 and test windows 2019 same node as im in powershell, i get those informations about DCs ( errors ) - those info are after validation with this command located in file of validation report
i do not want to put w2016 and w2019 in failover, i want to put 2 x w2019 in failover from AD/DC w2016 failover clustering manager
w2019 are physical and w2016 is VM.

0 Votes 0 ·
jiayaozhu-MSFT avatar image jiayaozhu-MSFT HORDZIEJEWICZAndrzej-1260 ·

Hi,

Thanks for your reply!

Based on your condition, I think you may need more in-depth investigation such as log analysis and simulation test, which are beyond our forum's scope. Besides, our environment may not be able to support your test appropriately. In this case, I strongly suggest you contact Microsoft Customer Support and Services where more in-depth investigation can be done so that you would get a more satisfying explanation and solution to this issue. In addition, if the issue has been proved as system flaw, the consulting fee would be refund. You may find phone number for your region accordingly from the link below.
Global Customer Service phone numbers:
https://support.microsoft.com/en-us/help/13948/global-customer-service-phone-numbers

Thanks for your support and understanding!

BR,
Joan

0 Votes 0 ·

0 Answers