We have attempted to blank the update URL in the 2X client policy Options General tab to stop configured client connections for prompting for update. However, our users are still being prompted to update their client, how can we turn this off to keep the end users from updating? This is causing us endless printing issues that are caused by end users accepting the prompt to update to 10.1 since our servers are still on 10.0 this of course causes a default printing issue. Any help would be appreciated, thank you.
So after talking with support there is evidently no way for us to turn this off as it is controlled by 2X. This is costing us thousands of dollars in support man hours. Which will certainly factor in to our decisions to continue with 2X as a product. Its unfortunate that 2x would choose to interrupt our end users environment without allowing us the capability to control it in any way shape or form.
Hmm... as I can't follow you with this I would be interested in the details of your client environment. If I e.g. just using the 2X Client for Windows v10.0.1167 it is indeed asking for updates to 10.1, but only as long as the associated option in '2X Client - Options - General tab' is not disabled. As soon as this option is disabled the client do not ask for an update within our customer environments anymore. Further more the update execution only starts when the users have administrative rights... Thanks in adv.,
We have a mixed environment some users logon via web portal and you are correct they can manually disable the update option. We have other clients configured via direct connect (ie, a configured 2X client). Once you configure the client policy for the client management tab. The end users options tab is no longer available therefore they cannot turn off the check for updates. In the 2X client policy under the options/general tab it lists an update URL which by default is set to check http://www.2x.com/downloads/2xvds-client.xml. It apparently does not matter if you remove this site from the entry it still prompts for update. This in itself is problematic due to SSO (Single Sign On) being enabled by default. So once the end user performs the update now suddenly they cannot connect due to invalid credentials. We host EMR and medical billing software for many different practices ranging from small 5 station workgroups to 150+ user domain environments with their own IT support. Many users do have administrative rights to their own machines. So when they update to 10.1 this of course causes printing problems for a variety of reasons. The quickest way to repair it is to roll back the client to 10.0 however then the prompts for updates start over again. This changed several weeks ago it has worked fine without prompting for update for a year or more. I can only assume 2X changed the 2xvds-client.xml to 10.1 rather than the 10.0 that it was. We are in the process of testing the 10.5 update in our lab environment, upgrading from the 10.0 to 10.5.1308, first attempt failed we are working with support to determine the issue.
Thanks for typing down the details. I think i catched up now I would advise to try to import/set the following registry key for the v10.0.1167 BEFORE starting the 2X client on the client devices: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\2X\AppServerClient] "CheckForUpdateOnLaunch"=dword:00000000 should switch the check for a client update on launch off. Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\2X\AppServerClient] "CheckForUpdateOnLaunch"=dword:00000001 should switch it back on. KR,
Thank you for your assistance that does indeed work, unfortunate that we will have to manually edit registry keys for a few thousand users to address it but at least there is some solution possible.
I am glad that I could be of help a little and beside this I also learned s.th. new from your case Btw no group policy, no logon script or alike are available for the devices from which the users are coming to push the needed registry key? Good speed!
