command to output the policies that are being applied to a user/computer. Make sure the client pc's have the internal DNS server, NOT an internet DNS service or ISP.One of the sections lists the policies that were either successfully or unsuccessfully applied. Permission Denied) next to the policies not applied. It's also useful because it drills down and tells you every rule that is currently in place, so it's easy to see what's working and what's not. Once you've done that, do a "gpupdate /force" to update the local policy.Here is the link to the output of What you're seeing is perfectly normal.The Local Group Policy editor is for viewing and configuring the Local group policy object and its settings, not for viewing domain based Group Policy settings.
This is where we tell WSUS how computers are added to groups. The default option is to add those computers manually, but we don’t want that, so choose the second option Use Group Policy or registry setting on computers. I’m going to create two groups here, one will be Group Policy Management. As you can see we have a lot of options here to configure Windows updates, but I’m going to configure just some of them, the rest I’ll live it to you. In the Target group name for this computer type XP Computers, click OK, and close the Group Policy Management Editor.To understand what I’m talking about, think of a network of 300 PCs, maybe that network is already in your company; you deployed a WSUS server but clients still go to Microsoft for updates, and you want to point them to your WSUS Server.Off course is an ugly job to do this manually for 300 clients, but this is where Group Policy comes in.I have Microsoft Small Business Server 2011 and when creating a GPO for my SBSComputers the settings do not apply.For instance I have enabled Verbose vs normal status messages in the Group Policy Management Editor in the Windows SBS Client Policy.