How to configure a Dell iDRAC card without rebooting

Posted on Updated on

First of all download the Racadm tool from the this link. It is included in Dell OpenManage DRAC Tools. The Dell Remote Access Controller (DRAC) console is management station software designed to provide remote management capabilities for the Dell systems. You can remotely connect to the DRAC hardware and access the DRAC features either by using a web browser or the RACADM Command Line Interface (CLI). RACADM CLI is the command line user interface to the DRAC.

Syntax Usage

The following shows an example of a simple RACADM subcommand, getsysinfo, used with each RACADM utility. See the end of this article for links to documentation containing the full list of RACADM commands.


Remote RACADM commands must include the ip address or hostname of the idrac, and the idrac username and password.

racadm -r <ip address or hostname> -u <username> -p <password> <subcommand>

racadm -r -u root -p calvin getsysinfo

NOTE: Remote racadm uses the web server SSL certificate of the iDRAC to authenticate the session. You will receive a warning message if certificates have not been configured or if the certificate is invalid. However, the command will execute normally following the message. If you wish to halt the command on certificate errors, use the -S option in the command. For information on configuring certificates on the iDRAC, see the user’s guide for your iDRAC linked at the end of this article.


You do not have to specify the ip address, username, or password in Local RACADM commands.

racadm <subcommand> eg. racadm getsysinfo

racadm getniccfg

racadm setniccfg –s
racadm getconfig -g cfgLanNetworking
racadm config -g cfgLanNetworking -o cfgNicIpAddress
racadm config -g cfgLanNetworking -o cfgNicNetmask
racadm config -g cfgLanNetworking -o cfgNicGateway
racadm config -g cfgLanNetworking -o cfgDNSServer1
racadm config -g cfgLanNetworking -o cfgDNSServer2
racadm config -g cfgLanNetworking -o cfgDNSRacName ServerName-DRAC
racadm config -g cfgLanNetworking -o cfgDNSDomainName

SSH/Telnet/Serial (Firmware) RACADM

You do not have to specify the ip address, username, or password in Firmware RACADM commands.

racadm <subcommand>   eg. racadm getsysinfo


racadm <Enter> – takes you to a racadm>> prompt  eg. racadm>>getsysinfo

Raising a support case for ProLiant/Blades Series Servers, the step by step approach!

Posted on Updated on

Now a days HP has segregated the support types, the server support comes under Hewlett Packard Enterprise.

Select your product

HP ProLiant BL Server Blades

HP ProLiant CL Servers

HP ProLiant DL Multi Node Servers

HP ProLiant DL Servers

HP ProLiant MicroServer

HP ProLiant ML Servers

HP ProLiant Packaged Cluster Servers

HP ProLiant Scalable Systems

HP ProLiant WS Workstation Blades

HP Server tc Series


if you are not able to find your product, check the below link to manually search the server model/ number in the Hewlett Packard Enterprise Products: eg. ProLiant DL360 Gen9


HP warranty and support

You will get log of results like below:


HP Support
Select the appropriate one, for me it is in yellow as above. Clicking it will land you to the product page as below. You will find Top issues, Most viewed solutions, manuals, Trouble a problem links which are very useful from troubleshooting point of view as all the known issues will be captured there. Apart from these you will find the latest drivers links with respect to the OS on the server etc. Most importantly, You can check the product warranty information from this page.


hp support page


Finally if the above of these do not help then you can raise case by clicking the below link. You need to create a HP passport login in case you do not have an account. HP Passport is a single sign in service that lets you use one User ID and password for all HP Passport-enabled websites.

Submit or manage support cases

hp support manager

You may also check existing ticket updates by providing the case ID.

I hope techies find it useful 🙂


Connections and Ports in ESX and ESXi

Posted on Updated on


A high resolution pdf can be downloaded here Connections and Ports in ESX and ESXi

VMware ESXi Release and Build Number History – A must for confirming your ESXi hosts are up to date!

Posted on Updated on

The following listings are a comprehensive collection of the flagship hypervisor product by VMware. All bold versions are downloadable releases.

