FSLogix Profile Details - OS Test

FSLogix is a container-based solution that is used to store the Windows User Profile or Office-related files (like those used with Outlook and OneDrive) of users logged into non-persistent VDI machines, within a VHD/VHDX file on a network share.

FSLogix has two container-based technologies namely Profile Containers and Office Containers. Profile Containers encompass the entire user profile while Office Containers cover the part of the user profile pertaining to Microsoft Office and supporting technologies like Microsoft OneDrive.

Profile Container moves all profile files and folders of the users into a VHD / VHDX file in the network and then mounts it as a container in the target system when the users log into the target system. This will replace the existing profile solutions where the files are copied over the network to the target system, like Roaming Profile or Universal Profile Management.

In a VDI environment, the profile container is dynamically attached to the user soon after the user attempts to log into a virtual desktop. The user profile is immediately available and appears in the system exactly like a native user profile.

If, for any reason, the profile container fails to attach to the user or takes a longer duration, then the logon process may take longer than usual or may eventually fail. Similarly, if the user exhausts the disk space allocated for their user profile, then the user's file on disk will be lost once the user disconnects the session. This will impact the productivity of the users and overall user experience with the virtual desktop. Therefore, it is imperative that administrators keep track of the time taken for attaching the Profile container to the user and the disk space allocated to the user. This can be easily achieved using the FSLogix Profile Details - OS test.

This test tracks the FSLogix profile containers created for each user and alerts administrators if any user is experiencing undue slowness while the Profile containers are being attached. This test also monitors the disk space allocated to the users and identifies the user profiles that are currently running out of disk space. This way, administrators are prompted to rapidly initiate remedial measures, so that bottlenecks can be resolved before it impacts the user experience and productivity. This test also reports additional metrics for the Summary descriptor which throws light on the following:

whether/not the FSLogix profile container is enabled
whether/not the FSLogix application service is running
the profile type
whether/not the VHD(X) file used for storing the user profile is dynamic and
whether/not concurrent user sessions are allowed for the FSLogix user profiles.

Using the metrics reported by the Summary descriptor, administrators can quickly figure out if the FSLogix profile container is enabled and if its application service is running.

Target of the test : A Nutanix AHV VDI server

Agent deploying the test : An internal/remote agent

Outputs of the test: One set of results for each user who is currently logged into each virtual desktop on the target virtual server to be monitored.

