Forum Widgets
Latest Discussions
AVD with FSLogix - profiles not loading
Setup AVD with FSLogix several months back and profiles had been loading fine. About a month ago, profiles stopped loading and the logs show "Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced." This is in regards to connecting to the profile share path. If I manually try to go to that path, I receive the same error. The accounts do have a password, so it shouldn't be anything to do with a blank password. There are no sign-in time restrictions enforced on these accounts. What's left is a "policy restriction", which is kind of vague. Things I've tried: update to latest FSLogix verify permissions on profile storage enabled these in local policy: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options ‘Accounts: Limit local account use of blank passwords to console logon only‘ = disabled Computer Configuration > Administrative Templates > System > Credentials Delegation ‘Restrict delegation of credentials to remote servers‘ = disabled I have a ticket open with MS support for 3 weeks now, but thus far they've been completely useless.
AVD Single Session - Password is incorrect - lockout screen
Hi Guys, I hope you are all well. Recently I set up these policies for my AVD env: Set time limit for active but idle Remote Desktop Services sessions - Disabled Set time limit for active Remote Desktop Services sessions - Disabled Disconnect remote session on lock for legacy authentication - Disabled Disconnect remote session on lock for Microsoft identity platform authentication - Disabled The result is that the after some idle time session is not completely disconnected but AVD is being locking out, and that is good but - from lock screen I can't log-in again - I received info that the password is incorrect. In event viewer I see: Event ID 4673. From that place I can disconnect session, restart machine or add additional keyboard layout -> after I click "Update" I am being moved to Desktop, but still poor solution. Password is definitely correct, account is not being locked out/disabled. All machines are Entra ID Joined. Any ideas? Best regards, Damian
Sending notifications with Azure Virtual Desktop Auto-Shutdown
We have several Virtual Desktops that are used during business hours. I know I can use the auto-shutdown feature to shut the VM down at a scheduled time at night to save costs. What I would like to do is notify the logged-on users (we use personal and pooled host pools) that their VM will be shut down in fifteen or thirty minutes and give them the chance to extend by an hour in case they are working late. I saw a webhook by fortytwoservices called avd-shutdown on github that may do what I want, but the documentation on implementing it is a bit unclear to me. Is there a solution, native or add on that would send notifications like this for me? Thanks, Eric.,AVD Single Session - Password is incorrect - lockout screen
Hi Guys, I hope you are all well. Recently I set up these policies for my AVD env: Set time limit for active but idle Remote Desktop Services sessions - Disabled Set time limit for active Remote Desktop Services sessions - Disabled Disconnect remote session on lock for legacy authentication - Disabled Disconnect remote session on lock for Microsoft identity platform authentication - Disabled The result is that the after some idle time session is not completely disconnected but AVD is being locking out, and that is good but - from lock screen I can't log-in again - I received info that the password is incorrect. In event viewer I see: Event ID 4673. From that place I can disconnect session, restart machine or add additional keyboard layout -> after I click "Update" I am being moved to Desktop, but still poor solution. Password is definitely correct, account is not being locked out/disabled. All machines are Entra ID Joined. Any ideas? Best regards, Damian
duplicate fslogix profile issue
There are two profile for few users one is starting with sid_username and another with username_sid for pooled azure virtual desktop. We want all user profile having naming convention username_sid for all users. Below are the settings configured: - -Swap directory name components is enabled -flipflopprofiledirectory Name is set to 1 Any recommendation will be helpful.
Windows App, pasting files hangs OS
Hi all, We’re experiencing an intermittent but frustrating issue when using the Windows App to connect to our Azure Virtual Desktop environment. Issue: When users attempt to copy and paste certain files from their local machine to the remote session, the operating system on the remote side hangs. The mouse still moves, and the clock continues to tick, but: -Start menu becomes unresponsive -Taskbar icons stop registering clicks -Desktop icons are frozen -No error messages appear This occurs sporadically and seems to affect files of varying sizes and types — 100KB up to 20MB. What we've tried: -Updating the Windows App to the latest version -Verifying clipboard redirection is enabled -Using MSTSC, and the Remote Desktop Store App. These work but don't support Session Pools, Remote -Apps, or SSO. -Using RemoteDesktop_1.2.6228.0 (MSI Install) Has the same issue as Windows App Environment: -Remote app hosted in Azure Virtual Desktop (AVD) -Users connecting from Windows 10/11 clients -Windows App version: 2.0.419.0, 2.0.420.0, and 2.0.500.0 All ideas welcome - is a major disruption to our business processes.
Latest Remote Desktop client not starting on W10 LTSB 1607
Hello. We're using about 50 thin-clients to connect to our AVD systems. The HP t530 thin-clients are running Windows 10 Enterprise 2016 LTSB / ver 1607 / build 14393 / RS1 and have the Remote Desktop client for Windows (msi) installed, with auto update enabled. This all worked fine until the most recent releases of the Remote Desktop client. Starting with version 1.2.6186 the app simply doesn't start anymore. There's no gui, no errors, nothing. Just for a few seconds the spinning blue circle next to the cursor. It does create msrdcw_xxx.etl files in %temp%\DiagOutputDir\RdClientAutoTrace, however i couldn't locate any obvious errors in it. Upgrading to 1.2.6187 does fixes the problem temporary (but that's probably because it's actually based on the older 1.2.6081 version). Upgrading to the latest releases 1.2.6188, 1.2.6227 and 1.2.6228 reintroduces the problem. It's not something in the thin-client image, also did a fresh Win10 1607 install with latest Windows Updates, same problem. Is there anything i can do or try, except blocking all future updates and staying on 1.2.6187?
MultiMonitor Support for AVD Webclient
Hello, We have users using HP ThinPRO to connect to AVD. They normally use AVD client but that seems having latency. However user confirmed once they use AVD Webclient via browser https://client.wvd.microsoft.com/arm/webclient/ its working pretty fine. There is only one challenge as they can use more than one monitor. Is there any option to use more than one monitor with AVD webclient? Thanks PankajAVD Configuring with O365
I am in the process of setting up Azure Virtual Desktop (AVD) infrastructure for our 10 users located across South India. While most configurations are in place, I am currently encountering a few issues that need your attention: Access Issue on Laptops: I am able to successfully access AVD from mobile devices. However, when attempting to log in from a laptop, I am facing an issue. I’ve attached a screenshot for your reference. Team Error on Windows 11 with O365 Image: I have deployed the Windows 11 image with Microsoft 365 Apps. Unfortunately, when trying to access Microsoft Teams, I receive an error. Further assistance on this would be appreciated. User ID Customization: I’d like to create user IDs that are simple and easy for our users to remember. Could you guide me on where and how to configure or rename the user IDs? My test user id is email address removed for privacy reasonsPrepare now for Remote Desktop client for Windows end of support
On March 27, 2026, the Remote Desktop client standalone installer (MSI) for Windows will reach end of support. Before that date, IT administrators may need to migrate their users to Windows App so they can continue connecting to their remote resources via Azure Virtual Desktop, Windows 365, and Microsoft Dev Box. Remote Desktop client will continue to receive security updates until end of support, after which it will no longer be available for download. To learn more about how to prepare for end of support on March 27, 2026, please read aka.ms/RemoteDesktopClient.
