Jump to content

Search the Community

Showing results for tags 'uda'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
    • Windows 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Official Forum Supporters
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Windows Server General
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL



Found 6 results

  1. Hi, the build in report "User device affinity associations per collection" doesn´t list the "OSD Defined" relationships. We are using powershell to import computers and set the UDA relationship with the following command: Invoke-WmiMethod -Namespace root/SMS/site_$($SiteCode) -Class SMS_UserMachineRelationship -Name CreateRelationship -ArgumentList @($WksResourceID, 6, 1, $User) -ComputerName $SiteServer The console shows the relationship and software deployment works well. If we change the parameter "source" from "6" (OSD Defined) to "2" (Administrator Defined) the report lists the relationship correctly. Any ideas? Best regards
  2. I am having an issue where User/Device Affinity does not appear to be working 100%. My client policy states 856 minutes across 6 days with auto affinity enabled. I see in the device logs where users are meeting that criteria and I even see the state message in WMI. Back in the console however, the application deployment monitor is saying these users are not meeting the criteria for their primary device. I came across an article about resetting the state messages and having them resent but that didn't do anything. I was able to get it to work by removing the users affinity manually then re-adding it back. Once that was done, the software installed. The same article I found with the state message info mentioned this may be a bug but it was pretty old. I'm currently running 2012 R2 CU3. Some clients are working however which really muddies the water. Any help would be appreciated since at this point I'm not sure what the next place to look is.
  3. Hi I removed a user as the primary user of a device just to test the "auto configure users device affinity from usage data" functionality. The user is "qualified" (has usage data that is more than the thresholds) to be the primary user of the device. I have restarted the client and updated the "configuration manager properties" on the client. The usage data is updated but the user is not set back to primary user of the device. I set the threshold minutes to 1 and days to 1. After this, I waited for 1 day to see if the primary user was set but no primary user was set on the device. I then deleted the device (object) from the sccm console and ran a system discovery. After the device was back in the sccm console the primary user was set by the auto UDA. Is this a normal behaviour of the UDA? I thougt that the user was set as primary user of the device automtaically after i removed it when the auto UDA was on?
  4. Hi I have been testing the User Device Affinity and have a question about the last user logged on. In the console when i click a computer object and select "edit primary user" i can see the last logged on users to that specific computer. What's strange is that the last logged on user is not actually when a user logs on to the computer but when the smsagent service on the client is started/restarted. I was under the impression that the last logged on user was gathered from Active directory? I tested this by not logging off and on the client computer but only restarting the service and then check the "edit primary user" on the computer object in the sccm console.
  5. Hello everyone, I've been digging through posts both here and over at the technet site...what I'm trying to come up with is a collection for devices which have a primary user set for them. I've tried a number of different queries from various posts, but each time they don't return any results. I'll openly admit that I'm pretty worthless when it comes to query building, but I can at least say that the queries I was trying out did not have any errors in them. The other thing that I'm seeing is that in some circumstances, Service Manager was installed in the environment as well. We presently don't have that setup here...is that a requirement for some of these queries? I'm hoping not... I honestly hope that there's someone out there who actually has something like this in place that can help me get it sqared away. Thanks!
  6. Hi, With SCCM 2012 we are targetting users to deploy software. In my Windows 7 OSD task sequence I set UDA to link the user to the machine, so the user's software can install without the user logging on. We don't want to provide a computer to a user with half of his software installed so I need a way to check if all user's software is properly installed. How can I do that? Thx.
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.