Are they Windows Embedded devices? Or CE or TOS? Or something else? Sent from my (new!) BlackBerry, which may make me an antiques dealer, but it's reliable as hell for email delivery :-)
-----Original Message----- From: Jesse Rink <[email protected]> Sender: [email protected]: Sun, 19 Jan 2014 17:10:40 To: [email protected]<[email protected]> Reply-to: [email protected] Subject: [NTSysADM] Thin Clients pointing to wrong server Just looking for some thoughts on this one. Had a situation the other day where I was called to go onsite because, starting a few days ago, only 2 users could logon to the (30) HP T510 thin client devices instead of the 30 users that normally could (it's a computer lab). After a couple minutes of investigation, I verified that the users were not logging into the terminal server itself, but actually logging into the domain controller (which didn't have the terminal services role installed, so they were obviously limited to two active RDP sessions/logins). Now, on the thin clients themselves, there's a configuration setting telling it the IP address that it's supposed to connect to. Oddly enough, all 30 thin clients had their configuration set to point to the IP address of the domain controller (x.x.x.2) instead of the terminal server (x.x.x.3). The lab instructor says he didn't change all 30 thin clients, and we doubt the students would have done it, so does anyone have an idea how all 30 thin clients might have ended up pointing to the domain controller (x.x.x.2) instead of the terminal server (x.x.x.3)?? Changing all the thin client devices to point BACK to the terminal server itself (x.x.x.3)allowed all 30 users to login again, but I wish I knew how the address on the T510 thin client had gotten changed. Any thoughts on this one? Thanks J
