Syed Jahanzaib Personal Blog to Share Knowledge !

June 15, 2012

Injecting RTL Driver in VMware ESXi 4.1 ISO using Windows OS

Howto inject RTL driver support in VMware ESXi 4.1 using VMware Customizer 2.7 in Windows OS 

I was installing vmware esxi on my test lab PC (Intel Desktop Board with RTL 8111 chipset NIC) but the Installation failed after I accepted the EULA and system halted.

unable to load module /usr/lib/vmware/vmkmod/vmfs3: failure

I tried several times to restart the installation but with the same error. After some googling , I found that my NIC was not in ESXi HCL (Hardware Compatibility List), This message usually points to incompatible NICs.  The list of supported components is short for a reason. Most embedded NICs on desktop motherboards just do not stand up well under load. Since in a virtual environment all the Virtual machines are sharing the NICs it doesn’t make much sense to even consider supporting something that isn’t well proven.

Fortunately I found driver pack for rtl 8111 , but I had to do some driver injection in ESXi ISO File. Following is the procedure on How I solve this problem.


# Windows 7 or +
# Copy of ESXI 4.1 Server in ISO format (Click here to Download) [Registration Required]
# RTL8111_8168_P55_integr_SATA_Ctrl.(AHCI).oem.tgz  (Click here to Download)
# VMware Customizer 2.7   (Click here to Download)

– Create a new Folder e.g esxi , Copy ESXi 4 ISO file in this folder,
– Download  RTL OEM TGZ file in same Folder,
– Download VMware Customizer in same Folder, then Execute it,
As showed in the image below . . .


*   In first Browse Field, Select the ESXi 4 ISO image,
*   In Second Browse Field, Select the Drive Pack in OEM TGZ format
*   In Third Browse Field, Select any folder where updated iso image output will be placed

Now cick on RUN to execute process . Once the operation begins, you will see something like below . . .


After completion of the process, it will notify you with the success results. Now burn this updated file on the Cd, and boot from this CD on your Server, and this time it will boot smoothly without giving you the error.

Happy Injecting 😉


Syed Jahanzaib

June 12, 2012

Windows 2003 (x86) Active Directory Migration to Windows 2008 (x64)

Recently I upgraded my company Active Directory infra structure from 2003 32bit to AD 2008 64bit. As we all know that direct upgrade from 2003 x86 to 2008 x64 is not possible, so it was a bit lengthy process , therefore I saved all the procedure in this small howto. I first tested the whole scenario in a VM environment, and then implemented it on our Live Production Servers. This guide was written so that it may be helpful for others and also it will be reference guide to me for future retrieval.

My Current Scenario:

  • Windows 2003 (x86) Domain Controller
  • Windows 2003 (x86) Additional Domain Controller

Upgrade Scenario:

  • Windows 2008 (x64) Domain Controller
  • Windows 2008 (x64) Additional Domain Controller

I first uninstalled the ADC to make things simpler. Then I installed Windows 2008 x64 on VM and configure it as ADC of Windows 2003 DC.



# Raise Windows 2003 Domain Functional Level to NATIVE Mode,
# Run ADPREP32.exe from Windows 2008 (x64) DVD on Windows 2003 DC,
# Install DNS Server Role [Primary or Secondary DNS Role] on Windows 2008,
# Configure Windows 2008 as ADC, Create Forward/Reverse Lookup Zone with same domain name, Replication from 2003 DNS to 2008 DNS will auto occur
# Transfer all FSMO roles from 2003 to 2008
# Run dcpromo on Windows 2003 to remove AD, after reboot, unjoin it from domain.
# Clear Win2003 old DC records from Windows 2008 DNS / Sites / Domain controller.

In this article, following naming schemes were used.

Domain Name =
Windows 2003 DC = xyz
Windows 2008 ADC/DC = WIN-71R3LJBPRK

Windows 2003 AD 32bit migration to windows 2008 AD 64bit


1) On Windows 2003 Domain Controller, Raise Domain Functional Level from mixed mode to to NATIVE mode by going to
START / Admin Tools / ADUC

