locked
not able to access windows server 2003 standard console in vsphere web client 6.5 RRS feed

  • Question

  • Hi,

    I did a V2V conversion from source environment to destination environment.Once the machine copied when i powered it on and opened the console it displays in blurred screen with many colours. Please see the error image below

    OS: Microsoft windows server 2003 standart 32-bit

    Thursday, September 6, 2018 11:57 AM

All replies

  • Q? have you adjusted Video Card settings under vSphere Client "edit settings..." 

    W.Maxx MCITP MCSE MCSA MCP 2k8 2k3 2k nt4 AD, Exchange, DNS, IBM iSeries RIM blackberry

    • Proposed as answer by MaxxSound Monday, March 25, 2019 9:39 PM
    Thursday, September 6, 2018 12:36 PM
  • P2V and V2V methods can be risky especially with older operating systems. You'll probably have better luck clean installing in the destination environment.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Thursday, September 6, 2018 1:39 PM
  • Hi,

    No we didn't do any modification in video card settings. Once the V2V conversion completed we powered on the machine and we could see the above screen in the console

    Friday, September 7, 2018 7:36 AM
  • Hi,

    I agree with your point but customer has expecting us to keep the server with all the datas as per in source environment. So we can't go with clean installing process

    Friday, September 7, 2018 7:37 AM
  • Hi,

    I want to confirm with you if it is Hyper-V host VM, or 3rd party virtualization host VM? 

    > vsphere web client 6.5
    This product you had mentioned is a 3rd party product which is manufactured by a company that is independent of Microsoft. I am afraid that I am unable to provide you more suggestion about it.

    If possible, try to establish the remote connection to the VM using Windows system built-in remote desktop connection – MSTSC and check the result. 

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, September 7, 2018 8:08 AM
  • Hi,

    It is 3rd party virtualization host VM....we couldn't login to the server itself and moreover we are getting error like at least one service or driver failed during system startup

    Friday, September 7, 2018 9:13 AM
  • Does the console work still? I had a server do this on VMware, the console would respond, the graphical display did make it hard to use but it could used :)

    The guest I had it on was an existing 2003 server so it had the VMware tools, so I restarted it and it cleared. I think somehow you are going to have to log into that server despite the display and install the VMware tools and reboot it.

    Saturday, September 8, 2018 3:34 PM
  • Hi,

    >we couldn't login to the server itself and moreover we are getting error like at least one service or driver failed during system startup
    If so, it seems that system itself has been crashed. As you had mentioned that problem happens after copying system, please confirm with the VM software supporter about the detail steps of VM copying. 

    Besides, you can try to repair the system:
    1. Using SFC command.
    2. Using external reparation sources, such as installation medium.
    3. System restore from available backup.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, September 12, 2018 9:41 AM
  • Hi,

    How things are going there on this issue?

    Please let me know if you would like further assistance.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, September 14, 2018 1:39 AM
  • hi,

    No still we are getting the same error. We followed the below steps

    1)uninstall the vmware tools and again installed it

    2)updated the vmware hardware version and reinstall the vmtools but again same issue facing

    Monday, September 17, 2018 7:05 AM
  • hi,

    Thanks for the reply. but we tried this method also by uninstalling vmtools and installed it again..but bad luck again we are facing the same issue

    Monday, September 17, 2018 10:54 AM
  • 1. shut down the vm

    2. go to tab configure

    3. go to settings -> vm hardware

    3. go to video card settings

    4. set the value of memory for the graphics card to automatic or if needed set manually a value 35+ megabyte (you could also use the integrated video card memory calculator)

    5. safe the settings and restart the vm


    • Edited by G_W Tuesday, February 18, 2020 8:54 AM
    Tuesday, February 18, 2020 7:36 AM