Use the above unetbootin utility to burn the iso to the usb flash. If you use my build on a usb drive like a cruzer fit or verbatim store n' stay you can leave the ts image in the machine without risk of it getting knocked out of the usb port. Just so I'm clear the logon issue you had was with the server farm and not thinstation or any of the RDP clients you tested? I will be back in the office next week and proceed to put this new build on the thin client. So, after three weeks of headaches, the problem was solved while testing your build. The error log simply says the user logged off. When the user logs off the GUI client, a "error log" is generated and displayed on the screen forcing the user to select ok or cancel. Futhermore, my original thin station build works also. I am confused with the reason this happens and intrigued but thrilled that it works. For whatever reason when the user hits the first server, everything works, when the user hit the second server it fails until the thin station computer name was added to the AD logon restrictions. Although the users had the authority to logon to both servers in the farm they did not have permission to log onto the newly created thin station device. I limit which computers a user can logon to via AD. When I log on as a user nothing happened. Yesterday I logged on as an admin and was redirected to the second server. Success!!! After quite a bit of troubleshooting with TS Station.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |