Taskbar Preview and Window Peek Does Not Function Correctly on Published Apps

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

Dynamic preview for multi monitors are disabled by default; this can be enabled by using below registry:

For 32 bit-

HKEY_LOCAL_MACHINESOFTWARECitrixICA ClientEngineLockdown ProfilesAll RegionsLockdownVirtual ChannelsSeamless Windows

Name: EnablePreviewForMultiMonitor

Type: REG_SZ Value: TRUE

For 64 bit-

HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeCitrixICA ClientEngineLockdown ProfilesAll RegionsLockdownVirtual ChannelsSeamless Windows

Name: EnablePreviewForMultiMonitor

Type: REG_SZ Value: TRUE

OR

In the default.ica file for the Web Interface or StoreFront, in the [WFClient] section, add the entry “EnablePreviewForMultiMonitor=TRUE”.

Related:

Updates to Management Agent – For XenServer 7.0 and later

For Windows 8.1, Windows 10, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server Core 2016, Windows Server 2019, Windows Server Core 2019:

  • xenbus 9.0.0.41
  • xeniface 9.0.0.11
  • xennet 9.0.0.7
  • xenvbd 9.0.0.30
  • xenvif 9.0.0.19

For Windows 7, Windows Server 2008 SP2, Windows Server 2008 R2 SP1:

Related:

Site Server – Task Service: “Installed, inactive”

I need a solution

Hi there

We’re running SMP 8.1 RU4 and I’ve just had to setup a new site server for one of our sites as the old site server was on Server 2008 R2 and needed to be retired.

The new site server is on 2012 R2.  Having battled at length to get get the IIS pre-reqs setup and the right .NET version installed (server kept auto updating via Windows update to 4.8), I finally got the SMP console to allow me to install the Task Service.  It also has the Package Server role.

However…  Although now the Task Servic is apparently installed, it’s showing in the console as “Installed, inactive”.  I’ve no idea why.

Any ideas please?

0

Related:

Distribute Disk Image: Unable to boot to Windows automation

I need a solution

Hello, I have a Windows Server 2012 R2 server with GSS 3.3 installed. Client computer OS is Windows 10, Disk Management looks like this:

Create image command: -CLONE,MODE=CREATE,SRC=2,DST=%IMAGE_FILENAME% -SURE -IB -SPLIT=0 -Z3

Restore command: -CLONE,MODE=PRESTORE,SRC=%IMAGE_FILENAME%:4,DST=2:4 -sure

The create image job works fine. Restore image job also works for the first time but failed for the second time, job status displayed “Unable to boot to Windows automation”.

I searched a little bit in this Forum and found similiar posts, e.g. 

https://www.symantec.com/connect/forums/add-automa…

https://www.symantec.com/connect/forums/unable-boo…

For my situation, if the default boot setting is not correct initially, how the restore image job success for the first time? I am wondering, besides of checking boot order, is there any place I can check? Please advise, thank you in advance.

0

Related: