Friday, August 29, 2008

CommVault 7 and Exchange 2007

I don't know how many of you out there use the commvault backup system however I know the process of getting it to grab Exchange 2007 mailboxes on Windows Server 2008 is quite the ordeal. However after much frustration I have a resolution and will document the steps.

  1. Build Windows Server 2008
  2. Install and configure Exchange 2007 mailbox role <-- important if you anticipate backing up Exchange data :)
  3. Install and Patch the 64bit CommVault File System and Exchange database iData agents (the 64bit file system agent will be used to backup the file system)
  4. Add the following Registry Hive: HKLM\SOFTWARE\Wow6432Node\GalaxyInstallerFlags
  5. Add the following Registry keys underneath: DWORD bAllow32BitInstallOn64Bit = 1 DWORD bAllowMultiInstances = 1
  6. Download and install the Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1
  7. Disable UAC
  8. Create a User account for the CommVault backup. The account must hold the following exchange roles: Exchange Org Admin, Exchange View Only Admin, Exchange Server Admin on the mailbox server.
  9. Install 32bit CommVault mailbox, public folders (if using) and file system (required) iData Agents.
  10. Make sure all iData agents are up to date.

That's it! 10 steps I know but when they aren't documented it's alot of guess work to go wrong.

Tuesday, August 12, 2008

VMware bug AHOY!

Per this snip it from VMware.com/support:

"An issue with ESX/ESXi 3.5 Update 2 causes the product license to expire on August 12, 2008. VMware engineering has isolated the root cause of this issue and will reissue the various upgrade media including the ESX 3.5 Update 2 ISO, ESXi 3.5 Update 2 ISO, ESX 3.5 Update 2 upgrade tar and zip files by noon, PST on August 13. These will be available from the page: http://www.vmware.com/download/vi. Until then, VMware advises against upgrading to ESX/ESXi 3.5 Update 2. "

What does this mean? It means if you build a new VM power off and try to power on a VM you are f'ed! No turny ony for you.

Possible work around change the date on your VM host pre Aug 12 if you can. But don't worry we'll have a patch TOMORROW! I would not be surprised if we don't get a patch today, at least I hope I am surprised.

Thursday, August 7, 2008

OCS 2007 client for BES

So finally after much anticipation RIM has finally released the OCS 2007 client for the blackberries. It looks like the official release occurred on July 28th. This was all after releasing SP6 for BES 4.1 on July 16th and not having the client available. Which while yes HTML email is nice I've been holding out for the OCS 2007 client for a looooong time now.

Anyway the nitty gritty:

So I had already installed SP6 for BES 4.1 and configured it to point to my OCS 2007 Web instance. All that is needed is to give BES the FQDN of the server and the port number. In our case we use https and port 444. This is configured in the Blackberry Manager console by going to the BBIM instance and editing properties and filling in the appropriate blanks.














This was the easy part the part that I ran into trouble with was being able to push OTA (Over The Air) the OCS 2007 client to the handhelds. I downloaded the OTA version of the client but to no avail it would not show when I would create a new software policy. So on a whim I decided to use the desktop version and that worked. Why RIM offers OTA versions of apps that don't load I don't know but then again BES admin is just a side gig for me out of my primary job duties.

The process to get OTA push of the client is as follows:

  • Download oc2007_Desktop_2.1.10c.zip
  • I created a folder called oc2007 in the following directory structure:

C:\Program Files\Common Files\Research In Motion\Shared\Applications\

  • Extracted the contents of the zip file into that folder so that there are the following files:

DIR For_4.1.0

DIR For_4.2.0

DIR For_4.6.0

OfficeCommunicator2007.alx

OfficeCommunicator2007_de.alx

OfficeCommunicator2007_en.alx

OfficeCommunicator2007_es.alx

OfficeCommunicator2007_fr.alx

OfficeCommunicator2007_it.alx

  • From a command prompt then run the following:

C:\Program Files\Common Files\Research In Motion\AppLoader>Loader.exe /index

This should add two files to the oc2007 folder called PkgDBCache.xml & specification.pkg. If you do not see these files then something has gone wrong and I recommend you look at the following article from RIM. Deploying OTA Applications

