Unset the local policy. Do a Machine Policy refresh. If the settings are set back, its configmgr
if not, do a gpupdate, and see what the results of a gpresult after that. Sent from Windows Mail From: Lindenfeld, Ivan<mailto:[email protected]> Sent: Wednesday, March 5, 2014 3:27 PM To: [email protected]<mailto:[email protected]> The symptom I see is the Client policy for workstations is set to “No” for limiting BITS bandwidth. The applied policy as seen in GPResult has this set to “Yes” with the remainder of the BITS settings set to default settings from the Client settings. These settings may be the default for this policy, so they don’t necessarily come from SCCM Client settings. The PC is a new build. SCCM Client was installed once. All of the other client settings are correct comparing GPResult or the registry to Client Policy. In GPResult, the winning policy is Local Group Policy. I believe it would say this if SCCM Client applied the policy or if it didn’t and was the default. I do not want BITS limiting. How can I prove what’s stuck? Thank ye. Ivan Lindenfeld Manager, Enterprise Deployment/SCCM Fidelity National Financial | Jacksonville, Florida
