Hmm, really doubt that. They don't have people knowledgeable enough onsite to make that happen. (no IT staffers, only a lab/computer teacher)
________________________________________ From: [email protected] [[email protected]] on behalf of Susan Bradley [[email protected]] Sent: Monday, January 20, 2014 11:10 AM To: [email protected] Subject: Re: [NTSysADM] Thin Clients pointing to wrong server Any chance the ip of the DC and the TS box got flipped? On 1/20/2014 8:56 AM, Jesse Rink wrote: > > LOL, yes. but it's not me that set it up. It's a new customer I > picked up and was amazed to learn that even the students can logon to > the DC via RDP. No idea why the previous support people set it up > that way...That's on a list of things to look at along with other > things I found during my first visit. > > ------------------------------------------------------------------------ > *From:* [email protected] > [[email protected]] on behalf of Charles Sullivan > [[email protected]] > *Sent:* Sunday, January 19, 2014 1:01 PM > *To:* [email protected] > *Subject:* RE: [NTSysADM] Thin Clients pointing to wrong server > > This may be beside the point, but are you saying that regular users > were able to log on using RDP to your DC? > > Charlie Sullivan > > Sr. Windows Systems Administrator > > *From:*[email protected] > [mailto:[email protected]] *On Behalf Of *Jesse Rink > *Sent:* Sunday, January 19, 2014 12:11 PM > *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 > -- Got your CryptoLocker prevention in place? http://www.thirdtier.net/2013/10/cryptolocker-prevention-kit-updates/ Only three more patching days of XP.... are you ready?
