none
Virtual PC, Cloud, RDC, local? The most efficient solution.... RRS feed

  • Question

  • At the office we have a computer with Windows XP that runs outdated but still useful licensed calculations software. This computer is joined to a domain and it is used alternatively by 20 users or less in any given day, some days it isn't used at all. They go to the workstation, log in, make the necessary calculations, print to PDF, log off, and leave the workstation.

    We gave users RDC access, but they often forgot to log off and thus locked the computer from being accessed remotely by other users, whether locally or remotely.

    Due to space requirements, we need to convert the computer to a virtual computer. The calculations software can be installed in 3 computers according to its license terms. We created a Virtual PC  with Windows XP and installed the calculations software on it.  We copied the Virtual PC twice and changed their computer names so that they would not conflict in the domain.

    So we have 3 Virtual PCs running Windows XP. We have tested them and they run as expected.

    What is the most efficient solution to give users access to these Virtual PCs?

    Should we have the Virtual PCs VHD hosted on a shared drive and install Virtual PC on the users' computers that require access to it?

    Should we have the Virtual PCs running on a Server and have users RDC to them? (We prefer not, due to the users being locked out of it)

    Your help and any suggestions would be appreciated.

    Thank you.


    Monday, August 25, 2014 2:47 PM

All replies

  • I will have to backup a couple of steps here,

    1. I would use Hyper-V as the hypervisor and not Virtual PC for obvious reasons
    2. The solution to users not logging off on a Windows XP VM is to configure the RDP service. In other words, you need 1 Windows XP VM not 3.

    If this was a Server 2003 VM for example, you'd open/run the TSCC.MSC and go to TDP-tcp connection properties:

    In the Sessions tab, change the config like:

    This will end an idle or disconnected session after 1 minute, which should solve your issue.

    All we just done in the Terminal Services Configuration snap-in (TSC.MSC) described above is change the following 8 registry keys from:

    HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\fInheritResetBroken: 0x00000001
    HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\fInheritMaxSessionTime: 0x00000001
    HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\fInheritMaxDisconnectionTime: 0x00000001
    HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\fInheritMaxIdleTime: 0x00000001
    HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\fResetBroken: 0x00000000
    HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\MaxDisconnectionTime: 0x00000000
    HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\MaxIdleTime: 0x00000000
    HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\UserOverride\Control Panel\Desktop\Wallpaper: ""

    to:

    HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\fInheritResetBroken: 0x00000000
    HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\fInheritMaxSessionTime: 0x00000000
    HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\fInheritMaxDisconnectionTime: 0x00000000
    HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\fInheritMaxIdleTime: 0x00000000
    HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\fResetBroken: 0x00000001
    HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\MaxDisconnectionTime: 0x0000EA60
    HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\MaxIdleTime: 0x0000EA60
    HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\UserOverride\Control Panel\Desktop\Wallpaper: "(None)"

    Since Windows XP does not have TSC.MSC, you can manually make the same 8 registry changes to produce the same result.


    Sam Boutros, Senior Consultant, Software Logic, KOP, PA http://superwidgets.wordpress.com (Please take a moment to Vote as Helpful and/or Mark as Answer, where applicable)


    • Edited by Sam Boutros Monday, August 25, 2014 3:52 PM
    Monday, August 25, 2014 3:51 PM