Windows Server Community
Build your future with Windows Server 2019
Try Now
Home
Options
1,374
Ned Pyle on 03-02-2020 11:17 AM
13.4K
JamesKehr on 02-26-2020 09:22 AM
4,290
JamesKehr on 02-21-2020 09:58 AM
2,223
Ned Pyle on 12-03-2019 02:27 PM
3,020
Ned Pyle on 11-18-2019 03:19 PM
5,483
Ned Pyle on 09-20-2019 04:37 PM
5,586
Ned Pyle on 09-17-2019 04:14 PM
2,005
Ned Pyle on 09-12-2019 06:53 PM
4,680
Ned Pyle on 08-23-2019 11:34 AM
3,798
Ned Pyle on 07-19-2019 03:01 PM
2,096
Arpita Duppala on 04-10-2019 07:53 AM
163K
FileCAB-Team on 04-10-2019 07:53 AM
2,965
Ned Pyle on 04-10-2019 07:53 AM
1,179
Ned Pyle on 04-10-2019 07:52 AM
16.6K
Cosmos Darwin on 04-10-2019 07:52 AM
1,477
Garrett Watumull on 04-10-2019 07:51 AM
5,302
Cosmos Darwin on 04-10-2019 07:50 AM
1,026
Arpita Duppala on 04-10-2019 07:50 AM
43.8K
FileCAB-Team on 04-10-2019 07:49 AM
2,935
Garrett Watumull on 04-10-2019 07:48 AM
1,194
Ned Pyle on 04-10-2019 07:48 AM
1,476
FileCAB-Team on 04-10-2019 07:48 AM
1,732
Cosmos Darwin on 04-10-2019 07:48 AM
1,384
Garrett Watumull on 04-10-2019 07:45 AM
1,043
Ned Pyle on 04-10-2019 07:45 AM
1,829
Ned Pyle on 04-10-2019 07:45 AM
2,119
Cosmos Darwin on 04-10-2019 07:45 AM
25.3K
Ned Pyle on 04-10-2019 07:45 AM
Latest Comments
I ran into this problem where we had two DCs, upgraded in-place for both of them to 2019, detested the idea of reintroducing a 2016 box into the mix and demoting then re-promoting. So here is the ultimately workaround to that! Copy DFSRS.exe from a windows 2016 box to your windows 2019 boxes, take o...
0 Likes
Fair enough. I can say that we have not heard of this issue outside of you two customers, and I'd highly suspect both an unusual network condition specific to your environments combined with a bug or design flaw in our cutover. A recent example of this was us finding customers who don't set subnet g...
0 Likes
Hi Ned, Don't have $500 to gamble on the fact Microsoft may decide this is a bug or not i'm afraid. We are just going to have to go with manually setting the IP address ourselves but In any case it definitely appears to not work between 2008r2 and 2019 I have tested a 2019 to 2019 migration and it w...
0 Likes
The previous person never opened a case or provided logs AFAIK. Your error was earlier in these logs, you are just seeing the result of not being able to contact the server with that OS warning. I need you to open a support case to figure this out - if it's a bug the case will be free.
0 Likes
Same issue as @Jeffwb2u, migrating from 2008R2 and in our testing its successful and 100% however the IP address doesn't migrate. was a resolution ever found for that? I see a warning in logs about failing to determine OS on the new server during the setting ips on destination section, everything el...
0 Likes