The user can now use the latest App-V package and work happily ever after.ĭuring testing I discovered a strange behavior how RES Workspace Manager handles the shortcuts while the original “production” version was still deployed on the machine. When the SCCM has completed the deployment and the workspace manager is refreshed the old shortcuts will disappear and the new are published. When the update process is started by SCCM the new App-V package version will be deployed on the machine. The shortcut’s of this version are published in the start menu and is behaving as normal. Users are having the old App-V package deployed on there systems. "Folder Vendor Name" - "Folder Application Name" - "Shortcut" The shortcuts are published in the following folder structure. Both versions are linked to the same AD security group. Because I updated the package I create double shortcuts based on the original “production” package and the new updated package. Users have to be a member of the application group to receive the correct shortcut. The shortcuts are published with RES Workspace Manager. The update part is covered by SCCM and has been tested successfully. Therefore I created an update script which updates an App-V package with SCCM. Because the shortcuts are the same the two packages cannot be deployed both to the same machine. SCCM is used to deploy the App-V packages. The package name is changed to a higher build “vendor-app-version-lang-release-build”. The shortcut location, name and version are the same because the executable’s where not modified and only some parameters where changed. Workspace Manager: RES Workspace Manager 2011 SR4 with Fix Pack 6 (9.5.4.6)ĭeployment: Microsoft Configuration Manager 2007 R2Īn App-V package has been upgraded with an application fix and not an update. Workspace Manager: RES Workspace Manager 2011 SR2 with Fix Pack 5 (9.5.2.5) Virtualazation Client: Microsoft App-V 4. Then I will explain the issue I encountered. I will first summarize the software and versions which are used for the deployment. Zlibwapi.dll - ZLib.During an update of an App-V package I discovered a bug in RES Workspace Manager. Wisgate.exe - RES Automation Manager Gate WisExch.exe - RES Automation Manager WisExch Outdated_wisstub64.exe - RES Automation Manager Stub Grantdesktop.dll (by Real Enterprise Solutions Development) - RES Automation Manager Grant DesktopĪgent.exe (by Real Enterprise Solutions Development) - RES Automation Manager AgentĪgent_updater.exe - RES Automation Manager Agent Updaterĭefrag.dll - RES Automation Manager Defragmentationĭeployer.exe - RES Automation Manager Component Deployer WisShell_2.0.exe - RES Automation Manager (RES Automation Manager Shell) While about 54% of users of RES Automation Manager 2014 SR4 Agent come from the United States, it is also popular in Canada.įiles installed by RES Automation Manager 2014 SR4 Agent Relative to the overall usage of users who have this installed on their PCs, most are running Windows 10 and Windows 7 (SP1). The installed file agent_updater.exe is the auto-update component of the program which is designed to check for software updates and notify and apply them when new versions are discovered. The setup package generally installs about 20 files and is usually about 6.94 MB (7,280,203 bytes). The software is designed to connect to the Internet and adds a Windows Firewall exception in order to do so without being interfered with. Delaying the start of this service is possible through the service manager. It adds a background controller service that is set to automatically run. Manually stopping the service has been seen to cause the program to stop functing properly. Upon being installed, the software adds a Windows Service which is designed to run continuously in the background. RES Automation Manager 2014 SR4 Agent is a software program developed by RES Software.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |