VMware TCO / ROI Calculator User’s Guide

You can directly use the Tool in this link = http://http://roitco.vmware.com/

You can read the detail description of TCO in here = http://www.vmware.com/pdf/TCO.pdf

 

This is some simple User Guide on How to use the Tool :

The VMware TCO Calculator was developed jointly by VMware, Inc. and ex-Gartner ROI / TCO experts from Alinean, Inc. to provide a Total Cost of Ownership (TCO) and Return on Investment (ROI) analysis for implementing VMware solutions to virtualize your IT environment including datacenter server infrastructure, testing/development labs and desktops.

You can quickly assess potential cost savings by completing five easy steps:

Step 1: Fill out a Simple Survey Questionnaire

Answer a few questions about your company (such as the type of industry you are in, and location) and which of the VMware solution sets you are most interested in:
1. Data Center Server Consolidation Cost Savings (Using VMware Infrastructure 3)
2. Virtual Lab Automation Benefits (Using VMware Lab Manager)
3. Desktop Control and Manageability Cost Savings (Using VMware Virtual Desktop Infrastructure VDI)

For each selected solution area of interest, you will be asked five to ten additional questions  about your existing assets such as the number of servers or desktops you intend to virtualize,  and about cost reduction opportunities such as current server management, management  activities, storage and other metrics.

Default metrics are provided for all of the questions based on Alinean research regarding your specified industry and location. These defaults can be reviewed and adjusted to best match your own unique metrics. This is the only information that is necessary to get a quick estimate of potential cost savings and return on investment (ROI)!

Step 2: Customize Assumptions

The tool uses over 200 additional metrics to help calculate a credible and achievable costbenefit / ROI analysis. Each of the 200 metrics is set using default assumptions based on the metrics you provided on the questionnaire regarding your industry, location, assets and current cost opportunities, and using industry average and third party research. All of these values are preset using this research, but can be easily reviewed and refined by clicking on the “View/Edit Default Assumptions” link on the bottom right corner of each solution set on the Questionnaire page. You can then review each default assumption and make adjustments to
precisely reflect your current environment and actual costs as needed. For a quick analysis, you can skip this step, revisiting the default assumptions for refinement later.

Step 3: Review Total Cost Savings and Return on Investment (ROI)

Click on the “Next” button to see your customized cost savings, comparing your current (As Is) total cost of ownership (TCO) over the next three years (managing a non-virtualized / business as usual environment), and the cost savings and business benefits estimated for a virtualized VMware environment. Key metric and financial improvements are summarized at the top, while specific details for each solution are provided in the tables, graphs and charts. For each selected VMware solution, you can click on the solution name in the table or the tab to view cost savings / benefit, investment and ROI details for VMware Infrastructure 3, VMware Lab Manager and VDI independently.  Continue reading VMware TCO / ROI Calculator User’s Guide

Step by Step for vCenter Upgrade from 5.1 to 5.5

I am taking this Tutorial from VMware Communitiies (VMTN). This is a very common questions to ask, so I re-post it again in this blog.

Make sure below 6 tasks has been completed before starting of vCenter Upgrade.

  1. 2 hours before the upgrade disable all Schedule VM backups for vCenter or 3rd Party Tools
  2. Once backup disabled request Database Team to backup below databases 30 mins before the vCenter upgrade –
    1. vCenter Server database
    2. SRM database
  3. On vCenter, make a copy of the SSL certificates, copy them backup folder
  4. Backup Inventory Service database. Follow below procedure
  • On the source machine, open the command prompt in the vCenter Server and change the directory to vCenter_Server_installation_directoryInfrastructureInventory Servicescripts.
  • Run the following command at the prompt to back up the Inventory Service database.
  • backup.bat -file gdciventoryvcenter.bak
  • When the backup operation finishes, the message Backup completed successfully appears, copy the file to backup folder
  1. Backup the SSO configuration
    1. Click on start/programs/vmware
    2. Select Generate vCenter Single Signon Backup bundle, this creates a zip file on the desktop
    3. Select Generate vCenter single Signon log bundle
    4. Copy these files to backup folder
  2. 5 minutes prior to upgrade of vCenter

    Create a snapshot of vCenter.

    ********** UPGRADATION **********

Once the jobs or tasks written in above completed, we will start with vCenter Server Upgrade from 5.1 to 5.5

We need to upgrade the vCenter Server in below sequence.

  1. Single Sign On – SSO
  2. vSphere Web Client
  3. vSphere Inventory Service
  4. vCenter Service
  5. vCenter Update Manager
  6. VMware Site Recovery Manager

     

  7. Single Sign On Upgrade:

     

  8. Mount the ISO and kick off the SSO installer under custom upgrade.
    1. All the required install files for all products we are upgrading are located on each VC server under “d:vCenter 5.5 and related”

     

