OpenFiler iSCSI SAN Network changes

So I have been playing with ESX 4.0 and am using Openfiler for it’s SAN. Best part is, it’s free and it is very simple to setup.

There are a few things here and there that need some work but you can find a work around for it most of the time.

Well I installed the OpenFiler from scratch and set it up with DHCP, this because I was not sure about the IP-address schema I wanted to use and it is just easier. When I was ready to set up the IP I ran into some issues, I could not change it from DHCP to Static.  Seems to be bug in OpenFiler.

Here is now to fix it:

edit:  /opt/openfiler/var/www/includes/

Search for and modify command "sudo /bin/grep \"eth\" /var/log/dmesg"  with the command "sudo ifconfig -a | grep ‘eth’"

Posted in Uncategorized

Changing the IP-address of a ESX 4.0 host

I’m playing with vSphere 4.0 and am running that on my laptop within VMware workstation. So the configuration that I have is that I have 2 ESX servers and 1 Openfiler as my SAN. Problem is that where ever I go, it uses DHCP and I have to reconfigure the ESX hosts and the Openfiler so they can talk to each other.

For now I am changing the IP’s instead of using DHCP which will make it easier. I really need to put the Virtual swich back in place so it does not matter anymore.

Anyway here is how to set the IP and Gateway on the ESX servers.

esxcfg-vswif -i <ip add> -n <net mask> vswif0

Add the gateway in the below file,

add the line

Restart the network service
#service network restart

Try this command to list the IPconfig
#esxcfg-vswif -l

Posted in Uncategorized

vSphere 4.0 Client on Windows 7


There seems to be a compatibility issue between the vSpere 4.0 client and Windows 7. The client will not run and through an error.

So there is a work around for this which I found online. I tested it and it works fine on my 64-bit Windows 7 box.

  1. Copy the file system.dll from the %systemroot%\Windows\Microsoft.NET\Framework\v2.0.50727 folder of a Windows XP installation which has .NET 3.5 SP1 installed to a temporary area
  2. On your Windows 7 client, move to the C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\ folder if you’re running 64-bit or C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\ if running 32-bit
  3. Create a new sub folder name LibXP and copy in the system.dll file
  4. Now open the VpxClient.exe.config file in the Launcher folder in a text editor. Add the section below to the file (don’t duplicate the </configuration> part)
        <developmentMode developerInstallation="true"/>
  5. Create a file, vpxclientwin7.cmd, in the Launcher folder with the following content. Note I’m running 64-bit. If you are 32-bit replace ProgramFiles(x86) with ProgramFiles.
    SET DEVPATH=%ProgramFiles(x86)%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\LibXP
    "%ProgramFiles(x86)%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe"
  6. You can now start the Vpx client by running this file 

I can now run under Windows 7, as shown here. Note that this is a workaround and shouldn’t be considered a long-term solution.

Posted in Uncategorized

vSphere 4.0 in VMware Workstation 6.5.2


Thanks to the folks over at Xtravirt for providing the documentation on how to do this.

Posted in Uncategorized

PowerShell: ADMemebers of multiple ADGroups

So you need to provide a list of AD groups and the AD members of those groups. The AD group names all start with FIN_.

Our friends over at Quest have written a great PowerShell snapin that can help us with this. The Snapin is Quest.ActiveRoles.ADManagement.

You can download it here:

Here is the code that will give you the output you need:

foreach($adgroup in get-qadgroup|where-object{$ -match "FIN_"}) {get-qadgroupmember $ | Format-Table -property $, name}

We are using a foreach loop so that we can run through all the groups and then pull the members. Main reason we do it this way is because we need to maintain the groupname for the output in the table.

So we stick the groupname in $adgroup, we match the groups with the where-object{$ -match "FIN_" command. Now that we have the groups, we use the $ to pull the members.

There might be a better, shorter, and, or, more efficient way to do this, but this works perfect.

Posted in Uncategorized

Exchange 2007 Full Mailbox Access

One of the things that changed overtime from Exchange 4.0 through Ex2K is that you could always access any mailbox with the ServiceExchange service account.

When Microsoft released Ex2K3 they made it a lot harder to get this ‘feature’ to work. Now in Ex2K7 it’s even harder.

No matter what the reason is that you need this ‘feature’, some companies just need it.

Check out the link to find out how you can leverage powershell to make it work:

Posted in Uncategorized