What is Hybrid Azure AD Join ?
Let’s just start with the official definition from the Microsoft documentation:
Hybrid Azure AD Join: Joined to on-premises AD and Azure AD requiring organizational account to sign in to the device.
This means that after the device is Hybrid Azure AD joined, it behaves the same as any other computer connected to Active Directory.
Sign in with an Active Directory account is required.
User credentials are verified against an Active Directory domain controller.
Group Policy objects for users & computers read from the domain controller are applied automatically.
After the Active Directory connection process is complete, additional steps are performed asynchronously in the background to register the device in Azure AD as well.
Continue reading “Why a Windows Server 2019 VDI should be Hybrid Azure AD joined”
The new Long Term Service Release of Citrix Virtual Apps and Desktops is now available. It contains many new features compared to the last Current Release and of course more regarding the last LTSR.
The following new features have been added compared to the last current release.
Continue reading “Citrix Virtual Apps and Desktops 7 1912 LTSR is out now”
Delivery Groups: New Studio interface for creating machine restart schedules
In earlier releases, you used Studio to create a restart schedule for machines in a Delivery Group. To create multiple schedules, you used PowerShell cmdlets. Now, the updated Studio interface enables you to create and manage one or more restart schedules.
A schedule can affect either:
Continue reading “What’s new in Citrix Virtual Apps and Desktops 7 1811”
- All of the machines in the group.
- One or more (but not all) machines in the group. The machines are identified by a tag that you apply to the machine. This is called a tag restriction, because the tag restricts an action to only items (in this case, machines) that have the tag.