To install the Azure Linux Agent on Centos 8 follow these steps:
dnf install WALinuxAgent
Enable the agent to start at boot time and start the service:
systemctl start waagent
systemctl enable waagent
Enable Azure Serial Console for replicated Linux VMs – Azure
If you replicate a Linux VM right away you might end up with the serial console not working. This could be especially an issue if you have your network interfaces set as static and you have to change the IP addresses.
To enable the Serial Console you have to log into your on-premise Linux VM and run the following:
systemctl start serial-getty@ttyS0.service
systemctl enable serial-getty@ttyS0.service
Wait until the changes will be replicated, then connect directly from the Azure Console.
Change Outlook profiles from one month cache to online in AVD/WVD
Unfortunately, at this time, there is no way to change Outlook profiles from cached mode (1 month retention) to online mode in the Outlook settings.
To configure the cache settings in Outlook (2016/365) in a WVD session you need to use Active Directory GPOs or local Group Policies.
To use local group policies follow these steps:
- Download the following ADMX in your environment: https://www.microsoft.com/en-us/download/details.aspx?id=49030
- Extract the files
- Copy the outlk16.admx file to %systemroot%\PolicyDefinitions\
- Based on the language folders you see in your WVD host copy the outlk16.adml file from the admx\xx-xx folder to the relative folder in %systemroot%\PolicyDefinitions\
- Open gpedit.msc
- Go to User Configuration > Administrative Templates > Microsoft Outlook 2016 > Account Settings > Exchange > Cached Exchange Mode.
- Set “Use Cached Exchange Mode for new and existing Outlook profiles” to Disabled
Check whether you are using an FSLogix profile in Azure Virtual Desktop – AVD
To check whether you are using an FSLogix profile in an AVD session enter the AVD instance, then browse to the following folder:
C:/Program%20Files/FSLogix/Apps
Open frxtray.exe and open the System Tray as shown in the following picture:
Right-click on the frxtray icon and click open:
From here you can see that we get “Profile status: Active”, which indicates that we are using an FSLogix profile. If you are using a local profile you will get a yellow light on the traffic light and a warning message.
Sysprep fails due to an app that was installed for a user, but not provisioned for all users
Example errors:
1. Package Microsoft.LanguageExperiencePackit-IT_19041.3.7.0_neutral__8wekyb3d8bbwe was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.
2. SYSPRP Failed to remove staged package Microsoft.LanguageExperiencePackit-IT_19041.49.150.0_neutral__8wekyb3d8bbwe. Failed to remove apps for the current user.
To fix this kind of errors, mainly found in Azure Virtual Desktop implementations with custom languages, you must manually delete the app that was provisioned just for your current user, and that is crashing your sysprep attempts.
To fix the issue, take a snapshot of the client, then remove the provisioned app package:
Remove-AppxProvisionedPackage -Online -PackageName Microsoft.LanguageExperiencePackit-IT_19041.3.7.0_neutral__8wekyb3d8bbwe
Whatever output you get, complete the removal of the app using the following command:
Remove-AppxPackage -allusers Microsoft.XboxApp_31.32.16002.0_neutral_~_8wekyb3d8bbwe
You should now be able to sysprep the VM without issues.
Error 53 when mounting Azure File Share – Azure
If you get an error 53 when trying to mount an Azure File Share, you got two main issues that might be causing it.
Port 445 is blocked
To check the effettive connection, and start the troubleshooter, run the following:
login-azaccount
$ResourceGroupName = "ba-weu-wvd-rg"
$StorageAccountName = "baweufslogixsa"
$storageAccount = Get-AzStorageAccount -ResourceGroupName $resourceGroupName -Name $storageAccountName
Test-NetConnection -ComputerName ([System.Uri]::new($storageAccount.Context.FileEndPoint).Host) -Port 445
If the error is, on the other hand, NTLMv2 is not enabled, please note that Azure files only supports NTLMv2 (not v1). Set the value of the following key to 3 on your local PC/Server:
HKLM\SYSTEM\CurrentControlSet\Control\Lsa > LmCompatibilityLevel
IdFix – Pre AdConnect assessment for your on-prem AD
IdFix is a tool to discover and remediate identity problems pre synchronization to Azure Active Directory.
To use IdFix you will need:
- A domain joined computer / server
- A user account with at least read access to the AD objects
The process is really straightforward.
Get IdFix from here:
Install and open IdFix, then click on “Query”.
After the process has been completed you will be shown all the problems you might have with your environment, if any.
If no errors are shown, or you are confident you can work around them, you can begin the synchronization.
Links:
Set up synchronization:
Microsoft guide on how to use IdFix:
How to cancel a reservation – Azure
To cancel a reservation you have to have specific permissions on the reservation order. The permissions are not inherited from the subscription, so… contact who created the reservation (or just open a ticket with the Azure Engineers).
Once you have the right account, (or you’ve been given the permissions) go to the reservations tab in the Azure Portal. It’s best to have at least a couple of people who have permissions on the resource. To get to the reservations tab follow the link below:
https://portal.azure.com/#blade/Microsoft_Azure_Reservations/ReservationsBrowseBlade
Select the reservation you want to cancel and click on the name of the resource.
From the top click on “Refund”
Click on return reserved instances once you see the “Refund subtotal” pop up
Please refer to the following docs for additional informations:
Move resources request is blocked by an Azure Backup job.
Error message:
The move resources request contains resources like “*OsDisk*” that are being backed up as part of a Azure Backup job. Browse the link https://aka.ms/vmbackupmove for information
If you encounter this error check if the VM’s backup is stopped. If it’s stopped you need to remove the istant snapshot that has been created by the system:
- Find the location of your virtual machine.
- Find a resource group with the following naming pattern:
AzureBackupRG_<location of your VM>_1. For example, AzureBackupRG_westus2_1 - In the Azure portal, check Show hidden types.
- Find the resource with type Microsoft.Compute/restorePointCollections that has the naming pattern
AzureBackup_<name of your VM that you're trying to move>_###########. - Delete this resource. This operation deletes only the instant recovery points, not the backed-up data in the vault.
- After the delete operation is complete, you can move your virtual machine.
VM has reported a failure when processing extension ‘joindomain’ – AVD
If you encounter this error while creating a new VM from the host pool wizard, try following these suggestions to solve the issue, or at least drill down on the problem:
- Check whether you can resolve your domain from your VNET
- Check what DNS Servers are configured on your VNET, correct accordingly (follow this guide: Change VNet DNS Servers)
- Check if you have permissions to join the domain using the credentials you provided
- Check if the specified credentials are correct
- Check if the domain to join (and the OU), specified in the wizard, is correct (parameters in the JSON:
domainToJoin,ouPath,existingDomainUPN,existingDomainPassword). - Try to join a VM to the domain from the same network and subnet
If all the above are met, you should be able to join the VM successfully to the domain. If not, at least you should have more context to further troubleshoot the issue.
Error opening directory /mnt in Azure Storage Explorer for Linux
When you try to upload files in Azure Storage Explorer from the /mnt or /media partition, you get a permission denied error.
The error is related to the snap version of Azure Storage Explorer. This is a common error with snap applications.
To fix, from snap, enter Azure Storage Explorer, then click Permissions.
From there enable “Read/write files on removable storage devices”
Activate Azure Update Management for on premise servers using Log Analytics
Requirements:
i. Log Analytics workspace
ii. Azure Automation Account
From the Log Analytics Workspace, click Connect a data source
Save the Workspace ID and Workspace key
Install the agent on the server, providing the Workspace ID and Key found in the workspace
Go into the automation account, then from the left into update management
Enable update management on the VM by clicking on “Click to manage machines”
You can then see the missing updates and create an update deployment
Please allow up to 24hrs for all the servers to show up (it usually takes about an hour)
Azvise 