James,
The one thing that I forgot to mention in the e-mail is that you'll want to raise the priority of your custom user settings package appropriately, such that it supersedes any other custom client settings packages that might override that setting. As a general rule, your more broadly focused client settings packages will have a lower priority, whereas the more specialized client settings packages will have a higher priority. Cheers, Trevor Sullivan From: [email protected] [mailto:[email protected]] On Behalf Of Beardsley, James Sent: Tuesday, September 24, 2013 4:14 PM To: [email protected] Subject: RE: [mssms] User Device Affinity Good idea. I'll try that. Thanks for the suggestion. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Trevor Sullivan Sent: Tuesday, September 24, 2013 2:14 PM To: [email protected] <mailto:[email protected]> Subject: RE: [mssms] User Device Affinity James, I could be wrong, but I think what you could do is: 1) Create a user collection containing the users that you don't want to be assigned to a device 2) Create a custom user settings package that disallows the "Allow user to define their primary devices" option 3) Deploy the custom user settings package to the collection in step #1 Hope this helps. Cheers, Trevor Sullivan From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Beardsley, James Sent: Tuesday, September 24, 2013 1:04 PM To: [email protected] <mailto:[email protected]> Subject: [mssms] User Device Affinity Hello all - Is there a way to prevent certain user accounts from being detected as possible options for user device affinity? Does discovering the user account with AD User Discovery dictate whether or not they can show up in UDA? Or is UDA independent of discovery? We have some service/admin accounts that we don't want to be assigned to machines but the help desk uses them to Run-As in cases where users don't have permissions to install some apps. So when our help desk uses these admin accounts to install the app, SCCM determines that as a potential user account on that machine when I open the "Edit Primary Users" properties on a particular machine and look in the "Users of this device in the last 90 days" section. I have my client settings configured to automatically assign users based upon usage data and the admin/service account is not used enough to become assigned that machine automatically but I'd rather they not even show up as an option to be selected on accident, for example, when our hardware department is matching machine to user after a PC migration. The chances of that happening are slim so this isn't a major deal. but just curious. Thanks, James _____ IRS Compliance: Any tax advice contained in this communication (including any attachments) is not intended or written to be used, and cannot be used, for the purpose of (i) avoiding penalties imposed under the Internal Revenue Code or applicable state or local tax law or (ii) promoting, marketing, or recommending to another party any transaction or matter addressed herein. _____ Confidentiality Notice: This e-mail is intended only for the addressee named above. It contains information that is privileged, confidential or otherwise protected from use and disclosure. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, or dissemination of this transmission, or taking of any action in reliance on its contents, or other use is strictly prohibited. If you have received this transmission in error, please reply to the sender listed above immediately and permanently delete this message from your inbox. Thank you for your cooperation. _____ IRS Compliance: Any tax advice contained in this communication (including any attachments) is not intended or written to be used, and cannot be used, for the purpose of (i) avoiding penalties imposed under the Internal Revenue Code or applicable state or local tax law or (ii) promoting, marketing, or recommending to another party any transaction or matter addressed herein. _____ Confidentiality Notice: This e-mail is intended only for the addressee named above. It contains information that is privileged, confidential or otherwise protected from use and disclosure. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, or dissemination of this transmission, or taking of any action in reliance on its contents, or other use is strictly prohibited. If you have received this transmission in error, please reply to the sender listed above immediately and permanently delete this message from your inbox. Thank you for your cooperation.
<<image001.png>>
