Surrogate Computer for Virtualized Server. RRS feed

  • Question

  • We have a server that is stuffed into a closet because it has to have close proximity to multiple serial connections.

    The server gets choked up with dust a lot and it is close to death. We have a hyper-v server 2012r2 setup available.

    I haven't spent too much time on this, but we are thinking that it would be best to virtualize the server that does the processing and stores the data while having some kind of surrogate or thin client to act as the interface for the serial connections on behalf of that virtualized server.

    Is this the wrong way of going about this? Any ideas?

    Other information:
    - The serial connections are standard 9pin
    - There are 4 connections that need to be made (was thinking just 4 serial to usb dongles)
    - There is only 1 ethernet connection to the closet; we really would like to avoid making more runs.

    Mediocre Access 2010 | (Baby) Beginner C Sharp | OK at Active Directory (2012 R2) | Fragmented understanding of DNS/DHCP | Laughable experience with Group Policy | Expert question asker on MSDN Forums

    Wednesday, December 9, 2015 2:40 PM


  • Hyper-V doesn't have direct USB or serial port access, so if those are requirements, you're looking at the wrong product.
    • Marked as answer by UpTide Friday, June 16, 2017 6:23 PM
    Friday, December 11, 2015 4:17 AM