Author Archives: Melbin Mathew

About Melbin Mathew

I am Melbin Mathew, Systems Engineer from Kerala, India. I live with my parents, daughter and my wonderful wife. I graduated in 2004 with a bachelor’s degree in Electronics and Hardware from Mahatma Gandhi University, Kottayam and completed certification in MCITP, RHCE, CCNA, VCP ...Read More

VMware virtual IDE to virtual SCSI hard disk conversion steps – Windows XP

I was trying to upgrade a Windows XP 32bit machine to Window 7, the hard part was the hard disk free space was nearly full and I can’t expand the drive as it is IDE. VMware virtual machine Edit settings is not allowing me to expand the hard disk, as the expansion setting shows greyed out. To expand the Windows XP hard disk, first the disk controller needs to be changed to SCSI.

VMare virtual machine IDE to SCSI conversion involve six parts,

  1. Adding a new SCSI disk to the virtual machine.
  2. Install iSCSI drivers on the virtual machine.
  3. Install VMware tools.
  4. Detach the IDE hard disk.
  5. Edit .VMDK file and change the controller type.
  6. Reattach the hard disk.

Imp: Take a backup of the virtual machine before proceeding.

To convert the IDE disk to SCSI:

  • Download the driver (LSI20320-R controller) from the LSI site

    (
    Windows XP SP3 virtual machines require the LSI Logic driver version 1.34.02.

    ESXi 4.1 hosts with Windows XP virtual machines need the LSI Logic driver version 1.34.02. The LSI Logic 1.34.02 driver filename is SYMMPI_SCSI_WinXP_x86_1.34.02.zip.

    ESX 4.0 hosts with Windows XP virtual machines need the LSI Logic driver version 1.28.03.

    The Windows Hardware Quality Labs (WHQL) 1.20.18.00 driver for Windows XP filename will be LSI20320-R_xp_50700_01034132IT_1201800_1005239.zip .

    The 1.28.03 driver download contains another zip file named symmpi_wXP_1201800.zip . Make a floppy image of the contents of symmpi_wXP_1201800.zip and insert this floppy disk when you are prompted for a driver disk during the Windows XP installation process. )

  • Power off the virtual machine.
  • From the Edit Settings menu for this virtual machine:
    • Click Add > Hard Disk > Create New Virtual Disk.
    • Change the Capacity
      to 1 GB and click Next.
    • Ensure that the Virtual Device Node is set to SCSI.
    • Complete the wizard and select the New SCSI Controller.
    • If the current type is not LSI Logic Parallel Select Change Type, change the type toLSI Logic Parallel.
    • Click OK.
    • Choose the same controller as in Step 4 as the adapter type. The SCSI ID should read SCSI 0:0.

  • Power on the virtual machine.
  • Follow the Found New Hardware wizard or in the Windows device manager inside the Windows guest and select the unknown device.
  • Right-click Update Driver and select the LSILogic SCSI controller driver downloaded earlier. This installs the drivers for the LSILogic SCSI controller inside the guest operating system.

  • Install latest VMware Tools and reboot.
  • Power off the virtual machine.
  • Locate the datastore path where the virtual machine resides.
    For example:
    # cd /vmfs/volumes/datastore_name/vm_name/
  • From the ESX Service Console, open the primary disk (.vmdk) using the vi editor. For more information, see Editing files on an ESX host using vi or nano (1020302).
  • Look for the line:

    ddb.adapterType = “ide”

  • To change the adapter type to LSI Logic change the line to:

    ddb.adapterType = “lsilogic”

    To change the adapter type to Bus Logic change the line to:

    ddb.adapterType = “buslogic”

    In some instances the entry appears as 

    ddb.adapterType = “legacyESX”.

    In this case change the line to:

    ddb.adapterType = “lsilogic”

  • Save the file.
  • From VMware Infrastructure/vSphere Client:
  1. Click Edit Settings for the virtual machine.
  2. Select the IDE virtual disk.
  3. Choose to Remove the Disk from the virtual machine.
  4. Click OK.Caution: Do not choose delete from disk.
  1. From the Edit Settings menu for this virtual machine:
    1. Click Add > Hard Disk > Use Existing Virtual Disk.
    2. Navigate to the location of the disk and select to add it into the virtual machine.
    3. Choose the same controller as in Step 9 as the adapter type. The SCSI ID should read SCSI 0:0.
  2. If a CDROM device exists in the virtual machine it may need to have the IDE channel adjusted from IDE 0:1 to IDE 0:0. If this option is greyed out, remove the CD-ROM from the virtual machine and add it back. This sets it to IDE 0:0.

Reference: VMware KB 1007035 & 1016192

 

Stop Error “CRITICAL_STRUCTURE_CORRUPTION

