Windows 10: AD Connect Sync / On-prem DC can't boot VM

Hi, We are currently experiencing a problem with our Virtual Machine that is not booting up; this is the Domain Controller, and it is deployed with the Azure AD Connect Sync agent. We only have one DC, and there is no backup for the VM. What are your recommendations and best practices for re-syncing our DC? Is it a good idea to start a new VM?

:)

 

Azure AD Banned Password List without On-Prem Agent

Hi All,

I am considering enabling banned password list for our Azure AD in our hybrid environment and want to ask, how doing that will affect our environment if we do not install the on-prem DC agent, as our on-prem does not meet minimum requirements.

Which password resets and changes will be validated through banned password list and which will not?

Will 'noncompliant' passwords synced from on-prem to Azure AD be causing issues?

TIA,

W

 

Migrating On Prem VM to Azure

Hi Experts, We have a requirement of moving out VMs as is in Azure from Current On-Prem and the process we are following is

1. Create a RAW image from an on-prem VM.
   
2. Convert the RAW image to VHD.
   
3. Move the VHD file to Azure Storage.
   
4. Convert the Disks to managed disks.
   
5. Mount the OS disk to the C drive and other disks respectively.
   

Issue - Once we mount the OS disk we are not able to RDP to the machine we have followed the steps suggested in the below links and as usual there are millions of documents and none point in the right direction unfrotunately.

Links followed to figure out options to get this done -

Prepare a Windows VHD to upload to Azure - Azure Virtual Machines | Microsoft Docs - Microsoft documentation.

Create a Windows VM from a specialized VHD in the Azure portal - Azure Virtual Machines - Microsoft documentation.

Upload a VHD to Azure and create a virtual machine - Stephanie Kahlam - Some helpful people created this and

We have tried options

1. Created image from managed disk and tried to initiate the VM and got exception as below
   Provisioning failed.
   OS Provisioning for VM 'demo-1' did not finish in the allotted time. However, the VM guest agent was detected running. This suggests the guest OS has not been properly prepared to be used as a VM image (with CreateOption=FromImage). To resolve this issue, either use the VHD as is with CreateOption=Attach or prepare it properly for use as an image:
   * Instructions for Windows: https://azure.microsoft.com/documentation/articles/virtual-machines-windows-upload-image/
   * Instructions for Linux: https://azure.microsoft.com/documentation/articles/virtual-machines-linux-capture-image/.
   
   
   and the suggested solution 1 to use CreateOption=Attach creates the VM but does not allow us to RDP to the machine so we are assuming it's not booting up. The other option suggested in the hyperlink is to create image using SysPrep which is not an option for us as we are performing a lift and shift.
   

I would like to get some guidance from experts on to the right process to follow.

 

Things to do once connected new G-Sync monitor

I'm getting my G-Sync monitor today.

I think I have to take the following steps:

• Connect 1440p G-sync monitor with DP cable
• Connect second 1080p 60Hz monitor by HDMI
• Startup PC
• Reinstall display driver
• Restart PC (I always do that after display driver install)
• Activate G-Sync in NV control panel (I believe also V-Sync is auto on after that?)
• Set my 1440p monitor from 1080p to 1440p
• Calibrate my 1440p monitor

Also ingame, I should turn off V-Sync?
Are there any problems running a second 60Hz 1080p monitor?

Is there anything else I should do/know?