The connection cannot be completed because the remote computer that was reached is not the one you specified. This could be caused by an outdated entry in the DNS cache. Try using the IP address of the computer instead of the name.


If you are facing this error message when trying to RDP to a Domain-joined Server :

The connection cannot be completed because the remote computer that was reached is not the one you specified. This could be caused by an outdated entry in the DNS cache. Try using the IP address of the computer instead of the name.


1st to check is as told by the message; DNS configuration. Client-side and Server-side.

If that’s fine, the problem is elsewhere.

You should be able to connect using the IP address


using the Hostname but login with a Local Account instead of a Domain Account.


If I’m correct, your Server CLOCK is not Synchronized with your Domain. Simply Sync it using w32tm or modify it manually and try to connect.


Hope this helps.


WSUS – Client stuck at 0% when downloading Windows 10 version 1703 followed by error 0xc1800118

Download issue resolved by adding the MIME type .esd (application/octet-stream) into IIS.

Edit : it seems it only solve the download issue. Following update and steps have to be done. This should also update WSUS and add the MIME type .esd.

Once download is completed, client was unable to install the upgrade; error 0xc1800118. 

  • Install KB3159706 from Windows Update Catalog and follow the following steps from MS Support :

  • Check the WSUS Db and repair it :



Edit : Finally, I ended by recreating the SUSDB as the above did not work and CU 1703 won’t install.

Remote Desktop Services – Service won’t start. Error: 1075 – the dependency does not exist or has been marked for deletion

The Remote desktop Services won’t start.

Error: 1075 – the dependency does not exist or has been marked for deletion.

Solution: Backup your Registry then Delete the “DependOnService” key in “\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService”. RDS service should start a next boot.


Activate P2V Windows XP or Server 2003 if OEM licence

Issue: After visualizing a physical Windows XP machine, Windows requires activation.

Background: After converting a PC from physical to virtual, Windows recognizes that there has been a hardware change.  This will send it into “Activation Mode”, which will require you to activate Windows XP before use.  In order to work around this, you can apply a new VALID key to your Windows XP installation.

Resolution: Recreate the converted VM’s config files, boot to the Windows installation disk and run the Repair function, which will allow you to specify a Windows XP license key.  You will need to load the VMware SCSI Controller drivers before repairing.


–  Ensure the PC is powered on and networked

  • Clean up any unnecessary data on the physical machine so that it is not converted over to the virtual environment

– Download and install the latest version of VMware Converter

–  Open VMware Converter and select “Convert machine”

  • Enter the following:
    • Select source type: Powered-on machine
    • Specify the powered-on machine: A remote machine
      • IP address or name: <PC Name>
      • User name: <Admin user on source PC>
      • Password: <Password>
      • OS Family: Windows
  • Click Next

– When prompted with the following, choose “Automatically uninstall the files when import succeeds” and click Yes

– In the Destination System screen, enter the following and click Next:

  • Select destination type: VMware Infrastructure virtual machine
  • Server: <VMware host or Vcenter management server>
  • User name: <VMware user with Admin rights>
  • Password: <Password>

– In the Destination Virtual Machine screen, enter the following and click Next:

  • Name: <PC Name>
  • In the “Inventory for:” field, select the destination

– In the Destination Location screen, select the host for the new VM, then choose the appropriate datastore and click Next

– In the Summary screen:

  • Click Edit in the “Data to copy” field
    • Choose the “Destination layout” tab and highlight C:
    • Click the “Size/Capacity” drop-down and choose “Type size in GB”
    • Enter the required size of the drive…make this as small as possible to preserve space, e.g. if there is only 26GB of used space on the physical machine, make the new virtual disk 30GB
  • Click Edit in the “Services” field
    • Check the boxes to stop any services that could slow the conversion process (i.e. antivirus)
  • Click Next

– Click finish and Converter will create the new VM…the process may take over an hour depending on your disk size.

– Once the VM is created, open Vsphere client and connect to your host.

– Switch to the Datastores and Datastore Clusters view and select the datastore that you created the VM on

  • Click “Browse this datastore” and locate the VM that you just created
  • In the VM’s directory, delete all files except for the .VMDK and .VMX files
  • Upload the Windows XP SP3 ISO and VMware SCSI Driver floppy image to the datastore

– Switch back to the Hosts and Clusters view in Vsphere and power on the VM

  • When prompted, choose the option “I moved it” and click OK

– The VM will boot, when you try to log on, it will prompt you for activation

  • Click Cancel and the VM will shutdown

– Edit the VM’s settings

  • Connect the XP ISO as the disk drive and the SCSI driver as the floppy drive (you may need to add a floppy drive)
  • Under the Options tab > Boot Options, check the box in the “Force BIOS Setup” field
  • Click OK and boot the VM

– When the VM boots to the BIOS, set the disk drive as the primary boot device, save changes and exit, you will then boot to the XP installer

– When prompted, press F6 to load third party SCSI drivers

– Hit S to Specify Additional Device

– Hit ENTER to select the VMware SCSI Controller, then hit ENTER again to continue with Windows Setup

– Hit ENTER to set up Windows

– When prompted, select R to repair the existing Windows XP installation.

– After going through the standard installation procedure and entering a valid XP license key, Windows will boot as normal and you will not be prompted to activate

– Network settings may have to be applied manually to bring the VM online, depending on your environment


Source :


Determine Windows Licence type

Simply open a Command Prompt and run:

slmgr -dli
License Type Description
Retail This when you buy a Full Packaged Product (FPP), commonly known as a “boxed copy”, of Windows from a retail merchant or purchases Windows online from the Microsoft Store. Product keys can be transferred to another PC.
OEM Product keys are issued by the original equipment manufacturer (OEM) and are not-for-resale and may not be transferred to another computer. They may, however, be transferred with the computer if the computer is transferred to new ownership. If the OEM PC came preinstalled with Windows 8 or Windows 10, then the product key will be embedded in the UEFI firmware chip.
Volume KMS Client and Volume MAK product keys, are volume license keys that are not-for-resale. They are issued by organizations for use on client computers associated in some way with the organization. Volume license keys may not be transferred with the computer if the computer changes ownership. This form of licensing typically applies for business, government and educational institutions, with prices for volume licensing varying depending on the type, quantity and applicable subscription-term. A volume license key (VLK) denotes the product key used when installing software licensed in bulk, which allows a single product key to be used for multiple installations. For example, the Windows Enterprise edition is activated with a volume license key.


Note : SLMGR is not available on Windows Server 2003, unless you installed the “key-management-service-kms-host-for-windows-server-2003”