Getting Windows ready, don't turn off your computer
Installing Exchange on a VM and installed the .NET4.7 and C++ prerequesits. Server's been sitting at "Getting Windows ready, don't turn off your computer" for over an hour. Both VM's took awhile longer to install updates after installation but nothing like this. Any ideas? Don't have much choice but to leave it. Sadly I'm reading allot online where 2016 Server has serious update issues.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
See what happens after a lengthy delay. I hope it comes back for you.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
<flame....ish> look at the number of people using m$ products who face similar issues and rethink your choices </flame>
ASKER
skullnobrains, Microsoft has it's share of issues "as well as every other piece of tech" if wasn't this way EE wouldn't exist and an industry be built around it.
Came back from dinner updates finished, installed Exchange, configured, and already half way through importing email from the SBS2008 server. I manage allot of 2016 Servers and really don't have any issues. Not sure why this one was slower during updates but it's humming along nicely now.
Came back from dinner updates finished, installed Exchange, configured, and already half way through importing email from the SBS2008 server. I manage allot of 2016 Servers and really don't have any issues. Not sure why this one was slower during updates but it's humming along nicely now.
ASKER
John and David, thank you, appreciate the input.
You are very welcome and I was happy to help and glad to hear that the server is working.
happy to hear that worked out.
take the previous comment as a mostly useless joke cluttering the thread for the sake of providing reading while you were waiting. IRL, i'm not that much anti-m$ though i do believe there is no single reason to prefer such idiotic full screen messages to an update log with messages stating what is going on.
more seriously, the reason why it was long should be visible in said log. quite often a KB won't manage to install and windows keeps trying over and over a number of times before it decides to fail that one and move to the next. or some download kept failing for a while.
windows core has updates that run in a terminal with a decent amount of logging. i'm unsure exchange works properly on windows core, though. last time i checked, it did not.
take the previous comment as a mostly useless joke cluttering the thread for the sake of providing reading while you were waiting. IRL, i'm not that much anti-m$ though i do believe there is no single reason to prefer such idiotic full screen messages to an update log with messages stating what is going on.
more seriously, the reason why it was long should be visible in said log. quite often a KB won't manage to install and windows keeps trying over and over a number of times before it decides to fail that one and move to the next. or some download kept failing for a while.
windows core has updates that run in a terminal with a decent amount of logging. i'm unsure exchange works properly on windows core, though. last time i checked, it did not.
ASKER