vSphere ESXi 6.0

Name Version Release Build
ESXi600-201511001 ESXi 6.0 Express Patch 4 2015-11-25 3247720
ESXi600-201510001 ESXi 6.0 Update 1a 2015-10-06 3073146
VMware ESXi 6.0 Update 1 ESXi 6.0 Update 1 2015-09-10 3029758
ESXi600-201507001 ESXi 6.0b 2015-07-07 2809209
ESXi600-201505001 ESXi 6.0 Express Patch 2 2015-05-14 2715440
ESXi600-201504001 ESXi 6.0 Express Patch 1 2015-04-09 2615704
VMware ESXi 6.0 ESXi 6.0 GA 2015-03-12 2494585

 vSphere ESXi 5.5

Name Version Release Build
ESXi550-201512001 2015-12-08 3248547
ESXi550-201510001 ESXi 5.5 Update 3a 2015-10-06 3116895
VMware ESXi 5.5 Update 3 ESXi 5.5 Update 3 2015-09-16 3029944
ESXi550-201505002 ESXi 5.5 Patch 5 2015-05-08 2718055
ESXi550-201504002 Recalled 2015-04-30 2702864
ESXi550-201504001 ESXi 5.5 Express Patch 7 2015-04-07 2638301
ESXi550-201502001 ESXi 5.5 Express Patch 6 2015-02-05 2456374
ESXi550-201501001 ESXi 5.5 Patch 4 2015-01-27 2403361
ESXi550-201412001 ESXi 5.5 Express Patch 5 2014-12-02 2302651
ESXi550-201410001 ESXi 5.5 Patch 3 2014-10-15 2143827
VMware ESXi 5.5 Update 2 ESXi 5.5 Update 2 2014-09-09 2068190
ESXi550-201407001 ESXi 5.5 Patch 2 2014-07-01 1892794
ESXi550-201406001 ESXi 5.5 Express Patch 4 2014-06-10 1881737
ESXi550-201404020 ESXi 5.5 Express Patch 3 2014-04-19 1746974
ESXi550-201404001 ESXi 5.5 Update 1a 2014-04-19 1746018
VMware ESXi 5.5.1 Driver Rollup 2014-03-11 1636597
VMware ESXi 5.5 Update 1 ESXi 5.5 Update 1 2014-03-11 1623387
ESXi550-201312001 ESXi 5.5 Patch 1 2013-12-22 1474528
vSAN Beta Refresh 2013-11-25 1439689
VMware ESXi 5.5 ESXi 5.5 GA 2013-09-22 1331820

vSphere ESXi 5.1

Name Version Release Build
ESXi510-201510001 2015-10-01 3070626
ESXi510-201503001 5.1.0 Patch 7 2015-03-26 2583090
VMware ESXi 5.1 Update 3 5.1.0 U3 2014-12-04 2323236
ESXi510-201410001 5.1.0 Patch 6 2014-10-31 2191751
ESXi510-201407001 5.1.0 Patch 5 2014-07-31 2000251
ESXi510-201406001 5.1.0 Express Patch 5 2014-06-17 1900470
ESXi510-201404001 5.1.0 Patch 4 2014-04-29 1743533
ESXi510-201402001 5.1.0 Express Patch 4 2014-02-27 1612806
VMware ESXi 5.1 Update 2 5.1.0 U2 2014-01-16 1483097
ESXi510-201310001 5.1.0 Patch 3 2013-10-17 1312873
ESXi510-201307001 5.1.0 Patch 2 2013-07-25 1157734
ESXi510-201305001 5.1.0 Express Patch 3 2013-05-22 1117900
VMware ESXi 5.1 Update 1 5.1.0 U1 2013-04-25 1065491
ESXi510-201303001 5.1.0 Express Patch 2 2013-03-07 1021289
ESXi510-201212001 5.1.0 Patch 1 2012-12-20 914609
ESXi510-201210001 5.1.0a 2012-10-24 838463
KB2034796 5.1.0 Hot-Patch 837262
VMware ESXi 5.1 5.1.0 GA 2012-09-11 799733

