Unsolved
This post is more than 5 years old
1 Message
0
1168
May 26th, 2011 14:00
vWorkspace agent on windows 2003r2/2008r2
Will I be able to install the agent on a windows server (either 2003 r2 or 2008 r2) and access it just like I would a Windows 7 or Vista desktop? I do not want to install the terminal services/remote desktop services role. I did some searching on here but I could only find things relating to setting up a server as a terminal server.
Any help is appreciated, thanks.
No Events found!
DELL-David Y
228 Posts
0
May 31st, 2011 11:00
Hi Chris,
I presume when you say the vWorkspace agent that you mean the PNtools, which would typically be installed on a computer to allow the vWorkspace enhancements over a remote connection. The PNtools can be installed on both Windows 2003 R2 and 2008 R2. The full list of supported platofrms is shown in the vWorkspace System Requirements document, extract shown below:
PNTools can run on a guest with any of these operating systems:
• Microsoft Windows XP, Service Pack 2 (x86 and x64 editions)
• Microsoft Windows XP, Service Pack 3 (x86 and x64 editions)
• Microsoft Vista, Service Pack 1 (x86 and x64 editions)
• Microsoft Windows 7 (x86 and x64 editions)
• Microsoft Windows Server 2003, Service Pack 2 (x86 and x64 editions)
• Microsoft Windows Server 2003 R2, Service Pack 2 (x86 and x64 editions)
• Microsoft Windows Server 2008 (x86 and x64 editions)
• Microsoft Windows Server 2008 R2
Regards
David
hbui-sbcpro.de
25 Posts
0
June 1st, 2011 01:00
Hi Chris,
we do what David listed down in his answer in some customer environments. We use to install the PNtools to a Windows Server to schedule Tasks for this maschine or just to make the logon for remote administration 'more vWorkspace integrated'.
What we never tried so far is to use the agent/PNtools scenario on a TS or RDSH to connect more than one user at once to it for using it as a plain Microsoft TS/RDSH. I guess this isn't supported anyway and the interesting question to me would be why s.o. would want to do this?
The other scenario that we have in two environments, is that there are 3 WTS that are running w2k3 server. Two of them are the WTS the users use to connect to with round robin load balancing running plain Microsoft terminal services. On both of them is installed only the current Quest vWorkspace connector for Windows that starts automatically with SSO in desktop integrated mode within every session. The connector is used to make the users able to lunch a financial application on the 3rd terminal server that is running the terminal server role of Quest vWorkspace. We do this because the financial application wouldn't run properly among with the standard applications of this customer.
The only reason for us to not activate the terminal services role of Quest vWorkspace on all 3 WTS was that the environment was already up and running on the two main terminal servers. It was all about the pricing for the roll-out as well as for the licenses.
Holger