Sage 100

Have you found a way to tell definitively whether installing a .NET pre-requisite will result in the server rebooting automatically (no prompt)? I find that a high percent of my upgrades where .NET is flagged as a prerequisite will reboot without warning. This is a problem when there are users in the system or other applications are sharing the Sage server. I'm a the point where anytime there is a .NET prerequisite I have to stop and wait until a time when nobody is in the server because many times the server reboots as a result of the .NET.

I've never had it reboot automatically but always assume that .NET will require a reboot so only do installation when I can do a reboot. Sometimes I do the .NET installation on the server ahead of time because I've had the .NET install hang the server.

Yes, I've experienced the said reboot several times. Check Programs / Features in Control Panel for .NET 4.5.2 or greater. On Server 2012 R2 or greater look in Server Features to see if already installed. Hope this helps.

Agreed this is an issue. We have also had several automatic reboots. We plan our installs for time that the server can be rebooted just in case. It would be good to be able to definitively identify this ahead of time.

If .NET 4.5.2 is listed in Control Panel -> Programs Features no reboot is necessary. This on Server 2008 R2 and Server 2012. Server 2012 R2 has .NET 4.5.1 native to the OS. Can't recall ever having to reboot if that is installed. Can check via Server Manager / Local Server -> Manage -> Add Roles / Features, NEXT until Features list displayed. Look for .NET Framework 4.5 installed. Good news is if not, does not require reboot to add and will work - thus preventing reboot by Sage installer. At least that's been my experience. Again, hope this helps.

I've also has a reboot after installing Sage Exchange for a higher level of .NET, and always plan my installs for when a reboot is OK.

Always requires a reboot but have also experienced the No Warning reboot on a certain percentage during the install as apposed to a prompt to reboot.

I'm usually surprised when prompted... I've grown so used to the auto-reboot.

Just thinking through it, prior to Windows installer there used to be a reboot prompt (if required) that you could actually say No to and reboot later - once able to get users out of applications hosted on server. With intro of Windows installer in v2013 believe this changed to a prompt that had a bit of a warning, but rebooted within a minute or so after .NET install. In v2016 (thinking so) / v2017 (definitely) if it requires a reboot per .NET install the server is going down as soon as .NET installation completes. Only warning is the fact .NET is being installed. If that's seen, it's time to be sure all users are getting off quickly. The .NET install does usually take a few minutes, that's the only grace period given. However, if verify that .NET is already installed as outlined previously reboot will not be necessary. In other words, reboot necessity can be scoped.

@AndyAdkisson , I'm not sure on the versions where this began to impact Sage but your experience matches mine. In short, if you start the install on the server during working hours and hit a prerequisite of .NET it's safest to stop and to alert IT that a server reboot is highly likely and that it's very likely the reboot will happen automatically after the .NET is installed.

I always plan accordingly under the assumption that the server auto-reboot will occur, however it _appears_ it doesn't happen when .NET isn't listed on the initial ""pre-req's to be installed"" screen that comes up at the beginning of the installation - although I can't say that with 100% certainty.

That's my experience - if .NET is NOT listed as a pre-requisite then I have NOT had an issue with a reboot. It is only certain combinations of .NET where the server reboots without asking. In order to be safe any time that .NET comes up as a pre-requisite then I stop and tell IT that the server is probably going to be rebooted.