domain to workgroup mistake..need some info

K

kseine

New Member
here is the situation:

I made a rookie mistake and accident changed my work comp from a domain computer to a workgroup comp. I wa snot able to log in locally since i did not have a username or password. I used boot disk tool to reset the local admin password.

Here is my question: Since i am not the admin of the domain (work it dept is), what will they need to do in order to fix my issue. How is the computer fixed? Do they need physical access to the comp or could they remote in based on the ip address the dhcp server assigns when i log in to the local via admin account? Is my account profile still sitting some where and can be retireved when the domain is switch back?

Please educate me as i am not the best with network administration (obviously)
 
if the admin account is open (you remove the password right ?)
then the IT dept can put you back on the domain in one time, its no big deal.
you domain account is fine and its waiting for you to sign on.
 
lol why are you booting off of third party utilities to hack your company computer, see what happens when you don't know what you are doing, you cause more damage than good.
 
wow, using third party software on your own accord withour your IT dept knowing about is a big no no. if you get caught, youll be dealt with i can tell you that. winternals is a big one, some "users" like to use now. Its not a prob in my dept becuase if i catch someone doing that, there out of the system for good. let your IT dept take care of that, but normally, as ong as it can still grab an IP from the DHCP server, and you know the local admin password, they can fix it remotely, but if you changed the admin password, they are going to need it
 
It's not even a big issue. I work in the IT dept. in my office, I'm actually here right now. When we set up a new computer we have to put it on the Domain, it's the same thing. Nothing's affected, all your files will still be there. A year ago we were having problems and the quick fix solution till we figured out what was really wrong (turns out corrupt active directory, among other things), was to take them off the domain, then put them back in. Users couldn't log in unless we removed them from the domain then re-added them. Not a big deal, no damage, but certainly using 3rd party software would be enough to piss me off, let alone the network admin here. He'd go off on you if you worked here.
 
its just a pain really, when users try to fix their own computer and really do more damge thn good. then we have to go in a fix it. the one thing i like about server 03 is the ability to basically cache the entire profile, so if something like this does happen, the user can still log in, minus whatever applications need network resources, but all the old email, documents, etc, will still be available, on every computer that you have logged into, but only have the info up until the last time you logged into that ocmputer. then it will update itself when you finally do log back into the network, or sometimes, change whatever file you modified during the non network period to the most current file the network servers have. theres pros and cons with evertyhing
 
Platinum said:
It's not even a big issue. I work in the IT dept. in my office, I'm actually here right now. When we set up a new computer we have to put it on the Domain, it's the same thing. Nothing's affected, all your files will still be there. A year ago we were having problems and the quick fix solution till we figured out what was really wrong (turns out corrupt active directory, among other things), was to take them off the domain, then put them back in. Users couldn't log in unless we removed them from the domain then re-added them. Not a big deal, no damage, but certainly using 3rd party software would be enough to piss me off, let alone the network admin here. He'd go off on you if you worked here.
Click to expand...


here in lies the problem, there is still a local user account, and when someone modifies the local admin account they get root privileges to the system, locally. Obviously the domain and the AD are not effected because no one is exploiting anything on the network, they are exploiting the local machine.

Which causes more damage than good because people do not know what they are doing in these types of situations. It annoys me more than it actually makes me angry because it just causes more work. Then again when i see this happen at work I just reimage the whole computer.
 
Platinum said:
Why would you reimage the whole computer? That seems a bit excessive, speaking of causing more work.
Click to expand...

easily, if the local machine had been exploited, local users been added or modified who knows what else they have done to the machine locally. Install malicious software, or botch the registry or what not. Reimaging over the network takes a few moments of my time and everything else is automated via shell scripts, so really it creates less work.
 
thats one of the best things to do, reimage. they could've added their own software, keyloggers, added spyware virus's and not know it. who knows..
 
tlarkin said:
easily, if the local machine had been exploited, local users been added or modified who knows what else they have done to the machine locally. Install malicious software, or botch the registry or what not. Reimaging over the network takes a few moments of my time and everything else is automated via shell scripts, so really it creates less work.
Click to expand...

Very true. I hate when people know just enough to screw things up, but not enough to fix it. That's why people should just not try to fix things, and let the professionals do it.
 
basicly mate you should not of done what you did but just go see your IT team tell them you dont get the option to log on to the domian and just gives the local pc name when you first turn on.

They will logon as local admin then put the machine on the network all that is needed is a connection ie CAT5 or WLAN then a username which will be administrator at a guess and a password which you wont guess im sure and then it will take a while and will pick your pcs account up in active directory and re assign your pc to it so all your account etc will be there then a restart is needed to put it on the network then once restarted you will have the option to logon to the domain and away you are again back as normal

Has that made it more clearer for you then the other posts

Guys how to do you re-image a pc over the network i would like to know your methods as i do it but physically. Would like to know your methods ie how to action it any software you use etc and if the pc has to be on the network still and how much you image ie just the OS and Basic software or each PC in turn.

Thanks Danny
 
DanDaMan said:
Guys how to do you re-image a pc over the network i would like to know your methods as i do it but physically. Would like to know your methods ie how to action it any software you use etc and if the pc has to be on the network still and how much you image ie just the OS and Basic software or each PC in turn.

Thanks Danny
Click to expand...

not to high hack the thread but, we use zen imaging solution from novell. Netboot the clients, and automate the imaging process through shell scripts. My advice is buy ghost if you can afford it, it is really the best thing out there. If not acronis is an okay second solution.

If you want open source and can handle dealing with Linux, DRBL is very good as well.
 
This is kinda funny. The same thing happened to me (except I was the IT guy that came to fix it).

Poor girl attempted to fix her PC and instead kicked herself off the domain and couldn't get back on! It's an easy fix so don't sweat it. Just (if you havn't yet) let your IT dept know and they can get you up and going in no time.
 
DanDaMan... hahaha... you tried to make it more clearer but instead you even confused me! and I work int he IT dept of my office! I see a total of 3 periods in your entire thread... you just keep goin on and on =D

Anyway, we use Norton Ghost to image computers here in the office. Often we use it when we have a new computer, we just upload the image to the new PC (assuming it's the same brand/model) and it saves us about an hour per computer. That way we dont need to install all the software and edit all the settings for each, it's all right there on 1 file that we need to upload.
 
You must log in or register to reply here.
Back
Top