Jump to content

Daniel Weszligling

Legacy Group
  • Posts

    26
  • Joined

  • Last visited

Posts posted by Daniel Weszligling

  1. 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

  2. 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.
  3. 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.

  4. 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

  5. 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

×
×
  • Create New...