Configurable parameters for the test
Parameter	Description
Test Period	How often should the test be executed
Host	The host for which the test is to be configured.
Port	The port at which the specified host listens. By default, this is NULL
Prism Element IP	If the eG manager had discovered the target Nutanix AHV server by connecting to the Nutanix Prism Element, then the IP address of the Nutanix Prism Element server used for discovering this Nutanix AHV server would be automatically displayed against the Prism Element IP parameter; similarly, the Prism Element User and Prism Element Password text boxes will be automatically populated with the Prism Element user credentials, using which Nutanix AHV discovery was performed. If this Nutanix AHV server has not been discovered using the Nutanix Prism Element, but you still want to monitor the Nutanix AHV server via the Prism Element, then select the IP address of the Prism Element server that you wish to use for monitoring the Nutanix AHV server from the Prism Element IP list. By default, this list is populated with the IP address of all Nutanix Prism Element hosts that were added to the eG Enterprise system at the time of discovery. Upon selection, the Prism Element user and Prism Element Password that were pre-configured for that Nutanix Prism Element will be automatically displayed against the respective text boxes. On the other hand, if the IP address of the Prism Element server of interest to you is not available in the list, then, you can add the details of the Prism Element server on-the-fly, by selecting the Other option from the Prism Element IP list. This will invoke the MANAGER DISCOVERY - VIRTUAL PLATFORM SETTINGS page. Refer to the Configuring eG Enterprise to Monitor Nutanix AHV topic for details on how to use this page.
Prism Element User, Prism Element Password and Confirm Password	If the eG manager had discovered the target Nutanix AHV server by connecting to the Nutanix Prism Element, then the IP address of the Nutanix Prism Element server used for discovering this Nutanix AHV server would be automatically displayed against thePrism Element IP parameter; similarly, the Prism Element User and Prism Element Password text boxes will be automatically populated with the Prism Element user credentials, using which Nutanix AHV discovery was performed. If this Nutanix AHV server has not been discovered using the Nutanix Prism Element, but you still want to monitor the Nutanix AHV server via the Prism Element, then select the IP address of the Prism Element server that you wish to use for monitoring the Nutanix AHV server from the Prism Element IP list. By default, this list is populated with the IP address of all Nutanix Prism Element hosts that were added to the eG Enterprise system at the time of discovery. Upon selection, the Prism Element User and Prism Element Password that were pre-configured for that Prism Element server will be automatically displayed against the respective text boxes. On the other hand, if the IP address of the Prism Element server of interest to you is not available in the list, then, you can add the details of the Prism Element server on-the-fly, by selecting the Other option from the Prism Element IP list. This will invoke the MANAGER DISCOVERY - VIRTUAL PLATFORM SETTINGS page. Refer to the Configuring eG Enterprise to Monitor Nutanix AHV topic for details on how to use this page.
SSL	By default, the Nutanix Prism Element server is SSL-enabled. Accordingly, the SSL flag is set to Yes by default. This indicates that the eG agent will communicate with the Prism Element server via HTTPS by default.
WebPort	By default, the Nutanix Prism Element server listens on port 9440. This implies that while monitoring a Nutanix AHV server via the Prism Element server, the eG agent connects to port 9440.
Exclude VMs	Administrators of some virtualized environments may not want to monitor some of their less-critical VMs - for instance, VM templates - both from 'outside' and from 'inside'. The eG agent in this case can be configured to completely exclude such VMs from its monitoring purview. To achieve this, provide a comma-separated list of VMs to be excluded from monitoring in the Exclude VMs text box. Instead of VMs, VM name patterns can also be provided here in a comma-separated list. For example, your Exclude VMs specification can be: xp,lin,win,vista. Here, the * (asterisk) is used to denote leading and trailing spaces (as the case may be). By default, this parameter is set to none indicating that the eG agent obtains the inside and outside views of all VMs on a virtual host by default. By providing a comma-separated list of VMs/VM name patterns in the Exclude VMs text box, you can make sure the eG agent stops collecting 'inside' and 'outside' view metrics for a configured set of VMs.
Ignore VMs Inside View	Administrators of some high security Hyper-V environments might not have permissions to internally monitor one/more VMs. The eG agent can be configured to not obtain the 'inside view' of such ‘inaccessible’ VMs using the Ignore VMs Inside View parameter. Against this parameter, you can provide a comma-separated list of VM names, or VM name patterns, for which the inside view need not be obtained. For instance, your Ignore VMs Inside View specification can be: xp,lin,win,vista. Here, the * (asterisk) is used to denote leading and trailing spaces (as the case may be). By default, this parameter is set to none indicating that the eG agent obtains the inside view of all VMs on a Hyper-V host by default. Note: While performing VM discovery, the eG agent will not discover the operating system of the VMs configured in the Ignore VMs Inside View text box.
Ignore WINNT	By default, the eG agent does not support the inside view for VMs executing on Windows NT operating systems. Accordingly, the Ignore WINNT flag is set to Yes by default.
Inside View Using	By default, this test obtains the “inside view” of VMs using the eG VM Agent. Accordingly, the Inside view using flag is set to eG VM Agent by default. The eG VM Agent is a piece of software, which should be installed on every VM on a hypervisor. Every time the eG agent runs this test, it uses the eG VM Agent to pull relevant 'inside view' metrics from each VM. Once the metrics are collected, the eG agent then communicates with each VM agent and pulls these metrics, without requiring administrator privileges. Refer to Configuring the Remote Agent to Obtain the Inside View of VMs for more details on the eG VM Agent.
Domain, Admin User, and Admin Password, and Confirm Password	By default, these parameters are set to none. This is because, by default, the eG agent collects 'inside view' metrics using the eG VM agent on each VM. Domain administrator privileges need not be granted to the eG agent if it uses this default approach to obtain the 'inside view' of Windows VMs.
Report By User	While monitoring a Nutanix AHV server, the Report By Userflag is set to No by default, indicating that by default, the guest operating systems on the AHV server are identified using the hostname specified in the operating system. On the other hand, while monitoring AHV desktop environments, this flag is set to Yes by default; this implies that in case of VDI servers, by default, the guests will be identified using the login of the user who is accessing the guest OS. In other words, in VDI environments, this test will, by default, report measures for every username_on_virtualmachinename.
Report Powered OS	This flag becomes relevant only if thereport by user flagis set to ‘Yes’. If the Report Powered OS flag is set to Yes (which is the default setting), then this test will report measures for even those VMs that do not have any users logged in currently. Such guests will be identified by their virtualmachine name and not by the username_on_virtualmachinename. On the other hand, if the Report Powered OS flag is set to No, then this test will not report measures for those VMs to which no users are logged in currently.
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test

Measurement

Description

Measurement Unit

Interpretation

FSLogix profile container attached status

Indicates whether/not the FSLogix profile container is attached for this user.

The measure values that this test can report and their corresponding numeric values are listed in the table below:

Measure Value	Numeric Value
Not-attached	0
Attached	1

Note:

By default, this measure reports the above-mentioned values to indicate whether/not the FSLogix profile container is attached. In the graph of this measure however, the same is represented using the numeric equivalents i.e., 0 or 1.

The detailed diagnosis of this measure lists the Profile name, Volume name, VHD root file path, VHD location, Error info, Profile start date, Profile end date, Duration(Seconds), Session ID and Session name.

FSLogix profile container attached reason

Indicates the reason i.e., how the FSLogix profile container is attached for this user.

The measure values that this test can report and their corresponding numeric values are listed in the table below:

Measure Value	Numeric Value	Explanation
Attached with error	0	The FSLogix Profile has been attached with errors
Not in white list	1	The user is not a member of the FSLogix Include group, and should therefore not receive a FSLogix Profile.
In black list	2	The user is a member of the FSLogix Exclude group, and should therefore not receive a FSLogix Profile.
Local profile exists	3	A local profile for the user already exists.
Short SID	4	The FSLogix system will not handle profiles for special users.
Unset	5	The FSLogix system has been initialized to empty state.
Component not enabled	6	Component is not enabled in product key (legacy)
Windows temporary profile	7	The FSLogix profile is a Windows temporary profile.
Not AVD session	8	The FSLogix Session is not an Azure Virtual Desktop Session.
Profile load failed	9	The FSLogix Profile had failed to load.

Note:

By default, this measure reports the above-mentioned values to indicate how the FSLogix profile container is attached for this user. The graph of this measure however is represented using the numeric equivalents i.e., 0 to 4.

The detailed diagnosis of this measure lists the name of the user, reason, status, VHD location of the user profile, Error information, Profile start date, Profile end date, Duration(Seconds), Session ID and Session name.

FSLogix profile load duration

Indicates the time taken to load this user’s FSLogix profile.

Seconds

A low value is desired for this measure.

A high value for this measure indicates that the user profile is taking too long to load. A persistently high value may have an impact on the user experience and productivity.

FSLogix profile logon notification duration

Indicates the time taken for displaying this user's FSLogix profile logon notification.

Seconds

FSLogix disk capacity

Indicates the disk capacity allocated to this user's FSLogix profile.

FSLogix disk free space

Indicates the amount of space available for use in the disk allocated to this user's FSLogix profile.

