Hi Henrik,

The ability to run multiple clients during the transition / upgrade processing (with Multiple Servers) when we change versions is a really nice option to have.

I have no problem with where you are at present, that there is only 1 'official' version installed at a time.

What appears to work <7.2.1 Production, Testing 7.6.3> is creating a shortcut as you have described in the past <see below> but there appears to be dependencies (dlls ?) so I can get this to work but I have to copy the whole install from somewhere rather than just the VisualCronClient.exe and then setup a shortcut.

<One spot where the original work around was communicated here -http://www.visualcron.com/forum.aspx?g=posts&t=3506 >

*without* trying to complicate your life (too much 😉 )

It would be *nice* if:

1) This Workaround / process could be a FAQ &/or some sort of supported instructions
2) That the VisualCronClient.exe was again standalone, or that we only had to copy a small number of files to have a "Version x.y.z" Container that operates that client version, rather than the 'full' set of files.

Not too stressed as we have transitioned to accelerated deployments to mitigate this issue, but having some options would be nice to support our testers and local users, particularly as to support the enhancements and new task roll outs you are doing (a good thing !) the protocol and the client needs to keep moving with the server.

ps at present when you run the 763 client (for us Test) and then later return to a Production Server using the *Installed* 721 Client we get some new UI colours / 2013 Client Theme in the Job Grid. We can correct this simply by running back through the Start Guide and Resetting the old style Client Theme.