Configuration - Windows Update - Allow a Standard User to use Windows Update
0 Votes |
Versioning - This is the latest version.
1 | Allow a Standard User to use Windows Update | 12/5/2012 10:39:30 AM |
2 | Configuration - Windows Update - Allow a Standard User to use Windows Update | 8/29/2013 1:29:16 PM |
Description
Property Details
2583 | |
QA - Ready for Production Level Testing | |
Configuration - Windows Update - Allow a Standard User to use Windows Update | |
BESC | |
Configuration | |
0 | |
jgs194 | |
8/29/2013 12:00:00 AM | |
Standard User Update Registry Edit | |
True | |
jgstew on 8/29/2013 1:29:16 PM | |
jgstew on 8/29/2013 1:29:16 PM | |
3911 Views / 4 Downloads | |
![]() ![]() ![]() ![]() ![]() |
Relevance
Used in 2 fixlets | * Results in a true/false |

exists value "ElevateNonAdmins" whose (1 != it as integer) of key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update" of native registry
Windows Only (Relevance 2997197)

/* Windows Only */ windows of operating system

/* Windows Vista or Higher */ version of operating system >= "6.0"
Actions
Action 1 (default)
Action Link Click
here to initiate the deployment process.
Script Type
BigFix Action Script
regset64 "[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update]" "ElevateNonAdmins"=dword:00000001Success Criteria
This action will be considered successful when the applicability relevance evaluates to false.
Sharing
Social Media: |
Comments
![]() |
|
You're very welcome. Also, this task is an example of an issue I have been seeing lately... The are listed in the order they were originally submitted to bigfix.me (the relevance number) and not the order of precedance that the relevance follows from the actual task as uploaded. This mostly happens when updating old tasks with new relevance. |
![]() |
|
Awesome! I was hoping some else would come up with these... I'll add these to a special patching automation collection. |