Hyper-V is a hypervisor-based virtualization technology. Hyper-V uses the Windows hypervisor, which requires a physical processor with specific features. For hardware details, see System requirements for Hyper-V on Windows Server.
Purchase an Azure subscription and activate only the cores you need for your hyperconverged infrastructure deployment ($10 per physical core, per month). For Windows Server Datacenter, customers with Software Assurance get Azure Stack HCI at no additional cost.
Get up and running quickly and reliably with validated Azure Stack HCI solutions including integrated systems and validated node solutions. They're available from a range of hardware partners that offer solutions on industry-standard x86 hardware with service and support. Explore a wide variety of hardware solutions from select partners to reduce your acquisition costs. Leverage the Microsoft ISV ecosystem to maximize the value of your hyperconverged infrastructure solution. Enhance security with Secured-core server with Azure Stack HCI integrated systems and simplify the planning of your new solutions with the Azure Stack HCI sizer tool.
Essentially, Hyper-V installs a hypervisor on top of your hardware but beneath your virtualized systems. This hypervisor makes it appear to all your virtualized systems as though they are running directly on the hardware, not sharing it with other virtualized systems. There is one parent system (running the full version of Windows Server 2008 or the Server Core version) that maintains the structure of Hyper-V.
In this setup, we are using two Windows Server 2016 Server Core installations to minimize moving parts and to improve security. Using the Windows Server 2016 Server Core installation eliminates a lot of unnecessary components and reduces the footprint. The increased difficulty of administration with Server Core is offset by the benefits of efficiency and security. You can also use the newer Windows Server versions, such as Windows Server 2019 for Hyper-V cluster setup.
IMPORTANT: Wonderware System Platform 2014 R2 SP1 installs .NET 4.5.2 if the currently installed version of .NET is 4.5 or lower. If .NET 4.5.1 or later is installed, no change is made to the .NET Framework. Prior to upgrading your existing applications to Wonderware System Platform 2014 R2 SP1, we strongly recommended that you:Back up your applicationsFamiliarize yourself with the changes introduced by Microsoft in the .NET FrameworkReview your .NET scripts and .NET controls for any required changesAfter upgrading to Wonderware System Platform 2014 R2 SP1, you should perform application testing on application scripts and on script libraries used by the application to ensure they continue to function properly under .NET 4.5.2. We also recommend you test the upgrade in a staging system prior to upgrading your production system. Wonderware System Platform 2014 R2 SP1 leverages Microsoft .NET Framework 4. The Wonderware System Platform installation program will install .NET 4.5.2 if your system uses version 4.5 or lower. No change is made if your system uses .NET 4.5.1 or higher. Multiple versions of the .NET Framework can coexist. On nodes where SQL Server is installed, .NET 3.5 is also installed by Wonderware System Platform to support SQL Server. In this scenario, other applications you have on the same machine with dependencies on .NET 3.5 will access .NET 3.5. Wonderware System Platform 2014 R2 SP1 will use .NET 4.5.1, 4.5.2, or later. All user-supplied .NET code that runs in the context of InTouch HMI and Application Server requires .NET Framework 4.5.1 or higher. Although .NET Framework 4.5.1 (and later) is highly compatible with applications that are built with earlier .NET Framework versions, you may have to update your scripts, if your .NET scripts were created prior to Wonderware System Platform 2014. These changes may also affect .NET controls developed with .NET 3.5.In ArchestrA scripting, some .Net codes could fail if not using proper text encoding, and could cause a script to exit without completion. The UTF8Encoder is the default BinaryStream decoder in .Net 4.5. To enable an ArchestrA script to decode ASCII XML data, for example, insert the following snippet:
Although .NET Framework 4.0 is highly compatible with applications that are built with earlier .NET Framework versions, Microsoft has introduced changes in .NET 4 to improve security, standards compliance, correctness, reliability, and performance that may require changes to .NET scripts you may have created with ArchestrA System Platform 2012 and earlier versions of Application Server, InTouch HMI, the Historian, Historian Client, and Wonderware Information Server. These changes may also affect .NET controls developed with .NET 3.5.
Microsoft offers a variety of Windows Server and SQL server subscription licenses in in both 1-year and 3-years terms. Microsoft subscription licenses provide customers with latest software versions, complete mobility, and continuous support among other benefits. Below is a comparison between perpetual and subscription licenses from Microsoft:
ThinkAgile MX Certified nodes combine the Microsoft Storage Spaces Direct technology included in Windows Server 2022 Datacenter with industry leading Lenovo servers to give HCI building blocks to build your infrastructure solutions. ThinkAgile MX Certified Nodes are designed for deploying highly available, highly scalable hyper-converged infrastructure (HCI) and software-defined storage (SDS) from Microsoft on Lenovo enterprise platforms. 2b1af7f3a8