Problem - Default file association with Remote app in WVD
We are experiencing an issue with WVD Remote apps where default file associations are not working, even though if we configure via GPO using a .xml file. Note that we are only using remote apps and not the full desktop. Any advice on how to resolve this problem? or if not would like to know if it's in the road map to address this problem. Thank You! BR, Romero SilvaWVD Scaling Script: Doesn't Logoff user sessions and stop VMs during off-peak hours
Hi, We have experienced that during the off-peak hours the scaling script doesn't logoff user sessions and stop VMs when there are active or disconnected sessions. Minimum number of running session host threshold is set to 1 Findings: Script recognize it as off-peak hours but doesn't logoff any user sessions. But we have noticed following log not sure if there is any relation. Number of user sessions is more than 90 % of the max number of sessions allowed with minimum number of running session hosts required (10). Adjusted minimum number of running session hosts required to 2 Any advice or a solution for this ? Thank You! BR, Romero Silva
App-V on Multi-Session Windows Virtual Desktop
After activating the built-in App-V client and connecting to App-V Management and publishing server infrastructure. Any Apps that use VFS within the packaged app environment report an Application error(0x0000142). The simple apps that do not use VFS work fine.
Another user is signed in. If you continue, they'll be disconnected. Windows 10 Multi Session
We have successfully rolled out our WVD Tenant after many hurdles. We are now faced with "Another user is signed in. If you continue, they'll be disconnected. Do you want to sign in anyway?" Background info on the Image. The original build came from Market place using "Windows 10 Enterprise for Virtual Desktops Preview, Version 1809". We installed and configured our apps, joined domain to enable security group etc. Installed FSLogix and made appropriate reg keys. After all was configured as we wished we did a Sysprep, Generalize Shutdown. Of course it had the standard gamet of errors regarding Applications assigned to another user. Anyway it eventually generalized and shutdown. We went to the managed disk and Captured to Azure Images. After doing all prepwork in Powershell we moved on to the Azure GUI and Deployed. We have done several restarts, shutdowns etc. Deployed and Redeployed several times. When we do a winver we are noticing license states Windows 10 Pro, screenshot attached. We have seen other screenshots around here and other places showing "Windows 10 Enterprise Multi Session" as the License. Does something happen with licensing after the Machine is generalized that is removing the Enterprise Multi Session License? I believe Documentation will need some help before this goes GA. Specifically the ordering of steps. Our biggest hurdle was likely our own fault but we were having random issues that made no sense. Specifically the same one that most have been seeing, user not authorized to query management service. We turns out we were creating all of these items in a Visual Studio Subscription that was tied to our main subscription. Once we did "set-azcontext -Name "Subscription Name" -SubscriptionId xxxx-xxx-x-xx things begin to start falling in place. You can check the context you are running under by running a "get-azcontext:.