Under the assumption you do have these files then all that is left is to create the Software Configuration in the BES Manager and the Application policy.

  • Open up the BES Manager
  • At the BlackBerry Domain level select the Software Configurations Tab
  • Click Add New Configuration
  • In the Configuration Name identify the application in this case I used OCS2007
  • In the Configuration Description I put Office Communicator 2007 client
  • Under Device Software Location this is where you put in the UNC path to the share you created to distribute OTA Applications. Again if you have no idea what I'm talking about at this point see the link above.
  • Once the UNC path is put in you should see a list of all the applications available in this case we want to only check the Enterprise Messenger under Application Software.
  • Lastly create the policy
  • Click on the Policies button.
  • Click New
  • Give the Policy a Name in my case I called it OCS2007
  • I set the Disposition to Required and allowed the application access to all phone functions as this is a trusted application and I don't want my users bothered with questions.
  • At this point OK all the way out.

The application is now ready for deployment. Now because I'm impatient I went into the Users area and right clicked on myself and said assign software configuration and selected OCS2007 and low and behold OCS 2007 client is now on my phone and working.

That's all I hope this helps anyone who ran into the application deployment situation like I did.

Wednesday, July 30, 2008

VMware Fix the VC installer

So last evening I downloaded the newest version of VC 2.5 U2 so that I can take advantage of all the new features in ESX 3.5U2. All and all the upgrade went well however it does agitate me that during the upgrade of the VC I must manually fix the Virtual Center service by hand.

To get domain authentication the VMware Virtual Center Server service runs as a domain account which allows it to talk to our AD for permissions etc. However when the upgrade happens it resets this service to local system, then proceeds to hang at starting service till I go into services.msc and change it back to the domain account and start the service by hand.

I mean come on how hard would it be to either A) keep the current service credentials or B) ask for a service account or run as local system during the install.

Other than that gripe I think this is a great product update, allowing for hot cloning is huge for us as we're never allowed to take anything down outside of the second Saturday of every month. No fun as I don't want to work the weekend.

Monday, July 28, 2008

Happy Qlogic iSCSI Day!

As I mentioned one of the functions of my job is to maintain, upgrade and envision our virtualization environment aka VMware ESX 3.5 Server.
Well we recently did quite the face lift to our environment in our PDX datacenter. We upgraded to all diskless Dell PowerEdge 2950 Mark III servers. We boot from a new Equallogic iSCSI SAN using Qlogic QLE4062C iSCSI HBAs.

A problem with this that I discovered at time of implementation is that I could not boot from iSCSI if I enabled Jumbo Frames on the Qlogic HBA. The system would just hang at Qlogic BIOS searching for a bootable LUN. Workaround at the time was not to use Jumbo Frames, while this works performance does take a hit. Given that instead of getting a 9000 byte datagram the server is forced to chop it into 1500 byte datagrams.

Well in doing my normal browsing today I figured well it's been about 4 months since I last looked to see if this has been address and low and behold it has. The firmware for the QLE4062C that works is:

FW: 3.0.1.49
BIOS: 1.14

The process is fairly easy hit the Qlogic website go to Support > Downloads. Look up Linux 32bit FW for the QLE4062C. Download both zip files and extract to a single folder and then burn to a CD. Wasteful I know but the PE2950s don't have floppy drives won't boot from USB floppy either so what are you gonna do.

I boot from a simple Dos boot CD swap in my FW/BIOS CD and then run the following:
iflash /fb - Flashes the BIOS
iflash /ff - Flashes the Firmware

That's all there is to it. Enjoy Jumbo Frames support in an ESX 3.5 environment.

Post UNO

So I've decided to start blogging. For those of you that know me you probably guessed by the title it will be job related. For those that don't here's a synopsis for what I do.

Title: Sr. Infrastructure Administrator (for now we're in a merger could change who knows)
Job Functions: EVERYTHING! more specifically:

MS Windows Server 2k - 2k8
MS Exchange 2k3 - 2k7
VMware ESX server 3.5
VMware VDI
SCOM
SCCM
SMS
Blackberry
Cisco IP Tel
Cisco WAN
Cisco LAN
Cisco WiFi
MS OCS
MS Sharepoint <-- hopefully passing off please dear god :)
Server Provisioning
Desktop / Laptop Tier 3 Support
Video Conferencing
QoS

I am sure there are other things but for now that's what pops into my head. So expect to see this blog fill with technical detail regarding these and other topics.