Continue reading Step by Step for vCenter Upgrade from 5.1 to 5.5

Fight the FUD – Oracle Licensing and Support on VMware vSphere

In this post I will copy-paste one of the Best reading for Virtualizing Business Critical Applications from Michael Webster’s blog. This can explain that Oracle Database can be virtualized in VMware! Enjoy!

These are the source :

http://longwhiteclouds.com/2012/07/21/fight-the-fud-oracle-licensing-and-support-on-vmware-vsphere

http://longwhiteclouds.com/2013/01/17/return-of-the-fud-oracle-licensing-on-vmware-vsphere/

http://www.vmware.com/files/pdf/techpaper/vmw-understanding-oracle-certification-supportlicensing-environments.pdf

—-

 

I keep hearing stories from Customers and Prospects where Oracle appears to be trying to deceive them for the purposes of extorting more license money from them than they are legally required to pay. I also keep hearing stories of Oracle telling them they would not be supported if they virtualized their Oracle systems on VMware vSphere. This has gone on now for far too long and it’s time to fight back and stop the FUD (Fear, Uncertainty, Doubt)!

In my opinion the best way for you to prevent this situation for your company is by knowing the right questions to ask, and by knowing what your obligations are. The aim for this article is to give you the tools to pay only what you legally owe, while making the most efficient and economic use of your licenses, and get the world class support that you are used to, even in a virtualized environment on VMware vSphere. All without sacrificing availability or performance.
I’m going to start this article by quoting Dave Welch, CTO, House of Brick – “I believe in paying every penny I owe. However, beyond that, it is my discretion to who or what I donate and in what amount. I have no patience with individuals or entities that premeditate the creation of OLSA compliance issues.  I similarly have no patience with the knowing spreading of FUD by some professionals in what could be construed as extortion of funds beyond customers’ executed contractual obligations. I will continue to vigorously promote and defend the legal rights of both software vendors and their customers even if that means I induce accelerated hair loss through rapid, frequent hat swapping.” Source Jeff Browning‘s EMC Communities article – Comments by Dave Welch of House of Brick on Oracle on VMware Licensing.

I agree with Dave on this. So I am going to show you how you can pay what you owe, while using what you pay for as efficiently and cost effectively as possible, and show you how you can still enjoy the full support you are entitled to. Without the scaremongering that sometimes accompanies discussions with Oracle Sales Reps.

For those that aren’t familiar with the term FUD, it is an acronym which stands for Fear, Uncertainty and Doubt. Something some companies and professionals seem to go to great lengths to create in the minds of customers.

FUD #1 – Oracle Licensing and Soft Partitioning
Oracle’s Server/Hardware Partitioning document outlines the different types of partitioning and how they impact licensing. Oracle may try and tell you that licensing a VMware environment will be more expensive as they don’t consider VMware Hard Partitioning. This is complete rubbish. This assertion is completely irrelevant unless you were only planning on deploying a single small database on a very small subset of a very large server. In this case you probably wouldn’t be using Enterprise Edition and may not be paying per CPU Core (Named User Plus instead). Why would you deploy such a system when you could easily purchase a server that is the right size for the job and licensed appropriately for the job? There is absolutely no requirement to run Oracle Enterprise Edition just because you are virtualizing your databases.

There is absolutely no increase in licensing costs over and above what you would have to pay for the same physical infrastructure to run your Oracle Database if you were running it in the OS without virtualization. You still have to pay what you owe, for what you use. The truth is that your costs could actually be significantly less when virtualizing on VMware vSphere as you can get more productive work done for the same amount of physical hardware, and therefore the license requirements and your costs will be significantly less. This is because you can run multiple Oracle databases on the same server and effectively share the resources, including memory, provided you take care during your design to ensure any undesirable performance impacts are avoided.  Take this image for example showing consolidating two dissimilar workloads on the same hardware (Source: VMware).

Continue reading Fight the FUD – Oracle Licensing and Support on VMware vSphere

Daftar Komprehensif mengenai Default URL, Username, dan Password di berbagai macam Produk VMware Inc.

Berikut ini adalah daftar yang sangat komprehensif mengenai default username dan password untuk berbagai macam produk dari VMware. Saya mengutipnya dari Blog Kendrick Coleman, agar tidak sering lupa jadi saya memasukkan ini di dalam blog BicaraIT.com.

 

