Sage 100

Anyone come up with a definitive way to install Sage Exchange Desktop 2.0 when the customer is prompted as mandatory update and swears they are admin? UPDATE: One reason for failing Sage Exchange Desktop 2.0 is that the update won't install on an OS earlier than Windows 7. Note, [Sage Exchange 1.0 will be sunset June 2018](https://support.sagepayments.com/link/portal/20000/20000/Article/5034/Sage-Exchange-Desktop-SED-1-X-Sunset). This means any customers on an old OS (earlier than Windows 7) will be forced to upgrade in order to install Sage Exchange Desktop 2.0. Make sure they do this before June 2018. https://www.youtube.com/watch?v=ZvCI-gNK_y4

Tell them that they HAVE to log onto the workstation as the system admin then do the install. If they don't, then they can call 800-854-3415 to talk with someone who gives a shxx. And good luck with that.

LOL! @JeffSchwenk While I agree with Jeff, I think it depends on the OS. For me, I have Windows 10, and I had to use my admin account to install it. I also had to stop the old 1.0 Sage Exchange and use Control Panel to remove it. However, others in my office did not have that problem. It is definitely a crap shoot...like Jeff wrote (shxx)!

Who the hell writes an installer routine where the splash screen cannot be moved and covers every other prompt and image on the desktop? I haven't seen this since 1980s

There appear to be at least 5 steps. 1. Prompts for mandatory update 2. Installs what appears to be an update to some type installer 3. Prompts for Sage Exchange Desktop 2.0 Install 4. If that's successful, prompts to UNinstall SED 1.x 5. Then another prompt comes to install SED 2.x (what exactly did step #3 do??)

Sage R&D/support seems to have been blindsided by this pushing out. Can't say that I'm surprised. I'm looking to fine tune a graceful email to suggest that a customer call Sage directly on these things. I can't come up with a good reason why we should act as the unpaid warranty department.

Follow-up: after reviewing it seems that Admin creds, user permissions & group policy admin rights have been causing an issue for some

I am not a developer but wouldn't best practices dictate that you are either first testing for appropriate permissions or if that's impossible displaying a message that the user should be logged in with local administrative rights? Just plunging face first into the install, throwing up a non-movable splash screen and hoping for the best strikes me as reckless.

Feel free to chime in here: https://sagecity.na.sage.com/support_communities/sage100_erp/f/98/t/103393

I sent it publicly to Sage Support on twitter this AM. Absent any other provided contacts I presume Sage is happy to air their dirty laundry in public. I'm waiting on a call from Ronnie to see what the scoop is. As best I can tell Sage's position is they expect all users to have full admin rights to their machines at all times. This flies in the face of probably 75% of the companies that have Sage installed and who have dialed back user rights to help prevent aggressive viruses such as cryptolocker. Sage got caught here with their pants down, imo (ie unprepared).

This appears to be an operating system issue. I think that Sage Exchange Desktop 2.0 will not install to Windows versions earlier than 7.0. I had a customer on XP and Windows Server 2008, When I downloaded the full Sage Exchange Desktop 2.0 and ran that as standalone it refused to install BUT gave me an error that installation to less than Windows 7 was not supported. The problem is that the self-install does NOT give that error message so you are left guessing as to why it fails.

https://support.sagepayments.com/link/portal/20000/20000/Article/5034/Sage-Exchange-Desktop-SED-1-X-Sunset