Sage 100

This Sage integration engine is running neck and neck with administrative password as the greatest pain in the ass for year end upgrading of tax tables. 99 times out of 100 my customers are not using anything requiring the integration engine yet Sage insists that it starts up on the server during install. Not a problem when you're RDP or remotely connecting to the server - because yeah just shut that sucker down. But for customers who don't have server access and use outsourced IT consultants - it's a a pain.

I almost always disable it once the install is completed unless they are using something that requires it (CRM).

Once the initial install is complete, I stop it and set it to manual. Never have an issue again until the next upgrade..... If it is a 200 install, I use the user logon (always different than the admin logon) that runs the MAS service to run the integration engine. After installation, I shut it down.

I'm fighting that right now and couldn't agree more!