![]() Has multiple (5) sessions in pool cn=terminal The view manager log displays that there are multiple sessions for a user I plan on placing a support call here soon. I looked all over for a setting that would stop this from happening, but could not find one. I wanted to get the thing working and I knew what would make it work. This literally happened on monday and I have not had a chance to contact support about the issue. so now I have 100 new users in my AD just for View client connects. The only solution I found was using an individual user/password to connect the view client as. The View clients then all exit and relogon. When one computer attempts to logon it disconnects the other sessions. View apparently only lets a user maintain 1 view session at a time. I then rolled out and found a whole bunch of problems. This worked fine in testing and I didn't notice any problems. I have my reasons for doing it this way that I won't get into. The idea was the users then logged in as their user name when the walked up to the computer and selected the pool and press connect. Well the view clients were all set to use the same user name using the command line options. View is set to a session timeout of 1440 minutes since the systems are rebooted automatically every 24 hours 2 hours before the clinic opens. I had them autologon with a single users and use the shell replacement script that relaunches the view client after exit. My primary pool that these systems use is a terminal server. ![]() I too have 100 or so thin clients running XPe w/sp3. I recently came across a somewhat similar problem. The thing I do not understand is nobody else seems to have this issue, I cannot be the only person that uses VMWare or remote desktop connection in this way, by that I mean leaving the view client or RDC logged in so it presents a logon box of the VM for the students to login to, also it seems to do this from the default configuration of a fresh install of XP. I believe it to be an RDP issue, it would have just been helpful if the VMWare support person could have offered more support in this area instead of basically saying it's not an issue with VMWare. I have hooked the NIC's up together using a crossover cable to eliminate everything else and I still get this issue. I have installed 2 fresh PC's with official Microsoft XP Pro SP2 and SP3 software downloaded from their site. Once I have established a connection and just leave it at the windows logon prompt it disconnects at around 3 minutes, sometimes 2m 50s or 3m 10s but always around the 3 minutes. The VMWare support person basically asked me to use XP (Pro SP2) remote desktop connection and remote control another XP (Pro SP2) machine outside of VMWare altogether. ![]() I have tried this and it still disconnects at the vm login screen after 3 minutes. Thanking you in advance for any input you can give. If I cannot solve this I will have to look at other solutions. I would have thought as there technology relied upon RDP to function that they would support it, officially or unofficially. I raised a support incident with VMWare who diagnosed the problem as a RDP issue and not the view client, which in one way was good for troubleshooting, but also not very good as they did not seem interested in helping to solve the problem any further, which means I cannot roll out the 600 thin clients I wanted to do. I have changed the settings for 'idle' within the VMWare GPO's as well as the standard GPO for XP under terminal services - sessions. I am hoping that somebody else has experienced this and has a solution. I do not think this is a view client problem, but an RDP issue. But as soon as they logoff, the client automatically relaunches and then the 3 minute 'idle' timer seems to start. Once the person then sits down and logs in to the VM then there is no issue and the session will stay open all day, which is fine. Also because of this sometime the thin client needs to be actually turned off as some freeze up after 3 hours of constantly doing it. The problem is, if the view client is just sitting there and nobody is logging on or there is nobody in the room but the thin client is turned on, the view client automatically disconnects after 3 minutes and as I am running a script it will load back up again within 6 seconds, but all the thin clients doing this every 3 minutes is not ideal. I have done this and if the person logs off the VM or just closes the client down it automatically loads up again. The idea is to have the view client load up automatically when the thin client (XPe) boots up. The setup I want is to have a room of thin clients for students to logon to. I have a problem with the view client and RDP.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |