How to rdp into your linux server

Remote Desktop Protocol (RDP) is a proprietary protocol developed by Microsoft , which provides a user with a graphical interface to connect to another computer over a network connection. The client PC uses RDP client software (often mstsc.exe) for this purpose, while the other computer must run RDP server software. This tutorial will teach you how to RDP to Linux machines.

Open your terminal in Linux machine then type the following command line in it (Ubuntu-based machines!)

 sudo apt-get install xrdp  

In fedora-based machines you can use

 yum install xrdp  

It will will ask permission to install the package , so just type your admin password and hit enter, and then type ” y ” to continue

This will install the xrdp package and start the RDP service in your Linux machine. Now you will need to determine the IP of the Linux machine. For that, type following command line in terminal:


In this case my Linux machine`s IP is Now type mstsc in the Windows Search field, which will open up the following window:

Now, simply type your Linux machine`s IP in the Computer: field, and then click connect. You will likely need to click through an authentication/version warning. Now you can see a xrdp login session. At this point, type your username and password for the Linux machine and click OK.

You are now connected to the Linux PC via RDP!

How to add Custom Drivers to VMware Esxi iso image !

How to add Custom Drivers to VMware Esxi iso image !

Hi friends once i have try to install VMware Esxi in my old pc . but it failed because absence of network driver in it , so i have to customise Esxi image and add driver to it

For this you will need ESXi-Customizer
Download from this link 
used this driver vmware-bootbank-net-r8168.vib

Run ESXi-Customizer-v2.7.2 as Admin

This will extract to a folder open it and run “ESXi-Customizer.cmd ” as Admin

Brwose VMware.iso

Browse Destination

Browse Driver

Browse VMware.iso



Configuring Raid 5 With 1 Hot Spare in HP Proliant ML310e Gen8

What is RAID 5


RAID 5 comprises block-level striping with distributed parity. Unlike in RAID 4, parity information is distributed among the drives. It requires that all drives but one be present to operate. Upon failure of a single drive, subsequent reads can be calculated from the distributed parity such that no data is lost. RAID 5 requires at least three disks.
In comparison to RAID 4, RAID 5’s distributed parity evens out the stress of a dedicated parity disk among all RAID members. Additionally, read performance is increased since all RAID members participate in serving of the read requests.

Diagram of a RAID 5 setup with distributed parity with each color representing the group of blocks in the respective parity block (a stripe). This diagram shows left asymmetric algorithm


hot spare disk is a disk or group of disks used to automatically or manually, depending upon the hot spare policy, replace a failing or failed disk in a RAID configuration.

The hot spare disk reduces the mean time to recovery (MTTR) for the RAID redundancy group, thus reducing the probability of a second disk failure and the resultant data loss that would occur in any singly redundant RAID (e.g., RAID-1, RAID-5, RAID-10). Typically, a hot spare is available to replace a number of different disks and systems employing a hot spare normally require a redundant group to allow time for the data to be generated onto the spare disk. During this time the system is exposed to data loss due to a subsequent failure, and therefore the automatic switching to a spare disk reduces the time of exposure to that risk compared to manual discovery and implementation.

The concept of hot spares is not limited to hardware, but also software systems can be held in a state of readiness, for example a database server may have a software copy on hot standby, possibly even on the same machine to cope with the various factors that make a database unreliable, such as the impact of disc failure, poorly written queries or database software errors. 

Adding License key in HP iLO

How to add License key to HP iLO 

go to this url then click on License tab

choose license you want

for this tutorial i have chosen 60 days trial license

you will receive an e-Software confirmation mail

follow the link which is given in you email 
you will get your License 
after that enter your iLO 
Click administration

Enter you Licence Key 
Click Install 
Done Enjoy HP iLO !

How to Install & configure iLO, HP Integrated Lights Out (iLO) on Android

go to Google play and search HP iLO or here is the link to Google Play 

Supported servers

  • HP ProLiant Gen8 Servers
  • HP ProLiant G7 Servers

Supported mobile operating systems

  • Android 2.2 or greater
  • iOS 4.3 or greater


  • Operate the server power switch
  • Use the Remote Console to interact with the operating system, including BIOS and ROM configuration changes
  • Mount an ISO CD/DVD image. The disk image is available on the server as a USB CD/DVD drive. You can boot from the disk image and deploy an operating system
  • Launch HP iLO scripts and monitor their progress
  • Access the iLO web interface
  • Store the list of servers you want to manage
install it and launch it 

after launching the application click 
configure iLO option
add assigned ip for iLO 
Login name and password

click done after adding the details 
click the iLO ip 
you will get 3 options 
  1. Remote Console
  2. Lauch Script
  3. iLO Web Interface
click Remote Console
 for using iLO

Quick tips

  • Show/Hide menu bar – Tap once with two fingers to show or hide the menu bar in the Remote Console
  • Show/Hide iLO web interface – Tap the server health icon in the Remote Console to show or hide the iLO web interface
  • Ctrl/Alt/Del Command – Tap Ctrl+Alt+backspace to enter the Ctrl+Alt+Del command

Intelligent Provisioning 1.60 breaks 2008 R2 install (will not accept product key during setup)

Intelligent Provisioning 1.60 breaks 2008 R2 install (will not accept product key during setup)

On HP Proliant ML 310e V2 Gen8 / DL380p Gen8 servers to install 2008R2 /2014R2 using IP 1.60.  After the GUI for Windows setup starts, it fails on the autounattend.xml that IP 1.60 generates on the ProductKey.

After the setup fails it drops you back to a command prompt in WinPE

in the command prompt type the following command

notepad c:autounattend.xml 

this will now open up autounattend.xml in notepad

now press ctrl + f and search for the string ProductKey

just below this string insert a new line contains the string “only the tags”
now save the file
then type the command to begin the installation process


installation will end fine 🙂

Pin It on Pinterest