Windows 7 Enterprise domain login error

Question

So I have this school computer. And I got help from a friend who managed to make the program sethc.exe to become an command promt that you could make pop-up by using sticky keys and from there I created a local admin account off the school domain network. My school computer is hooked up to a domain network and when I would login to my school account(non-admin) I would write ad.stockholm.se\ab63124 Im from Sweden. Hence the "stockholm" and ".se". ab63124 is my user name. After that I type in my password which I know is correct. But the problem is that It doesn't work. For example. Before the summer when I was on the login screen. It said what domain I was login on. (ad.stockholm.se) But now, it behaves like a private computer. It's like I can't connect to the school domain server. And the login fields won't allow me to use a domain account. As I write this Im on the local admin account. The folder for my school account still exist C:\Users\ab63124. But I can't accses it.

I need help with this, because I gonna hand this in to my school in approximetly 1,5 years. And if it isn't solved by then. Well I don't know.

Edit:

So this is how we managed to create an admin account:

First I called the student support and managed to get the BitLocker key for the harddrive. After reciving it. We unscrewed the laptop and took out the harddrive. Then I plugged it into my other computer and unlocked the harddrive with the BitLocker-key. Now we navigated to system32 folder and searched for sethc.exe. When we found it we removed sethc.exe from the folder and replaced it with another program called sethc.exe but it was actully cmd.exe. So when I then put the harddrive back in place and started the school computer and came to the log-in screen. I pressed SHIFT 5 times, and instead of "Sticky Keys" popping up. Now a command prompt popped up. Now we could create a local admin account on the computer. And that's how it went down.

Update: I now know what I did. I went into System Properites and in the "Computer Name" tab I clicked on "Change" and unchecked Domain. So it went off the network. However, now I tried to change it to my school domain network, but that didn't work I get errorcode: 0x0000232B RCODE_NAME_ERROR it doesn't find the DNS name of the domain. Does that mean I have to change it while Im at school ?

Answer 1

Unless your account has privileges to add computers to the domain, you cannot add it back. You could theoretically, and I mean theoretically, use some other computers to run a windows server, make THAT domain for your school again and connect the laptop to IT. It's not actually going to ACTUALLY FIX the problem at all, but they will likely think that the domain trust is broken and won't dig too deep into why.

So, what it would look like to them is:

• computer is in their domain, but it's not taking their logins.
  • It might even give a trust relationship is broken error since it's trying to talk to your fake domain and the only one it can talk to doesn't have the right info.
• they log in as an local administrator account,
• remove the machine from your fake domain and put it in a workgroup
• Put the computer back into the real domain
• computer works like normal. Well, maybe not sticky keys.... but you could probably get this from an unscrewed-with machine and just place it.

---

And here is the more fun way and what I would probably do. First, get anything you'll need off it. We're going to destroy this windows install.

If you aren't willing to make your own fake domain in a closed environment, or it's just way too complicated, then just tear the thing to the ground. Fabulously destroy the windows install. Delete random DLLs from system32. rename things. move stuff. your goal is to get yourself a fantastic bluescreen. Preferably many so that if they fix one there's another waiting behind it. You might want to try a boot disc or live CD so you can get to some files that it won't let you normally mess with.

Once you have it totally screwed up, take it to the helpdesk or whoever and tell them you're not sure what happened. It kind of kept getting slower and slower and then, mention popups and things like browser toolbars. These are the kind of things that inject themselves into stuff and cause problems, but are rarely a real risk. They might struggle with it for a little while, but they're probably just going to restore you from some kind of backup or just re-image the machine.

Just avoid mentioning anything that could be construed as something you ought not to have done. Things like accidentally installing browser toolbars and clicking things you shouldn't have happens all the time, but saying you dropped it and then all this happened would be bad and would likely get you made responsible for it. Software they can easily fix. If they think it's just that it's not really a big deal, if they think it's to do with a physical problem you're more likely to get charged for something.

---

Update: You know? You might could just file a ticket saying something along the lines of: I can't log in to my computer! It says the trust relationship failed! and they might just remote in and re-connect it. It happens more often than it should even without people screwing with the OS.