This post is more than 5 years old
1 Rookie
•
90 Posts
0
5999
December 16th, 2010 13:00
RDP port : vWorkspace 7.2 upgrade
Hi all,
I;ve noticed that after updating the vWorkspace to 7.2 from 7.1 MR1 the RDP port is changed to 0
After changing this back I can then connect via the Quest client, web and app portal, but I've noticed other application are now not working... Imprivata OneSign, Flash! and others...
During the upgrade install I do get errors
Anyone else having issues and any advice?
Cheers!
No Events found!
caleb.grant-ohi
1 Rookie
•
90 Posts
1
December 16th, 2010 14:00
I found reinstalling the OneSign agent after the upgrade fixes the issue, after uninstalling it... a couple of reboots but it works...
Regarding RDP port issue... I think this was related to one of our build images as it's fine on 17 TS servers and not on 3, which were the first ones built before we noticed some problems and rebuilt the image
caleb.grant-ohi
1 Rookie
•
90 Posts
0
December 16th, 2010 13:00
These are Windows 2003 R2 Enterprise Terminal Servers...
caleb.grant-ohi
1 Rookie
•
90 Posts
0
December 16th, 2010 14:00
Disabled... I had issues using EOP so I disabled it all all my TS servers.
Michel Roth
173 Posts
0
December 16th, 2010 14:00
Hi Caleb,
What was your exact EOP Xtream configuration when before you started the upgrade ?
Michel Roth
173 Posts
0
December 16th, 2010 15:00
Hey Caleb,
Can you try and manually register the file?
yoda-ict
8 Posts
0
December 17th, 2010 07:00
Hello,
This is certainly a problem in the 7.2 release. After upgrading all 5 terminal servers (4x windows 2003 x32 and one windows 2008R2 server) all servers refused to be accessible by RDP. I had to edit the registry to reset the default listening port to 3389. On all servers it was set to 0. So something is not right in deinstalling older versions here.
About the vmCOM.dll error: on one system i receive the same error. I got this also when installing 7.1 MR1. Don't know if this file is needed as it's a vmware scripting library. Manually register the file does not work; regsvr32 does not display a popup with the status, just returns to the prompt.
Michel Roth
173 Posts
0
December 17th, 2010 12:00
Did you have EOP Xtream disabled before you started the upgrade?
yoda-ict
8 Posts
0
December 21st, 2010 06:00
Michel,
Yes, EOP XStream was disabled on all terminal servers before upgrade
caleb.grant-ohi
1 Rookie
•
90 Posts
0
December 21st, 2010 11:00
Yes, I also had EOP XStream disabled.
Michel Roth
173 Posts
0
December 30th, 2010 07:00
Just as an update, this is something we are investigating right now. Watch this thread.