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 648909
To read all comments associated with this story, please click here.
RE[3]: Great question
by Rokas on Fri 15th Sep 2017 08:08 UTC in reply to "RE[2]: Great question"
Member since:


Sure, if you have significant load. But not all enterprises warrant dedicated servers for each function. It increases operational and licensing costs for not much benefit. This was the case at one of the places I worked at with about 20 desktop computers.

Well yes, of course a company with 20 computers is a very, very different case :-)

Sure if you have load issues, then dividing the high usage processes makes sense, but otherwise I'd recommend just keeping it simple ;)

Nope. Role segregation is not just about load distribution. It's mostly about security, interoperability issues and ease of upgrades. You see, when you have only one role on the server, it's much, much, MUCH easier to reboot it, upgrade it, do maintenance on it than on the server where there are dozens of very different critical services running, each of which might have it's own needs/requirements... When you do maintenance on such a monolithic server, you're basically taking down entire infra and there's much higher risk that one or another role/service will fail after maintenance.
Also, if any single service/role gets compromised on such a monolithic server, you are totally screwed, since it means complete takeover of all your infra.

Edited 2017-09-15 08:09 UTC

Reply Parent Score: 2