Monday, October 29, 2012

VMware - Change SCSI Controller Type

How To Change the SCSI Controller Type on a VMware VM

I just built out a new VM and accidentally selected the wrong SCSI controller type. I used the default "LSI Logic SAS" instead of picking "LSI Logic Parallel". So now when I switch it, the OS flips out and I get nothing but a big honking BSOD. So what now? Do I build out a new VM with the correct SCSI Controller? NOPE!

Below are the needed steps to get the new Parallel Controller installed, and to be able to remove the old SAS Controller.

  • Power on the VM and get log into the OS
  • While the VM is on, add another Hard Drive

  •  Select "Hard Disk"
    • Click "Next >"

  •  Select "Create a new virtual disk"
    • Click "Next >"

  •  Change "Disk Size" to 1GB
    • Select any "Disk Provisioning" and "Location" option
    • Click "Next >"

  • !!! IMPORTANT !!!
    • Select SCSI (1:0)
      • (Selecting 1:0 will force a new SCSI Controller to be created with your new vDisk)
    • Click "Next >"

  •  Click "Finish"

  •  You will now see a new vDisk and a new SCSI Controller that VMWARE is trying to add

  •  Click on the new SCSI Controller
    • Click "Change Type"

  •  Switch the type to "LSI Logic Parallel"
    • Click "OK"

  •  You will now see that you are adding a new vDisk with a Parallel Controller
    • Click "OK"

  •  Now go back to the console of your VM
  • After seeing that the new LSI Adapter is installed, shut down the VM

  •  Once the VM is shut down edit the settings of the VM
    • Remove the new vDisk you just added 
    • Click "OK" to apply the removal

  •  Now that the vDisk is gone, the second controller will delete itself
    • Click the first SCSI Controller
    • Click "Change Type"

  •  Switch the Type to "LSI Logic Parallel"
    • Click "OK"

  •  Click "OK"

Now power on your VM. Since the newly installed Parallel Controller is installed, the OS will not BSOD. HA-ZAA! Situation Fixed!

NSVPX - Generate SSL CSR

NetScaler - Generate Certificate Signing Request

It's that time of year again, and the question always comes up, "How do a generate the SSL CSR request for my NetScaler?". It's a quick and easy process. 

  • Open up the WI for your NSVPX
    • Select the "SSL" node from the left panel menu
    • Click on "Create RSA Key"

  • Enter in the "Key Filename"
    • (The file in which the generated RSA key is stored)
  • Enter in the "Key Size"
    • I am going to use 2048 

  •   Click on "Create"

  •  Click on "Close"

  • Select the "SSL" node from the left panel menu
    • Click on "Create Certificate Request"

  •  Fill in the "Request File Name" with the name of your CSR request
  • Fill in the "Key File Name" with the location of the RSA key we generated earlier
    • /nsconfig/ssl/
  • Fill in the "Distinguished Name Fields" with the appropriate information

  • Click on "Create"

  • Click on "Close"

  • That's it! You now have a CSR generated that you can use to create a new SSL Certificate for your NetScaler. You can use WinSCP to download the CSR from the /nsconfig/ssl directory or just SSH and "CAT" your /nsconfig/ssl/ file.

Friday, October 12, 2012

"F" Keys don't work!

HP Blade Integrated Lights-Out Setting Hot Keys

I just shipped out a HP Blade Server to Fresno California yesterday, and I had my remote hands push the blade into the chassis this morning. I log into the iLO console to install ESXi, and it says "Press F12 to Continue". The "F" keys don't work! They do nothing at all. "Hmmm.... How do I set the hot keys inside an iLO session?" Great question!
  • First things first, open the Onboard Administrator via the IP of your blade chassis
    • The log in page should look something like this
  • Once logged in, you'll see this interface

  • Drill down through the Left Panel to "iLO" on the server you want to configure
    • Enclosure Information
      • Device Bays
        • %SERVERNAME%
          • iLO

  •  In the right pane, click on "Web Administration"
  • You will be presented with an interface like the one below
  • Click on the "Remote Console" tab

  • Click on "Settings" option in the left panel
  • Click on the "Hot Keys" tab in the right panel
  • Drop down the boxes to select the hot keys that you need
  • In my case, I need
    • F2, F11, F12

 After all that, make sure you have the correct JRE installed, and use the "Remote Console" to remotely manage your server. If you don't, chances are things like your arrow keys won't work inside the console session. Now when it says "Hit F12 to Continue" you can hit "Ctrl-V". Success!

Wednesday, October 10, 2012

Rebuild Citrix EdgeSight Server Connection

I ran into an issue with my secondary persistent disks not having enough space for both my PageFile and my vDisk Cache. The resolution was that I added a new VDI to each VM in vSphere in place of the old one via deploying a template so that all secondary vDisk's had the same UID. The problem was, during the process, the EdgeSight Server pulled down it's data folder to the secondary disk and then I deployed it to all 10 vm's. Now all 10 VM's have the same "SInstance" and "Hostname" inside the EdgeSight.ini file.

The quick solution to resolving this is:
  • Shut down the EdgeSight Monitoring Service
  • Delete the Data Directory
  • Start the EdgeSight Monitoring Service
If you wanted to do this via a batch script, you could do the following:

:: Script :: Change Event Log Location
:: By :::::: Keith Smith
:: Email :::
:: www :::::
:: www :::::

:: Stop the Citrix System Monitoring Agent
net stop rscorsvc

:: Remove the EdgeSight Data Directory
rd /s /q "D:\Documents and Settings\All Users\Application Data\Citrix\System Monitoring\Data"

:: Start the Citrix System Monitoring Agent
net start rscorsvc
After all that, check your EdgeSight.ini ( X:\Documents and Settings\All Users\Application Data\Citrix\System Monitoring\Data\EdgeSight.ini ) file to make sure that the Hostname is correct, and that a new SInstance is generated.

Wednesday, October 3, 2012

Citrix XenApp - Publishing Active Directory Users and Computers

Publishing Active Directory Users and Computers

In the following scenario, I am using:

  • Windows Server 2008 R2
  • Citrix XenApp 6.0

Your Help Desk needs quick easy access to Active Directory Users and Computers to reset passwords. Well that's easy, just publish ADUC out via Citrix WI. To accomplish publishing ADUC, we need to complete the following tasks:

  1. Add the AD Tools Feature inside the OS
  2. Publish ADUC via Citrix Delivery Console

Adding the Active Directory Tools

  • Open the Server Manager
    • Click on Features in the left menu
    • Click on Add Features

  • Scroll down and click the checkbox next to “AD DS and AD LDS Tools”
    • Click Next

  • Click “Install”

Publishing Active Directory Users and Computers

  • Open up your favorite flavor of Citrix Management Console
    • Right Click Applications
    • Click “Publish Application”

  • Enter in the “Display name” and “Application description”
    • I am going to name mine “ADUC”
    • Then click “Next”

  • Make sure you choose the following settings
    • Application
    • Accessed from a server
    • Installed application
    • Then click “Next”

  • Input the following into the relevant section
    • Command Line
      • mmc.exe C:\windows\system32\dsa.msc
    • Working directory
      • C:\windows\system32\
    • Then click “Next”

  • Add the XenApp Servers that you want to load balance the application over
    • Then click “Next”

  • Add the security groups and/or users that need access to the application
    • Then click “Next”

  • Choose the icon that best fits your needs
    • Then click “Next”

  • Click “Finish” 

 Your Service Desk can now go to , and all they have to do is click on the icon named "ADUC" to open up the Active Directory Users and Computers published application via Citrix XenApp to do a quick password reset.

Where’s my enabled Users?

Where’s my enabled Users? I’m going through and fine tuning our Proodpoint Spam solution and noticed one of the filters needs to be updated....