a strange issue has come up to my vista users,
i have published a windows terminal server on my portal, and allowed WSAM to only the exchange servers.
1.user logs in to the IVE, the WSAM connects automaticly.
2.when a user clicks on the terminal server link the message "connecting" appears until a timeout
3.if the user right clicks the WSAM icon and exit and tries to open the terminal server link it succeeds
this issue is happening only to my vista users
my IVE OS is 6.4.R1
anyone have this issue?
I have exactly the same problem until point 3. That I need to test, but it can be a temporary workaround.
Our IVE is 6.4 R2.
Any help is welcome.
Thanks in advance,
what is your workaround for this issue?
i understand that there somthing in the UAC sevices of vista that can solve this, not sure though...
I have no workaround for this.
Since I update from 6.2R1 to 6.4R2, I have several problems with vista 32bit which I can't fix.
- It needs 20 to 30 seconds for SAM to connect! (normally it happens simultanious)
- Once connected with SAM, I cannot start any terminal service session. It starts but freezes trying to connect.
When I check our network firewall or with a policy trace, no traffic comes in.
I also tried with disabling the Vista firewall, but also no solution...
This is a very frustrating problem,
So any workaround, hint, solution is welcome.
Thanks in advance,
After some testing I found the problem (Hope this is the same problem for you Player).
We have Realms with several Roles.
This could be Citrix (WSAM), Terminal Services, Etc.
When a user has access to a Citrix Role and a Terminal Service Role, the Terminal Service freezes when trying to connect.
When I remove the Citrix Role, the Terminal Service session works fine.
I am not sure it is related to WSAM or Citrix...
In release 6.2R1 this worked together, but it seems that in release 6.5R2 this is not the case.
In the release note I found the following:
WSAM is not supported on multiple Terminal Service/Citrix sessions running on the same Windows server (419891)
I hope this helps.
the terminal services in those role are not including citrix although we have a role with citrix configured.
the problem is with when the WSAM is active, that's issue i think. i'm running 6.4r1 i'm thinking about upgrading to 6.4r2
perhaps that will solve this WSAM issue...
what do you think?
As i'm trying to simplify things for my users,
i have created a securemeeting based on their username also, and they liked it very much,
so now they want they same thing to access their own pc,