Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
Just been handed a laptop that orignally was attached a domain. The local security policy has been ammended by the domain group policy which we need to get rid of s it's now going to be used as stand-alone.
I've joined the laptop to a fictitious Workgroup but the local security policy settings are still greyed out as if Domain GP is still active. Rebooted twice but the same symptoms occur. This method of getting rid of domain GP has worked in the past but not this time.
I'm beginning to think this is a windows corruption. Anyone else come across this behaviour and found a solution. Any advice?
Cheers
If you have spent more than 8 hrs trying to sort that Laptop, it must be a very expensive one? or you are working for a very low wage!
Re-Image it into a bin liner and tell them get a new one.
Just think of Microsoft Windows in the same was as a dirty little un-house-trained dog that keeps having a poo around the house. At one point its not worth cleaning the carpet and furniture so you just throw them out and start again.
Easiest and quickest would be just re-image it. You could spend ages trying to work out what's wrong and if it is corrupt (as you suspect) it's going to need to be re-imaged anyway.
Just think of Microsoft Windows in the same was as a dirty little un-house-trained dog that keeps having a poo around the house. At one point its not worth cleaning the carpet and furniture so you just throw them out and start again.
Glad to se someone else has the slash 'n' burn mentality! 90% of the jobs I do involve reimage or a new profile.
And very valuable we Sys Engs/Admins/Tech Support people are to. Can't undertand why coder crunchers always look down their noses at us. If we didn't keep the infrastructure running, they'd have nothing to run their code on.
I guess some people think they are more vlauable than others in the IT game
Easiest and quickest would be just re-image it. You could spend ages trying to work out what's wrong and if it is corrupt (as you suspect) it's going to need to be re-imaged anyway.
Glad to se someone else has the slash 'n' burn mentality! 90% of the jobs I do involve reimage or a new profile.
Easiest and quickest would be just re-image it. You could spend ages trying to work out what's wrong and if it is corrupt (as you suspect) it's going to need to be re-imaged anyway.
This is what I thought, although actually we don't do images, we run RIS and in time old fashion, the RIS server is playing silly buggers at the moment. but thanks anyway.
Easiest and quickest would be just re-image it. You could spend ages trying to work out what's wrong and if it is corrupt (as you suspect) it's going to need to be re-imaged anyway.
Just been handed a laptop that orignally was attached a domain. The local security policy has been ammended by the domain group policy which we need to get rid of s it's now going to be used as stand-alone.
I've joined the laptop to a fictitious Workgroup but the local security policy settings are still greyed out as if Domain GP is still active. Rebooted twice but the same symptoms occur. This method of getting rid of domain GP has worked in the past but not this time.
I'm beginning to think this is a windows corruption. Anyone else come across this behaviour and found a solution. Any advice?
Leave a comment: