Re: Roaming Packages

Thank you very much for the link; I should have known there was a tool on
myitforum! Right now we brand the registry with this information during build
time, but this data can become outdated so this tool will come in handy.
Also, as I mentioned in a different post, combining User Resources and System
Resources in one query can be difficult, as the registry option would entail.
Now I have to come with the query that links the Username from the AD
Distribution Group with the Owner entry with its corresponding Computer Name,
the ultimate collection target.

"Kim Oppalfens" wrote:

> In article <16F7D420-EED5-4ACE-9E36-2F3CC9C4CEDC@xxxxxxxxxxxxx>,
> JAW@xxxxxxxxxxxxxxxxxxxxxxxxx says...
> > I would like to know how someone else handled the problem of user-targeted
> > packages installing on every computer that user logs on. There are certain
> > applications that should not roam with a user, but should install on the one
> > computer that is considered their "primary" or "owned" computer. Simply
> > targeting computers instead of users is not an option for us. Thank you.
> >
> Why is targetting computers not an option? Don't you know which machines
> are their "primary" or "owned" computer? If that is the case then how is
> sms going to know?
>
> If that is ineed your problem, may I suggest implementing the sms user
> logon audit security tool?
> http://myitforum.techtarget.com/blog/tmintner/archive/2005/05/09/6066.as
> px
>
> This inventorizes user logons, and allows you to query who logs in to a
> station the most. Presummably the user that logs in to a station the
> most (called the top user) is also the computer owner.
>
> You still might want to verify this report with reality, but it should
> be a serious step in the right direction.
>
> Kim Oppalfens
> MVP SMS
> --
> Kim Oppalfens
> MVP SMS
> Computacenter Belgium
>
.

Relevant Pages

  • Re: Roaming Packages
    ... >>> packages installing on every computer that user logs on. ... >>> targeting computers instead of users is not an option for us. ... >> Kim Oppalfens ... >> MVP SMS ...
    (microsoft.public.sms.admin)
  • Re: Advanced Client install woes (please please help)
    ... the trace in the logs on the management point. ... Kim Oppalfens ... MVP SMS ...
    (microsoft.public.sms.admin)
  • Re: SMS Inventory Capability
    ... >>> written to wmi or registry for collection. ... >>> Kim Oppalfens ... >>> MVP SMS ... >>> Computacenter Belgium ...
    (microsoft.public.sms.inventory)
  • Re: Roaming Packages
    ... > packages installing on every computer that user logs on. ... Kim Oppalfens ... MVP SMS ...
    (microsoft.public.sms.admin)
  • Re: Client Push Installation account error - SOLVED
    ... "Kim Oppalfens" wrote: ... > 2)Once unpacked install manual site accounts tool. ... >>> I assume you already tried a different account? ... >>> MVP SMS ...
    (microsoft.public.sms.admin)