VMware VCAC 6.0.1

Hello all,

I know i’m a Microsoft Fan but i’m also an Integrator and part of my job is to design solutions for IT challenges.

This week my boss came to me with a new challenge VCAC, at first i didn’t understand what he was saying I’m not kidding such a bad name i got to say.

Anyway the task was to prepare a DEMO for the VMware Event in Tel-Aviv and show the world this product by VMware.


Ok so i started up creating my lab but this time it had to be a big lab and i will also need to export it to the event.

I got V7000 by IBM for the storage side, 3 IBM X3550M3 for the Vsphere ESXi 5.5 Infrastructure, Fiber Channel Switch Cisco, A Network Switch 1GB Cisco, Management Station

So i put it all together and installed the VCenter + Update Manager + V7000 plug-in…

I added an Active Directory and DNS server 2012R2 ofcourse…next i created a few templates such as an IIS server 2012R2, A clean 2012R2, A clean 2008R2, FileServices 2012R2.

Now I’m ready to install the VCAC, but wait i forgot to tell you about it LOL…

Lets start with the full name VMware vCloud Automation Center so now you get the idea, this product basically extends the IT ability to control the private and public cloud infrastructure by creating a one stop place were users can easily create and manage their Virtual Machines whether there in the private or out side in the public (Azure, Amazon)

It’s amazing how simple this makes provisions a new VM (Iaas) (Xaas) also it can give you a comparison chart while completing the request forum.

Here’s the Main site with a short video about the product :


So i started the installation and im telling you it’s not easy i thought it will be a walk in a park but it’s not, I work with a lot of VMware products and other IT products but this was the worst.

you basically need two VMware Appliance the VCAC appliance and the Identity appliance for the SSO and the last part is the IIS yep that’s right you must have a Microsoft Windows Machine with IIS…thats because this entire product works on the Microsoft Orchestrator (System Center) WOW, i heard from a friend that they are trying to move it on to another appliance but for now it a requirement.


Here’s a great installtion guide :






How to increase the Exchange Server 2003 Service Pack 2 18-gigabyte database size limit up to 75 GB


New functionality has been included with Microsoft Exchange Server 2003 Service Pack 2 (SP2). You can now configure database size limits.

The database size limits for Microsoft Exchange Server 2003 Standard Edition have been increased from 16 GB to 18 GB. The limit can be increased to as much as 75 GB by using a registry key.

Microsoft Exchange Server 2003 Enterprise Edition does not have a maximum database size limit.

For more information about how to set the database size limit, see the Exchange Server 2003 Help topic. The Help topic was updated during the installation of Exchange Server 2003 SP2.


Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To increase the Exchange Server 2003 SP2 database size, follow these steps.

Important Before you increase the maximum size of an Exchange database, verify that sufficient hard disk space is available for the larger database.


On the computer that is running Exchange 2003 SP2, click Start, click Run, type regedit, and then click OK.


Click one of the following registry subkeys, as appropriate for the store that you want to increase:

For a mailbox store, click the following registry subkey:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\Server name\Private-Mailbox Store GUID

For a public folder store, click the following registry subkey:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\Server name\Public-Public Store GUID


On the Edit menu, point to New, and then click DWORD Value.


In the New Value #1 box, type Database Size Limit in Gb, and then press ENTER.


Right-click Database Size Limit in Gb, and then click Modify.


Click Decimal, and then type an integer from 1 to 75 in the Value data box.

Note These integer values represent the maximum size of the database in gigabytes (GB). For example, a value of 75 represents a database that has a maximum size of 75 GB.


Click OK, and then exit Registry Editor.


Restart the Microsoft Exchange Information Store service. To do this, follow these steps:


Click Start, click Run, type cmd, and then click OK.


At the command prompt, type the following command, and then press ENTER:

net stop msexchangeis


After the Microsoft Exchange Information Store service has stopped successfully, type the following command, and then press ENTER:

net start msexchangeis


Examine the Application log to verify that the database size has been set successfully. To do this, follow these steps:


Click Start, click Run, type eventvwr, and then click OK.


In the Event Viewer tool, click Application.


Double-click event ID 1216 to verify that the database size has been set successfully.


