Laszlo Denes

<div>
Thank you. I will go with removing it one by one from each server and then finally from DC once it is done... I have assurances from my Manager that we have zero legacy applications now. Cheers
</div>


Thank you. I will go with removing it one by one from each server and then finally from DC once it is done... I have assurances from my Manager that we have zero legacy applications now. Cheers

<div>
DC part you test in pre-production or test environment first. if you have any. As i remember now, my client faced issue, after WINS removal from DC's.
</div>


DC part you test in pre-production or test environment first. if you have any. As i remember now, my client faced issue, after WINS removal from DC's.

<div>
DC's are relatively new and were implemented and ran fine without WINS for a while, but thanks for the tip
</div>


DC's are relatively new and were implemented and ran fine without WINS for a while, but thanks for the tip

<div>
<div class="content wysiwyg-content">
As always many thanks in advance for all insights.<br />
We are running AD with two 2016 DC with the usual GC/DNS, etc. on a 2012R2 FFl/DFL, but still have WINS installed on both (replication). Not my choice and I want to get rid of it as I have assurances that none of the current applications or servers running them still need WINS. I note we also have a SharePoint 2013 and Exchange 2013 (cluster). What would be the best approach for this? I could remove WINS entries from the static IPv4 entries on each server and then see over a 24 hour window if anything breaks which sees the safer option or just turn off WINS on the two DC, see what happens over 1 week and if nothing then remove the roles altogether? Thoughts? Cheers!
</div>
</div>


As always many thanks in advance for all insights.
We are running AD with two 2016 DC with the usual GC/DNS, etc. on a 2012R2 FFl/DFL, but still have WINS installed on both (replication). Not my choice and I want to get rid of it as I have assurances that none of the current applications or servers running them still need WINS. I note we also have a SharePoint 2013 and Exchange 2013 (cluster). What would be the best approach for this? I could remove WINS entries from the static IPv4 entries on each server and then see over a 24 hour window if anything breaks which sees the safer option or just turn off WINS on the two DC, see what happens over 1 week and if nothing then remove the roles altogether? Thoughts? Cheers!

Best Approach to test WINS removal on Servers?

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Microsoft Sharepoint is a software platform and family of software products used for collaboration and web publishing combined. These capabilities include developing web sites, portals, intranets, content management systems, search engines, wikis, blogs, and other tools for business intelligence and collaboration. SharePoint has a Microsoft Office-like interface, and it is closely integrated with the Office suite.

Microsoft SharePoint

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

Windows 10 is a personal computer operating system featuring the "universal application architecture" (UAP); apps can be designed to run across multiple devices with nearly identical code, including PCs, tablets, smartphones, embedded systems, Xbox One, Surface Hub and HoloLens. Windows 10 also includes a virtual desktop system, a window and desktop management feature called Task View, the Microsoft Edge web browser, support for fingerprint and face recognition login, voice-based search (Cortana), new security features for enterprise environments, and DirectX 12 and WDDM 2.0 to improve the operating system's graphics capabilities for games.

Windows 10

Microsoft Azure is a cloud computing platform and infrastructure for building, deploying and managing applications and services through datacenters. It provides both platform-as-a-service (PaaS) and infrastructure-as-a-service (IaaS) services and supports many different programming languages, tools and frameworks, including both Microsoft-specific and third-party software and systems. Cloud Services is a PaaS environment and can be used to create scalable applications and services; there are specific software development kits (SDKs) provided by Microsoft for Python, Java, Node.js and .NET. Azure also has file and storage services, data management, analytics and DNS services.

Azure

Windows Server 2016 is the successor to Windows Server 2012 R2. Built upon the same core code as Windows 10, Windows Server 2016 brings enhancements in security, servicing, and connectivity. A particular focus on this release was hybrid-cloud scenarios, and has close ties to Azure and other Microsoft cloud initiatives. This does not detract from the many improvements that are available for on-premises-only deployments

Windows Server 2016 comes in Datacenter, Standard, and Essentials editions, and for servicing, has adopted windows 10's cumulative model. The new nano-server install is designed to be remotely managed and is designed to be kept current through continuous feature updates. The full GUI install operates similarly to windows 10's "Long Term Servicing Branch" (LTSB) model with cumulative security updates.

Windows Server 2016 has also shifted from a per-processor-and-CAL licensing model to a per-core-and CAL licensing model. This brings Windows Server's licensing more in line with Microsoft's other products and makes hybrid-cloud license planning easier as well.