This KB adds ability to replicate VM groups and VMs that use shared VHDs! (I’ve not tested yet)
This KB describes an issue in which end users can’t track the shared disk ownership change if Guest clustered virtual machines (VMs) with shared disks are running Windows Server 2012 R2 or Windows Server 2012.
Notes
It’s important in scenarios such as replication tracking where the disk changes are tracked. This fix is applicable only for scenarios where the guest OS runs on the VM that’s running Windows Server 2012 R2 or Windows Server 2012.
After you apply this hotfix, you can track the ownership changes of the disk between Guest clustered VMs by using a CLUSCTL_GROUP_GET_LAST_MOVE_TIME cluster control code in a shared Virtual Hard Disk (VHD) guest cluster scenario.
Prerequisites
To apply this hotfix, install update 2919355 in Windows Server 2012 R2.
#Import Rights Management module
Import-Module aadrm
#Get credentials (global administrator)
$cred=Get-Credential -Credential rlevchenko@<tenantname>.onmicrosoft.com
#Connect to RM Service and activate it.
Connect-AadrmService -Credential $cred -Verbose
VERBOSE: https://admin.eu.aadrm.com/adminV2/admin.svc
A connection to the Windows Azure AD Rights Management (AADRM) service was opened for rlevchenko@<tenantname>.onmicrosoft.com.
Enable-Aadrm -Verbose
The Rights Management service has been successfully enabled although additional
configuration of other services might be required. For more information, see h
ttp://go.microsoft.com/fwlink/?LinkId=251909.
#Add user to RMS administrators group
Add-AadrmRoleBasedAdministrator -EmailAddress "user1@<tenantname>.onmicrosoft.com"
user1@<tenantname>..onmicrosoft.com was added to the list of administrators for the
Rights Management service.
#Disconnect from RM Service
Disconnect-AadrmService -Verbose
Connection to the AADRM service closed.
#I have already connected to MS online so it's not necessary to execute Connect-MSolService.
#Reset user's password to random password. User will be required to set new password on the next sign in.
Set-MsolUserPassword -UserPrincipalName user2@<tenantname>.onmicrosoft.com
Toha1184
#....Not to random password
Set-MsolUserPassword -UserPrincipalName user2@<tenantname>.onmicrosoft.com -NewPassword Pass123!
Pass123!
#Set expiration of password
Set-MsolUser -UserPrincipalName user2@<tenantname>.onmicrosoft.com -PasswordNeverExpires $true
#Set password expiration policy
Set-MsolPasswordPolicy -DomainName <tenantname>.onmicrosoft.com -ValidityPeriod 90 -NotificationDays 14
#Get password expiration policy
Get-MsolPasswordPolicy -DomainName <tenantname>.onmicrosoft.com
ExtensionData NotificationDays ValidityPeriod
------------- ---------------- --------------
System.Runtime.Serializ... 14 90
#First step it is to delete user with "soft" option
Remove-MsolUser -UserPrincipalName user3@<tenantname>.onmicrosoft.com -Force
#Delete user from recycle bin = hard delete
Remove-MsolUser -UserPrincipalName user3@<tenantname>.onmicrosoft.com -RemoveFromRecycleBin -Force