Archive for WHS – Page 2

WHS Errors: Cqsvc.exe and MediaSmart Server Software Update

I have had a WHS server at one site for nearly three years. They use it just for backups, and that’s all I ever really check on a quarterly basis for them.

Today, while reviewing this server, I opened up Event Viewer and noticed a slew of warning messages related to “cqsvc.exe” and error events related to “MediaSmart Server Software Update”.

image

I quickly located a solution from Kelvyn Taylor’s website which workedbeautifully for me. Simply remote into the WHS server, and from a command line prompt, run:

winmgmt /resyncperf

No rebooting of the server required. When you go back into Event Log you will find that things are nice and quiet!

image

HP MicroServer AddIn Cards

The HP MicroServer is a great little unit to use for development/testing purposes. I have one on my workbench with 8gb of memory with Hyper-V. It allows to test out new versions of Workstation software, WHS, SBS and Multipoint.

Note that the HP MicroServer comes with built-in Raid-0/Raid-1 support.

The server has slots for two half-size cards.

The inner slot (the one closer to the on-board NIC) can only be used for the HP MicroServer Remote Access Card (RAC), which is sort of like a basic version of the HP ILO card for servers, and provides remote (virtual) KVM.

image

The second slot (the one closer to the outer edge of the box) can be used for other purposes, such as a low profile PCIe X16 Graphic Add-in card.

WHS System Drive Freezing Up

I have a Windows Home Server (WHS) unit installed at nearly every onee of my customers. I’ve also installed Windows Storage Server Essentials 2011 (WSSE) at two larger sites. The WHS units are working wonderfully, but as they get older, the chances of a drive failure increases.

I had a customer earlier this week whose WHS unit kept freezing up every day.

image

I checked memory and it was OK. I then ran chkdsk on each of the three installed drives. Turns out that the Data partition on the first (system) drive was the culprit.

To resolve the issue I followed the excellent steps to Successfully Clone and Upgrade a WHS System Drive from Alex Kuretz. I used Storagecraft’s ShadowProtect IT Edition to make an exact duplicate of the drive.

Disabling SSLv2 for PCI-DSS Scan

Are you running a Small Business Server (SBS) or a Windows Home Server (WHS)? If so, chances are you have forwarded port 443 (SSL) on your router or firewall to point to your server in order to utilize the Remote Web Workplace (Access) feature of these servers. The Payment Card Industry (PCI) requires certain standards to be in place if you are processing credit card information. One of those standards is that SSLv2 is deemed unacceptable, and you will fail a PCI scan if its enabled.

Disabling SSLv2 requires a simple registry edit. I have tested this with both SBS and WHS. Copy and paste the following lines into a empty text file, and aftersaving it, rename the text file to use a .reg suffix (e.g. disable-sslv2.reg).

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\PCT 1.0\Server]
“Enabled”=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server]
“Enabled”=dword:00000000

WHS Console Won’t Start

Last week I ran into an interesting issue with a Windows Home Server (WHS v1) unit. I could connect via RDP/Mstsc to the WHS box and login as the administrator, but I could not startup the WHS Console program. Likewise, trying to start the WHS console by right clicking on the WHS Taskbar icon from a workstation also failed.

Unfortunately, there were no errors in the event logs, and nothing in the WindowsHomeServer log file folder.

Most posts I found on this issue suggested a bad add-in being the cause. To determine which add-in was failing, they suggest to rename all the associated HomeServerConsoleTab.XXX.dll files, and then rename them back, one at a time, until you find which one causes the Console program to crash or not run.

Unfortunately, that did not fix my issue – but it pointed me in the right direction.

I compared the contents of C:\Program Files\WindowsHomeServer folder with a known good WHS box. That’s when I discovered an extra file on the WHS server that was not wotking. The file in question was named HomeServerConsole.exe.config. I renamed this file, and the console started up properly.