This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 9%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMH%3C/text%3E%3C/svg%3E)
Does AD migrate from Windows Server 2012 R2 to Windows Server 2022 affect Lync Server 2013
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Looks like if DFL is not raised above 2012 R2 may be the safer option.
The two prerequisites to introducing the first 2019 or 2022 domain controller are that domain functional level needs to be 2008 or higher and older sysvol FRS replication needs to have been migrated to DFSR
I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2019 or 2022, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.
--please don't forget to upvote and Accept as answer if the reply is helpful--
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 24%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
Hi @MOHAMAD HANIFF BIN WAHIDIN
Agree above said, 2012R2 looks the safer option when you deploy Lync Server 2013
Just checking if there's any progress or updates?
--please don't forget to close up the thread here by marking answer if the reply is helpful--
Will update here after server migrates to WS2022.
Sounds good, in the mean time, please don't forget to close up the thread here by marking answer if the reply is helpful.
Just checking if there's any progress or updates?
--please don't forget to close up the thread here by marking answer if the reply is helpful--
We transferred all fsmo role to new server 2022 before disconnect old server.
Last Friday, two of the new Windows Server 2022 machines have been successfully joined to the domain and promoted to Domain Controllers. Afterward, we disconnected the network from two Windows Server 2012 R2 machines and reassigned their IP addresses to the newly promoted Domain Controllers. Currently, there don't appear to be any issues with accessing Lync and other applications. We are actively monitoring the end user experience to ensure everything continues to run smoothly.
Remaining one WS2012R2 to be migrated. Then we will decommission all old server.
Glad to hear, please don't forget to close up the thread here by marking answer if the reply is helpful--
Please don't forget to close up the thread here by marking answer if the reply is helpful--
AD Windows Server 2012 R2 can be migrated to Windows Server 2022 while maintain forest functional level without Lync server affected. Based on situation at our client site. Thanks