![]() ![]() There is a specific registry value that the Workspace Manager agent checks to see if it has the latest cache version. The trick is to understand the cache update process. We need to check Dynamic Priviliges since the script involves hacking the HKLM registry and we need to check Wait for task to finish… because we’ll add a second command later (also if you check Dynamic Privileges the script won’t run properly without the Wait option checked). Note that the powershell command has to be run with the -executionpolicy Bypass parameter in order to run properly. Then I added an Execute Command action to the Actions tab in Configuration with the following settings: Here’s how I did it (you’ll find a care package at the end of the blog □ ):įirst I created an application without a command line. Impatient as I am I started to poke around and I’ve come up with a way to create an application to force the local cache from the client using a Powershell script. I’ve requested this feature in RES Uservoice a while ago but there aren’t enough votes yet (help!). I find it annoying to have to leave the section I’m modifying in order to update the clients cache and then go back again, especially if it happens a few dozen times a day! Would’t it be great if we could force a cache update from the client with the click of a mouse button? Unfortunately there’s no command line option to force a cache update like there is for Refresh Workspace. The only way to be sure is to force a cache update from the console. The cache on your test client has not updated yet so when you’re testing the modifications it can seem like it’s not working. ![]() Sometimes you can be a little too fast with the Refresh Workspace action. When you’re in the building stage of a new RES Workspace Manager environment you have to test new settings and new applications very often. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |