Linked by Thom Holwerda on Thu 14th Sep 2017 22:11 UTC

Today, we are thrilled to unveil the next step in our journey for Windows Server graphical management experiences. In less than two weeks at Microsoft Ignite, we will launch the Technical Preview release of Project "Honolulu", a flexible, locally-deployed, browser-based management platform and tools.

Project "Honolulu" is the culmination of significant customer feedback, which has directly shaped product direction and investments. With support for both hybrid and traditional disconnected server environments, Project "Honolulu" provides a quick and easy solution for common IT admin tasks with a lightweight deployment.

I've never managed any servers, so it's difficult for me to gauge how useful of popular tools like these are. What is the usual way people manage their servers?

Permalink for comment 648919
To read all comments associated with this story, please click here.
RE[6]: Great question
by Alfman on Fri 15th Sep 2017 15:36 UTC in reply to "RE[5]: Great question"
Member since:


I am talking OS patching. And I think both Windows and Linux still need a reboot after installing most OS/Kernel level patches.
Also, maintenance can include more activities than just updating... Even if you're not expecting any downtime for a given maintenance activity, you must consider that possibility and act accordingly...

True, but the majority of kernel updates are for new features that can often be postponed to a convenient time or even indefinitely if you didn't need those features. Only the security updates have any real urgency. I tend to handle it on a case by case basis.

About the rest, yes, I agree. Many things are different in small companies with very small IT budgets.

I find this to be one of the biggest challenges with small companies. They want everything running smoothly 24/7 on a shoestring budget, alas those are often mutually exclusive, but you do the best you can, haha.

Reply Parent Score: 2