A new client utility called the Launchpad delivers health alerts about the system and server (e.g.
WHS 2011’s client software can now be installed directly via a browser, and both Windows and Mac systems are supported (the existing 10 user limit remains in place). (To facilitate sharing and streaming, WHS 2011 supports DLNA 1.5 and can participate in Windows 7 HomeGroups). Upon completing installation, WHS 2011 provides a checklist of (and convenient links to) the initial configuration tasks that should be performed, such as configuring server backups, enabling remote access, and setting up file sharing and media streaming options. Microsoft has done much to simplify the process of getting WHS 2011–and the systems you’ll connect to it–up and running. To be sure, WHS 2011 addresses most of its predecessor’s biggest shortcomings, though not all of the changes are necessarily for the better. Formerly known by its “Vail” code name, Windows Home Server 2011 delivers a number of major improvements, not the least of which is that it sports 64-bit Windows Server 2008 R2 under the hood–a major step up from the 32-bit Windows Server 2003 that underpins the current version. It’s been a long time coming, but the next version of Microsoft’s Windows Home Server is finally poised to make its debut this month. Upon starting all of the above services, this fixed the problem with the dashboard but upon rebooting my WHS box the services failed to start again.The latest version of Windows Home Server adds a lot of features–and subtracts a big one too. The majority of these services all depend upon the Windows Server Service Provider Registry service. Windows Server Addins Infrastructure Service Windows Server Identity Management Service Windows Server Notifications Provider Service Windows Server Remote Web Access Administration Provider Windows Server Media Streaming and HomeGroup Service Windows Server Client Computer Backup Provider Service For me these were mostly the services beginning with Windows server: To resolve I sorted all my services by startup type Automatic and started all of the ones that were stopped. There were quite a few services that weren't started despite their start up type being set to
I had no users listed within the dashboard, no shares, unable to connect remotely using the web front end etc.
0 kommentar(er)