vSphere ESXi 5.0

Name Version Release Build
ESXi500-201510001 2015-10-01 3086167
ESXi500-201502001 5.0.0 Patch 11 2015-02-26 2509828
ESXi500-201412001 5.0.0 Patch 10 2014-12-04 2312428
ESXi500-201408001 5.0.0 Patch 9 2014-08-28 2000308
ESXi500-201407001 5.0.0 Express Patch 6 2014-07-01 1918656
ESXi500-201405001 5.0.0 Patch 8 2014-05-29 1851670
ESXi500-201401001 5.0.0 Patch 7 2014-01-23 1489271
VMware ESXi 5.0 Update 3 5.0.0 U3 2013-10-17 1311175
ESXi500-201308001 5.0.0 Patch 6 2013-08-29 1254542
ESXi500-201305001 5.0.0 Express Patch 5 2013-05-15 1117897
ESXi500-201303001 5.0.0 Patch 5 2013-03-28 1024429
VMware ESXi 5.0 Update 2 5.0.0 U2 2012-12-20 914586
ESXi500-201209001 5.0.0 Patch 4 2012-09-27 821926
ESXi500-201207001 5.0.0 Patch 3 2012-07-12 768111
ESXi500-201206001 5.0.0 Express Patch 4 2012-06-14 721882
ESXi500-201205001 5.0.0 Express Patch 3 2012-05-03 702118
ESXi500-201204001 5.0.0 Express Patch 2 2012-04-12 653509
VMware ESXi 5.0 Update 1 5.0.0 U1 2012-03-15 623860
ESXi500-201112001 5.0.0 Patch 2 2011-12-15 515841
ESXi500-201111001 5.0.0 Express Patch 1 2011-11-03 504890
ESXi500-201109001 5.0.0 Patch 1 2011-09-13 474610
VMware ESXi 5.0 5.0.0 2011-08-24 469512

vSphere ESXi 4.1

Name Version Release Build
ESXi410-201404001 4.1.0 Patch 11 2014-04-10 1682698
ESXi410-201312001 4.1.0 Patch 10 2013-12-05 1363503
ESXi410-201307001 4.1.0 Patch 9 2013-07-31 1198252
ESXi410-201304001 4.1.0 Patch 8 2013-04-30 1050704
ESXi410-201301001 4.1.0 Patch 7 2013-01-31 988178
ESXi410-201211001 4.1.0 Patch 6 2012-11-15 874690
VMware ESXi 4.1 Update 3 4.1.0 U3 2012-08-30 800380
ESXi410-201206001 4.1.0 Express Patch 3 2012-06-14 721871
ESXi410-201205001 4.1.0 Express Patch 2 2012-05-03 702113
ESXi410-201204001 4.1.0 Patch 5 2012-04-26 659051
ESXi410-201201001 4.1.0 Patch 4 2012-01-30 582267
VMware ESXi 4.1 Update 2 4.1.0 U2 2011-10-27 502767
ESXi410-201107001 4.1.0 Patch 3 2011-07-28 433742
ESXi410-201104001 4.1.0 Patch 2 2011-04-28 381591
VMware ESXi 4.1 Update 1 4.1.0 U1 2011-02-10 348481
ESXi410-201011001 4.1.0 Express Patch 1 2010-11-29 320137
ESXi410-201010001 4.1.0 Patch 1 2010-11-15 320092
VMware ESXi 4.1 4.1.0 2010-07-13 260247


How to generate VMware ESXi logs and how to Upload via the FTP portal using a third party FTP client for a VMware Support Case

Posted on Updated on

How to generate VMware ESXi logs:

Identify the ESXi host on which the server is hosted, putty to the Host and run the following command. But before you run the command, you need to select a  desired datastore  to direct the support log bundle to a location using the same command (mentioning the destination path).

For example:

vm-support -s > /vmfs/volumes/datastorexxx/vm-support-Hostname.tgz

 Datastorexxx = will be datastore with free space

