Archive for February, 2012

A bug in Bugzilla 4.0.4

There was a request to have a new tool custom report tool created for our Bugzilla installation so I had to re-deploy a copy of Bugzilla onto our development environment. Installation was a bit tricky with a specific Perl module (YAML) being the main issue. The install script keeps saying that this is missing:

Checking for YAML (any) not found

Checking the system, YAML is indeed installed and available. What is actually broken is the CPAN.pm file in the Bugzilla package – it doesn’t require the module.

To fix this, add the YAML module into the CPAN.pm file found in the bugzilla/lib directory. Search for:

use Text::Wrap ();

And replace with:

use Text::Wrap ();
use YAML;

Running the install script now works with no errors.

WDS Deployment spanning multiple subnets

This turned out to be simpler than I had first imagined. Reading the Microsoft documentation looked like we had to make changes to the DHCP, however this was not the case.

To make it clearer, our current environment looks like this:

  1. DHCP is a Linux CentOS Server
  2. WDS and DHCP servers are on the same subnet
  3. Client machines are on various subnets
  4. Cisco core switch and router stack

For our setup, we only needed to make sure the Cisco ip helper-address was set to point to the IP address of BOTH the DHCP and WDS. Once this was done, everything went as intended.

WDS Installation and Deployment

We’re deploying a new WDS (Windows Deployment Service) server at work and at first everything looked alright until I ran into my first snag – I wasn’t able to start the role / server after I installed it.

Looking everywhere on the manuals and guides provided by Microsoft didn’t help either. All they say is to add the role to the server and then configure the server with deployment images etc.

Upon closer inspection, it seems like you need to initialize the server before it will even start. In order to do this, you need to run a command via an elevated command prompt window:

wdsutil.exe /initialize-server /reminst:<path to WDS data files>

I created my own folder for the WDS data files and then plugged that into the command. WDS started up with no further issues.

Next posting… how to get WDS to work with multiple subnets. I’ll post that when I get it sorted out! :)

VMware vSphere Client cannot mount local optical drive

Another quick post regarding a nagging issue I’ve had for awhile now. Every time I wanted to connect to my local optical drive it would complain with the following error immediately:

Remote device disconnect
The remote device on <host> connected to <path> is disconnected.

Digging around I found that the cause of this is because of Windows 7 permissions again. Running the application as Administrator or checking off the “Run this program as an administrator” under the Compatibility tab of the vSphere Client shortcut solved the issue!

Hope this helps you all as well.