[Unable to use Environment Variable set by WEM at first logon of a new user with published apps]

Removed anything from the autolaunch but without success, if a new user without launch a published app the first time settings are missing.

At the second logon the user could use the apps and the settings are working.

[Unable to use Environment Variable set by WEM at first logon of a new user with published apps]

Hey James,

we are refreshing the cache on machine startup.

I tested some more and could see that Citrix Files is configured for Autolaunch and kicks in while my published app is starting.

I will disable the Autolaunch of Citrix Files and test again.

[Unable to use Environment Variable set by WEM at first logon of a new user with published apps]

Hey James,

thanks for your fast respons, tried it with this way you descripted in this blog post but without success.

I have to check some settings on my servers, if there are any autolaunch apps in the background and will test again.

 

Best regards,

Daniel

[Unable to use Environment Variable set by WEM at first logon of a new user with published apps]

Hello guys,

we have an interessting problem with Environment variables set by WEM.

If a new user launch the first time a published application the Environment variables are listed under HKCU:\Environmentt but the user or an other application could not use this variables.

After logoff and logon again the user or an other application could use the variables.

If our new user launch a published Desktop first instead of a published app the user or an other applicatopm in the session could use the variable immediately.

 

Does anybody has an idea why published Desktops and published apps Show here an differently behavior?

 

Best regards,

Daniel

[PVS 7.15.9 (CU3 Update Process)]

the easiest way would be an inplace upgrade of the pvs Server.

1. update the pvs console on your Server.

2. update the first pvs Server

3. After update the first pvs Server, Launch the config wizard, generally you could click next. At the end of this you would asked to upgrade the pvs database. (The Account which Launch the wizard Need the permissions on the database)

4. update the remaining pvs Servers.

 

You could take a look at the blog of Carl Stalhood here: https://www.carlstalhood.com/provisioning-services-server-install/#upgrade

[PVS 7.15.9 (CU3 Update Process)]

Hi,

thats new for me I had tried it a while back to let the PVS Server on an older 7.x Version and update only the PVS target device driver to the newest 7.x.

For me it Ends that my vDisk with the newer target device driver would not boot. After I update the PVS Server to the same Version it works.

 

The Supported way by Citrix is to update PVS Server first and then the target device driver, the VDA Version is irrelevant at this Point.

 

Here the text from a CTX articel with link to it:

 

PVS target and server version compatibility

Question and Answers

Q: Can a PVS environment be configured with PVS target version higher than the PVS server version?

A: No, The PVS target version should be the same as the PVS server version
Configuring PVS environment with PVS target version higher than the PVS server version may work however if there is an issue that need to be troubleshot by support then it will be considered unsupported configuration

It is recommend to upgrade the PVS server first and then upgrade the targets. This is the way engineering tests the product for upgrading, Engineering does not test newer targets with older PVS servers

https://support.citrix.com/article/CTX225210

[PVS 7.15.9 (CU3 Update Process)]

Yes you could update your PVS Server and let your target devices on the old target device Software.

The new PVS Server could communicate with the old target device Driver.

The other way updating target device driver first and let the PVS Server on an older Version would not work.

[PVS 7.15.9 (CU3 Update Process)]

No that is not correct, if you update your PVS Server and let your VDA on an older target device Version it will boot.

If you install a newer target device Software as your PVS Server, this vDisk will not boot.

 

Your PVS Server must be newer or on the same Version as your pvs target device Software.

 

[WEM 1811 Application Icon File Path Bug (?)]

In 4.7 it's converted correctly, too. It Comes with 1808.

[Pass Username and Password via URL]

Have you take a look at the blog from Carl Stalhood?

He describes single sign on for the director here http://www.carlstalhood.com/director-7-16/#directorsson

regards

Daniel

[VHD Replication issues, Server not available]

Hi,

have you configured an active directory account for the pvs services with the pvs configuration wizard?

If you have configured an active directory account is this in the local admin group on both servers?

[VHD Replication issues, Server not available]

How are you sync your vhd and pvp files from PVS01 to PVS02? 

The vDisk Replication Status shows you only if both PVS Servers have the same files for the vDisk you are looking for. It would never start a sync of these files.

 

[Failed to validate the Domain User and Password]

Have you tried to reboot the ELM appliance? Had a similar problem, after the reboot of the appliance it worked for me.

 

Regards,

Daniel

[VDA stays unregistered until login]

I had this issue with an earlier version, the only thing that helped was to install the VDA new.

Take a look at this post https://discussions.citrix.com/topic/387949-app-servers-remain-unregistered-unless-i-rdp-to-them/#comment-1974289

[Host Connection time out during initial configuration]

Have you tried to enter the fqdn and ip of your vcenter server to the local hosts file of your delivery controller?

Or is there a firewall?

[XenDesktop 7.9 - RDSH- Maximum Desktops per User]

Hi Christian,

 

have you try it with this steps, descripted here? https://docs.citrix.com/pt-br/xenapp-and-xendesktop/7-9/install-configure/delivery-groups-manage.html

 

1. Select Delivery Groups in the Studio navigation pane.
2. Select a group and then select Edit Delivery Group in the Actions pane.
3. On the Desktop Assignment Rules page, set the maximum desktops per user value.
4. Click Apply to apply any changes you made and keep the window open, or click OK to apply changes and close the window.

[User Desktop Session Disconnects at startup]

Have you installed print drivers on your vda where you try to connect?

[User Desktop Session Disconnects at startup]

It is possible for you to create an test account which have only permissions to connect to your citrix application and desktop without mapped printers and network shares?

In the past I had a similar problem which was triggered from a printer which was mapped to the user but no longer exists. Citrix try to map the non existing printer and crashed on this try. After removing the printer anything works fine again.

[User Desktop Session Disconnects at startup]

Have any user this problem?

What you could try is to create a new user in your AD and give this one the permission to connect to your application or desktop but without any printer or mapped drive if this is possible.

[User Desktop Session Disconnects at startup]

Have you the same problem if someone connect via rdp to the machine?

[User Desktop Session Disconnects at startup]

could you check if your vda would loose the registration in studio if a user connect to it?

Have you checked the event logs of your vda, storefront and delivery controller?

[Prevent annoying popup 'An account is not configured. Please contact your administrator']

Hi,

 

maybe this one would help you http://discussions.citrix.com/topic/373967-fix-how-to-get-rid-of-the-annoying-add-account-window-after-44-upgrade/

[XenApp slow logon times, user get black screen for 20 seconds.]

Alternativly I have try it with this in a powershell script as logon script and it worked for me, but without any warranty so use it on your own risk!

 

#WMI Query for the SID of the User which is logging in and put it in the SID Variable

$SID = (Get-WmiObject win32_useraccount -Filter "name = '$env:USERNAME' And domain='$env:USERDOMAIN'").SID

#Delete the SHC Key for the User
Remove-Item -Path REGISTRY::HKEY_USERS\$SID\SOFTWARE\Microsoft\Windows\CurrentVersion\UFH\SHC -Recurse

[XenApp slow logon times, user get black screen for 20 seconds.]

Could you find this Registry under HKCU\Software\Microsoft\Windows\CurrentVersion\UFH\SHC\ and delete this one at logon?

So you don't need the SID of each user for the HKU\S-1*\Software\Microsoft\Windows\CurrentVersion\UFH\SHC\

[XD 7.9 on vSphere - Migration to new vCenter]

Hi Robert,

 

I think it is not possible to migrate your existing catalogs and VDAs to the new vCenter, because if you create a catalog it is mapped with some unique IDs to your hypervisor, the network, storage etc. So you have to create your catalogs and the VDAs new.

 

Please take a look at CTX140041 for more Information about this.

 

What you could migrate is your Infrastructure like your PVS Server, Storefront Server and the DDCs for example.

 

Regards

Daniel