Some computers randomly changing group membership in WSUS with server side targeting.

We have a server 2003 based WSUS server that is doing strange things.  

I have configured it to use Server Side targeting.  I have noticed it doing a strange thing that appears to be random and infrequent enough.  I have configured a few groups or containers for computers in the WSUS console, of which currently only one is getting automatic approvals pointed at it.  The other containers are not being targeted (for now) and as such will not get updates.  All of these groups contain some number of computers that I have assigned to them.

Now the strange part.  Some of the computers change container membership by themselves, jumping from one to the other, while other or even the same computers disappear entirely and then come back.  Also note, that I am entirely aware and cognizant of that "filter computers by" filter and ensure I have it set to any followed by a refresh.

Does anyone have any ideas why some computers disappear and or change container membership?

Thanks.
CnicNVAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Don S.Commented:
If you set the target in the computer's registry either manually or via GPO, then that computer will return to it's target each time it contacts the WSUS server.  If you later move it to another group in WSUS, it will move back to what it knows as it's target group the next time it contacts WSUS.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
CnicNVAuthor Commented:
Thanks, yeah that was one of the first things I checked and client side targeting on all relevant OUs is disabled and as such the container paths cannot be specified :(

Thanks though.
0
Don S.Commented:
Check the registry of the clients, I don't think targeting is one of those items that reverse or remove its self in the registry when the gpo item is disabled.
0
CnicNVAuthor Commented:
Ok, sorry of the delay in grading this.

I have not changed anything, but it looks like the problem computers have stopped changing membership by themselves without intervention.  It has been a week and a half so far and everything seems to be fine.

Thanks for the info though.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.