Sccm get user primary device
09.07.2020 | by Goltishura
Then for each machine we're trying to find the user that used that machine the most, i. Name Group-Object where Count -ge 2. What is the correct query to have one machine name connected to one primary user with SamAccountName and FullUserName? It's possible that 1 device can be Primary device of many users, and also 1 user can have more than 1 Primary device. It depends on the criteria configured in Client Settings to identify Primary device.
By default if some users logs into a device for 48 hours in a month then it's considered as Primary device of that user. This criteria can be changed.
How are we doing? Please help us improve Stack Overflow. Take our short survey. Learn more. Asked 1 year, 1 month ago. Active 1 year, 1 month ago. Viewed 3k times. Thank you for your help. DarkLite1 DarkLite1 7, 22 22 gold badges 66 66 silver badges bronze badges.
Active Oldest Votes. Mudit Bahedia Mudit Bahedia 1 1 silver badge 10 10 bronze badges. Sign up or log in Sign up using Google. Sign up using Facebook.
Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Cryptocurrency-Based Life Forms. Q2 Community Roadmap. Featured on Meta. Community and Moderator guidelines for escalating issues via new response…. Feedback on Q2 Community Roadmap.
Triage needs to be fixed urgently, and users need to be notified upon…. Dark Mode Beta - help us root out low-contrast and un-converted bits.
Technical site integration observational experiment live on Stack Overflow. Related 0.User device affinity in Microsoft System Center Configuration Manager is a method of associating a user with one or more specified devices. Configuration Manager cmdlets must be run from the Configuration Manager site drive. The examples in this article use the site name XYZ.
For more information, see the getting started documentation. DisableWildcardHandling treats wildcard characters as literal character values. Cannot be combined with ForceWildcardHandling.
Get users with no primary device in SCCM
ForceWildcardHandling processes wildcard characters and may lead to unexpected behavior not recommended. Cannot be combined with DisableWildcardHandling.
You may also leave feedback directly on GitHub. Skip to main content. Exit focus mode. Gets a Configuration Manager user's device affinities. Note Configuration Manager cmdlets must be run from the Configuration Manager site drive. Specifies an array of device IDs. Specifies an array of device names.
Specifies an array of IDs of the primary users of the devices. Specifies an array of names of the primary users of the devices. Is this page helpful? Yes No. Any additional feedback? Skip Submit. Send feedback about This product This page.
This page. Submit feedback. There are no open issues. View on GitHub.In environments where Primary user feature of SCCM is used, it helps for troubleshooting issues that we have the name of the users responsible for machines to improve the co-ordination.
You are commenting using your WordPress. You are commenting using your Google account. You are commenting using your Twitter account. You are commenting using your Facebook account. Notify me of new comments via email. Notify me of new posts via email.
Hi Guys, In environments where Primary user feature of SCCM is used, it helps for troubleshooting issues that we have the name of the users responsible for machines to improve the co-ordination. Name0, C. Name0, d.
MachineResourceID where C. Like this: Like Loading Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in:.
These methods are:. Once the association has been created we can create our Deployment. Keep in mind we are deploying to a User based collection, and we are going to have to make this a required deployment in order for it to automatically install before the user even logs into the device. On the Deployment Properties section of the deployment wizard, we will make our deployment Required. At this point, the deployed Application will install when the policies on the client device have refreshed.
Any mandatory software deployments will be installed automatically because by this time it will actually know what user is going to use the computer given the UDA information is accurate. Any pending software deployments will have its content downloaded to the computer and will be available to the user. Fill in your details below or click an icon to log in:.
You are commenting using your WordPress. You are commenting using your Google account. You are commenting using your Twitter account. You are commenting using your Facebook account. Notify me of new comments via email.
Notify me of new posts via email. Search for:.
SCCM Query to See Device Owner Using User Device Affinity (uda)
These methods are: Automatic This method automatically associates a user to a device based on a threshold defined in Client Settings. This can be accomplished from either the User or Device object. Manual via User This method will allow a User to define the ownership of the device via the Software Center on the device itself. Share this: Twitter Facebook. Like this: Like Loading Leave a Reply Cancel reply Enter your comment here Email required Address never made public.
Name required. Post to Cancel.Assigning your users to their primary machines in SCCM is a common task. It permits to identify the primary machine of a specific user and opens the possibility to install software only on primary machines.
Once your associations are created, there are multiple ways to see the associations. This blog post will detail the various way to identify your user and primary machines and we also provide a free SCCM primary device report that you could use to easily find an association.
The most simple way to identify a primary machine for a user is to use the console. This method is simple but you will need to do that for each user which is not really productive. You can also click Primary Device in the related objects in the bottom right pane. Since SCCM version, the console now includes a column for primary users. You can also click Primary Users in the related objects in the bottom right pane. There is a built-in report User device affinity associations per collection but the report is not giving you the option to search for a specific machine or user.
You can easily search for a specific user or machine. The report will list all machines associated with a specific user. It can also be scoped by collections. Founder of System Center Dudes. Working in the industry since His specialization is designing, deploying and configuring SCCM, mass deployment of Windows operating systems, Office and Intunes deployments. AD User Discovery is enabled and several attributes loaded. Primary devices show up properly when I access a user object directly and vice-versa.
Am I missing something? Thanks in advance. Hello, I have this query for obtain all machines that have primary users. How can obtain all the primary users in the same column separate for commas. SerialNumber0 AS [Serial]dbo. Manufacturer0 AS [Manufacturer], dbo. Model0 AS [Model], dbo. Capacity0 [Memory in MB], dbo. WHERE dbo. We work nonstop to offer you speedy reaction and backing to get out of all hardships in a few couple of minutes.This week a relatively short blog post about a recently introduced feature in Configuration Manager, version That feature is the option for the user to select a device as a primary device, by using Software Center.
Previously the Application Catalog was still required to provide users with that specific option. That was also practically the only reason to still use the Application Catalog. From that perspective, this also provides a clear path for further simplifying the Configuration Manager hierarchy.
That configuration can be achieved by using Client Settings. The 3 steps below show how to enable this option for the users. When using Custom Client User Settings this setting is the only available setting. Note : Theoretically, when Automatically configure user device affinity from usage data is set to Nothe administrator must still approve the affinity request. However, my experience is that the primary user configuration is immediately processed. When the user now opens Software Center and navigates to the Options section, the user will find a new checkbox named I regularly use this computer to do my work.
SCCM Report primary device for user
When that checkbox is selected, the user will be marked as the primary user of that specific device. For more information about lettings users create their own device affinity, refer to this article about User device affinity section Let users create their own device affinities. The idea of this blog post is identical to my blog post about the permissions required to use Resultant Client Settings that I did a couple of weeks ago.
For those following me on Twitter, this blog post will be an extended version of a tweet I posted last week. Also, this blog is a lot easier to find for future references. This option allows the administrator to configure the primary user of a device and to configure the primary device of a user.
Keep in mind that providing the administrator with the minimum rights required to use these options, it does not mean that the administrator can add every user, or every device. In the form, that allows the administrator to add a primary user or a primary deviceit is also possible to search ALL users or ALL devicesbut this search is limited to the collections that the administrator is scoped to.
Now the key thing of this blog post, the minimal permissions required to use the Edit Primary Users option and the Edit Primary Devices option. There will be a small surprise between the required permissions. To provide an administrator with the minimal rights required for using these options, use the following list:.
The surprise in the required permissions is the fact that the read, modify, delete and create permission are required. This is not always the ideal situation. Well, actually the question was more about the easiest way to do this. The easiest way can be different depending on the current configuration. In this post I will go through three methods that can be used to set the UDA, so it can be used during and after the task sequence.
Before using the first, or the second method, there are a couple of prerequisites that need to be in place, like setting the task sequence variable SMSTSAssignUsersMode to Auto and configuring Allow user device affinity with automatic approval in the PXE configuration. The first method is probably the easiest method in the most situations. Also, it might remind everyone of an often used method to simply provide an input for a computer name, when using unknown computers.
The nice thing is that this exact same method can be used to provide the UDA information. This will cause the task sequence to request input for that specific variable. The second method is pretty similar to the first method, in a way that it will also generate an input request. This method requires some custom scripting to create an input form that request for an user name. That input form can be started as a prestart command on the boot image.It's pretty simple and straightforward to build a device collection based on combinations of other device collections.
It is also doesn't take much to teach someone how to use the GUI query builder to create a device collection filtered on one of the many hardware inventory fields, such as OS version, or devices with a specific software GUID installed. But what if you want to create a device collection of the primary devices of a specific group of users?
Where's the option in the GUI query builder for that? Ok, that was a trick question. You can't do it. When you are creating a device collection, you're not even offered the option to select from or join to user collections.SCCM - Populate device collections with AD groups
You're really sharp! It sure does. We have classes defining our computers. We have classes defining our users. We have classes defining the relationships between our computers and our users. We even have classes defining the membership of all the other existing collections in SCCM. It seems like we should be able to combine this data in a way that produces the device collection we want.
And we can - we'll just have to bypass the limited query builder. As they say, if you want something done right, you have to script it yourself. Or something like that. I know you're just dying to dive into the WQL at this point, but let's quickly cover a couple of ConfigMgr concepts that are important to understand. Feel free to skip this if you don't need the crash course. This data is summarized and then returned to SCCM via hardware inventory collection cycles. Based on the usage summaries, the SCCM client also calculates the single user who has been the most frequent user of the the computer based on total console usage time.