Wsus approving updates without set rules

hi,

i'll start background story.

i created new rule '' accept updates/install" created test pool. test pool supposed test pool receive updates before clients in company does, since 80% of machines ghosted found ourselves duplicated sid.
in other words, updates sent pratically computers.

things did stop : immediatly removed computers in test pool , deleted rule ''accept updates/install''.

problem : the major problem here, after deleting rule, wsus server still seem approve updates randomly , computers. since have duplicated sid doesn't , it's pratically impossible control which updates install computer.
i've run reports approved updates , weird thing here is, not approved our wsusadminacc nor other administrator, approved wus server ( have no idea is, seems me it's wsus server ).

it's getting chaotic here, since updates causing error , force restart, isolated our wsus server now.
does deleting rule, revert does? doesn't seem me, updates have been approved still approved removing prevent future updates being approved. wsus approving alot , random updates , it's pushing clients no apparent reason, no approval made seem wsus automatically approve updates sees deployed on clients.

 edit :
after alot of google search, i've found 2 articles had same issue me.
when create rule, if set applied specific group it's being applied "all computers" default ? true?

 

however since 80% of machines ghosted found ourselves duplicated sid.
in other words, updates sent pratically computers.

ghosting , duplicate susclientid issues assuredly not cause of updates being sent of computers.

problem : major problem here, after deleting rule, wsus server still seem approve updates randomly , computers.

so, couple of points basic functionality of wsus useful here:

1. removing computers group not stop installation occuring. if client has detected/downloaded/scheduled update installation , not execute detection before scheduled installation event (at point discover update no longer approved virtue of having been removed group), updates still install.

2. deleting auto-approval rule not delete actual approval update.

3. sounds me auto-approval rule defective begin with, , may have caused update approved more specified test group. if so, removing computers test group may not have been functional, every computer continue member of "all computers".

4. wsus server not approve updates "randomly", can discount statement, pending more definitive statement , evidence supporting actual behavior.

since have duplicated sid doesn't , it's pratically impossible control updates install computer.

while understand may think accuate statement, can tell 100% certainty duplicate ids have absolutely nothing how updates approved, or how they're detected client systems. in fact, impact of duplicate susclientid how computers report wsus server, of happens after fact.

i've run reports approved updates , weird thing here is, not approved our wsusadminacc nor other administrator, approved wus server

confirms auto-approval rule defective. yes "wus server" indicates updates approved pursuant auto-approval rule. wsus server did told do. whether told wanted question answered.

does deleting rule, revert does?

no.

it doesn't seem me, updates have been approved still approved removing prevent future updates being approved.

correct.

also wsus approving lot , random updates , it's pushing clients no apparent reason. no approval made seem wsus automatically approve updates sees deployed on clients.

well, no isn't, appreciate perception @ moment.

after alot of google search, i've found 2 articles had same issue me.
when create rule, if set applied specific group it's being applied "all computers" default ? true?

not true. i'm not sure "articles" found, please careful when reading such articles accept information knowledgable sources. there lot of incorrect , misleading opinions floating around forum sites. in fact, post here great exampe, why made point of noting each inaccurate statement... lest other new wsus admin read post , think these things true because posted such.

incidentally . . . have read of wsus product documentation?

the truth dozens, perhaps hundreds, have had similar issues . . . , in every case fundamental issue using product without first understanding how so, , causing undesirable happen because event or option misconfigured. 

---

lawrence garvin, m.s., mcitp:ea, mcdba, mcsa
principal/cto, onsite technology solutions, houston, texas
microsoft mvp - software distribution (2005-2010)
mvp profile: http://mvp.support.microsoft.com/profile/lawrence.garvin
blog: http://onsitechsolutions.spaces.live.com

Windows Server  >  WSUS