This 2x upgrade process is killing me.

I have several complaints from my users that the version 6 client upgrade is not properly connecting to the server. It doesn't connect or work unless you reboot twice. Even still, it is a little shaky on some computers.

Even worse, some of the buttons have changed and the instructions that I sent to the users now longer work.

My 2x server is still running version 5. My license key does not work on version 6. But... I just read on this forum that it won't work. I need to be notified before. Now I am under extreme pressure to get these clients downgraded back to something that I know was working.

To the good people at 2x... you are absolutely killing me. I am in a very, very uncomfortable position AGAIN, because of your automatic upgrades. This has got to stop. I love what 2x does for me, especially with the printing, but I need to have full control over the client upgrades so that I can properly test.

I would like to ask for two things to be done to help guys like me who can't afford to have changes pushed out without my notice.

1. Please turn off your automatic upgrades on the client. I want a switch or option on the server where I can decide whether or not to automatically upgrade the clients that connect. Upgrade notices on the server are fine.

2. Please have the clients pull the upgrades directly from the server and not across the internet. Not all of the computers accessing the server are allowed internet access. This way, I can be sure that I have the client matching the server. There will be no version 5 to 6 confusion.

Please send out notifications before major upgrades. We need to test everything first to be sure.

It would be nice if someone from 2x would at least acknowledge that they understand my position on this. I've made the decision to stick with 2x but I need a little help from you guys

Thanks

Maurice Dorris
maurice@paradigminfosystems.com

 

why dont you switch the automatic update off, there is an option for that.
also the update is checked only if the user has administrator rights on the machine... so i would advice not to allow users to have full rights on the machine otherwise they can make a mess of the system

 

these are good ideas, but not always good options for me. I do not have control over the client computers that are connecting to the terminal server. We host our applications over the internet. Using 2x has completely removed our desire to port our applications to be web based.

Most of the users are remote (many in different countries) and are connecting via the internet. I never see many of the client computers, I just get the phone calls. The phone calls start at 6am pacific for our US users and start at 10:30pm for our European users. I have instructed the users verbally and written to turn off the automatic updates but they don't.

I wish I had smarter and more knowledgeable users, but I don't. I know its their fault, but at the end of the day, the system is not usable the sys admins take the heat.

This is why I want centralized control over this.

 

Afaik it's possible to modify the MSI installer and put in your own preferences. Then instruct your customers to download the customized MSI file, so the update check is disabled by default.

 

Hi there,

May I suggest the following:

Make a copy of the xml at http://downloads.2x.com/appserver-loadb ... client.xml, modify it and host it on your web server.

Modify the client MSI, to edit the UPDATECLIENTXML property to point to your xml file.

Redistribute the modified msi and your clients will only get prompted to update their client when you update your xml file.

Nixu

 

thats cool, you can have complete control on the version they are using.
i tried it out and you can even switch off the automatic update from the msi. thanks Nixu

 

I gonna have to agree with the original poster. Although it's great that there's a workaround this is something that really should be handled from within the program, without the need to modify msi's and setting up webpages.

We already have a client server relationship, getting this fixed shouldn't be all that hard.

 

Thanks for agreeing. I really don't have time to mess around with building my own setup programs and such. I use 2x because it worked well out of the box. Its turning out that it takes time and energy to watch over it.

We might be all alone on this one. Apparently, there are many guys that like to buy 2x and then modify it.

 

Maurice, I agree 100%.

To 2X, Centralized control without needing to modify the .msi would be great. Many of us are stretched thin as it is, working 55+ hours per week; we don't have the time to babysit applications.

Overall 2X is great, but this is a glaring weak point.