My environment currently has a Windows 2003 server running terminal services. That server has the visual studio 6 IDE installed. It also is responsible for running a very old ( and poorly built ) VB6 application. I'm currently testing methods for deploying a Windows server 2012 running the RDS role to our employees. One of the major hurdles has been making that legacy VB6 application available to the 2012 RDS server. Up to this point I've only found success in having an RDS client connected to the 2012 server then run a RDP session to the 2003 server to execute the legacy app. I'm trying to make the process of running that legacy app more seamless to the users. Is there a method where I could have a more seamless execution of that legacy app for the RDS clients of the 2012 server? I've been looking at Microsoft's App-V product but am still unsure if this will accomplish what I'm looking for.
Method of deploying a VB6 app to a Windows server 2012 RDS server
applicationvirtualizationwindows-server-2003windows-server-2012
Related Topic
- Supported .net frameworks on windows server 2012 r2
- When deploying a single server on new hardware, do you virtualize it or not
- Windows 2012 RDS – Fixing Temporary Profile Issues for Administrator
- Installing ADAM on Windows Server 2012
- Is Easy Print working on the Windows Server 2012 R2 RDS server
- Trouble with interactive service on Windows Server 2012
Best Answer
...
(Source: http://blogs.technet.com/b/uspartner_ts2team/archive/2010/04/20/what-s-the-difference-between-app-v-and-med-v.aspx)
Whether VB6 is supported or not on Server 2012 and Server 2012 R2 is a rabbit hole. Regardless of it is or not, I would personally not want it installed on my server because it is ancient. Therefore, I would prefer a Med-V solution as opposed to installing VB6 directly on my shiny new server.