Windows 10: Migration of 2012R2 VMs from a 2012R2 DC server stack into Azure HCI stack

bkoch-radntx · Jun 28, 2023

My old VM stack hosts are running 2012R2 DC with VMs running 2012R2.I now have a new Azure HCI 2022 server stack that I'm moving the 2012R2 VMs to will upgrade VMs OS later. Every 2012R2 VM now tells me to activate Windows. How do I fix this?

:)

Joseph Seyler · Jun 28, 2023

Migrating AD/DC, DNS, and DHCP from Server 2003 to 2012r2

Hello,

I have 2 DC's -1-2003 and second one that was 2016.

The secondary domain controller (Windows server 2016) went belly up and I was tasked with building a new one. What I noticed was the System admin who had built it before put it on a server that was over kill. Thus, I re-purposed that server for other things,
and began with a fresh 2012r2 build on an entirely different machine. (Mainly because he didn't have any backups taken anyway).

I decided this would be a great opportunity to upgrade and get off of 2003 and spring board to 2016 or 2019. The 2003 server is a AC/DC, DNS and DHCP server. I am using 2012r2 as a stepping stone to get up to the 2016 or 2019 edition, so essentially I will
be doing this exercise 2 more times.

Anyway.. I began by following the below article. How to Migrate Active Directory Server 2003 to Active Directory Server 2016 Step by Step.

Replication (ADDC/DNS) between the 2 servers seems good, and I got all the way to switching the 5 FSMO roles, which worked smoothly. My issue is this: I wanted to test before going onto the part about demoting the 2003 server, so I unplugged the network
cable. I was able to login to my machine still (on the domain) but doing something as simple as sending a skype message, checking email, getting out to the web stopped working. I plug the 2003 server network cable back in, everything works again.

I am at my wits-end as I can not even think about demoting the 2003 server until I 100% know that the those issues are resolved. Please help!

DavidZGrubb · Jun 28, 2023

how to register a dll on windows server 2012r2

how to register a dll on windows server 2012r2

Brink · Jun 28, 2023

Azure Stack Guidance against speculative execution vulnerabilities

Azure Stack guidance to protect against the speculative execution side-channel vulnerabilities

Summary

Microsoft is aware of a new publicly disclosed class of vulnerabilities referred to as “speculative execution side-channel attacks” that affect many modern processors and operating systems including Intel, AMD, and ARM.

Microsoft has not received any information to indicate that these vulnerabilities have been used to attack customers at this time. Microsoft continues working closely with industry partners, including chip makers, hardware OEMs, and app vendors, to protect customers. To get all available protections, hardware or firmware updates and software updates are required. This includes microcode from device OEMs and, in some cases, updates to antivirus software.

This advisory addresses the following vulnerabilities:

CVE-2017-5715 (branch target injection)

CVE-2017-5753 (bounds check bypass)

CVE-2017-5754 (rogue data cache load)

To learn more about this class of vulnerabilities, see ADV180002.

Overview

The following sections will help you identify, mitigate, and remedy Azure Stack environments that are affected by the vulnerabilities that are identified in Microsoft Security Advisory ADV180002.

To address these issues, Microsoft is working in partnership with the hardware industry to develop mitigations and guidance.

Recommended actions

Azure Stack customers should take the following actions to help protect the Azure Stack infrastructure against the vulnerabilities:

Apply Azure Stack 1712 update. See the Azure Stack 1712 update release notes for instructions about how to apply this update to your Azure Stack integrated system.

Install firmware updates from your Azure Stack OEM vendor after the Azure Stack 1712 update installation is completed. Refer to your OEM vendor website to download and apply the updates.

Some variations of these vulnerabilities apply also to the virtual machines (VMs) that are running in the tenant space. Customers should continue to apply security best practices for their VM images, and apply all available operating system updates to the VM images that are running on Azure Stack. Contact the vendor of your operating systems for updates and instructions, as necessary. For Windows VM customers, guidance has now been published and is available in this Security Update Guide.

FAQ

Q1. How can I tell whether my Azure Stack is affected by this class of vulnerabilities?
A1: All Azure Stack integrated systems are affected by the class of vulnerabilities that are described in the MSRC Security Advisory ADV180002.

Q2. Where can I find the Azure Stack update to fix this class of vulnerabilities?
A2: See Azure Stack 1712 update release notes for instructions about how to download and apply this update to your Azure Stack integrated system. For more information about updates for Microsoft Azure Stack, see Azure Stack Hub servicing policy - Azure Stack Hub.

Q3. Where can I find the firmware updates for my Azure Stack integrated system?
A3: Firmware updates are OEM-specific. Refer to your OEM vendor website to download and apply the updates.

Q4. My Azure Stack integrated system is not running the latest update (1711). What should I do?
A4: Azure Stack updates are sequential. You would have to apply all previous updates before you can apply the Azure Stack 1712 update. For more information, see Azure Stack 1711 Update.

Q5. I'm running an Azure Stack Development Kit (ASDK). Is that affected by this class of vulnerabilities?
A5: Yes, it is. We recommend that you deploy the latest version of the ASDK. For firmware update, see your OEM vendor website to download and apply the updates.
Click to expand...

Source: https://support.microsoft.com/en-us/...on-side-channe

Windows 10: Migration of 2012R2 VMs from a 2012R2 DC server stack into Azure HCI stack

Migration of 2012R2 VMs from a 2012R2 DC server stack into Azure HCI stack

Migration of 2012R2 VMs from a 2012R2 DC server stack into Azure HCI stack

Migration of 2012R2 VMs from a 2012R2 DC server stack into Azure HCI stack

Migration of 2012R2 VMs from a 2012R2 DC server stack into Azure HCI stack - Similar Threads - Migration 2012R2 VMs

Azure Stack HCI Failover Cluster Test report Domain Controller Error.

Azure Stack HCI Failover Cluster Test report Domain Controller Error.

Migration of 2012R2 VMs from a 2012R2 DC server stack into Azure HCI stack

Windows Server 2012R2 Auto Restart

Windows Server 2012R2 Auto Restart

Migrating AD/DC, DNS, and DHCP from Server 2003 to 2012r2

Hep with WSUS server 2012r2

Blue Screen Windows Server 2012R2

New Year’s Resolution: Evaluate Windows Server 2012R2 and System Center 2012R2