The guest OS stops running with Stop Error “CRITICAL_STRUCTURE_CORRUPTION”, on such condition we need to manually edit the virtual machine setting and change CPUID Mask as mentioned below. This problem is commonly seen while hosting newer versions of operating systems and is resolved in vSphere 5.0 Update 3

To manually create a CPUID mask for the affected virtual machines:

  • Power down the virtual machine.
  • Right-click the virtual machine and click Edit Settings.
  • Click the Options tab.
  • Select CPUID Mask under Advanced.
  • Click Advanced.
    • For Intel:
      • Under the Register column, locate the edx register under Level 80000001.
      • Paste this into the value field:—-:0—:—-:—-:—-:—-:—-:—-For example,

        cpuid.80000001.edx = —-:0—:—-:—-:—-:—-:—-:—-

    • For AMD:
      • Select the AMD Override tab.
      • Change cpuid.80000001.edx.amd = ———–H——————– to
        cpuid.80000001.edx.amd = —-0—————————
  • Click OK to close the virtual machine properties.


Error installing Windows server role and feature required for the Exchange 2010

Go the below warning message “error #install-windowsComponent –ShortNameForRole “AdminTools” – ADToolsNeeded $RoleADTools Needed”.

Exit the 2012 Exchange installation

Enable the IIS Management Tools

Download latest Microsoft Exchange SP3 the package supported for Windows 2012. Extract to a temporay location and run the Setup.exe as Administrator.

Check “Automatic install Windows server role and feactures required for Exchange”

How to set IIS website URL path redirection

How to set IIS website URL path redirection

Sometimes we used to get requests for redirecting website URL; the process involves configuring the webserver to redirect the client request to another target allowing bypassing the requested URL without any manual interference and disturbance. This website redirection often required for newly purchased domains list, maintenance websites, internal websites, redirect website to another web server like JBOSS etc.

The website needs to host in IIS and DNS points to the IIS webserver. Header value should be set to recognize the hosted website. The two 2 methods that was commonly used are,

1st Method

1. Go to Windows Run, type the command “inetmgr” to open IIS manager console. Choose the website which we need to redirect.

2. Open properties and select Home Directory.

3. Change the radio mark to “A redirection to a URL” and specify the target URL. Click Apply and stop and start this particular website.

2nd Method

1. Go to Windows Run, type the command “inetmgr” to open IIS manager console. Choose the website which we need to redirect.

2. Open properties and select Home Directory and identify the HOME directory (eg: c:\inetpub\wwwroot)

3. Open the home directory and create a new index.HTML (backup if there any)

4. Add the HTML redirect code and stop/start this particular website.

<html><meta http-equiv=”refresh” content=”0;url=http://techiesweb.com/alpha” /></html>

Repair broken Windows trust relationship between domain controller and client machine

Repair broken trust relationship between domain controller and client machine

Trust as the word indicates “Allow without fear”, the domain controller and client trust each other using a bond. Clients accept securities, policies, authentication mechanism etc. deployed in the domain controller and domain controller accepts and agrees communications from client machine. If the trust was broken, it fails the communication between domain controller and the client machine.

There are certain conditions the security bond between clients and domain controller broke, I would like to share the method that I use to fix the issue.

Better ways to fix Windows trust relationship failure issues. I cannot tell this would be a complete solution, but like to share the knowledge and effort.

First Method

  1. Disjoin the trust broken client machine from domain.
  2. Search the Active Directory computers and delete the computer account. The computer account will not be removed immediately and will be taking some time. If we suddenly rejoin the client machine, it will be picking the existing computer account for creating the bond (SID).
  3. Add the client computer back to domain.

Second Method

  1. Ensure the client machine clock is synchronized with the domain controller time, otherwise the trust relation will be having issues. The clock cannot be slow and I don’t think it will allow more than 5 minutes.

Third Method

  1. The searches the computer account in Active directory and reset the password, the computer account password changes automatically on certain period (30 days default).

Fourth Method

  1. Never have duplicate machine names in same network and apply proper SID changes if the machine were cloned.

Fifth Command Line Method

1)      Find out the domain controller that was used by the client machine.

        Netdom query dc

2)      Test the trust relationship of the machine using PowerShell command.

Test-ComputerSecureChannel –Server *dc name* -Verbose

  • If command output returns False, proceed to 3rd step.

3)      Repair the trust relationship of the client machine using PowerShell command.

Test-ComputerSecureChannel –Server *dc name* -Repair -Verbose

  • If the command output returns error message “Cannot find the computer account for the local computer from the domain controller”, go to Active directory and create a new computer account for the client machine and rerun the PS command once again.
  • If successful repaired, the command output show “True”.

repair trust relation.techiesweb.com

 

How to install and enable Remote Server Administration Tool in Windows 8 and 8.1

How to install and enable Remote Server Administration Tool in Windows 8 and 8.1

