System Administrator

VMware VC Client Error: Unable to contact the MKS or VMRC error When we try to open the console from VC we use to get error on the TOP. To resolve this issue, remove the environment variable from the vSphere Client machine or vCenter Server:  Step 1:  Migrate the VM from existing esx to another esx. or Step 2: 1.     Click Start > Run, type sysdm.cpl, and press Enter. The System Properties window opens. 2.     Click the Advanced tab. 3.     Click Environment Variables. 4.     Remove any user variable and any system variable named User . 5.     Reboot Windows and launch vSphere Client. Step 3: If the issue persists, end any vmware-vmrc.exe processes in the Windows Task Manager: 1.     Close all vSphere Client sessions. 2.     Open Windows Task Manager. 3.     Search for any vmware-vmrc.exe processes and end the process. 4.     Start the vSphere Client ...

Many customer/service request we receive from our client is.. is it possible to reduce the disk? This means the files inside the VM, but the size of the VMDK as well.   So I wanted to shrink my VMDK size as much as possible.  After cleaning up the VM itself and running  sdelete , it’s time to shrink the VMDK. First let’s review the actual usage of it: The virtual disk size can be seen with  ls –lh *.vmdk .  In my example, I have a  40 GB  virtual size. To see the ‘real’ size of the vmdk, run  du –h *.vmdk .  This gives us a  36 GB  size (while the VM itself actually uses about 10 GB). Issue the command  vmkfstools –punchzero  VM.vmdk.  This will take a while so be patient (and oh yes, you VM must be powered off). On a 40 GB VMDK it took me about 10 minutes, but this will depend mostly on your SAN speed. After it’s done, let’s re-issue  du –h *.vmdk . N...

iSCSI Target Server – windows 2012 server standard   Error: Unable to import the virtual disk. A Virtual disk with that file path already exists When I try to import the virtual disk into Windows Server 2012 iSCSI Target Server, I encountered this error : Problem: The registration of virtual disk in iSCSI Target is not deleted properly in the registry . Solution: 1 . To v erify the iSCSI Target VHD that cause the issue Open Registry Editor and navigate to the following path      "HKLM\SOFTWARE\Microsoft\iSCSI Target\WTDisks" 2. Delete the value from the corresponding ID 7. Lastly, "Microsoft iSCSI Software Target" Service must be restarted . Verify the iSCSI Target VHD that cause the issue

-           Production server clone Step 1: Take the backup or image copy if the source machine. Step 2 : convert the source machine from domain to workgroup                ( Note : 1. Before convert into workgroup just take the information of SID’s                             2. After convert into workgroup try to find the SID’s ) Step 3: proceed with clone request Step 4: Once the clone VM got deployed.                 Task 1: Update the IP Details and change the hostname to new hostname                 Task 2: Reboot the machine        ...

Blue Screen of Death If you have been working on computers or are just starting to use them, one of the most disturbing events that can occur is the BSOD or Blue Screen of Death. The BSOD is actually an error screen that is displayed by specific operating systems informing the user that a critical system error has occurred. The Blue Screen of Death can be found on many different types of operating systems, but is most notably infamous for occurring on Microsoft Windows Operating Systems. Common Causes of the Blue Screen of Death Occurring\ Not Cause 1. It doesn’t occur because of operating system Cause 1. Including a poorly written device driver 2. Faulty memory 3. Incompatible DLL’s or a corrupt Registry. (3rd party software) Poorly written device driver: A device driver is usually created by a third party company to run a device such as a peripheral (printer, scanner, mouse, etc). These third party companies’ create small driver programs which make it possible for these devices t...

Windows 2008 R2 Remote Desktop Service The Remote Desktop Service (RDS) on windows 2008 server R2 were tested and implemented successfully; Required Parameters: Priority Host Farm requires xx numbers of windows 2008 R2 64bit server. If the Server are installing on ESX Host, Host must support 64bit OS, All HOST Farm Servers are in Same Subnet Networking. All the host Farm servers are belongs to Domain with Admin access policies Users Groups are defined for HOST FARM to access App from Intranet & Internet The Windows Server 2008 R2 Remote Desktop Services (RDS) architecture consists of the following components: Active Directory Domain controller RD Session Host (RDSH) Server RD Connection Broker (RDCB) Server RD Web Access server RD Gateway server RD Licensing Active Directory Domain Deployment Scenario: On deploying windows 2008 R2 RDS, we need integrated with the active directory that include the groups policy setting and all the Remote Desktop users Roles w...

Add Multiple Users using PS $objOU=[ADSI]“LDAP://OU=OUNAME,DC=DOMAIN,DC=com” $dataSource=import-csv “user.csv” foreach($dataRecord in $datasource) { $cn=$dataRecord.FirstName + ” ” + $dataRecord.LastName $sAMAccountName=$dataRecord.FirstName + “.” + $dataRecord.LastName $givenName=$dataRecord.FirstName $sn=$dataRecord.LastName $sAMAccountName=$sAMAccountName.ToLower() $displayName=$sn + “, ” + $givenName $userPrincipalName=$sAMAccountName + “Prasanth” $objUser=$objOU.Create(“user”,”CN=”+$cn) $objUser.Put(“sAMAccountName”,$sAMAccountName) $objUser.Put(“userPrincipalName”,$userPrincipalName) $objUser.Put(“displayName”,$displayName) $objUser.Put(“givenName”,$givenName) $objUser.Put(“sn”,$sn) $objUser.SetInfo() $objUser.SetPassword(“Password”) $objUser.psbase.InvokeSet(“AccountDisabled”,$false) $objUser.SetInfo() }