Error: “Your User Profile was Not Loaded Correctly” in XenApp

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

Complete the following steps to resolve the issue:

  1. Rename or delete the user’s folder in <SystemDrive>Users.

  2. Delete the Security Identifier (SID) that corresponds with the user’s account in the following registry key:

    HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionProfileList.

To locate the SID that corresponds to the user’s account, click each of the subkeys in the ProfileList, and observe the ProfileImagePath string value, as shown in the following screen shot:

User-added image


Note:

Also make sure that Citrix Profile management service is Running

    Related:

    • No Related Posts

    Load Index – Server load 10000

    We have to rebuild Performance Counters with LODCTR from an elevated command prompt.

    • Launch Command Prompt as Administrator (right click Runs As Administrator).
    • Drop into the C:WINDOWSSystem32 directory by typing CD then CD WindowsSystem32
    • To rebuild your resource counters type the following command:

    lodctr /r

    • This will rebuild your counter values and may take a few moments so please be patient.
    • Once the rebuilding operation is done, close the command prompt.
    • Restart the Citrix Desktop Service on the VDA where you have rebuild the counters.

    If the Load Index value still shows 10000 on the Citrix Studio for the VDA where the changes have been made, follow the below steps to identify if any of the Operating System counters is disabled.

    • Launch Command Prompt as Administrator (right click Runs As Administrator).
    • Drop into the C:WINDOWSSystem32 directory by typing CD then CD WindowsSystem32
    • To query the state of the performance counters, run the below command.

    lodctr /q

    This will give you something like the following:

    Performance Counter ID Queries [PERFLIB]:

    Base Index: 0x00000737 (1847)

    Last Counter Text ID: 0x000031D2 (12754)

    Last Help Text ID: 0x000031D3 (12755)

    [.NET CLR Data] Performance Counters (Disabled)

    DLL Name: %systemroot%system32netfxperf.dll

    Open Procedure: OpenPerformanceData

    Collect Procedure: CollectPerformanceData

    Close Procedure: ClosePerformanceData

    [.NET CLR Networking] Performance Counters (Enabled)

    DLL Name: %systemroot%system32netfxperf.dll

    Open Procedure: OpenPerformanceData

    Collect Procedure: CollectPerformanceData

    Close Procedure: ClosePerformanceData

    and etc

    If you find any of the performance counters disabled on the VDA server, follow the below steps to enable them.

    In the query if you have provider name that is Disabled, Use this Cmdlet to enable it.

    lodctr /e:<provider name>

    for example (think in above query Performance Counters is disable ) :

    lodctr /e:Performance Counters

    If you perform this step and it doesn’t work, please see the event log and search for if there is Event ID = 3006 in it? if yes,

    Please go to registry and change Disable Performance Counters from “1” to “0”.

    HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionPerflib

    Related:

    • No Related Posts

    On-screen keyboard in the endpoint pops up when the published desktop is launched

    Add the below registry key for disabling the pop-up and reboot the machine –

    Location: HKEY_LOCAL_MACHINESOFTWAREWow6432NodeCitrixICA ClientEngineConfigurationAdvancedModulesMobileReceiver.

    Name: DisableKeyboardPopup

    Type: Reg_Dword

    Value: 1

    Refer below documentation for more details –

    https://docs.citrix.com/en-us/citrix-workspace-app-for-windows/configure.html#printer

    Related:

    • No Related Posts

    CVAD-While Installing the Citrix components (Delivery Controller, Storefront,License )/, it prompts for reboot. Error “You must restart the machine before continuing ” “

    – On the DDC VM, run the below steps to identify the pending reboot registry.

    -1. Open an elevated PowerSell session.

    2. Install-Module PendingReboot ( Internet access required on DDC machine )

    3 . Set-ExecutionPolicy -ExecutionPolicy “Unrestricted”)

    4. Import-Module PendingReboot

    5. Test-PendingReboot -detailed

    6 – Delete the registry key mentioned in the Powershell output.

    7- Now the DDC, can be upgraded without restart prompt.

    Related:

    • No Related Posts

    “An RDS Licensing mode has not been configured by the License Server with the Per User Client Access RDS Licensing type” warning on Citrix Cloud Monitor

    Ensure that the RDS License Server is configured properly through GPO on the VDAs as per CTX238259 . You can run RSOP to verify that it is being applied.

    If the configuration is correct, check the following registry entry:

    Path: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerRCMLicensing Core

    Key: Licensing Mode

    The DWORD value needs to be 4 (if using Per User licenses) or 2 (if using Per Device Licenses)

    If you find the value to be 5, change it to either 4 or 2 and start a new session to the VDA. A reboot is not usually required.

    Related:

    XenApp Server Is Not Listening On Port 1494 Preventing Connections

    There are two solutions.

    Solution 1

    Complete the following steps to resolve the issue:

    Caution!Refer to the Disclaimer at the end of this article before using Registry Editor.

    1. Run Regedit.

    2. Navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices.

    3. Create a key named WDICA.

    4. Manually add the following values:

      ErrorControl: REG_DWORD : 0

      Start: REG_DWORD : 0x3

      Type: REG_DWORD : 0x1

    5. Reboot the server.

    6. After the reboot, a subkey named Enum will be created with the following values:

      0 : REG_SZ : RootLEGACY_WDICA000

      Count : REG_DWORD : 0x1

      NextInstance : REG_DWORD : 0x1

    7. Make a Custom ICA Connection to the server IP address. The connection should now connect successfully.

      Complete the following steps if the preceding resolution does not resolve the issue:

      1. Check if HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumRootLEGACY_WDICA and its subkeys exist.

      2. Add permissions to the key in order to save and restore the key from a working server. When this key is manually deleted and the server is rebooted, the key should regenerate automatically.

      3. If the key does not automatically regenerate, restore a copy of this key from a known good server or manually create the entries. When replacing this key with a copy of the key from another server, navigate to the following location:

        HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumRootLEGACY_WDICA000Control

      4. Delete the data of the following value located within the key referenced in step 1 and reboot the server:

        “DeviceReference”=dword:8188fd10

      5. Data should repopulate after the reboot.

        Note: The cause for the disappearance or corruption of these registry keys is currently unknown. Reboot the XenApp server after making the preceding registry changes.

        Solution 2

        Because Windows 2008 removing and re-adding the ica-tcp port creates problems due to a Microsoft change to sfi the port is not listening we would need to repair the install of XenApp to repair the ica-tcp port that is not working as follows:

        Add/Remove programs > Change > repair > XenApp 6.5.

        Related:

        • No Related Posts

    Alt+Tab Does Not Pass Through the VDI in ICA Session

    Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

    To resolve this issue change the following registry key on the client machine:

    32-bit OS:

    Key: HKEY_LOCAL_MACHINESOFTWARECitrixICA ClientEngineLockdown ProfilesAll RegionsLockdownVirtual ChannelsKeyboard

    Type: REG_SZ

    Name: TransparentKeyPassthrough

    Value: Remote

    64-bit OS:

    HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeCitrixICA ClientEngineLockdown ProfilesAll RegionsLockdownVirtual ChannelsKeyboard

    Type: REG_SZ

    Name: TransparentKeyPassthrough

    Value: Remote

    Related:

    App Layering Recipe for Java

    Licensing Considerations

    There are no licensing considerations with Java.

    Layering Naming and Versioning

    Unidesk recommends including the OS Type and OS bit level in the name, for Example Java Win7x32. For versions remember that when choosing a layer you can see the version name but not the version description. Use naming that will allow you to differentiate versions appropriately. Java is updated frequently so it is recommended to use a format of Date and Time for versions. For example while still in development/testing “2/6/2013 9:57AM QA ONLY”, but when ready for production “2/6/2013 9:57AM”.


    Installation Steps

    Java can easily be downloaded from http://www.java.com. You can also download the installer and install from a network share if desired.


    Updates

    Java, by default, will want to automatically update itself. If Java is allowed to do this, the updates will go into the personalization layer and thereby bloat the personalization with unnecessary updates. It is best to turn off automatic updates completely.

    Unidesk recommends using Group Policy to disable automatic updates or you can manually set the flag in the registry when building the application layer. If you are using 32-bit Java on a 32-bit system or 64-bit Java on a 64-bit system the key is HKEY_LOCAL_MACHINESoftwareJavaSoftJava UpdatePolicy. The entry is called EnableJavaUpdate and is a DWORD value. Setting the value to 0 will disable automatic updates. If you are using 32-bit Java on a 64-bit system the key is a little different. It can be found at HKEY_LOCAL_MACHINESoftwareWoW6432NodeJavaSoftJava UpdatePolicy. The value is still the same as above.

    There is also a java scheduled updater that gets added to the registry that needs to be removed or the updater will still run. It’s in HKLMSoftwareMicrosoftWindowsCurrentVersionRun it runs the jusched.exe file at startup and should be pulled for VDI images or any image that shouldn’t be auto updating.

    So the scheduled tasks that sometimes get added would need to be disabled.


    Considerations for Non-Persistent Desktops

    None

    Related:

    XenApp URL Redirection Does Not Work

    The multi-string value “ValidSites” when entered into the registry creates a “whitelist” of URLs to be redirected, but when the key is left in blank, with no URLs or values listed, it will prevent any URLs from redirecting to the client device.

    As per http://support.citrix.com/article/CTX106094 “…When specifying sites with the valid sites registry key, all the URLs that are not in the list, open in the server….”

    Related: