[Roddy Gelberty]

Please create an SCCM task sequence and use the run PowerShell script step. Deploy the task sequence. Use the following script.

$tsenv = New-Object -COMObject Microsoft.SMS.TSEnvironment
$BIOSpassword = $tsenv.Value('BIOSpassword')
$devcs = Get-WmiObject -Class win32_computersystemproduct
$strBlueToothStatus = gwmi -class Lenovo_BiosSetting -namespace root\wmi -ErrorAction SilentlyContinue | Where-Object {$_.CurrentSetting.split(",",[StringSplitOptions]::RemoveEmptyEntries) -eq "BluetoothAccess"} 
if (!($($strBlueToothStatus.CurrentSetting) -eq "BluetoothAccess,Enable"))
{
    (gwmi -class Lenovo_SetBiosSetting –namespace root\wmi).SetBiosSetting("BluetoothAccess,Enable,$BIOSpassword,ascii,us")
    (gwmi -class Lenovo_SaveBiosSettings -namespace root\wmi).SaveBiosSettings("$BIOSpassword,ascii,us”)
}

In your target SCCM Collection add a collection variable called ‘BIOSpassword’ and assign it your password.

[Roddy Gelberty]

Hey Luna, When do you think you’ll post the SCCM compliance report that you spoke about in your previous comment. We are struggling to get our compliance percentages up. It would be nice to identify the gaps.

[Roddy Gelberty]

Its a work in progress. It has to get cleared by security before it gets published online. Covid19 has introduced a delay in all our processes. What reports do you folks use within you organization at the moment? I’ve got a teaser for you. 🙂

[Roddy Gelberty]

That worked. The SCCM client settings for the WSUS server were not set because the Registry.pol file was corrupted and 0 bytes.

[Roddy Gelberty]

Sarah, import the configuration manager PowerShell module.
Run the below PowerShell command.

Get-CMCollection | Where-Object {$_.PowerConfigsCount -gt 0 } | select -Property Name, PowerConfigsCount 

[Roddy Gelberty]

Rename the file ‘C:\\Windows\\system32\\GroupPolicy\\Machine\\Registry.pol’. I am assuming the C: is your system drive.
After renaming the above policy file. Run the following command as an administrator.

gpupdate /force

• This reply was modified 4 years, 9 months ago by  Roddy Gelberty.

[Roddy Gelberty]

A few amendments to Topaz’s answer. use ‘start-process‘ cmdlet to start ‘cleanmgr.exe‘.

If(Test-Path -Path($((Get-WmiObject Win32_OperatingSystem).SystemDrive) +"\windows.old")){ 	New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\VolumeCaches\Previous Installations" -Name "StateFlags1221" -PropertyType DWORD  -Value 2 -Force | Out-Null 	Start-Process -FilePath "cleanmgr" -ArgumentList /SAGERUN:1221 -Wait -WindowStyle Hidden}

[Roddy Gelberty]

Hey Jessica, We use baseline based compliance reporting internally at osd365. We run 12 baselines dedicated to each month per year. The baseline is based on pre-approved updates.
The baseline will include both Windows 10 and Office365 updates. Reporting compliance this way is more accurate because the result is Binary (1 or 0) 1 – Compliance and 0 – Non_Compliant.
I’ll need approval to make the report publicly available. So watch this space.

[Roddy Gelberty]

That works as treat. I’ll just copy and paste and create a table in SQL server reporting services report. Thank you for your help.

[Roddy Gelberty]

Thats a good response.

[Roddy Gelberty]

Use the new experimental feature in the Microsoft End Point Configuration Manager 2004 release called “Orchestration Groups’. This is used to call the “Server Groups” historically.
https://docs.microsoft.com/en-us/mem/configmgr/sum/deploy-use/orchestration-groups
Pretty straight forward. Gives you an opportunity to run a script before and after software update deployments for a group of devices managed by SCCM.
Also, remember if the software deployment begins on one device the deployment would also start on the other devices in the ‘Orchestration Group’.
This is a cool feature with multiple use cases.

[Roddy Gelberty]

The last time I checked Microsoft only sold HoloLens to online customers. So as always you could buy it from resellers and/or Microsoft Online.
Physical Microsoft stores ( I hear) are a thing of the past (secondhand information; do your research); so I doubt you’ll get it from there.
You being a developer might be able to leverage Microsoft’s “special developers program‘

[Roddy Gelberty]

You could put it all in one script.
In short,

• Pre-populate necessary fields from INI.
• Operator fills in additional details.
• Write back to the same INI or different INI (depending on your needs).

Hope that helps.

[Roddy Gelberty]

Thanks a lot Bobby!

[Roddy Gelberty]

@bobby-brown
Bobby,
Quick question, Do i have to treat step 1, step 2, step 3 as separate powershell scripts?
for instance, form in step 1 goes as form.ps1, then read ini files and pre-populate as readini.ps1
and write form to the ini file as WriteFormtoINI.ps1, and set them as run powershell scripts in the task sequence?

Thank you!