753713's Posts

logontime with appvolumes agent 4 without appstacks 70 sec., with disabled appvolumes agent 20 sec. what is wrong???
It would be nice if all PCoIP and Blast settings, in their own templates z.b. could import as xml files into smart policies. A cool feature would be synonymous, when I log in, I get a SmartPol... See more...
It would be nice if all PCoIP and Blast settings, in their own templates z.b. could import as xml files into smart policies. A cool feature would be synonymous, when I log in, I get a SmartPolicy with 2 Mbit, but if I start an application that requires more bandwidth, a different bandwidth is defined via DirectFlex.
the smart policies are super flexible, unlike admx, and can be used with triggered task
the bandwidth profiles are given, can I create ones with different bandwidths myself?
I use UEM 9.4, after configure the Bandwith Profile i cannot see the PCoIP Bandwidth configuration in: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Teradici\PCoIP\pcoip_admin_defaults and the UEM log:... See more...
I use UEM 9.4, after configure the Bandwith Profile i cannot see the PCoIP Bandwidth configuration in: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Teradici\PCoIP\pcoip_admin_defaults and the UEM log: 2018-10-10 15:59:32.218 [INFO ] Collected Horizon Smart Policies settings to apply for bandwidth profile ('SMART LAN.xml') 2018-10-10 15:59:32.234 [INFO ] Applied Horizon Smart Policies settings how can I configure it?
do you use persistent or non-persistent desktops?
do you use VDI Desktop with refresh/reset after logoff?
Hi all, is this statement correct? any VM that does not refresh on logoff is unsupported with App Volumes and therfore will affect the use of UEM
please look: map network printer on persistent desktop without writable volume
the agent 2.13.2 does not work with printer map
yes and no, with 2.13 agent and writable volume work printer mapping fine. I think, it should work without writable volume. Experts, what is the recommendation? network printer on persisten... See more...
yes and no, with 2.13 agent and writable volume work printer mapping fine. I think, it should work without writable volume. Experts, what is the recommendation? network printer on persistent desktop with or without writable volume?
Hi all, with the latest version 2.13.2 we have the same error, with the version 2.12 works fine.
the appvolumes agent 2.13 has this problem with printer, can I use the 2.12 agent with 2.13 appvolumes manager? This works fine for me.
with the version 2.13.1 the same effect. I see in the version 2.13/2.13.1 in process explorer the call to printer function ->(0043E818 FF1598554B00 call [USER32.dll!wsprintfW]), in the version 2... See more...
with the version 2.13.1 the same effect. I see in the version 2.13/2.13.1 in process explorer the call to printer function ->(0043E818 FF1598554B00 call [USER32.dll!wsprintfW]), in the version 2.12 i cannot find this.
With the Appvolumes agent 2.12 works this fine. I think since the Version 2.13 exists this problem.
in my Appstacks I have no installed printer, I test only with Notepad++ Appstack. By first login works my printer with appstack, only from the second login i have the error.
the problem is, after second login I cannot map my network printers from my print server. Whether manual, script or uem I cannot map my printes, i have the error: network connection. On the sec... See more...
the problem is, after second login I cannot map my network printers from my print server. Whether manual, script or uem I cannot map my printes, i have the error: network connection. On the second login I can map new printers (another driver, another printer type) without problem, but after the next reboot I have the same error: network connection.
hmm, I have a error by map the network printer manually, with script or uem. On my persistent desktop without writables volume (desktop not refresh by restart) I can map my network printers by fi... See more...
hmm, I have a error by map the network printer manually, with script or uem. On my persistent desktop without writables volume (desktop not refresh by restart) I can map my network printers by first logon on the desktop. By second logon I cannot map the network printers. After refresh/reset the desktop I have the same effect, by second logon I cannot map my printers, network connection error. I use appvolumes 2.13.
what is the best way to map network printer on persistent desktop without writable volume?