A high value is desired for this measure.

FSLogix disk used space

Indicates amount of space that is already utilized from the disk space allocated to this user's profile.

A value close to the FSLogix disk capacity measure indicates that the user profile is currently running out of space.

FSLogix disk usage

Indicates the percentage of disk space utilized by this user's FSLogix profile.

Percent

A high value indicates that the FSLogix profile of the user is running out of disk space.

Is FSLogix profile container enabled?

Indicates whether/not the FSLogix profile container is enabled.

This measure is applicable only for the 'Summary' descriptor.

The measure values that this test can report and their corresponding numeric values are listed in the table below:

Measure Value	Numeric Value
No	0
Yes	1

Note:

By default, this measure reports the above-mentioned values to indicate whether/not the FSLogix profile container is enabled. The graph of this measure however is represented using the numeric equivalents i.e., 0 or 1.

Is FSLogix application service running?

Indicates whether/not the FSLogix application service is running.

This measure is applicable only for the 'Summary' descriptor.

The measure values that this test can report and their corresponding numeric values are listed in the table below:

Measure Value	Numeric Value
No	0
Yes	1

Note:

By default, this measure reports the above-mentioned values to indicate whether/not the FSLogix application service is running. The graph of this measure however is represented using the numeric equivalents i.e., 0 or 1.

Profile type

Indicates the type of FSLogix profile.

This measure is applicable only for the 'Summary' descriptor.

The measure values that this test can report and their corresponding numeric values are listed in the table below:

Measure Value	Numeric Value
Normal	0
Read-Write	1
Read-Only	2
Read-Write fall-back to Read-Only	3

Note:

By default, this measure reports the above-mentioned values to indicate the type of FSLogix profile. The graph of this measure however is represented using the corresponding numeric equivalents only i.e., 0 to 3.

Is dynamic VHD(X)?

Indicates whether/not the size of the VHD(X) files on which the profiles are placed grows dynamically.

This measure is applicable only for the 'Summary' descriptor.

Profiles are placed in VHD(X) files and mounted at run time.

If Dynamic VHD(X) allocation is enabled ie., if the value of this measure is Yes, the VHD(X) files are assigned dynamically. This means that the file size of the VHD(X) file only grows when data is added to the Profile/Office Container. If this option is not enabled, automatically created VHD(X) files will be directly allocated to the full data storage space.

The measure values that this test can report and their corresponding numeric values are listed in the table below:

Measure Value	Numeric Value
No	0
Yes	1

Note:

By default, this measure reports the above-mentioned values to indicate wwhether/not the size of the VHD(X) files on which the profiles are placed grows dynamically. The graph of this measure however is represented using the numeric equivalents i.e., 0 or 1.

Is allow concurrent user sessions?

Indicates whether/not concurrent sessions are allowed for the FSLogix profiles.

This measure is applicable only for the 'Summary' descriptor.

If the value of this measure is Yes, then it indicates that the target system is multi-session enabled and allows simultaneous logins for the same Windows account on the same server.

The measure values that this test can report and their corresponding numeric values are listed in the table below:

Measure Value	Numeric Value
No	0
Yes	1

Note:

By default, this measure reports the above-mentioned values to indicate whether/not concurrent sessions are allowed for the FSLogix profiles. The graph of this measure however is represented using the numeric equivalents i.e., 0 or 1.

Is profile using cloud cache?

Indicates whether/not the cloud cache is configured for the profile container attached to this user.

If the value of this measure is Yes, then it indicates that the cloud cache is configured on the profile container attached to each user.

The measure values that this test can report and their corresponding numeric values are listed in the table below:

Measure Value	Numeric Value
No	0
Yes	1

Note:

By default, this measure reports the above-mentioned values to indicate whether/not cloud cache is configured on the FSLogix profile container attached to each user. The graph of this measure however is represented using the numeric equivalents i.e., 0 or 1.