Vsphere 5.5 on Netapp FAS2220

This week i am converting a Hyper-V 2008R2 Infrastructure to VMware Vsphere 5.5 Infrastructure.

Firstly i would like to say the “walk in the park” isn’t the best word to describe the Netapp Installation and don’t get me started with the Ontap upgrade that’s just not friendly.

So starting off the first thing is to boot up the Netapp and connect your laptop to the Console and fire up the Putty via Serial.

You will get the initial setup like the Host-name and IP configuration, once your done with that guess what you need to do this again on the second controller.

Once your done with that you will need to install the client component to gain access to the storage called (On command 3.0)

Then you will receive this screen


Next you will add your IP/Hostname of both controllers.


The next step was to install the Vsphere ESXi 5.5 on the temp Server X3250M4

Once the installation is a success  and configure the Network parameters just install Vsphere Client and connect to the Temp ESXi.

Next connect the ESXi to the Storage via NFS, before that we need to create a volume and configure NFS permission (Exports) on the netapp side.

Now just create a new virtual machine and install the Windows Server 2008R2 add it to the domain and install the Vsphere SSO + Vcenter + Web Client + Vsphere Client + Update Manager yeah i know a bunch of installs but don’t worry it’s fast.

Connect to the Vcenter’s IP from the Vsphere Client.



Create a new Datacenter and finish up the creation of new Cluster.

You need to pick your poisson “HA, EVC, DRS”….

After that all you need to do is just start adding the ESXi Host to the Datacenter.

Now you are managing the Vsphere ESXi via Vsphere VCenter…whats that all about ?!?

Once you want to use the ablity such as VMotion, Storage VMotion, HA, DRS, FT….all that and more will be available only when working with Vsphere VCenter rather than the VSphere ESXi Free Edition !

Unlike Microsoft Hyper-V 2012R2 that can do almost all of above without purchasing the SCVMM (The Microsoft version for VCenter).

But still our client is moving his Hyper-V cluster to a VMware cluster so lets continue….


Next up V2V conversion Hyper-V to VMware.

A little brif, the Hyper-v uses  VHD and VHDx for Virtual HardDrives, and VMware uses VMDK.

We need an application to provide a conversion from VHD to VMDK.

A small search on Bing.com will get you a few options but I will summarize the top three:

1.VMware Standalone converter 5.5


2.StarWind Convertor


3. Disk2VHD


I used the VMware Standalone converter 5.5 and converted 2 servers for test, when finished you will need to install the VMware Tools to provide the VM with newly vmware drivers instead of Integration services that the Hyper-v provided before.

After successfully converting the entire infrastructure I have destroyed the HV Cluster and installed on both hosts the ESXi 5.5 and joined them to the VCenter Cluster pre created.

Now Vmotion all servers to the newly imported ESXi’s and evict the TEMP servers for the project.

Thats it,

Hope u enjoyed

Henry Hazot


Group policy reset to default

So will start with resetting the domain level Group Policy.

1. Log on as a domain administrator to one of you Domain Controllers.
2. Start a command line session. 
3. To reset the Domain GPO, type 
dcgpofix /target:Domain
To reset the Default DC GPO, type 
dcgpofix /target:DC
To reset both the Domain and Default DC GPOs, type 
dcgpofix /target:both

4.After you enter the appropriate command in Step 3, enter Y to both prompts. 
5. Close the command window. 

Use the command-line tool dcgpofix:

When using Exchange, you should also read the following:

Now for resetting the local GPO account that’s a bit different:
To Reset “Local Group Policy” to Default using a VBS File

NOTE: You must be logged in as an administrator in Windows to be able to do this option.

1. Click/tap on the Download button below to download the VBScript file below, then run it.


2. If prompted, click/tap on Open
NOTE: If you like, you can stop getting the Run prompt by unblocking the downloaded .vbs file.

Continue reading

Hyper-V 2012R2 installation via IBM V3700

This week i had the pleasure of setting up a new system for my client…

V3700 IBM Storage two controllers

X3550M4 fully loaded to rock and roll

2 HP 5500 switch

The main idea is to create a classroom lab for students at High-School, cool right now your probably thinking this is a private school but your wrong it’s a Public High-School so good for them…:-)

