RE: troubleshooting client not receiving policy for AD Sec group C

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Thanks Sherry, I'll make sure the users on the computer have logged off and
back on and aren't using cached credentials. Didn't think of that. I agree
with you on the targetting of computers rather than groups. Most of our
distributions are handled like that. We actually just acquired 1E's shopping
tool to replace the process were using the user groups for. Thx again for
the tip I'll check it out and let you know if that worked.

"Sherry Kissinger [MVP-SMS]" wrote:

We target to usergroups as well; where the members of the usergroup are user
ids. The main issue is to confirm that the users have logged off/on since
being added to the usergroup. And, of course, they did so when a domain
controller was available. Logging off/on using cached credentials at a
coffee shop doesn't count. The new usergroup tokens aren't attached to the
user ID in the interactive login until that happens.

fyi; we're trying to move to targetting computers more often than
usergroups. The reason is that the majority of 3rd party utilities for
remotely examining the SMS Client can only successfully look at/remotely
rerun machine-targetted ads. (like Roger Zander's Client Center, or right
click tools (Corey Becht's; Stuart Watret's does have user-targetted ads
tools).

--
Standarize. Simplify. Automate.


"Mike A" wrote:

I have a series of ads set to collections with groups that were discovered w/
AD security group discovery. the groups are in my collections and some of
the clients are receiving the advertisements, but how do I troubleshoot the
ones that aren't since the machine names aren't in the collection, but the
user group is. I have verified the logged on users are in the groups, but the
machines never receive policy.

Thanks,

.

Relevant Pages

  • RE: id- 1030 source - Userenv
    ... Thanks for using the SBS newsgroup! ... I understand that the issue to be: all client ... computers got 1030 error and can not connect to the SBS 2003 server box. ... Click Internet Protocol, ...
    (microsoft.public.windows.server.sbs)
  • RE: Remote Web Workplace - Connect to client workstations
    ... In Connect to Client desktops item lists all client computers on your SBS ... network that are running Windows XP or above; In Connect to Server desktops ... On the Tools menu, click Internet Options. ...
    (microsoft.public.windows.server.sbs)
  • RE: Domain naming issue
    ... computers discover other computers on the network. ... so that the client computers resolve .local names correctly. ... you can configure a Macintosh computer ... One thing that will support desktop sharing with a Mac is Microsoft Office ...
    (microsoft.public.windows.server.sbs)
  • RE: Unable to connect to Server/Client desktop using RWW
    ... When you remotely connect to Server Desktops (Client Desktops) ... Please verify all computers have allowed users log ... We can download the Remote Desktop Web Connection from Microsoft web ...
    (microsoft.public.windows.server.sbs)
  • Re: Users cant find SBS server- Help needed
    ... all appears to be working except that no computers show up ... under the domin name in windows network and the client computers don't see ... the server in their windows network. ... The server still does not show up in Network places nor does any other ...
    (microsoft.public.windows.server.sbs)