Simplest way to get rid of your snapshot delta files in Vmware workstation 10

My initial vmdk file was 40GB, then I created 4 snapshots which added the file -0001.vmdk–>0002.vmdk—>0003.vmdk and finally 0004.vmdk. In my settings for VM, the hard disk was pointing to 0004.vmdk which had grown to the size of 50gb now.

That’s right, my original VM was about 40GB in total size and now with snapshots, it was taking almost 120GB.

The easiest workaround I found was to

  • BACK UP all my inside to the VM to as NAS drive.
  • Stop the VM
  • Edit the .vmx file in notepad and change the configuration to scsi0:0.fileName = “original.vmdk”
  •  Start the VM again

It started as it was in the fresh state before any of those snapshots were created.


BAM Portal Not working?

The server encountered a critical failure while trying to access the list of Views. The Business Management Web Service requires Administrator’s attention.

Use the navigation bar on the left to access Business Activity Monitoring views.
If the problem persists, contact your System Administrator.



Reconfigure BAM using BizTalk configuration wizard, If the reconfiguration does not work then you may have to delete the app pool in IIS and the BAM website and try reconfiguration again.BAM Reconfiguration


ESB Exception Handling

To leverage the exception handling provided by the ESB toolkit, Below are the steps

Add the exception block to your Orchestration

Add the code as in the snapshot inside the exception block


When the exception occurs, this block would publish the faultmsg to message box

By default, All fault messages are picked up by the send port “ALL.Exceptions” which populates the ESBExceptionDb. This can be viewed in ESB Management Portal

If you do not want this behavior, then you would have to subscribe the fault messages using “Application” or similar property and handle it in either sharepoint or any other custom mechanism.

How much do you invest on a BizTalk developer for hardware and software?

Recently, I had to analyze and provide per yearly cost incurred by the company to setup the Microsoft BizTalk Server development environment for its developers.

Assuming that each developer would be provided with individual virtual machine to remote in and work, below table depicts the costs that would typically incurred for “per developer per server”. All numbers below are approximation.

Software Cost – MSDN License
for Visual Studio Professional. Includes Operating system, SQL Server and BizTalk Server

$1200 for 1st year.

$799 recurring.

Hardware cost

 $2000 / Server

Recurring Server maintenance cost

 $600 / Year

VM maintenance cost

 $480 /Year


Appr. $4280 / Developer per year


MSDN Subscription chart is found below or in the following link :



TFS – Team Foundation Server is included in the MSDN subscription, so you would not have to buy a separate license for the developers, who are already subscribed for MSDN.

For Non-developers, such as PMs, Bas, you need to purchase a CAL license individually or on volume licensing, which may typically cost around $300-400


Microsoft licensing white paper regarding TFS states as below.

Visual Studio Team Foundation Server 2012 can be obtained using MSDN subscriptions. Visual Studio Ultimate with MSDN, Visual Studio Premium with MSDN, Visual Studio Professional with MSDN, and Visual Studio Test Professional with MSDN subscribers can download and deploy one instance of Team Foundation Server 2012. These same MSDN subscribers are granted a Team Foundation Server 2012 CAL to be used within their organization (it is not valid for use of Team Foundation Server acquired by a different organization). ”

BizTalk Development Virtualization Models

Here’s the list of comparative factors between the two Development Virtualization Models discussed:

A)    Local Virtualized Machine loaded on the developer’s Computer, using technologies such as VM Ware Workstation.

B)    Hosted Machine, where developers remote into the servers and work remotely.



(A)  Local Virtual Machine

(B)  Hosted Machine

Ram upgrade required

Yes (min 4GB for VM)

N/A (min 4GB)

Hard Drive upgrade required

Yes(min 40GB for virtual disk)

N/A (min 40 GB)

Can develop offline



Can developer take snapshots



Server Team management



Can developer mount ISO



Backed up







Hardware Upgrade

Server Hardware Maintenance

BizTalk Server 2013 licensing model

BizTalk Server Licensing model has changed to per core basis, Below is the cost sheet advertised to public

Here are key points to consider while licensing a BizTalk server:

  • You must license all the cores used for the BizTalk server
  • Minimum of 4 core licenses required ( even if your server has less than 4 cores, ex: single core and dual core machines)
  • Core licenses can be purchased in pack of two.
  • Processor Cores are priced at 1/4 the cost of BizTalk 2010 processor license. BizTalk 2010 processor license was around $44,000, the new core license is $10,835. So if you are licensing a server with only quad core processor present, then the pricing is identical to BizTalk 2010 pricing.
  • Actual number of core licenses required may vary based on processor type and core factor.

    Also, May be most of you know this, BizTalk Server Developer edition is available license free and can be installed in Dev and Test environments. Dev edition also offers the fail-over clustering, so there by companies who wish to save on budget can install developer edition in their Test environments.

    Courtesy :