In a server environment administrators use Group Policy to configure computers that are members of domains, sites, and organizational units, affording them the flexibility of controlling hundreds of different aspects from one location.On a smaller scale, which is what this article will deal with, the local Group Policy object on an XP computer can be used to manage many changes that are implemented in the registry (registry based policy) as well as implement policies that control scripting functions and security options.Delete the "HKCU\Software\Policies\Microsoft" Key Delete the "HKCU\Software\Microsoft\Windows\Current Version\Group Policy Objects" Key. To answer your question - yes it's physically removed from the domain and now joins a workgroup. Basically, how this works is it (since it gets no policy when you run the command), it applies an empty policy, which effectively removes the stuck policy once and for all. If you see the DC or evidence that it pulled a policy, separate your computer from the network that's running on the DC and plug the machine into a separate network. Basically, does the system know it's not on the domain?Delete the "HKCU\Software\Microsoft\Windows\Current Version\Policies" Key. No internet connection is required for this solution, but the link needs to be up, and it needs to have an IP address. If you are still logging into an account that was used while it was on the domain, chances are it hasnt been removed from the domain.If it does, you need to disjoin the machine from the domain through the computer name tab in the advanced system settings and stop using the domain level account to log in. In my case even after a month later, it was trying to use Windows Update configured via group policy.If it is physically off the domain, and you ARE using a local account to log on, and it still carries the group policy settings, not only would i be very surprised, but something is wrong. To answer your question - yes it's physically removed from the domain and now joins a workgroup. I'm not sure if power settings and windows update settings fall under the same category but OP's scenario sounds quite possible.A few of my computers that were not imaged correctly had the same Sus Client ID used by my Windows Update Server which prevented them from downloading updates and reporting status.
Even if you have a single, stand alone computer with multiple users, Group Policy can be put to good use.The conversion went quite well, however a few cases did show up where some Windows XP computers were not mapping the drives.After some investigation, I was able to determine that this was caused by a missing Windows Update.But when Group Policy is not being applied, we can fix it!Microsoft has provided great guidelines and tools in order to troubleshoot.Group policy will apply if it is a domain account, regardless of physical connection to the network that the domain resides on.