Horizon Application Manager

http://IPorDNS/SAAS/login/0

http://IPorDNS

 

Horizon Connector

https://IPorDNS:8443/

 

vCenter Appliance Configuration

https://IPorDNS_of_Server:5480

username: root

password: vmware

 

vCenter Application Discovery Manager

http://IPorDNS

username: root

password: 123456

default ADM management console password is 123456 and the CLI password is ChangeMe

 

vCenter Chargeback

http://IPorDNS:8080/cbmui/

username: root

password: vmware

 

vCenter Infrastructure Navigator:

https://IPorDNS_of_Server:5480

username: root

password: Supplied during OVA deployment

 

vCenter Log Insight

https:// log_insight-host/

username: admin

password: password specified during initial configuration

 

vCenter MOB

https://vcenterIP/mob

 

vCenter Web Client Configuration

https://IPorDNS_of_Server:9443/admin-app

username: root

password: vmware

 

vCenter vSphere Web Client Access

https://IPorDNS_of_Server:9443/vsphere-client/

username: root

password: vmware

For vSphere 5.1  = Windows default username: admin@System-Domain

For vSphere 5.1 = Linux (Virtual Appliance) default username: root@System-Domain

For vSphere 5.5 = default username: administrator@vsphere.local
Continue reading Daftar Komprehensif mengenai Default URL, Username, dan Password di berbagai macam Produk VMware Inc.

VCDX – Supporting Documentation

Berikut ini, saya mengutip resource yang sangat baik dari http://vcdx133.com mengenai persiapan untuk mengambil sertifikasi VCDX. Sertifikasi tertinggi dari VMware Inc.

Once you have finished your design documents, you then have to prepare the supporting documentation.  The length of this task is very often underestimated by aspiring candidates, who either rush the job to make the submission and possibly have their application rejected due to incompleteness or miss their submission date.

 

List of articles in VCDX series:

  1. VCDX – Recipe for Success
  2. VCDX Study Plan – Networking
  3. VCDX Study Plan – Security
  4. VCDX Study Plan – Storage
  5. VCDX Study Plan – BC/DR
  6. VCDX Study Plan – Compute & vSphere
  7. VCDX – The Submission
  8. VCDX – The Presentation
  9. VCDX – D-Day
  10. VCDX – Think like a Panelist
  11. VCDX – I passed, now what?
  12. VCDX – Design Scenario Strategy
  13. VCDX – Troubleshooting Scenario Strategy
  14. VCDX – Mock Design Scenarios
  15. VCDX – Mock Troubleshooting Scenarios
  16. VCDX – Learn to speak “VCDXese”
  17. VCDX – How do I measure if my Customer Requirements are being met?
  18. VCDX – Logical & Physical Design Blueprints
  19. VCDX – Study Group Etiquette
  20. VCDX – Supporting Documentation

The term “Supporting Documentation” refers to the following documents/sections from the VCDX Blueprint:

  • Implementation Plan
  • Configuration Guide
  • Test Plan
  • Standard Operating Procedures

Assuming you have validated that your design meets your Customer’s Requirements, you now have to ensure that your supporting documentation will allow the design to be implemented, configured, tested and operated successfully.  This is where we separate the men from the boys, so much effort has gone into the design process, you then need to marshal your resources and push through the creation of the supporting documentation.

The strategy is very simple, create a linked list that maps from each physical design decision to the Implementation Plan, Configuration Guide, Test Plan and the SOPs.  This is summarised in the diagram below:

VCDX_Documentation_Overview

It is very important to maintain a unique numbering system throughout all of your documentation; this will allow you to quickly verify that all components and scenarios are covered and then collate them into a matrix to ensure that nothing is missed.  For example: supporting_documentation_template and supporting_documentation_matrix.

 

Source: http://vcdx133.com/2014/07/11/vcdx-supporting-documentation/

VSPHERE 5.5 | BEST PRACTICES SUMMARY

LOGO1

Berikut ini adalah Summary yang sangat baik untuk mengumpulkan Artikel mengenai Best Practice di VMware vSphere 5.5, saya mengutip dari blog Dan C Barber.

BEST PRACTICE SUMMARY: UPGRADING GOTCHAS

BEST PRACTICES SUMMARY: GENERAL MANAGEMENT & MONITORING

BEST PRACTICES SUMMARY: PERFORMANCE OPTIMIZATION

BEST PRACTICES SUMMARY: TROUBLESHOOTING

BEST PRACTICES RESOURCES

 

Source: http://www.datacenterdan.com/blog/vsphere-55-best-practices-summary