You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-desktop/azure-stack-hci-faq.yml
+11-1Lines changed: 11 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,17 @@ sections:
37
37
Can I use Azure Virtual Desktop with other on-premises infrastructure besides Azure Stack HCI?
38
38
answer: |
39
39
No. Azure Virtual Desktop's on-premises capabilities only extend to session hosts running Azure Stack HCI infrastructure.
40
-
40
+
41
+
- question: |
42
+
Is Azure Virtual Desktop an Azure Arc-enabled service?
43
+
answer: |
44
+
No, Azure Virtual Desktop is not an Azure Arc-enabled service. It is not supported outside of Azure, in a multi-cloud environment, or on Azure Arc-enabled servers besides Azure Stack HCI virtual machines as described in this technical documentation.
45
+
46
+
- question: |
47
+
Is Azure Virtual Desktop for Azure Stack HCI available in Azure Government?
48
+
answer: |
49
+
No, because Azure Stack HCI is not currently available in Azure Government.
50
+
41
51
- question: |
42
52
Does using Azure Virtual Desktop for Azure Stack HCI mean all my data is stored on-premises?
Copy file name to clipboardExpand all lines: articles/virtual-desktop/azure-stack-hci-overview.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ We're aware of the following issues affecting the public preview version of Azur
60
60
61
61
- The Azure Virtual Desktop tab in the Azure portal can't create new virtual machines directly on Azure Stack HCI infrastructure. Instead, admins must create on-premises virtual machines separately, then register them with an Azure Virtual Desktop host pool.
62
62
63
-
- When connecting to a Windows 10 or 11 Enterprise multi-session virtual desktop, users may see a message that says "activation needed," even if they have an eligible license.
63
+
- When connecting to a Windows 10 or 11 Enterprise multi-session virtual desktop, users may see activation issues, such as a desktop watermark saying "Activate Windows," even if they have an eligible license.
64
64
65
65
- Azure Virtual Desktop for Azure Stack HCI doesn't currently support host pools containing both cloud and on-premises session hosts. Each host pool in the deployment must have only one type of host pool.
Copy file name to clipboardExpand all lines: articles/virtual-desktop/azure-stack-hci.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,20 +34,22 @@ To set up Azure Virtual Desktop for Azure Stack HCI:
34
34
35
35
1. Create a new host pool with no virtual machines by following the instructions in [Begin the host pool setup process](create-host-pools-azure-marketplace.md#begin-the-host-pool-setup-process). At the end of that section, come back to this article and start on step 2.
36
36
37
-
2.Follow the instructions in [Workspace information](create-host-pools-azure-marketplace.md#workspace-information) to create a workspace for yourself.
37
+
2.Configure the newly created host pool to be a validation host pool by following the steps in [Define your host pool as a validation host pool](create-validation-host-pool.md#define-your-host-pool-as-a-validation-host-pool) to enable the Validation environment property.
38
38
39
-
3. Deploy a new virtual machine on your Azure Stack HCI infrastructure by following the instructions in [Create a new VM](/azure-stack/hci/manage/vm#create-a-new-vm). Deploy a VM with a supported OS and join it to a domain.
39
+
3. Follow the instructions in [Workspace information](create-host-pools-azure-marketplace.md#workspace-information) to create a workspace for yourself.
40
+
41
+
4. Deploy a new virtual machine on your Azure Stack HCI infrastructure by following the instructions in [Create a new VM](/azure-stack/hci/manage/vm#create-a-new-vm). Deploy a VM with a supported OS and join it to a domain.
40
42
41
43
>[!NOTE]
42
44
>Install the Remote Desktop Session Host (RDSH) role if the VM is running a Windows Server OS.
43
45
44
-
4. Enable Azure to manage the new virtual machine through Azure Arc by installing the Connected Machine agent to it. Follow the directions in [Connect hybrid machines with Azure Arc-enabled servers](../azure-arc/servers/learn/quick-enable-hybrid-vm.md) to install the Windows agent to the virtual machine.
46
+
5. Enable Azure to manage the new virtual machine through Azure Arc by installing the Connected Machine agent to it. Follow the directions in [Connect hybrid machines with Azure Arc-enabled servers](../azure-arc/servers/learn/quick-enable-hybrid-vm.md) to install the Windows agent to the virtual machine.
45
47
46
-
5. Add the virtual machine to the Azure Virtual Desktop host pool you created earlier by installing the [Azure Virtual Desktop Agent](agent-overview.md). After that, follow the instructions in [Register the VMs to the Azure Virtual Desktop host pool](create-host-pools-powershell.md#register-the-virtual-machines-to-the-azure-virtual-desktop-host-pool) to register the VM to the Azure Virtual Desktop service.
48
+
6. Add the virtual machine to the Azure Virtual Desktop host pool you created earlier by installing the [Azure Virtual Desktop Agent](agent-overview.md). After that, follow the instructions in [Register the VMs to the Azure Virtual Desktop host pool](create-host-pools-powershell.md#register-the-virtual-machines-to-the-azure-virtual-desktop-host-pool) to register the VM to the Azure Virtual Desktop service.
47
49
48
-
6. Follow the directions in [Create app groups and manage user assignments](manage-app-groups.md) to create an app group for testing and assign user access to it.
50
+
7. Follow the directions in [Create app groups and manage user assignments](manage-app-groups.md) to create an app group for testing and assign user access to it.
49
51
50
-
7. Go to [the web client](./user-documentation/connect-web.md) and grant your users access to the new deployment.
52
+
8. Go to [the web client](./user-documentation/connect-web.md) and grant your users access to the new deployment.
0 commit comments