Appsense Read Registry Value and Set as Environment Variable

FAQ: FSLogix Troubleshooting Guide

Almost FSLogix

Here is an overview of what FSLogix does.

Products:

• Profile Containers: Put users' profile folder (\users\<username) in a VHD(ten) and connect at logon to roam profiles without streaming.
• Office Containers: Put users' Microsoft Office cache files in a VHD(x) and connect at logon to roam Office data without streaming.
• Application Masking: Provide a mechanism to:
  • Hide or redirect files/folders/registry keys/ registry values
  • Set values for registry values
  • Hide Fonts or Printers
  • Redirect Webpages or Programs to the right version of Java.
• Cloud Cache (CCD): Prior to Cloud Enshroud (CCD) storage for FSLogix was in ane SMB location per container type, (though they tin be both in the same share with no naming collision by default).
  • The reason for separate shares is that the Contour containers demand better performance and backup. The Office container doesn't need to be backed upwardly since it can be automatically recreated from Exchange mailboxes and OneDrive locations (and so, it tin can exist stored on cheaper storage simply doesn't have to be).
  • Now with Cloud Cache (CCD) it can exist stored in multiple locations for backup and high availability requirements (ii locations is typical, each boosted location causes more overhead and slower performance). They tin be SMB or AzurePageBlob locations.

Components:

• The FSLogix agent runs client side (There are no external processes on other machines).
• Storage is in a VHD or VHDX.
• There are 2 services and 3 drivers (all properly signed through the HLK). https://docs.microsoft.com/en-us/fslogix/fslogix-installed-components-functions-reference
  • Services: frxsvc.exe, frxccds.exe
  • Drivers: frxdrv.sys, frxdrvvt.sys, frxccd.sys
