Very Wierd GP Occurance

**Ardesco** · 8 June 2007, 09:30

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.

**Kyajae** · 8 June 2007, 09:39

Originally posted by Ardesco

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.

**gingerjedi** · 8 June 2007, 10:09

Originally posted by Ardesco

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.

**Kyajae** · 8 June 2007, 10:19

Originally posted by gingerjedi

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

**Ardesco** · 8 June 2007, 10:25

Originally posted by gingerjedi

Glad to se someone else has the slash 'n' burn mentality! 90% of the jobs I do involve reimage or a new profile.

I've spent a fair bit of time setting up test labs and slash and burn is the only sensible way to go

You never know what has been on a test machine so just assume it's a virus ridden unsecure POS that needs to be built from scratch

**Paddy** · 9 June 2007, 12:24

Originally posted by Ardesco

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.

**wizard1974uk** · 9 June 2007, 16:59

Originally posted by Paddy

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.

I like that analogy

**Diver** · 18 June 2007, 16:02

Originally posted by Kyajae

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.

Ps if it's the latter, wan a job?

"Under Water Nobody can hear you scream"

**chicane** · 18 June 2007, 20:11

Originally posted by Kyajae

I guess some people think they are more vlauable than others in the IT game

This is not the first time you've mentioned this; do you have a complex?

Very Wierd GP Occurance