I started by installing the new V3700 that by the way is a walk in the park compare to all kind of other vendors.

You receive a “Donkey” just plug it in your laptop and a nice clean wizard will startup and guide u to give a managment IP for the Cluster of the controller.

Then just plug it to the left controller and wait until the blinking stops…about 3 min.

Next open a browser and https://ClusterIPaddress the default username is SuperUser and the default Password is passw0rd the “O” is Zero.

Once you launch the GUI you get the Overview panel that is so nice and user friendly i got to say that for IBM this is a big step.

Next Configure a Pool of disk and RaidGroup btw this is also a wizard.

Create Volumes as requested, for our manners i created a 512GB fix size.

Add the servers Initiators to a new group and called them Hyper-V

Map the Vol to the new Group Hyper-V.

Configured the ISCSI ip for the second  network card for the ISCSI protocol.

That’s it…done.

Installed the new X3550M4 via ServerGuide pre downloaded from the IBM site.

Booted up and configure Raid 1 for the OS and run with the wizard until it asks you to replace the dvd with the Windows Server 2012R2

Finished the installation MUST fully update the OS via Microsoft update.

Rename and join the Hyper-V servers to the Domain…..btw i updated the Active Directory already to 2012R2 🙂

Configured all of the network cards as pre planned all teaming except the ISCSI.

2 cards for Managment

2 cards for Virtual Switch

2 cards for ISCSI

1 card for IMM

Installed MPIO and ISCSI for mapping the newly created Volume on the V3700…

Very Important not to use Teaming for ISCSI it’s not best practices and works bad, best is to use the MPIO by Microsoft.

Next…Connected the ISCSI initiators to the target Cluster IP of the V3700 and success login.

You can see that i successfully connected to the target V3700.

Next install on both Hyper-V the feature Fail Over Clustering and reboot.

Open the FailoverCluster and run the Validate Cluster Wizard….this process will check that all of the pre configuration are ready for creating the cluster Important to understand that this process only validates and doesn’t create.

I got some red errors about having a few more Network cards with the same IP 169.254.x.x…of-course Microsoft there not connected i had to just Disable these two cards on both servers before retrying the validation again.

Next, Give the Hyper-V cluster a name and IP you will need to pick on witch network cards you will like to relay i choosed the Management.

I Couldn’t print screen the real deal because of security issues so i just found this screen online.

Next up creating the CSV for the Virtual Machines .

It will look somthing like this…on the right there is the Add Storage wizard so easy just add the ISCSI Volume we created on the V3700.

Now just create a new a Virtual Switch or Virtual Fiber Swtich in our case it’s a Virtual Switch.

New external virtual switch and configure the bind with the pre configured Teaming for the Virtual Switch Card.

Create a new VM or via the Hyper-v Management or via the FailoverCluster Management….so whats the different. ?

If you would like the VM to be Highly Avalible and be able to LiveMigration you will pick the FailoverCluster Management but if you want just a simple VM pick the Hyper-V Management, i always want the HightAvailability so lets have a look….

That’s it…all done.


Henry Hazot

Backup Free ESXi & Hyper-V

Hello all,

I was looking for a while for a simple way to backup Hyper-V/ESXi free edition all versions.

I tried a lot of products but at the end i have to say the only product that was simple to use was the Trilead VM Explorer.

I know you probably wonder why not Veeam that was my first choice and i was a bit disappointed that they don’t support the Free ESXi Version 😦

So if you have a Free Hyper-V/ ESXi and you want a Free backup solution this is the product for you.

So whats the downside :

1. No Schedule (At least for the free edition)

2.Sometimes the snapshots won’t successfully removed and you will need to manually delete them.




VMware vSphere ESX/ESXi and Microsoft Hyper-V back-up and recovery solution

Trilead® VM Explorer® is a tool for the facilitation of management, back-up and disaster recovery tasks in your VMware ESX and Microsoft Hyper-V environment. VM Explorer® supports VMWare vCenter. Back-ups can be stored on ESX/vSphere, Windows, Linux or FreeBSD-based storage platforms, or directly to a SAN. VM Explorer® requires only one license for your infrastructure – no fees per host or CPU.