Just a quick follow up on this so I can track if the change is working. I modified the days to 21 to give it plenty of time to reach 2880 minutes.
Is there a SQL query available that can tell me any new auto-approvals? I'm going to dig around in SQL but figured I'd check to save me some time. From: [email protected] [mailto:[email protected]] On Behalf Of Beardsley, James Sent: Thursday, August 21, 2014 3:29 PM To: [email protected] Subject: [mssms] RE: UDA not auto-approving Ohh, that makes total sense. I was interpreting that as either 2880 minutes or 3 days. Thanks for the explanation Phil. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: Thursday, August 21, 2014 3:12 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: UDA not auto-approving Bump the Days setting back. That's the threshold you're looking for the user minutes to fall within. The way you have it set, they would have to be using the machine for 48 hours within a 72 hour (3 day) period. You need to give them a little more time to accumulate their 2880 minutes' worth of usage (unless you're working a sweatshop overseas somewhere). http://technet.microsoft.com/en-us/library/gg682067.aspx#BKMK_UserDeviceAffinityDeviceSettings (see highlighted note) Setting name More information User device affinity usage threshold (minutes) Specify the number of minutes before Configuration Manager creates a user device affinity mapping. User device affinity usage threshold (days) Specify the number of days over which the usage based affinity threshold is measured. Note For example, if User device affinity usage threshold (minutes) is specified as 60 minutes and User device affinity usage threshold (days)is specified at 5 days, the user must use the device for 60 minutes over a period of 5 days to automatically create a user device affinity. The report you ran shows the number of logins *in the last 90 days* for that system, which doesn't help you because you are looking for time within any given 3 day window. -Phil _________________________________________________________________ Phil Schwan | Technical Architect, Enterprise Windows Services Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI 48075 Lync: 312.756.1626 Mobile: 419.262.5133 www.projectleadership.net<http://www.projectleadership.net/> [Description: Description: Description: Arrow email]Lead with Strategy. Leverage Technology. Deliver Results. [linkedin_logo-19x20]<http://www.linkedin.com/in/philschwan>[Twitter-Logo1-20x20]<https://twitter.com/philschwan> [wordpress-logo3] <http://myitforum.com/myitforumwp/author/philschwan> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Beardsley, James Sent: Thursday, August 21, 2014 1:58 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] UDA not auto-approving If my client settings are configured for 2880 minutes and 3 days, does that mean that both of those values have to be met before it'll auto-approve UDA? Or is it that only one of them needs to be meet the criteria? My clients are not getting auto-approved and I'm trying to determine why. For example, I have a user who has logged on to his laptop 93 times and it still hasn't been approved. If I check the logs, it states that he only has 1426 usage minutes. How its possible to log in 93 times but only have 1426 usage minutes, I can't figure out considering one 8 hour work day is 480 minutes. [cid:[email protected]] I thought it might've been that the security log on the local machine may have been getting overwritten but I checked and it has over two months of events in it so it can't be that. Any ideas? ________________________________ 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. ________________________________ PRIVILEGED AND CONFIDENTIAL. This email and any files transmitted with it are privileged and confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. If you are not the named addressee you should not disseminate, distribute or copy this e-mail or any of its attachments. ________________________________ 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. ________________________________ 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.
