Re: Advertise to specific users?

If you cannot avoid targetting users, consider tatooing computers with a
regkey (containing the affected user) that you'll collect in your inventory.
When you migrate to SCCM you'll be able to query an AD field, so you can use
UserPrincipalName or some other relevant field.


"Barkley Bees" <barkbees@nomail.com> a écrit dans le message de groupe de
discussion : #oS1sLt0IHA.4364@TK2MSFTNGP02.phx.gbl...
> Thanks for the advice Sherry and T.Smith. Well, thankfully 'AD User
> Discovery' was disabled in the Discovery methods which prevented the 'All
> Users' collection from being populated. This prevented me from pushing out
> the advert to specified users and I learned something in the process =).
>
> We are doing a pilot test of a new client security app and need to push it
> out to select users regardless so instead I used the SMS Report 'Computers
> for a specific user name' to look up the users computers and manually
> added them into the pilot collection (unfortunately it was a big pilot
> group of 110 users...ugh). Also, thanks for the pointer on ESD2007
> Sherry, I will be taking a look at it for sure (seems to really fill some
> gaps). Cheers!
>
>
> "Sherry Kissinger [MVP-SMS]" <mofmaster@smsexpert.com> wrote in message
> news:F4BF9429-06D8-4AFC-8B74-525DF8DD9186@microsoft.com...
>>I agree w/T. Smith. Try anything you can to *not* deploy to a user. I'm
>> still in the process of moving from user-targetted ads to
>> machine-targetted
>> ads. In addition to the problem of exceeding licensing, or tech installs
>> on
>> end user computers; user-targetted ads place their local history on the
>> target computer in a different area in WMI--which means that all of those
>> cool tools for re-running a failed ad simply do not work; like Roger
>> Zander's
>> SMS Client Center.
>>
>> I have a quasi-complicated configuration to find the highest ranked user
>> (using SLAT from systemcentertools.com), user discovery enabled, and
>> collection queries to find "computers where the highest ranked user is in
>> the
>> usergroup "whatever"
>>
>> It's not the best, and I'm hoping to get away from that soon, too. What
>> I'm
>> trying to go to more and more is putting a the computer AD account in an
>> AD
>> group. Then the collection query is "resourceids in usergroup".
>>
>> If you have something of a budget, I suggest checking out Enhanced System
>> Discovery from http://www.systemcentertools.com/esd2007.html You can get
>> close to what ESD does for you using lots of external scripts, and rigid
>> processes/procedures, but ESD makes it easy.
>>
>> --
>> Standardize. Simplify. Automate.
>>
>>
>> "T. Smith" wrote:
>>
>>> Hi there,
>>>
>>> I'd recommend doing it by computers, or do it for a container of
>>> computers
>>> in Active Directory, or by a group that a section of computers belongs
>>> to to
>>> advertise to...
>>>
>>> If you advert to a user, every computer that user logs into will get the
>>> advertisement... I originally did this in my environment and forgot
>>> that PC
>>> support staff log into many machines, and it caused problems. You can
>>> advertise to users, and as long as you want every computer they log on
>>> to,
>>> to get the advertisement there should be no problem for you.
>>>
>>> To add users to a collection, I create a new collection say called Test
>>> Users...
>>> Right click on the collection and choose properties...
>>> Click on Membership rules, and then click Query rules (second icon
>>> beside
>>> Membership Rules:
>>> This brings up the query rule Propeties.
>>> Give it a name
>>> Change Resource class to User resource and click Edit Query Statement
>>> This brings up query statment Properties,
>>> Click on Criteria
>>> Click the star (New Criteria)
>>> Change the Where (Click Select button)
>>> Attribure Class: User Resource
>>> Attribute : You have several options here, to just pick 1 user select
>>> User
>>> name and for a group of users, I'd select User OU Name
>>> Click Ok
>>> Now I'd change the Operator value to "is equal to"
>>> and then for the value click values (may not display all) and select the
>>> container of users you want to add to the collection...
>>> When you hit ok and exit out, when you refresh the collection you should
>>> see
>>> all user accounts that are in your active directory container that you
>>> selected...
>>>
>>> Now you can create the advertisement and advertise to this container and
>>> all
>>> users will get the advertisement... This is one way to do it, there are
>>> others that are similar, you can look at the other Attribute Classes and
>>> change in there depending on how you want to search...
>>>
>>> a bit long winded, but hope this helps...
>>>
>>>
>>>
>>> "Barkley Bees" <barkbees@nomail.com> wrote in message
>>> news:eQpmb%23h0IHA.1768@TK2MSFTNGP03.phx.gbl...
>>> > I'm on SMS 2003 and I need to send an advert to specific users.
>>> > Initially
>>> > I
>>> > went through SMS to find what systems the users were using but this is
>>> > quite
>>> > a task and not fully accurate. So, came to my senses and figured it
>>> > would
>>> > be
>>> > better/easier to point the advert at a custom collection comprised of
>>> > the
>>> > specified
>>> > users (as some users change from PC to PC). The problem then became
>>> > that
>>> > when I created said collection I needed
>>> > to base this collection on the 'all users' collection which does not
>>> > appear
>>> > to be populated.
>>> >
>>> > So, on to my questions:
>>> >
>>> > 1 - how can I populate the 'all users' collection?
>>> > 2 - is advertising a package to specific users as mentioned above a
>>> > recommended way to get the job done?
>>> > 3 - will the package/advert behave any differently if is aimed at a
>>> > user
>>> > based collection rather than one based on computer names? Do I need to
>>> > do
>>> > anything different? Thank you.
>>> > 4- if user "A" is in the specified user collection and (s)he logs on
>>> > to
>>> > more than one machine, will both machines run the advert?
>>> >
>>> >
>>> >
>>> >
>>>
>>>
>>>
>
>