Share via

Troubleshooting issues with long or failed sign-ins

  • Article

Virtual machine has too many users or is too small for the workload

Virtual desktop environments allow multiple user sessions per machine, which provides a good cost benefit ratio. It's important to know the size (vCPU and Memory) and the OS disk performance characteristics as they're critical factors when deciding how many simultaneous users are on a single virtual machine. FSLogix does require network and performance of the virtual machine to operate. If your users are complaining about long sign ins, reviewing the virtual machines performance is a great place to start.

Important

Cloud Cache places an even greater performance load on the virtual machine. Size your virtual machines appropriately, starting with a 2:1 ratio (vCPU to user).

Recommendations

  • Review and understand the user density and workload placed on your virtual machines.
  • Reduce the number of simultaneous sessions per virtual machine.
  • Increase the virtual machine family or size based on user workloads.

Container size

In some cases, the user's container has reached the maximum size and without enough free space, the container fails to attach.

Note

Increasing the SizeInMBs value will affect all users with dynamic disks where configured.

Verify the container size on disk

  1. Check the SizeInMBs setting on the virtual machine.
  2. Locate the user's container on the SMB file share.
  3. Right-click the VHD(x) file and Select Properties.
  4. Compare the Size on disk value with the value from SizeInMBs from the configuration settings.
  5. The container must have more than 200 MB to attach successfully.

Increase the container size

FSLogix automatically increases the size of the container when a larger value is used in the SizeInMBs value. Once the disk as been expanded, you can manually mount the container during off-hours and investigate what is consuming the most space. Deleting content from the user's container allows it to compact1 during sign out.

1 VHD disk compaction requires version 2210 (2.9.8361.52623) or later.

Warning

Deleting the wrong data from the user's container could lead to data loss or profile corruption.

3rd Party Firewall or Intrusion Prevention Systems (IPS)

FSLogix is a file system virtualization product with two (2) Windows services and three (3) file system drivers. If there are 3rd party firewall or IPS applications installed on the same virtual machine as FSLogix, disabling those applications and reproducing the issue confirm if they're causing issues.

FSLogix under most configurations relies on using SMB as the primary protocol for communicating with storage providers. In a Cloud Cache configuration, FSLogix can use HTTPS when connecting to Azure page blobs.

Additionally, review our recommended list of exclusions to ensure there are no conflicts.

Network or DNS issues

FSLogix has a critical dependency many resources like network and DNS resolution. Users may encounter errors attaching their containers when the virtual machine is unable to communicate or resolve the name of the UNC path.

  • Test access to the storage provider from a different virtual machine.
  • Use Test-NetConnection to verify name resolution and protocol access:

    1. Select Start and Type powershell directly into the Start Menu.

    2. Select Windows PowerShell from the Start Menu.

      powershell start

      Figure 1: PowerShell in Start Menu

    3. In the PowerShell window, Type:

      • Test-NetConnection -ComputerName <server-fully-qualified-domain-name> -CommonTCPPort SMB

      powershell test net connection

      Figure 2: PowerShell Test-NetConnection output

Storage provider space issues

FSLogix relies on remote storage providers to store user containers. It's important to closely monitor your storage provider(s) for both performance and overall storage capacity. If the storage provider has reached it max size, users may encounter one or more issues:

  • Users can't create new containers and end up with a temporary or local profile.
  • Current user session becomes hung or unresponsive.
  • Users fail to mount or correctly detach containers during sign in or sign out.

Solution

Increase the capacity of the remote storage provider.