locked
Possible to deploy Client configuration settings via script? RRS feed

  • Question

  • Is it possible to modify or set specific client configurations via a powershell script during an OSD Task sequence or an application package? 

    Reason for the ask is we have a large number (5000) of HP Thin clients that operate in a Workgroup. We are in the process of moving these devices into our AD and they will be managed through SCCM. Our plan is to migrate most of the devices through attrition by our hardware lease cycle. When new devices come into the environment they will be imaged through SCCM and joined to the domain. We want to apply a specific client configuration setting to these devices. 

    An issue we have encountered with these devices is once the device is imaged and in the domain, the device will get the updated client configuration settings that are deployed to the collection they are a member of. Due to the write filters in place on the Thin Client, it requires a reboot to commit the changes to the device. When our devices reboot, the write filter is left in a disabled state. Normally SCCM handles the write filter through use of maintenance windows, and re-enables the filter after brief (15 minute) servicing window. During this servicing window, it locks the device and can not be used by the end user. We are a 24/7 healthcare facility and can not have the devices enter this serving mode, even for 15 minutes. 

    Currently I'm getting around this by using the SMSTSPostaction variable to call a powershell script that has the client check into sccm and download the policies for it, waits for 10 minutes and then enables the write filter. It's worked with mixed success at this point. I'm curious if its possible to apply the client configurations via powershell during the OSD task sequence to get around this issue. 

    Thanks

    Wednesday, April 11, 2018 3:52 PM

All replies

  • Are you referring to settings specific to ConfigMgr like those normally defined using client settings in the console?

    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, April 11, 2018 5:40 PM
  • Hi Jason, yes, I'm wondering if it is possible to define those settings at some point during the task sequence. I know from the SCCM cmdlet library contains cmdlets for collecting and setting client settings (ref: https://technet.microsoft.com/en-us/library/jj821742(v=sc.20).aspx) however I'm not sure they are intended to function in the manner that I am hoping for. 

    Thanks

    Thursday, April 12, 2018 12:39 PM
  • Correct, those cmdlets are for site configuration, not individual client configuration.

    To my knowledge, all (or nearly all) client settings are values in WMI. So ultimately, if you can find the write WMI class and attribute defining what you want to set, then you should be able to achieve your goal. There is no reference for where the client settings live in WMI though other than under root\ccm so you'll have to manually dig through WMI to find what you need.

    Here's an older article for directly configuring local policies: https://technet.microsoft.com/en-us/library/2006.09.customizesms.aspx. This essentially what the client settings feature set is doing for you in 2012 and CB. https://msdn.microsoft.com/en-us/library/cc146756.aspx may help as well.


    Jason | https://home.configmgrftw.com | @jasonsandys


    Thursday, April 12, 2018 2:51 PM