| Author |
Group Policy Issue
|
|
| kelvin1211 2003-10-01, 11:29 pm |
| Dear fellow admins,
Wondering whether anybody had faced this before? I have set a Default Domain Policy for authenticated users within the domain but it does not apply to a Windows 2000 workstation in particular. Using that login on other machines has resolved that issue but it fails to apply to that particular workstation. All the necessary rights have been given.
Pls advice if you happen to have any leads on this.
Cheers
Kelvin | |
| isles1 2003-10-02, 9:21 am |
| Are all the other machines Win 2000? Is that one workstation is a different OU?
Are there any other GPOs that may be overriding the settings?
Have you checked the event logs on the machine? | |
| kelvin1211 2003-10-02, 9:05 pm |
| Hi there,
No, that machine is just a standard domain W2K Pro Workstation.
I ran the utility GPResults and found that the "scripts" portion of the domain policy was not applied to it. Other portions applied successfully. Could it potentially be a case of registry corruption such that it cannot apply certain parts of the group policy?
Your views pls.  | |
| Tech Ranger 2003-10-03, 2:56 am |
| Do you have any loopback processing going on? | |
| kelvin1211 2003-10-05, 9:26 pm |
| Hi Tech Ranger,
Nope, no loopback policy applied. No Local policies applied at all too. | |
| Tech Ranger 2003-10-05, 9:39 pm |
| Have you determined what policies are being processed? | |
| kelvin1211 2003-10-06, 2:12 am |
| Yup, all, settings like EFS Recovery,Security, Registry and the works have all been successfully applied, except for Scripts, which there is no error.
Took the set off the network and created another computer with the same comp name for said user. Works without a hitch so is not a case of computer account policies
So looks like it is something to do with that physical PC itself, sadly, don't even know what happened here. | |
| Tarzanboy 2003-10-08, 12:35 am |
| Computer names don't matter, as the SID is different for the new system and the old. It sounds like a permissions issue, possibly caused by a misconfiguration, possibly by corruption.
Double check your ACLs.
Cheers,
TB | |
| kelvin1211 2003-10-21, 2:48 am |
| Hi Tarzanboy,
Ok, the problem can be attributed to this entry in the application log of the machine:
I have a couple of machines facing the same problem and they all have this entry:
Windows cannot determine the user or computer name. Return value (14).
All solutions point to disjoin and rejoin the pc to the domain. I have done so but with no success.
At least I know where the problem lies now, resolving it is another issue.
Cheers
Kelvin |
|
|
|