vm-support-Hostname.tgz = host name

  1. After the log bundle has been collected and downloaded from the datastore by browsing the particular datastore normally using the vSphere client, then upload the logs to the SFTP/FTP site.

How to Upload via the FTP portal using a Filezilla (FTP Client)
There are many third-party GUI-based FTP clients that run on multiple platforms. These clients are able to perform the operations in this article using an intuitive GUI interface. Feel free to use the FTP client of your choice, which supports passive mode.

FileZilla is a popular third party FTP client.

To upload files from Windows using FileZilla:

  1. Open the FileZilla client.
  2. Set the transfer mode to binary:

    Go to the Transfer menu > Transfer type > Binary

  3. Go to the File menu > Site Manager.
  4. Add the VMware FTP site to My Sites using the Site Manager. The credentials are:

    Address =
    Logon Type = normal
    User = inbound
    Password = inbound

  5. Click Connect.
  6. Change to the correct destination directory for your Support Request:
    1. If this is the first time you are uploading files to the VMware FTP Server for this case, create a directory in the root of the VMware FTP. To do this, right click the root directory on the remote site in the right pane and choose Create directory.
    2. If this is not the first time you are uploading files for this case, proceed to step 7.
  7. Change to your SR directory using the Remote site field.

    For example:

    Remote site: /12345678901


    1. For security reasons, you do not see any files or directories on the VMware FTP server, including files you have uploaded.
    2. The destination directory should contain numbers only. Do not enter letters or other characters.
  1. Once you connect to the correct destination directory, browse to the location of the log files on your local system using the file browser in the left pane or enter the full path in the Local site field.
  2. Right click the file and select Upload to start the transfer.
  3. Monitor the transfer progress in the Queued files pane.

How to power off a Virtual Machine on an ESXi host via Putty

Posted on Updated on

Sometime a virtual machine may not responsive and cannot be stopped or killed, then this is a workaround to reboot the virtual machine via putty.

The esxcli command can be used locally or remotely to power off a virtual machine running on ESXi 5.x or later.

  1. Open a console session where the esxcli tool is available, either in the ESXi Shell, the vSphere Management Assistant (vMA), or the location where the vSphere Command-Line Interface (vCLI) is installed.
  2. Get a list of running virtual machines, identified by World ID, UUID, Display Name, and path to the.vmx configuration file, using this command:esxcli vm process list
  3. Power off one of the virtual machines from the list using this command:esxcli vm process kill –type=[soft,hard,force]–world-id=WorldNumber

    Three power-off methods are available. Soft is the most graceful, hard performs an immediate shutdown, and force should be used as a last resort.
    Alternate power off command syntax is: esxcli vm process kill -t [soft,hard,force] -w WorldNumber

  4. Repeat Step 2 and validate that the virtual machine is no longer running.

Unable to view Roles and Features and receive error code 0x800706BE in Server Manager

Posted on

In this scenario, roles and features are not displayed with a yellow bang against them in the Server Manager window. You receive the following error message at the bottom of the Server manager if you try to open it:

Server Manager
Unexpected error refreshing Server Manager: The remote procedure call failed. (Exception from HRESULT: 0x800706BE)
For more information, see the event log: Diagnostics, Event Viewer, Applications and Services Logs, Microsoft, Windows, Server Manager, Operational.)

At the same time, the event below is added into the Microsoft-Windows-ServerManager/Operational log:

Log Name:      Microsoft-Windows-ServerManager/Operational
Source:        Microsoft-Windows-ServerManager
Date:          <date & time>
Event ID:      1601
Task Category: None
Level:         Error
User:          <user name>
Computer:      <computer name>
Could not discover the state of the system. An unexpected exception was found:
System.Runtime.InteropServices.COMException (0x800706BE): The remote procedure call failed. (Exception from HRESULT: 0x800706BE)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at Microsoft.Windows.ServerManager.ComponentInstaller.CreateSessionAndPackage(IntPtr& session, IntPtr& package)
at Microsoft.Windows.ServerManager.ComponentInstaller.InitializeUpdateInfo()
at Microsoft.Windows.ServerManager.ComponentInstaller.Initialize()
at Microsoft.Windows.ServerManager.Common.Provider.RefreshDiscovery()
at Microsoft.Windows.ServerManager.LocalResult.PerformDiscovery()
at Microsoft.Windows.ServerManager.ServerManagerModel.CreateLocalResult(RefreshType refreshType)
at Microsoft.Windows.ServerManager.ServerManagerModel.InternalRefreshModelResult(Object state)

Here are the steps to fix the issue:

  1. Get the Microsoft Update Readiness Tool from the location:
  2. Run the Microsoft Update Readiness Tool on the problematic computer.
  3. You open the %Systemroot%\Windows\logs\CBS\Checksur.log file after the scan was completed.
  4. You check corrupt information in the files. Here are some samples:

(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Package_for_KB978601~31bf3856ad364e35~amd64~~  Expected file name Package_for_KB978601_server~31bf3856ad364e35~amd64~~ does not match the actual file name

(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Package_for_KB979309~31bf3856ad364e35~amd64~~  Expected file name Package_for_KB979309_server~31bf3856ad364e35~amd64~~ does not match the actual file name


(f) CBS MUM Corrupt 0x800B0100 servicing\Packages\Package_for_KB978601~31bf3856ad364e35~amd64~~ servicing\Packages\ Package manifest cannot be validated by the corresponding catalog
(f) CBS MUM Corrupt 0x800B0100 servicing\Packages\Package_for_KB979309~31bf3856ad364e35~amd64~~ servicing\Packages\ Package manifest cannot be validated by the corresponding catalog


(f) CBS MUM Missing 0x00000002 servicing\packages\Package_114_for_KB955839~31bf3856ad364e35~amd64~~
(f) CBS MUM Missing 0x00000002 servicing\packages\Package_83_for_KB955839~31bf3856ad364e35~amd64~~

Further down you will see:

Unavailable repair files:

These files need to be copied into: %systemroot\Windows\Servicing\Packages

  1. You first need to gain control over that folder. In order to do this use the following commands:

    takeown /F c:\Windows\Servicing\Packages /D y /R

  2. Now assign full control using following command. This will grant you full control over the directory:

    cacls c:\Windows\Servicing\Packages /E /T /C /G “UserName”:F

  3. Now you need to gather the missing or corrupted files from the checksur log:
    Download the KB files for the missing files.

    servicing\packages\Package_for_ KB978601 ~31bf3856ad364e35~amd64~~

  4. Unpack them using the following command:

    Expand -F:* UpdateKBXXXX.msu x:\DestinationDirectory

  5. After you expand you will see a File. Expand it as well:

    Expand -F:* UpdateKBXXXX.CAB x:\DestinationDirectoryCAB
    Inside of this cab you will need to grab 2 files: update.mum and

  6. Rename the gathered update.mum and files exactly as they are in the checksur.log:

    Ex.: update.mum for KB978601 will be Package_for_ KB978601 ~31bf3856ad364e35~amd64~~
    Do the same for for all the other missing/corrupt files and place them into the directory specified in checksur.log (/servicing/packages)

After these steps the problem should be fixed. No reboot required.

Robocopy command to copy huge files and monitor their status

Posted on

robocopy “source_folder” “destination_folder” /s /e /tee /log+:”C:\temp folder\rcpylog.txt

FYI :- log+ option will create a log file which can be monitored by anyone who have access to the server.

How to generate a HP Survey log Offline?

Posted on

1) Boot the server using Smart Start CD

2) Select language as English (US), keyboard layout as US English and click Next

3) Accept HP EULA by clicking Agree button

4) Now you are the home page of SmartStart CD

5) Click on Maintenance from SmartStart CD Homepage

6) Now you are at the Maintenance Options window
7) Select HP Insight Diagnostics

8) The Survey tab is displayed by default

9) Change CATEGORY from ‘Overview’ to ‘All’ (The page would refresh after this)

