Want to know how to install the WSUS role on Essentials?
Robert Pearman has the details:
Yay! I’ve been waiting for this. Thanks.
This reminds me of a problem that I’ve had that has never really gotten a concrete answer on.
I’ve noticed that Embedded versions of Windows Server have all of the roles of the standard equivalents available through normal channels, including Hyper-V. So where does Microsoft draw the line between what is a general-purpose AD DC and storage server, and what is an “infrastructure appliance” with the same roles installed with the cheaper Embedded OS?
As you might already know, Embedded products have much longer distribution and support lifecycles. They are also cheaper than buying through a VL. I just don’t really get why there aren’t more Embedded OEM’s making cheaper appliance-type servers (or at least just marketing them like that). It sure would make IT simpler to manage.
Beancounters and licensing. They don’t want to cannibalize their other sales.
I just look at this and think: why can’t you just build an “infrastructure and VDI appliance” on Windows Server for Embedded Systems and use Windows Embedded Standard for desktop devices and deliver it as a platform solution to a business? You’d need to license the Windows Client OS for VDI, but as a partner, you could just bundle everything together for the client. There’s your low-maintenance (VDI) infrastructure and you’d just load up the “dedicated” client roles by way of whatever LOB app is required to get the “purpose-built” device. They even talk about providing intelligent *SOLUTIONS* on the Embedded website. Hasn’t that been the goal of Microsoft Partners (including the SBSC) all along?
I gotta really look into this. Hell, this is the solution for getting SBSs after it gets killed off in the other channels in a short while.
Featuring WPMU Bloglist Widget by YD WordPress Developer