Sage 100

Has anyone run into a Windows Server 2012 automatically rebooting during Sage 100 2016 installation? I got the traditional ""we need to install components"" then the next thing I know I'm looking at the screen and it says ""rebooting"" without any prompt whatsoever.

I think there was another post on this, although not finding at the moment.

Happened to me last night, but I was ready for it (Advanced version). The first prerequisite was dot net 4.5.2, I think

Alnoor posted earlier last month. https://90minds-com.socialcast.com/messages/30201952?ref=stream

Thanks - I thought this sounded familiar. I am pretty sure I've done a few 2016 where the server did NOT automatically reboot so I'm wondering if the issue is related to server configuration (perhaps there's a setting) or the server version (this happened on Server 2012

I've done a couple v2016 installs (to my local WIN 8.1, a couple 2012 R2's and a couple 2008 R2's and I have not encountered any rogue rebooting.

Last night's example that did restart was Server 2012 (installing Advanced) And I believe one that we did earlier this week was Standard on Server 2012

Mine today was standard on server 2012 - here's a screen capture of the exact server version

Do two 2012 Std's indicate a pattern? What exactly is the difference between Std and R2? I used to think not much until v2016 refused to install on my 2008 Std server. Should we be recommending 2012 R2?

Since I've seen this do the auto-reboot I may shift my initial installation to off-hours times so as to be sure nobody is in the system. This doesn't work as well with people who have web integrations that may exist on the same server and require some intervention to get back up and going. I'm thinking it's a Microsoft 2012 issue more than a Sage issue.

Fyi, this happened to me Wednesday with Advanced 2016.1 on Windows Server 2008 R2 Standard.

Happened to me on every server (today's was 2008 R2) since I started doing 2016 installs.