Remote Server Administration tool have several command line utilities that helps Administrators to investigate problems with the client computers. By default it is not enabled and installed.

Download appropriate version of Remote Server Administration from Microsoft website

Remote Server Administration Tool Windows 8

Remote Server Administration Tool Windows 8.1

Steps Involved

  1. Download and install the Microsoft package.
  2. Reboot the machine.
  3. Select Control Panel, Select Programs and Features and Click Turn Windows Features on or OFF.
  4. Select Remote Server Administration Tools and check appropriate Tool and Click OK

    Example:

    Netdom command is now recognized and available for Administration purpose.

     

Windows Shadow command to interact/connect with a user Remote Desktop Session

Windows Shadow command to interact/connect with a user Remote Desktop Session

Purpose of Shadow Utility

This Window feature allows a remote (RDP) user to interact with another remote user of the same server. Shadow allows both the users to view and interact with the remote desktop session.

For example: if don’t have Gotomeeting, WebEx to call the user for a meeting and the user is having less bandwidth, to view the problem that user facing in the remote desktop session, shadow the user session, view the issue and recommend the fix.

Shadow Remote Desktop Session on the terminal server

Scenario describes with two users O and M, where O wants to shadow M Remote Desktop session.

  1. Both user need to login the terminal server using Remote Desktop Connection.
  2. User O need to open Window “Task Manager” and identify the remote Session ID used by M.

  3. User need to open command prompt with Administrator privilege and enter the command
    “Shadow rdp-tcp#0″
  4. User M is prompted with a wizard for allowing access for O, after granting the access user session of M is shadowed.

Remote desktop shadow command line in Windows 8.1

An administrator can also run the following command line on a machine with the Windows 8.1 MSTSC.EXE package.

Mstsc.exe [/shadow:sessionID [/v:Servername] [/u:[Username]] [/control] [/noConsentPrompt]]

/shadow:IDStarts shadow with the specified sessionID.

/v:servernameIf not specified, will use the current server as the default.

/u:usernameIf not specified, the currently logged on user is used.

/controlIf not specified, will only view the session.

/noConsentPromptAttempts to shadow without prompting the shadowee to grant permission.

Before running mstsc.exe /shadow, it is assumed that the administrator would have found the user’s session ID using some other mechanism, such as qwinsta.exe.

Shadow desktop of users using Windows 2012 Remote Desktop Service

Select Remote Desktop Services, Choose the user, right click and select Shadow



Query Remote Desktop Session details using Command line

query session [<SessionName> | <UserName> | <SessionID>] [/server:<ServerName>] [/mode] [/flow] [/connect] [/counter]

Parameter Description
<SessionName> Specifies the name of the session that you want to query.
<UserName> Specifies the name of the user whose sessions you want to query.
<SessionID> Specifies the ID of the session that you want to query.
/server:<ServerName> Identifies the RD Session Host server to query. The default is the current server.
/mode Displays current line settings.
/flow Displays current flow-control settings.
/connect Displays current connect settings.
/counter Displays current counters information, including the total number of sessions created, disconnected, and reconnected.
/? Displays help at the command prompt.

The User Profile Service service failed the logon, user profile cannot be loaded

The User Profile Service service failed the logon, user profile cannot be loaded

After enabling disk quota setting for one of the server, the users were unable to login. Disabling the disk quota will be enable them logon the server.

Searching for the cause, we discovered the quotas were also applied to System Accounts, which prevent the correct functioning of the system accounts. The disk usage of the system user accounts where much above the quota limit that we have implemented causing failures.

Solution is to set system accounts with Unlimited quota usage thus allow their proper workings.

Step-by-Step Remote Desktop Connection Broker installation in Windows 2012 – Page 5

Step-by-Step Remote Desktop Connection Broker installation in Windows 2012 – Page 5

Step (5), Testing the RDCB and RDW deployments

This page explains the test process for the deployment of RDCB, RWA and RDSH

Open remote desktop connection and connect to rdfarm.techiesweb.com and login with domain user accounts.

The sessions can be viewed from connections

Open RWA URL, in my case https://meow.techiesweb.com/RDWeb, login with domain account

Published remote apps are listed, selected Calculator

Connecting to RDSH server

Apps opened.

Step-by-Step Remote Desktop Connection Broker installation in Windows 2012 – Page 4

Step-by-Step Remote Desktop Connection Broker installation in Windows 2012 – Page 4

Step (4), Publish Remote Apps in RDW

This page explains the steps to publish RemoteApp in Remote Web Access.

Choose Overview of Remote Desktop Services

Select the rdfarm.techiesweb.com collections, select Tasks and select Publish RemoteApp Programs

Choose the applications to publish and click Next

Click Publish


 

Progressing…

 


Completed, Close