Re: Old GPO still being applied

Tech-Archive recommends: Speed Up your PC by fixing your registry

The printer script is a simple vbs file.

"Meinolf Weber [MVP-DS]" wrote:

Hello pete0085,

So it is about removing the printers configured with the GPO? How did you
configure the printer's, script or printmanagement from 2003 R2?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


The old gpo still exists, but it's not located in that OU. The
workstation was moved from one branch to the other.

The gpo in question sets the default printers. I even deleted the old
printers in the list and today once the user signed on it added the
printer once again and set it to the old default.

The gpo is not linked in that OU, but it is the same workstation, with
a different computer name and placed in a different OU.

What else should I try to remove these old settings?

"Meinolf Weber [MVP-DS]" wrote:

Hello pete0085,

Did you delete/unlink an old GPO and now the settings still apply? If
only unlinked, link it again and revert the settings.

Unfortunal this can happen because some settings are a kind of
tattooing

and the policy setting has to be reverted before set to not
configured:

http://www.gpoguy.com/FAQs/FAQs/Whitepapers/tabid/63/articleType/Arti
cleView/articleId/5/Understanding-Policy-Tattooing.aspx

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
We swapped out workstations and changed the computer names. One of
the workstation, an old GPO is still being applied. I ran a
gpupdate /force on the server and workstation. A gpresult isn't
showing the policy being applied, but it must be somehow.

I logged on to the workstation last Friday as the administrator and
everything was normal. when the user logged on today, the old
policy was being applied for some reason that technically should not
exista and gpresult says it does not.

What else can I try? The next step was to remove the workstation
from the domain and re-add it.

The workstation is Windows XP and DC is server 2003.




.

Relevant Pages

  • Re: Group Police Question !
    ... A GPO linked so it will apply to a computer will apply the computer ... and one linked so it will apply to a user will apply the user settings. ... I have one Workstation for All internal ... > his Workstation will apply Group Police ...
    (microsoft.public.windows.server.general)
  • Re: Group Police Question !
    ... A GPO linked so it will apply to a computer will apply the computer ... and one linked so it will apply to a user will apply the user settings. ... I have one Workstation for All internal ... > his Workstation will apply Group Police ...
    (microsoft.public.windows.server.setup)
  • Re: Group Police Question !
    ... A GPO linked so it will apply to a computer will apply the computer ... and one linked so it will apply to a user will apply the user settings. ... I have one Workstation for All internal ... > his Workstation will apply Group Police ...
    (microsoft.public.windows.server.security)
  • Re: Old GPO still being applied
    ... So it is about removing the printers configured with the GPO? ... workstation was moved from one branch to the other. ... Did you delete/unlink an old GPO and now the settings still apply? ...
    (microsoft.public.windows.group_policy)
  • Re: AD Container
    ... I have a OU for all workstation that follow the same ... policies and I use and is untouch the computer container for computers on my ... As Meinolf mentioned, the ones that stick, need to be set to defaults or disabled in the GPO, then GPO must be refreshed on the machine. ... If you can elaborate on the GPO settings you have placed on the Workstation Organizational Unit, it may help us, or you can simply follow the link that Meinolf provided in his earlier post. ...
    (microsoft.public.windows.server.active_directory)