Setting Some PC's outside the Logon Warnign Banner

You have to clear the following 2 registry settings on the local machine:
HKLM\Software\Microsoft\Windows NT\Currentversion\Winlogon
- LegalNoticeCaption
- LegalNoticeText

You can do this by policy, but I think its easier to do it manually

On one of those machines go into the registry and look for:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon


LegalNoticeCaption
LegalNoticeText
Delete those two and see if you are then good to go.
Why do you want to login automatically?
Thanks
Mike

I'll certainly try the above, but concerned that GP will set it back.  Hey, we can always try!  

Auto login to run monitoring software.  Why not a service?  Ask the developer!

If you have block inheritance on I don't think it should....but haven't tested this exact scenario so I'm not 100% sure.
Thanks
 
Mike

The "easy" way to do it the following

- Put all these computers in the same OU
- On this OU block Group Policy Inheritance
- Go to each computer delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon\LegalNoticeCaption & LegalNoticeText or better setup a startup script to delete them for you

Done.

Create the following reg and batch files and assign the batch file as startup script to delete our keys automaticlaly

----------------start reg file ------------------
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon]
"LegalNoticeCaption"=-
"LegalNoticeText"=-
 
----------------end reg file ------------------
 
----------------start bat file ------------------
regedit /s \\servername\regfile.reg
 
----------------end bat file ------------------

Select allOpen in new window

Okay, I've blocked inherritence, deleted the registry keys and it works.  Until I gpupdate then it's all back.

how can it be back if blocked inheritance ?

did you restart you computer 2 times for it to know it has changed OUs?
at what level do you have the policy that enables the warning applied ?
is this policy set to "ENFORCE" ??
on one of these clients issue a gpresult is the policy still showing ? is it showing in the new OU ?

i'm going to try and test this out this weekend, now I'm intrigued.  Can't test at work.

mike my best guess is that the computers haven't picked up their new OU yet

yeah it is odd why its coming back, just want to see for myself.  That is not what I was expecting at all.  

I have rechecked the inherritence, the Def GPO is not enforced.  I ran a group policy results query to make sure it wasn't coming from somewhere else.  The results wizard actually sees no setting for the message.  

Many hours later, I have retried the reg hack.  Same things, works great 'til the GP refreshes.

PC is in proper OU clear as day.

I'm wondering if the default get special treatment.

Thanks

You have not answered the following questions

1) did you restart you computer 2 times for it to know it has changed OUs?
2) at what level do you have the policy that enables the warning applied ?
    I understood from the previous post that you did it on the default domain policy am i right ?
3) on one of these clients issue a gpresult is the policy still showing ? is it showing in the new OU ?

I have restarted it 3X, deleting the reg keys each time.  Always works til gp updates

warning is part of default domain, applied at domain root

gpresult shows no default GPO and shows proper OU membership

well if GPResult shows no default GPO means the warning is coming from somewhere else.

why don't you try to install gpmc.msi and run a GP modeling on one of these computers and check what, in theory, its settings should be

Akhater,

Here you go, if you'd like to see other settings, let me know.

M
gpresult.JPG

This is a GP Result of one of the computers with problem ??????

I had in mind a GP Modeling, however it clearly shows that that computer has no policy applied to enfor the warning banner !!!!

Are you facing this problem with many computers or just one ?

can you check the local policy on the computer itself ?

Yes, it is of the affected machine.  This is the 1st machine we are tring, so we only have one affected machine.  I checked the local policy and nothing there.