How to update Microsoft 365 Apps for Enterprise (aka Office) on WVD?
I have built a custom image that was originally based on the "Windows 10 multi-session + Microsoft 365 Apps" image in the Azure gallery. As far as I can tell, the Office apps are installed on this image using the settings specified in Install Office on a master VHD image - Azure | Microsoft Docs. One of those settings puts Office on the Monthly Enterprise channel, but it also disables updates. I understand that you don't want end users triggering the updates themselves, and maybe the typical sysadmin doesn't even want the updates getting installed during off-hours when nobody is logged in. But I can't figure out how to install the updates, period, even on a new image meant to replace the one in production. And I can't find this documented anywhere. I feel stupid. Help. 🙂
Windows Virtual Desktop shutdown for inactivity
We are using WVD with single provisioned host pools and single user images. This was by design. We can set auto shutdown for each desktop but we would really like to have the WVD autoshutdown after a period of inactivity and then be deallocated. Is there a solution that can do this? or is Microsoft working on this?
Lag on NV24 Session Host in WVD
We have a WVD Host pool Windows 10 Multiuser with FSLOGIX as the profile provider. Current Environment is 7 x NV24 VM, limited to 20 users per host in USW2 Standard Microsoft 365 Apps (Word, Excel, Outlook). Teams for Chat. Not integrating voice. OneDrive. IBM Access Client Solutions (5250 Emulation) UDP Shortpath disabled. 10 Locations, Fiber 10MB Connection to Internet. HQ is 100MB Fiber and has same issue. 120 users. We have users across the board that experience lag throughout the day between 5 and 30 seconds. When it occurs, we hear from multiple users that are connected to the same session host. When it occurs, CPU/Memory is below 30%. Servers are updated monthly, FSL and GPU Drivers are current. Remote Desktop Client is current. We have opened a ticket with MS several months ago, and are still fighting to get someone to own it. We have heard the standard "it is bandwidth, we don't see anything, not our group", etc. We have captured logs during a user lag and sent them. But they can find anything. They keep pointing to client, network even though we have told them when it happens it happens to multiple users on same server who are in different office locations. We migrated from RDS in Azure using NV12 VM's and could get 30-35 users per server with no lag. We did have other issues where a server would randomly reboot in RDS, but I would take that compared to this. Open to any suggestions from other NV Series WVD users who have experienced same. Thanks.. JamesWVD Personal Persistent session
Hi, we have deployed WVD in our tenant, the case here is that we have deployed WVD in personal pool session and we are evaluating the custom image that we have deployed. The problem that we are facing is that we are doing some changes in the VM, but when we disconnect the session and we tried to connect again to the VM, we are being redirected to a different VM, having different configuration and files in the VM. THere is any PS in order to configure a persistence session for VM? or does it make more sense to have a pooled session with FSLogix integration? Thanks in advance
Mac RD Client 10.3.12 Broken for WVD - no workspaces found for email address
Hi all, I've deployed several WVD using Powershell in different tenants. I have a few mac users and the latest Mac RD client does not work - it broke after an update a few months back and hasn't been fixed. If you go to workspaces, add workspace, type in the user's email address, it throws an error: No workspace is associated with this email address. The Windows client still works, as does the web client. I can't find any info online - I guess there aren't many mac users logging in to Azure hosted WVDs! Has anybody else out there experienced the same? I wonder whether this coincides with the new GUI tools in Azure which don't appear to work with WVD hostpools previously deployed via Powershell. Original post: https://docs.microsoft.com/en-us/answers/questions/55329/index.htmlMSIX app attach Azure portal integration public preview
MSIX app attach is an application layering solution that allows you to dynamically attach an application (that is an MSIX package) to a user session. Separating the application from the operating system makes it easier to create a golden virtual machine image, and you get more control with providing the right application for the right user. Previously, you had to use PowerShell scripts to enable MSIX app attach. MSIX app attach capability is now available in public preview in the Azure portal and is integrated with Azure Resource Manager. This eliminates the need for custom scripts and makes it possible to publish your packaged applications to application groups with a few clicks. Draft troubleshooting guide for MSIX app attach is available here. Overview and requirements Before you get started, make sure to fill out and submit this form to enable MSIX app attach in your subscription. If you don't have an approved request, MSIX app attach won't work. Approval of requests can take up to 24 hours during business days. You'll get an email when your request has been accepted and completed. The following are the requirements to setup MSIX app attach in a Windows Virtual Desktop environment: Host pool in Windows Virtual Desktop with at least one active session host Host pool in the validation environment MSIX packaged application expanded into an MSIX image MSIX image is uploaded to file share The file share is accessible for all session hosts in the host pool When using a digital certificate that is not sourced from a CA please follow instructions here on each VM in the host pool This video walks through the MSIX app attach UI. Deploy WVD (Windows Virtual Desktop) host pool The steps for deploying a WVD host pool are outlined here. It is mandatory to provision the session host pool in the validation environment. MSIX application MSIX app attach requires an application packaged as MSIX. If you do not have an MSIX application you can use the MSIX Packaging tool to repackage a Win32 application to MISX application. Instructions are available here. Prepare MSIX image MSIX app attach needs MSIX application to be stored in a VHD(x). Steps on how to perform the expansion are available here. If you do not have access to an MSIX application and MSIX images feel free to use these. They are provided without any guarantees and should not be used in production environments: Application name URL Chrome as MSIX image https://1drv.ms/u/s!Amut9BnVnw7mkOVMWy-sU8aiaStuxQ?e=AqwZ0D Chrome in an MSIX package https://1drv.ms/u/s!Amut9BnVnw7mkOVLPExhghP4iM8LRQ?e=wJHd9P Microsoft Edge Dev v89 as MSIX image https://1drv.ms/u/s!Amut9BnVnw7mkOVddlHiIoei4RdROQ?e=kwdvDq Microsoft Edge Dev v89 as MSIX package https://1drv.ms/u/s!Amut9BnVnw7mkOVczWWmEiUhv2IC3A?e=eBGL8B Microsoft Edge Dev v87 as MSIX image https://1drv.ms/u/s!Amut9BnVnw7mkOVbdz4gmTb7rqHoeg?e=6dEhj5 Microsoft Edge Dev v87 as MSIX image https://1drv.ms/u/s!Amut9BnVnw7mkOVaArIPkiAg5XzusQ?e=ZthNbz PowerBI as MSIX image https://1drv.ms/u/s!Amut9BnVnw7mkOVkUdswoKXTk9dfUw?e=fGTHy5 Note: this has dependencies that need to be delivered in the master image Links available here https://1drv.ms/u/s!Amut9BnVnw7mkOQth1hkT-SRdP2__g?e=YHbice PowerBI as MSIX package https://1drv.ms/u/s!Amut9BnVnw7mkOVi5SXqDxAr6MBAKw?e=pm1c2q WVDMigration as MSIX image (test different cert type) https://1drv.ms/u/s!Amut9BnVnw7mkOIEPLX6PYOzx96nrg?e=9qEpJc WVDMigrationBAD as MSIX image (bad packaging format) https://1drv.ms/u/s!Amut9BnVnw7mkOF6izJaA6rMxih_fQ?e=VU6Wbp Microsoft Edge Dev v87 as MSIX image (expired cert) https://1drv.ms/u/s!Amut9BnVnw7mkOJamDr-mrs3rOoeCg?e=43JT7E Notepad++ as MSIX image (missing cert test) https://1drv.ms/u/s!Amut9BnVnw7mkOF-o-E-bhp_btLgJw?e=6DO9ea If you are using your own application, you will need to install the certificate used to sign the MSIX package. Install certificates If you are using the provided MSIX applications, there are two certs: For Chome, Edge, and Power Bi: WVDContosoAppAttach. For WVDMigration*, WVDMigrationFabrikam Configure a file share All session hosts need access to the file share with MSIX app attach packages. This Tech Community blog covers the process. Configure MSIX app attach via Azure portal Open a browser, preferably in incognito mode, and load the following link: https://preview.portal.azure.com/?feature.msixapplications=true#home In the search bar type Windows Virtual Desktop and click on the service. Select a host pool where MSIX applications are to be delivered. Select MSIX packages. This will open the data grid with all MSIX packages currently added to the host pool. Click + Add. This will open the Add MSIX package blade. MSIX image path – this is UNC path pointing to the MSIX image on the file share. For example, \\storageaccount.file.core.windows.net\msixshare\appfolder\MSIXimage.vhd. MSIX package – if a valid, resolvable, and accessible path is provided this drop-down will be populated by all the MSIX packages in the MSIX image. Package applications – list of MSIX applications available in an MSIX package. Display name – Optional display name to be presented in the interface. Version – MSIX package version automatically delivered from parsing the package. Registration type On-demand – this is the recommended type of registration. It postpones the full registration of the MSIX application until and the user starts the application. Log on blocking – this type of registration is executing during session logon hence adding time to session logon completion. State – MSIX package has two states (Active and Inactive). When a package is active users can interact with it. Inactive packages are ignored by WVD and not delivered to users. Click Save. Publish MSIX application to an application group In the WVD resource provider navigate to the Application groups blade. Select an application group. Note: During MSIX app attach preview MSIX app attach remote apps may disappear from the user feed. The remote MSIX apps can disappear from the user feed because host pools in the evaluation environment may get served by an RD Broker in a production environment (this happens when the RD broker optimizes to improve the end-user experience). Because the RD Broker in the production environment doesn't understand the date of the MSIX app attach remote apps, it won't display them. Select the Applications blade. The Applications grid will display all currently added applications. Click + Add to open the Add application blade. Application source For desktop app groups the only source for applications is an MSIX package. For remote app group, there are three sources of applications. Start menu App path MSIX package MSIX package – display list of packages added to the host pool. Display name – Optional display name to be presented in the Applications interface. Description – Short description. Note the options below are only applicable to remote application groups. Icon path Icon index Show in web feed Click Save. Assign users to app group Select app group. Select Assignments To assign individual users or user groups to the app group, select +Add Azure AD users or user groups. Select the users you want to have access to the apps. You can select single or multiple users and user groups. Select Save. It will take five minutes before the user can access the application. Change MSIX package state Via the Applications grid Select MSIX packages. This will open the data grid with all MSIX packages currently added to the host pool. Select one or multiple that need to have their state change and click the Change state button. Via update package Select MSIX packages. This will open the data grid with all MSIX packages currently added to the host pool. Click on Package name in the MSIX packages grid this will open the blade to update the package. Toggle the State via the Inactive/Active button as desired and click Save. Change MSIX package registration type Select MSIX packages. This will open the data grid with all MSIX packages currently added to the host pool. Click on Package name in the MSIX packages grid this will open the blade to update the package. Toggle the Registration type via the On-demand/Log on blocking button as desired and click Save. Remove MSIX package Select MSIX packages. This will open the data grid with all MSIX packages currently added to the host pool. Select one or multiple that need to be removed click the Remove button. Removing MSIX application Navigate to the host pool and select Application groups. Select the application group from which the MSIX application is to be removed. From the application group blade select Applications. Select the desired application and click Remove.
[Resolved] WVD web client connection errors in Google Chrome and Microsoft Edge (Chromium)
UPDATE: This issue has been resolved in Production. A fix for pre-production environments will roll out with normal service updates. A number of users have reported issues connecting to the WVD web client using both Microsoft Edge (Chromium) and Google Chrome. The February release of the new Chromium 80 engine - used by both Edge and Chrome - included changes SameSite cookie classification. More information can be found on the Chromium blog and Chromium developer guidance. We are working on rolling out a fix to production. In the interim, please use the following workarounds to continue using the web client: Use Mozilla Firefox In your Microsoft Edge (Edge://flags) or Google Chrome (Chrome://flags) browser, disable both the SameSite by default cookies and Cookies without SameSite must be secure flags. Please note the warning presented: "By enabling these features, you could lose browser data or compromise your security or privacy. Enabled features apply to all users of this browser." We will post an update on this thread when a fix is available in production.Teams meeting button missing in Outlook
Hey all After installing Teams on my Session host (w10 multi-session) it seems like Teams Meeting button is missing from Outlook. I researched this issue and it appears to be some regedit keys that's necessary for this behavior. I have uploaded a picture of my HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect Which is set to 3 but i still don't have the teams meeting button in Outlook. I noticed that under "add-ins" in Outlook, i have a section called "inactive addins" and Microsoft Teams Meeting Add-in for Microsoft Office is appears there. I have tried turning it on, which makes the button appear. BUT!, after i myself or my users restart Outlook. It disappears again... I installed Teams via per-machine via Powershell 'ALLUSER=1' Can anyone please, help me with this issue?Microsoft Defender ATP now in preview on Windows 10 Enterprise multi-session
We are happy to announce on Microsoft Defender Advanced Threat Protection (MDATP) support on Windows Virtual Desktop enabling both single and multi-session scenarios. The support for Multi-user session scenarios is currently in Preview and limited up to 25 concurrent sessions per host/VM while the single session scenarios are fully supported. The support applies to the following operating systems: Windows 10 Enterprise multi-session, version 1809 or later Windows 10 Enterprise, version 1809 or later Windows 7 Enterprise Windows Server 2019 Windows Server 2016 Windows Server 2012 R2 Onboarding WVD devices to MDATP is done via the existing device onboarding process, follow the relevant onboarding instructions per the platform you are using: Follow these instructions for Windows 10 based VMs Follow these instructions for Windows Server-based VMs Follow these instructions for previous Windows client versions Regards, Pieter