10) Change VIEW LEVEL from ‘Summary’ to ‘Advance’ (The page would refresh after this)

11) Click ‘Save’ (internal or USB floppy drive would be required to save the log file)

How to generate a Survey log Online

Install HP Insight Diagnostics from the HP Service Pack for ProLiant

  1. Obtain the HP Service Pack for ProLiant (SPP) ISO image from


  1. As the super-user (root), mount the ISO image using the GUI, or from the command line using

the mount command.

NOTE: You may also burn the ISO image to a writable DVD using appropriate software, then insert the DVD into the server’s optical disk drive and open its contents.

  1. As the super-user (root), navigate to the directory hp/swpackages and run hpsum.exe.
  2. In HP Smart Update Manager (SUM), configure the Default source and localhost target. See HP SUM documentation for more information.
  3. Choose Select Components and ensure that the HP Insight Diagnostics Online Edition for Linux

component is selected. Select or unselect other components as desired, then click OK when done.

  1. Click Install to install Insight Diagnostics and any other selected components.
  2. Click Exit to exit HP SUM.

Starting HP Insight Diagnostics for Windows Online Edition

Starting from the Windows Start menu

  1. Go to Start > All Programs > HP System Tools.
  2. Select HP Insight Diagnostics Online Edition for Windows.

Starting from the HP Systems Insight Manager

  1. In HP Systems Insight Manager, go to the Device page.
  2. Select HP Insight Diagnostics from the Device Links box.

Starting from the HP System Management Homepage

  1. Click HP System Management Homepage on the Windows desktop.
  2. Click Webapps.
  3. Click HP Insight Diagnostics in Other Agents.

Starting HP Insight Diagnostics for Linux Online Edition from the HP System Management Homepage

  1. Open the browser.
  2. In the address field, enter the following:


  1. Press Enter. The System Management Homepage appears.
  2. Click Webapps.
  3. Click HP Insight Diagnostics in Other Agents

The Survey tab is displayed by default

Change CATEGORY from ‘Overview’ to ‘All’ (The page would refresh after this)

Change VIEW LEVEL from ‘Summary’ to ‘Advance’ (The page would refresh after this)

Click ‘Save’ (internal or USB floppy drive would be required to save the log file)

How to backup and restore share/NTFS permissions

Posted on

This can come handy in critical situations. By following some steps, backup and restore of the Share/NTFS permissions can be done. Here it is how:

Share permissions Backup/Restore

To backup share permissions, export the Shares registry key.

1.Open Regedit to the following location:


2.Right-click the Shares registry key and select Export. Give it a file name such as shareperms.reg.

When you want to restore the permissions, double-click shareperms.reg to import it back into the registry.

Use the Reg tool to backup the registry key from the command line:

reg export HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares shareperms.reg

If you need to restore it at some point, just run:

reg import shareperms.reg

NTFS permissions Backup/Restore

Use this command to backup NTFS permissions:

icacls d:\data /save ntfsperms.txt /t /c

The /T switch allows it to get subfolder permissions too. The /C switch allows it to continue even if errors are encountered (although errors will still be displayed).

Use this command to restore them:

icacls d:\ /restore ntfsperms.txt

Note that in the command to save the permissions, I specified the target folder D:\Data, but when I restored them, I specified just D:\ as the target. Icacls is a little funky like that, and here’s why.

If you open the text file with the exported permissions (ntfsperms.txt in the above example), you’ll see that Icacls uses relative paths (in bold below). Underneath the relative paths are the permissions for the folders in Security Descriptor Definition Language (SDDL) format.







Had I specified D:\Data in the command to restore the permissions, it would have failed looking for a D:\Data\Data folder:

D:\>icacls d:\data /restore perms.txt

d:\data\data: The system cannot find the file specified.

Successfully processed 0 files; Failed processing 1 files

You might think specifying D:\ as the target in the restore command may somehow mess up the permissions on other folders at that level, but as you can see from the ntfsperms.txt output file, it only has information about the Data folder and sub folders, so that is all it will change.