Malkware's Posts

OS: Windows 10 1909 Agent: Horizon 7.12 - Integrated Printing Issue: After applying February's updates any printer that uses the VMware Universal EMF Driver no longer functions. We receive various... See more...
OS: Windows 10 1909 Agent: Horizon 7.12 - Integrated Printing Issue: After applying February's updates any printer that uses the VMware Universal EMF Driver no longer functions. We receive various errors depending on the application, but nothing definitive. If we have a printer on the client that, in the VM, uses the expected driver (eg Sharp printer driver), then that printer will function correctly. Does anyone have any ideas?
Update: I managed to get the application by itself into an AppStack. I am then able to update that appstack for each Dept as needed. However, sometimes the Service in question disappears durin... See more...
Update: I managed to get the application by itself into an AppStack. I am then able to update that appstack for each Dept as needed. However, sometimes the Service in question disappears during the update process. WHY?!
Hello, I'm working on virtualizing PSICapture in 2.18 appstacks. PSICapture has a service called Capture Services that is configured for Automatic Start. I'm having a difficult time doing so. ... See more...
Hello, I'm working on virtualizing PSICapture in 2.18 appstacks. PSICapture has a service called Capture Services that is configured for Automatic Start. I'm having a difficult time doing so. Symptom: In both new AppVol and in Updated AppVol when the AppVol is assigned, the Capture Services service isn't Started when a user logs in. In other new AppVols and Updated AppVols the service will be started when the user logs in. I have not seen in logs where the Service is even attempted to be started after attachment. So, it doesn't appear that AppVol Agent thinks it needs to start the service after registering it. Behavior Summary: Update AppVol or Created new AppVol Install & Configure Application Assign AppVol User logs in Service is registered Service is not started Update AppVol or Created new AppVol Install & Configure Application Assign AppVol User logs in Service is registered Service is started All capture steps are the same between scenarios. Is there a way to manually edit the AppVol and force the agent to start the service? Or someplace else to check?
MobaXterm UEM Configuration Files
Windows 10 1809          UEM 9.6 Cisco Jabber v11.9.3 Build 60004 UEM Profile: [IncludeRegistryTrees] HKCU\Software\Cisco Systems, Inc. HKCU\Software\IM Providers\Cisco Jabber [Includ... See more...
Windows 10 1809          UEM 9.6 Cisco Jabber v11.9.3 Build 60004 UEM Profile: [IncludeRegistryTrees] HKCU\Software\Cisco Systems, Inc. HKCU\Software\IM Providers\Cisco Jabber [IncludeFolderTrees] <AppData>\Cicso\Unified Communications\Jabber <LocalAppData>\Cisco\Unified Communications\Jabber Settings like "View > Show docked Window" are not sticking across sessions Any help/advice appreciated