Right Click on domain name (e.g and select RAISE Domain Functional Level

Now here you will see Windows 2000 Native is currently selected as default, change it to
Windows server 2003
and click on RAISE. It will give you a warning ,
Click on OK to continue.
As showed in the image below . . .

Preparing Windows 2003 (x86) AD for the Windows 2008 (x64) Joining

On your Windows 2003 DC, Insert Windows 2008 x64 DVD,
Open command prompt
Change dir to \support\adprep

cd \support\adprep

& issue following command

adprepr32.exe /forestprep

It will give you warning , Type C and and press ENTER to continue
As showed in the image below . . .

After its completion, issue following command

adprep32.exe /domainprep

After its completion, issue following command

adprep32.exe /rodcprep

Ok, Windows 2003 section is done, Now moving to Windows 2008 Server to configure it as ADC [Additional Domain Controller]

Configuring WINDOWS 2008 (x64) as Additional Domain Controller

Start Active Directory Installation Wizard using dcpromo:

Goto Start / Run and type


AD Wizard will start, Click on Next, Next
As showed in the image below . . .

When it asks for Choose a Deployment Configuration,
& Click NEXT to continue.
As showed in the image below . . .

– On Network Credentials Screen, Type your Fully Qualified Domain Name e.g: ,
in Alternate Credentials, click on SET , and enter your Domain Administrator ID & Password. and Click NEXT to continue.
As showed in the image below . . .

– On Select a Domain screen, click on your domain name e.g and Click NEXT to continue.
As showed in the image below . . .

On Select a Site, Click on Default First Site-name, and Click NEXT to continue.
As showed in the image below . . .

On Additional Domain Controller Options. Click NEXT to continue.
 [Make sure you tick on DNS server]

Another warning screen may popup, telling you about DNS warning, Click YES to continue.
As showed in the image below . . .

in Next screen, it will inform you about the locations where AD Database will be copied.
Click NEXT to continue.
As showed in the image below . . .

in Next Screen, it will ask you to enter DSRM password, this is the password required when you run Windows in Directory Services Restore Mode to restore /troubleshoot AD, Enter your desired password and Click NEXT to continue.
As showed in the image below . . .

on Summary Window, It will show you all the info , Click on NEXT to continue.
As showed in the image below . . .

After it completes, simply Reboot.


Ok its time to transfer FIVE FSMO ROLES from Windows 2003 to Windows 2008 Server.
Lets Begin.

On Windows 2008 Server, Open ADUC and transfer following 3 roles.

1) RID
2) PDC
3) InfraStructure

on ADUC, Right click on domain name e.g: and select OPERATION MASTERS

Now you will see something like below image.

On RID, click CHANGE , it will ask your confirmation, Click on YES, & the role will be transfer to windows 2008 ADC.
As showed in the image below . . .

Repeat this process for PDC and Infra roles.

Now we will transfer 4th role , which is called SCHEMA MASTER.

From your Windows 2003 DC,
Open Command Prompt and issue following command

regsvr32.exe schmmgmt.dll

Now open management console by issuing following command


on MMC, goto file / ADD Remove Snapin

From the List , double click on ACTIVE DIRECTORY SCHEMA
and click Ok to close this window.

Now Right click on Active Directory Schema and select
Change Active Directory Domain Controller

Select your ADC Server and click on OK

Click on Change, and select YES when asked, it will transfer the OM role to your ADC.
As showed in the image below . . .


Now we will transfer Domain Naming Master role to ADC
Open AD Domains and Trusts,
Right click and click on Change Domain Controller,
Select Your ADC Server and click on Ok

Now right click and select OPERATION MASTER as showed in the image below
Click on CHANGE
As showed in the image below . . .

For better explaination of roles transfer, pelase see following guide.

All Done !!! Your ADC is now fully functional Domain Controller.

# Now remove AD from your Old Windows 2003 DC by running dcpromo. At end it will give you error that it fails to remove AD, Don’t worry, re-run the dcpromo again, and this time it will smoothly remove AD from 2003 server.

If it somehow failed to remove , you can use /forceRemoaval switch alongwith dcpromo to forcefully remove it.

# Make sure you UNCHECK option “This is the last DC in your domain

# Also don’t forget to remove the of W2003 DC DNS Entry on Windows 2008 DNS Server.

# Also remove 2003 DC Entry from AD Sites. You can also use metadata to clean the old entries.

# If Windows 2008 DNS server fail to replicate dns entries from 2003 dns, make sure ZONE TRANSFER is selected in Windows 2003 DC‘s DNS Server.

# So far we have manage to transfer all FSMO roles from Windows 2003 to Windows 2008, Now we want to move this Newly DC back to old machine so that IP address should remain same as previous old DC and also we will add ADC for this new DC.

Install Windows 2008  (x64) , configure it as ADC , transfer all FSMO roles from Windows 2008 (x64 DC) to this ADC, remove old 2008 DC,

Now remove AD from old 2008 DC, and again run dcpromo to make it ADC of 2008 x64.

I will write more data on this with some upgraded screenshots . . .

HOWTO verify DC’s are performing FSMO roles properly

Open Command promtp, and run

netdom query fsmo

dcdiag /test:fsmocheck

Syed Jahanzaib

June 8, 2012

winmail.dat issue in Lotus Notes [Solved]

Filed under: IBM Related — Tags: , , , , — Syed Jahanzaib / Pinochio~:) @ 10:00 AM

Howto Solve the winmail.dat issue in Lotus Notes

From past few days, Some of my users users were getting these “winmail.dat” attachments in Lotus Notes and were unable to open them and usually the sender is always from Mircosoft Exchange/Outlook User.

After some googling, I was able to sort it out.


Open Lotus Domino Administrator , goto SERVER , then SERVER CONSOLE, , and in the DOMINO COMMAND , issue the following commands , paste following two commands , one at a time . . .

set config TNEFKeepAttachment=1
tell router update config

The problem is that Outlook is tunneling rich text formatted information in an attachment through the Internet using a proprietary format (by Microsoft), rather than MIME (an Internet standard).

Microsoft opened up the format so other vendors could read the content, and IBM and other vendors have included that ability in later patches.

For more info, please read the below article from IBM.

Blog at