![windows home server 2011 troubleshooting windows home server 2011 troubleshooting](http://www.mediasmartserver.net/blog/wp-content/uploads/2011/04/05.png)
- WINDOWS HOME SERVER 2011 TROUBLESHOOTING INSTALL
- WINDOWS HOME SERVER 2011 TROUBLESHOOTING DRIVERS
- WINDOWS HOME SERVER 2011 TROUBLESHOOTING DRIVER
The first time you do this, you actually run the Windows Home Server dashboard. Launchpad is separate from Dashboard, so you can have different logins than your desktop system uses.Once the WHS connector is installed, you’ll run the Launchpad app. At that point, you’ll have to reboot, and then run the connector setup app again. You don’t have to search around for this the WHS connector app will launch it for you. If you have auto logon configured, you’ll be prompted to revert to login-required mode. You’ll download the WHS connector installer, and then run it. Replacing with the name that you assigned to the server during setup.
WINDOWS HOME SERVER 2011 TROUBLESHOOTING DRIVERS
Unlike in the Windows 7 setup, installing chipset drivers didn’t require a reboot.
WINDOWS HOME SERVER 2011 TROUBLESHOOTING INSTALL
Windows will unceremoniously dump you to the desktop, at which point you can install the chipset and the network drivers. After completing the ‘Preparing Desktop’ phase, you’ll see the ‘configuring Windows’ screen with a progress bar at that point, simply press Ctrl-Alt-Delete, open the task manager, and kill the setup process. In short, Windows Setup had entered an infinite loop.Įscaping this catch-22 is simple. That missing ingredient generated an error message, which resulted in a reboot, which led to the same problem and error message.
WINDOWS HOME SERVER 2011 TROUBLESHOOTING DRIVER
But we hit a snag at the end of the automated process: The system didn’t have a built-in driver for the gigabit ethernet controller. The entire process went smoothly at the beginning, and if you’ve ever run Windows Setup, you won’t find much different in the Windows Home Server routine. The system housed a single unformatted 2TB Western Digital GreenPower drive. This meant making sure that the system BIOS was set up to boot from the USB drive. The system lacks a DVD drive, so we used a Samsung external USB optical drive to handle the installation. The hardware used for this installation is built around a Zotac mini-ITX motherboard with an Intel Core i3 530 CPU and 4GB of DDR3 RAM. You can have read access, full access, or no access. The only drawback is that there’s setting up shares in this way results in a little granularity. Windows 7 HomeGroups: You can add a WHS 2011 box to your HomeGroup, which makes sharing files and printers much easier. But those aren’t needed any longer (though some may have additional features beyond those in WHS 2011.) The original WHS didn’t have this capability built-in, so various media server plug-ins were among the most popular WHS plug-ins available. As more HDTVs, A/V receivers, and other similar home electronic devices ship with built-in DLNA client capability, combining a robust media server and a robust PC server in one box becomes increasingly useful. It’s now a DLNA 1.5-compliant server, meaning that DLNA-capable client devices can connect to a WHS system set up as a media server. Better media server: Windows Home Server 2011 has robust media transcoding and streaming capabilities, and it supports a wide range of codecs–AAC, AVCHD, DivX, MPEG-2, MPEG-4, WMV, and more.