Search the Community

Hi, I am looking for a way to determine which client settings my SCCM client currently is using. The context of this question is that I have build a (hybrid) cloud deployment workflow, and as part of the workflow I am triggering several sccm actions. Condition for these actions is that the client has loaded its specific client settings, which are assigned based on a dynamic collection. I already have checks that the client is listed as member of the collection, but since initial processing of client settings take some time (and incidentally fails the first time which results in the default client settings being loaded) I need a check to determine which client settings are active on the client. I'd prefer to check it on the client (but am open to alternative possibilities) and to be able to do the check with powershell is a must (since the check if part of a workflow), I cant however seem to find where to find info on the active client settings. Possible scenarios I have in mind are: When proper client settings are loaded, we have a specific title in software center. If i can find where I can query this title with a script, I can determine the active client settings. If (and i would assume so) there is any info in the SCCM clients WMI space about the processed client settings or software center title, that would be great and easy to check. However I haven't been able to find where in the WMI space there is such info. If SCCM console somewhere in the device info what settings have been processed by the client, I could check that. Least desirable, but if this info is somewhere in the SCCM Database, I can check that. I hope my question is clear and somebody is able to help me out or give some pointers on where to find detailed info on processed client settings. Thanks in advance! [EDIT] I wasnt sure which category to pick, so if "collections" isnt the best option, my apologies

Gents, Do you konw if there is a way to configure the client settings so as to block application and package deployment and only allow software updates deployment ? I would like to deploy this client on servers in order to be sure that no applications can be install by mistakes. Sypa

I have had a few clients that have had the request of having multiple business hours for differnt sites or departments for one reason for another. When you have alot of machines its not the best idea to just bounce to each machine and set the hours so I stumbled upon this and it has been a life saver. Go to Asset Compliance > Configuration Items and right click to create a new configuraton item. You create a discovery script to get your current settings: $cmClientUserSettings = [WmiClass]"\\.\ROOT\ccm\ClientSDK:CCM_ClientUXSettings" $businessHours = $cmClientUserSettings.GetBusinessHours() $businessHoursCI = [string]$businessHours.StartTime + "," + [string]$businessHours.EndTime + "," + [string]$businessHours.WorkingDays Return $businessHoursCI It will return a value like 7,19,62 for 7 am to 7pm Monday-Friday all you would do to modify that is use the script below and the chart to add up the days. Sunday 1 Monday 2 Tuesday 4 Wednesday 8 Thursday 16 Friday 32 Saturday 64 So if you would want Sunday - Saturday it would be 127 then 5am to 7 pm you would just modify the script to look like it does below. You create a remediation script to set new business hours: $startTime = 5 $endTime = 19 $workingDays = 127 $cmClientUserSettings = [WmiClass]"\\.\ROOT\ccm\ClientSDK:CCM_ClientUXSettings" $businessHours = $cmClientUserSettings.PSBase.GetMethodParameters("SetBusinessHours") $businessHours.StartTime = $StartTime $businessHours.EndTime = $EndTime $businessHours.WorkingDays = $WorkingDays Try { $result = $cmClientUserSettings.PSBase.InvokeMethod("SetBusinessHours", $businessHours, $Null) If ($result.ReturnValue -eq 0 ) { "Success." } Else { "Failed to set SCCM client business hours." } } Catch { "Failed to set SCCM client business hours." } You can then deploy that to every machine or if you would like to have multiple business hours you would make multiple configuration items then just deploy them to seperate collections. This has come in handy for me being able to set multiple business hours across a company, I hope somebody else finds it useful. Bryan