• In that location are two admin installs (These can be on users' machines but typically are not.)
  • Application Rules Editor : For creating rules for hiding/redirection/registry set value/fonts/printers https://docs.microsoft.com/en-united states/fslogix/application-masking-users-groups-ht
  • Coffee Rule Editor: For creating java rules https://docs.microsoft.com/en-us/fslogix/java-version-command-rules-ht

Install

On the client side there is the FSLogixAppsSetup.exe. In that location is a Win32 and an x64 version of FSLogix (which must match the bitness of the Os every bit FSLogix won't install if mismatched).

Note: No matter the bitness of .exe files, the x64 FSLogix amanuensis volition work with x86 .exes on x64 systems.

Upgrade procedure:

1. You tin install a newer released version of FSLogix over a previous released version and and so reboot after upgrade.
2. For any other version changes, you need to uninstall FSLogix from Add/Remove programs and reboot before yous install the new version.

Versions:

You lot will need to upgrade to one of the two versions below to get support.

Note: FSLogix previously used two numbering systems for releases, a simple version number, like 2.8.11 and a longer build version, like 2.viii.6862.41985. You lot may find a simple version number online, only the properties of the files it shows the longer build number. The utility frx.exe [c:\programs files\fslogix\apps\frx version] also shows the longer build number. Since the July 2019 FSLogix release, following Microsoft standard naming conventions, releases at present evidence the simple version number plus the year and the month.

• Electric current version – Nearly customers should be running this version since this is the only version which is getting new bug fixes: FSLogix Apps 1907 (2.9.7117.27413) – Found at: https://aka.ms/fslogix_download with details at: https://docs.microsoft.com/en-usa/fslogix/install-ht
• Previous long-term service release – This version is also stable but does non have the Cloud Cache (CCD) feature and should only be used if there is a specific issue you are trying to resolve (this long-term release will likely exist replaced in the next 6 months to one year): FSLogix Apps 2.8.11 LTSR HF3 (2.8.6862.41985) – Institute at: https://support.fslogix.com/index.php/downloads/download/download/1fa77ff8107fda8df939321ca0bbb56190be43ddf3b0d4bdd4fb94900c1e9453

Licensing:

Until the July 2019 release, FSLogix used a license key, just the new version does not crave a license fundamental. If y'all are using an older version [c:\programs files\fslogix\apps\frx validate-key] will show the status of the license. This is likewise shown at the top of whatsoever FSLogix logs files. If your license primal is expired, you can utilise this key [MSFT0-YXKIX-NVQI4-I6WIA-O4TXE] for any current version. This cardinal has no expiration and includes all FSLogix features. Entitlement for FSLogix is now provided via Microsoft via Office and Windows SKUs at: https://docs.microsoft.com/en-us/fslogix/overview#requirements (Most customers with RDP or Office 365 licenses are entitles to use FSLogix).

Diagnostics

Control Line Tools:

• To see if the amanuensis is running from a command prompt run these commands:

SC query frxsvc

SC query frxccds

(The results should testify 'running'.)




• To see if the services are running, from a elevated command prompt run this control:

Fltmc

(The results should show: frxdrv, frxdrvvt, and frxccd in the list returned.)




Logs:

FSLogix logs are designed to be intuitive to read and empathise. Logs are found at c:\programdata\fslogix\logs and are separated by day. Two days' worth of logs are retained past default and tin can be increased by following the instructions from: https://docs.microsoft.com/en-united states/fslogix/logging-diagnostics-reference. Logs don't take much space, so they can safely exist set for many more than days if needed. Logs can too be redirected to a network share for non-persistent environments. There is one FSLogix log which is outside the normal location - \program files\fslogix\apps for Cloud Enshroud (CCD).




Operational Flow:

Hither is an overview of the basic operational flow of Profiles containers and Office containers that can be seen in the FSLogix logs:

1. User starts logon by entering password, PIN, fleck/carte etc. Doesn't affair to FSLogix.
2. FSLogix is notified very early in the logon process by Windows that the logon is starting.
3. FSLogix checks to see if the user should be using an FSLogix container. If non, FSLogix lets logon keep and doesn't practise annihilation.
4. If the user should become a container, FSLogix searches for existing VHDs. If they don't exist, they are created.
5. The VHDs are connected and the logon proceeds.
6. Every bit long as the user stays logged on, FSLogix containers stay continued (however, network issues or storage location admission bug can crusade problems.
7. User logs off.
8. Windows notifies FSLogix of log off.
9. FSLogix flushes buffers and disconnects the VHDs.
10. Windows finishes the logoff process. Note: Systems that shut the ability off and practise non let Windows to get through the normal logoff process tin crusade corruption issues with containers (as well every bit other problems).

Configuration Settings:

Almost all FSLogix configuration is washed through registry settings. FSLogix includes an .admx and .adml file for GPOs to allow configuration to exist handled through Active Directory (Advert) Group Policy.

Note: Some registry settings cannot exist prepare through a GPO as they need to be read too early in the boot process that a GPO can't set up them early on enough.

The cardinal configuration items are:

• Registry
  • Location to store files
    • VHDLocations or CCDLocations
    • CCDLocations overrides VHDLocations if they are both fix.
  • Enabled
• Membership of Local Group includes users to get FSLogix containers.
  • Note: past default, anybody is put into the include group. Typically, administrators should be manually added to the Exclude group. There is an Include and Exclude group for Profiles and Office containers.
• Difference of multiple sessions on same machine vs. beyond machines.
  • Multiple sessions on the aforementioned automobile are handled by the Windows Bone. FSLogix just connects the VHDs on the outset session.
  • Concurrent sessions across different servers:
    • Concurrent sessions – ConcurrentUserSessions reg value.
    • Profiles – ProfileType reg value
    • Part – VHDType reg value

Configuration references are found at:

• Registry Configuration:
  • Profiles: https://docs.microsoft.com/en-united states/fslogix/profile-container-configuration-reference
  • Role: https://docs.microsoft.com/en-us/fslogix/function-container-configuration-reference
  • Cloud Cache CCD: https://docs.microsoft.com/en-us/fslogix/deject-cache-configuration-reference
• Quick outset guides:
  • Profiles: https://docs.microsoft.com/en-united states/fslogix/configure-profile-container-tutorial
  • Office: https://docs.microsoft.com/en-united states of america/fslogix/configure-office-container-tutorial
  • Cloud Cache CCD: https://docs.microsoft.com/en-united states/fslogix/configure-cloud-enshroud-tutorial
  • Awarding Masking: https://docs.microsoft.com/en-us/fslogix/implement-awarding-masking-tutorial

Containers

Contour containers and Office containers can be used together. Profile containers alone will do everything Profiles containers + Role containers together will do, merely the VHD(x) file tin can become very large (generally Outlook .OST file and OneDrive cache) and customers may want accept them separated. Office containers can as well piece of work with other profile management solutions (such as: Microsoft roaming profiles, Microsoft UPD, Citrix UPM, Citrix WEM, VMWare UEM, Ivanti AppSense or RES.)

Profiles:

• To check that a user is getting an FSLogix profile, from command prompt run the post-obit control:

C:\program files\fslogix\apps\frx list-redirects (you can also listing-rules)

(The results should evidence the paths that are an alternate fashion of referencing the drives on a machine; HardDiskVolue2 is typically, the c: bulldoze. the location of the VHD is later the =>.)




• If something seems strange, to check the details on the names run the following commands from a elevated command prompt:

fltmc volumes

Diskpart

• List volume
• List vdisk
• You tin also employ Deejay Managing director to run across if the disks show as attached.

The profile disk by default is named Profile-<username>




Notation: on multi-user systems this command will evidence the redirections for all users logged on to the system and there for the listing can be quite long.

Troubleshooting Profiles:

• Where are the files are going? Are they going to the FSLogix VHD or somewhere else?
• Is some other profile solution in use? If so, is it putting files the files in another location?
• Try calculation a drive letter to the FSLogix disk and scan to it to run across if information technology contains what y'all expect. A profile should look like a profile. Exactly the same files and folders. When you are done, you tin remove the drive alphabetic character, but don't disconnect the drive or volition crash session.
• FSLogix creates a local_<username> folder when a user is logged on with an FSLogix profile. There are default files in this folder that should be removed at logoff. If not, FSLogix will try to remove these files at the next logon. Files in the folder will be deleted at logoff and can go on the Contour VHD from growing larger with temp files. User tin can control other file locations with redirections.xml (see https://social.msdn.microsoft.com/Forums/windows/en-US/029e130e-5892-4d1f-88a7-f8046d78f3b0/using-redirectionsxml-to-configure-what-to-copy-to-a-profile-with-fslogix?forum=FSLogix ).
• Do a quick scan of relevant logs (Profile, Part, and Search logs). These logs when in proper functioning nearly never have errors (most common exception: [Fault:0x80070005] SHSetKnownFolderPath fault (Error: 2147942405 / Access is denied.). Other logs can accept errors which are beneficial, and then y'all typically don't demand to await at those other logs unless they appear to be direct related to a feature causing a problem. (Meet https://docs.microsoft.com/en-us/fslogix/fslogix-fault-codes-reference )

Office container

Part containers piece of work almost the same as Profile containers. And so, the aforementioned general troubleshooting steps utilize. Some differences are listed below.

• To check that a user is getting an FSLogix Office container, from command prompt run the following control:

C:\program files\fslogix\apps\frx listing-redirects (y'all can also list-rules)

(The results should show the paths that are an alternating mode of referencing the drives on a machine; HardDiskVolue2 is typically, the c: drive. the location of the VHD is later the =>.)




Note: For the Role container at that place can be additional items redirected if there are additional Office components beingness used. And, on multi-user systems this command will show the redirections for all users logged on to the system and there for the listing can be quite long.

Office container deejay default proper name is O365-<username>.

Note: FSLogix Office container works with all versions of Office higher up Role 2013 whether the traditional versions or from Role 365.

Function containers attach to many different locations in the profile. These depend on the features which are enabled. The feature to handle some Microsoft Part components are enabled by default and others are non (Run into: https://docs.microsoft.com/en-us/fslogix/office-container-configuration-reference).

Application Masking and Folder Redirection

FSLogix is congenital on the cardinal components of registry, file, and folder manipulation. The drivers spotter calls to the file organization and registry and can act on those calls if they match the criteria for the rule to be applied.

Criteria for a dominion to be applied can exist:

• File/folder/reg cardinal/reg value proper name or path
• Assignment past user/group/IP address, etc.

FSLogix Masking and Redirection allow items similar the following to be configured depending on the dominion and how it is assigned:

• Icons and folders and files will be subconscious or not.
• Registry keys and values will be subconscious or not.
• Registry values will be changed or not.
• Access to files, folders, registry keys and values can be redirected from ane location to some other.

These actions let you to configure results such as:

• Installed programs to be hidden.
• Different versions of the aforementioned plan to be installed on the same machine and users to only see one or the other when they logon.
• Allowing different users to 'see' the same registry value with different values.
• Allowing programs that generally just work for one user because of the way they store data, to work for multiple users.

FSLogix rules are created with the editors and consist of a pair of files placed in the \program files\fslogix\Rules binder, which are processed by the FSLogix service.

• .fxr is the rule file.
• .fxa is the assignment file.

The files in the rules binder stay the aforementioned, only new compiled rule files for the driver to read and enforce, are placed in the \plan files\fslogix\CompiledRules folder.

• .fxc – the dominion file
• .fxac – the assignment file

The compiled files are besides readable and tin can be compared to the test files. Some rules tin accept a wild-card character [*] but they are not sub-string wildcards. They only replace a total segment of the path whether in the registry or the file system.

Troubleshooting rules:

• Validate that the compiled files of the rules exist.
  • Compare the compiled rule files to the examination files to ensure they are the same. Sometimes the rule editor doesn't work for special situations. Remember that compiled dominion files tin can be edited by hand. Make sure that tabs are included in any file you manually edit as the tabs are required to parse rule files.
• Validate that the order of assignments is correct.
  • In the assignments, proceed in mind that rules are evaluated top to bottom, then the last rule going downwardly the listing which the current user 'fits' will determine whether or not the dominion is applied. The consignment is tied to: a user, a group, or an IP address, to decide whether the rule should exist practical for a user.
• Environment variables can exist used in paths as long every bit they be on the system when FSLogix needs to utilize them.
  • Sometimes Surround variables only get set afterward the shell is open up for their path to the users Contour VHD. So, that won't work since FSLogix attaches the VHD for the Profile earlier the Crush is operating. If FSLogix tin can't find the VHD file considering the path has an environs variable which is non defined, the user tin't logon.

Encounter Also:

Search Troubleshooting

Outlook Search Troubleshooting Guide

childresspriagenction.blogspot.com

Source: https://social.msdn.microsoft.com/Forums/en-US/8a495cb9-d025-4b34-a122-e1c387d35a0b/faq-fslogix-troubleshooting-guide

Share this post