Sage 100

During the process of installing Sage 100 2022 Premium on a server that already had Sage 100 2019 Premium

Heads up, this spontaneous reboot while installing Microsoft prerequisites is still a thing.
I hadn't seen it in a long while, and it just happened on a large Sage 100 site.

I believe it's an issue with one of the Microsoft pre-requisites that does NOT prompt for a reboot
It happens at the "now installing prerequisites"

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT
------------------------------

If I see a .NET component about to be installed, I expect a reboot... and always schedule software installs on servers at a time when it is safe to reboot (...partly because we disable UAC with the registry hack before installing Sage server, which requires a reboot).

Great advice though it doesn't overcome the issue of needing to have all users off the server during the time that the prerequisites are installed - either individually or by Sage auto-install.

I don't believe it's Sage's install routine that is triggering the sporadic reboot but is one of the Microsoft prerequisites.

Business Case:
I'm on a really simple upgrade though the accounting department refuses to be off the system during working hours, every move I make is shadowed by 2-3 IT people who actually do the work.  It's not as cookie cutter as it may seem to require a formal IT department to be in working at 6 am or 6 pm to work around the end users who refuse to vacate the system. And, yes I know, Intacct will solve that. And after Intacct, there will be something else that solves what Intacct decided not to improve upon. I guess with enough time and money anything is possible.

Original Message:
Sent: 05-01-2023 14:11
From: Carmen Cruz
Subject: v2022 Premium UG from v2019 Reboots without prompting

Here is what I do peeps.  I install all the Pre-Requisites first.  I have all of them and I believe there is a link on MOTM.   If Sage has any left to install it is very few and I never have to reboot.  I also install .Net 4.8 as well and have the downloads for that.  If all this stuff is already installed on the server and server updates have been completed then your ready to install Premium.  When you don't have everything that even what Sage does not include I find that Premium becomes a bigger challenge.  Make her happy up front and she will play nice.  Just sayin.  If anyone needs links from me you can always find me.  

Have a great day, 

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106

Original Message:
Sent: 5/1/2023 11:02:00 AM
From: Kevin Moyes
Subject: RE: v2022 Premium UG from v2019 Reboots without prompting

If I see a .NET component about to be installed, I expect a reboot... and always schedule software installs on servers at a time when it is safe to reboot (...partly because we disable UAC with the registry hack before installing Sage server, which requires a reboot).

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
------------------------------

We no longer do the installations during normal working hours, and get all users out of Sage 100 before attempting any installs.  We have been "bitten too many times" where we were under the impression everything was installed that was needed, and it "still" rebooted on us.  BTW, I'd love that "Registry Hack" @Kevin Moyes if your willing to share.  

The UAC controls that Windows present only affect the warnings, not the actual "protection".
Set registry value EnableLUA to 0 (zero) and reboot to properly disable UAC for software install.

Reference:
https://social.technet.microsoft.com/wiki/contents/articles/13953.windows-server-2012-deactivating-uac.aspx
This article applies to Server 2012, but we've been doing it on more modern versions of Windows Server too, for 100% of our Sage 100 server installs.

Do you re-enable UAC (or change the registry back) once you've installed Sage 100?

Yes, usually.  It only needs to be disabled during the software install... and often Windows Updates will change it back automatically (reminding you to reboot, when you log in next).