please fix upstream downstream group membership change

[NVVN]

I'm in hope that new version will fix upstream / downstream group
membership change.

For example, client computer is member of group "regular". When on
downstream server I add client also to group "test" after synch. client
is on upstream server in two correct groups.

After I remove client on downstream server from "test" group client
stays at same group on upstream server. I can only delete client from
upstream server but client after synch. will be deleted also from
downstream server.

OK, it will after some time show up again in unassigned group on
downstream server. Well, move it again in "regular" group and after
synch. client is also again on upstream server in correct group.

But if I forgot to move client from unassigned group on downstream
server before scheduled synch. client will show up also in unassigned
group on upstream server, so again delete it, synch... and round and
round.

It is boring this synch, delete, move mumbo jumbo. :)

[Lawrence Garvin [MVP]]

Post by NVVN
After I remove client on downstream server from "test" group client
stays at same group on upstream server.

The only thing I see unusual here is that perhaps you're not waiting a
sufficient amount of time for the changes made at the downstream server to
replicate to the upstream server.

Everything else you've described here sounds like it's functioning exactly
as designed.

[NVVN]

Post by Lawrence Garvin [MVP]
The only thing I see unusual here is that perhaps you're not waiting a
sufficient amount of time for the changes made at the downstream server to
replicate to the upstream server.

Well, how much days I must wait ? If after 4 or more days change of
client group membership at downstream server is not propagated to
upstream server (i.e. client stays in former group at upstream server)
only solution is to delete client from upstream server, synch. wait to
appear again in unassigned group at downstream server, move to
appropriate group and synch. again.

However I will make this test again with waiting :)

[NVVN]

In article <***@msnews.microsoft.com>, ***@we.com
says...

Post by NVVN

Post by Lawrence Garvin [MVP]
The only thing I see unusual here is that perhaps you're not waiting a
sufficient amount of time for the changes made at the downstream server to
replicate to the upstream server.

Well, how much days I must wait ? If after 4 or more days change of
client group membership at downstream server is not propagated to
upstream server (i.e. client stays in former group at upstream server)
only solution is to delete client from upstream server, synch. wait to
appear again in unassigned group at downstream server, move to
appropriate group and synch. again.
However I will make this test again with waiting :)

Well, is it enough month and a half to wait ? :)

If I don't delete client manualy from upstream server, resynch... I can
wait almost a year and nothing will happen :)