Can we get some additional info here for Server 2019? It appears that Server 2019 under the hood is really Server 2016 v1809? and DFL/FFL can go no higher than 2016? I'm not sure why we didn't call it what it is? Either case; need something official on DFL/FFL possibilities with Server 2019
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
You’re correct no new FFL/DFL in Windows Server 2019. I haven’t had a chance to update the doc yet but will get it done next week.
John,
Thanks a lot and for fast response!!
Dave Patrick
512-690-1902 (mobile)
From: John Flores notifications@github.com
Sent: Saturday, October 13, 2018 4:12 PM
To: MicrosoftDocs/windowsserverdocs windowsserverdocs@noreply.github.com
Cc: DSPatrick dspatrick@gmail.com; Author author@noreply.github.com
Subject: Re: [MicrosoftDocs/windowsserverdocs] Server 2019 info? (#1649)
You’re correct no new FFL/DFL in Windows Server 2019. I haven’t had a chance to update the doc yet but will get it done next week.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/windowsserverdocs/issues/1649#issuecomment-429575669 , or mute the thread https://github.com/notifications/unsubscribe-auth/AjviQn5yX7Yo0eulZxWAGgD17sHyb1v2ks5uklcggaJpZM4Xa1Ec . https://github.com/notifications/beacon/AjviQo0RlxsGBIf42BoD2CIeizLYUA5sks5uklcggaJpZM4Xa1Ec.gif
It’s what we do as IT Pros. #in-progress
"You’re correct no new FFL/DFL in Windows Server 2019. I haven’t had a chance to update the doc yet but will get it done next week."
Hi John, can you also offer some guidance on whether we should reasonably expect to see a 2019 DFL/FFL at some point in the future. Thanks.
@sime3000 I can't comment on future product features.
Hi John. Did we miss your update to this article last week re FFL/DFL ? ?
Why was this one closed without updating the article?
The Issue was closed because it has been answered. We provide Github Issues for reporting inaccuracies in the Windows Server documentation set. When an issue is closed, it is not necessarily because it has been fixed or resolved, but because we have taken note and provided all the information we have at the time. We do not use Github Issues to track resolution of requests or bugs.
Please note that the issue, although closed, is not locked and you are still able to comment in it, and all participants are still notified when you do.
Thanks,
Corey
I’ll let you know when I update the article. Sorry about the delay.
Ok, thanks for clarification and also the update.
On Sun, Oct 28, 2018, 4:18 PM John Flores notifications@github.com wrote:
I’ll let you know when I update the article. Sorry about the delay.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/windowsserverdocs/issues/1649#issuecomment-433742371,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AjviQiIBDjYx_JZIb5Sza7WhQJg5PMwkks5uph84gaJpZM4Xa1Ec
.>
Sent from Pixel 3
@DSPatrick I pushed the button just now to get the following added to the article today.
Windows Server, version 1809
There are no new forest or domain functional levels added in this release.