Set Printer Share Comment to the Port Name

We use an asset tag naming system to target all of our printer ports to the physical printers. The queue names are abstracted from the actual printer it's self. All of the printers have a DNS name that is their asset tag plus the SCCM site code of the location that they're currently located in. The only problem with this is that it creates a bunch of extra clicking to determine what printer a queue is actually pointed to (okay, so its like 4 extra clicks to get the port name, but its still tedious). The work around we came up with is to set the comment tag on the printer to the port name of the printer. To do that we use the following bit of PowerShell code that runs on an hourly basis on the server. It was tested on Windows Server 2008, but should work just fine on Server 2003:

$printers = Get-WMIObject -Class "Win32_Printer" -NameSpace "root\cimv2" -computername "."
ForEach($printer in $printers){
$printer.Comment = $printer.PortName
$printer.Put()
}

Mounting CD and DVD in SuSE in Hyper-V with the Linux Integration Components Installed

SuSE Enterprise 10 SP2 works great on Hyper V, the performance (especially once you get the VMBus drivers installed) is near-iron, and the integration between SuSE and AD is great. It's the perfect setup for running a few Linux servers in a mostly Windows shop.

The only problem that I had getting the CD/DVD drive to mount. Once you get the VMBus drivers working properly, when you boot with the XEN kernal the CD Rom drive will show up as a Hard Disk to Linux. This will prevent SUSE from automatically mounting the CD/DVD drive when you swap out the discs (or upon boot). The solution is to mount the CD/DVD rom manually; to do that, do the following:

1. Open up Terminal
2. Make a directory as a mount point for the drive ( "mkdir /media/cdrom0" )
3. Mount the drive by typing in: "mount -t iso9660 /dev/hdc /media/cdrom0"

This is assuming that the DVD drive for the Virtual Host is on IDE Controller 1 location 0. If it is on another channel, you'll have to change the /dev/hdc line of the mount command to the correct value:

• IDE Controller 0, Location 0: /dev/hda
• IDE Controller 0, Location 1: /dev/hdb
• IDE Controller 1, Location 0: /dev/hdc
• IDE Controller 1, Location 1: /dev/hdc

Update: Found one more issue. When using YaST2 to configure the network interface, make sure that you use the "Traditional Method with ifup" and not "User Controlled with Network Manager". Otherwise it will continually fail to setup the network adapter without providing any relevant error messages.

HP Proliant Support Pack on Server 2008: Server Core

We had some problems early on with the initial version of HP's PSP on our HP DL380 G5s and Server Core. The problems seem to have been resolved in the latest (8.15) version of the PSP. To install it, simply extract the PSP to a directory and run the setup.exe from the command line in Server Core. You'll get the standard HP GUI to guide you through the installation (or you can use setupc.exe for the commandline driven installation). The only "note" is that you'll have to install the SNMP service before hand by using the command "start /w ocsetup SNMP-SC".

HyperV and Failover Clustering Qwerk

Setting up a HyperV failover cluster on Server 2008 Datacenter edition, we kept having an issue with VM's configuration object getting stuck in "Offline Pending" when moving the virtual machine between servers. Additionally, we were getting an error when trying to add additional Virtual Machines to the cluster:

"An error was encountered while loading the list of available virtual machines. The value cannot be null Parameter name ManagementObject" . With an EventID # 1183 error as well.

After banging my head over this issue, it turns out its rather simple. The Failover Cluster Management MMC doesn't automatically add the drive that the Virtual Machine Configuration is stored on as a dependency to the Virtual Machine Configuration object. It's strange because it does add it to the Virtual Machine object its self. The result is that the cluster service can offline the disk that the configuration is stored on before it's done writing to the configuration file, causing the problems.

The solution, of course, is to add the virtual disk as a dependency of the Virtual Machine Configuration:
Update:
If you've already deleted the VM Configuration, you can add it back by right clicking on the Virtual Machine Group in the Failover Cluster Management MMC, choosing Add Resource -> More Resources -> Add Virtual Machine Configuration. Alternatively you could reload VM on one of the cluster nodes and then go through the process to make it highly available again.

Update x2:
Microsoft has fixed the root problem in the Hyper-V Failover Cluster Management Hotfix; more info here:
http://hypervoria.com/hyper-v/hyper-v-failover-cluster-hotfix-now-public.aspx

SCCM 2007 & KB948109

We've got a single System Center Configuration Manager 2007 server running all of our SCCM roles, as well as running MS SQL 2005 Express Edition SP2. When we installed the latest MSSQL update, KB948109 , we found that it completely hosed the security on the SQL instance. It appears that this is a rather widespread problem, in generally it looks like this update is wroght with issues. Luckily, running SCCM's Repair Site wizard on the server followed by a reboot cleaned up the mess. The more you know.

Excel 2007, Vista, and Synergy

I've found a problem with the awesome, cross platform, multi-monitor program Synergy. When using it with Windows Vista (which, technically isn't supported but seems to work reasonably well), you can't disable the Scroll Lock key in Excel. If you pull up the Virtual Keyboard from the Ease of Access tools, you can see scroll lock turning on and off, but Excel 2007 doesn't seem to care. The solution is to: turn off Synergy, hit Scroll Lock, turn Synergy back on. The developer has expressed that he is working on the project again, so hopefully we'll see the filter driver fixed in Synergy 2.0.

Active@Boot Disk and Active@Undelete

So it turns out, the instructions I posted last year for getting Active@Undelete on a Windows Deployment Services system work just as well for getting the Active@Boot Disk on there as well. The only difference is that you have to use the Active@Boot Disk Creator first to generate the ISO image so that it will include your serial number and registration info.