Email Signature Platform - Help Desk and Knowledge Base

IT Pro: Deploy the required registry keys through SCCM (without GPO)

This is applicable when you are using SCCM to deploy your MSI package and refrain from using your GPO to deploy the ADM.

You may write the registry keys manually by including the below script on your SCCM deployment package.

Please save the below Powershell script as .PS1

$registryPath = "HKLM:\SOFTWARE\Policies\Xink\Xink Client AD\ADConfig"
$Name = "Mode"
$value = "ADClient"
IF(!(Test-Path $registryPath))
{
New-Item -Path $registryPath -Force | Out-Null
}
New-ItemProperty -Path $registryPath -Name $name -Value $value `
-PropertyType String -Force | Out-Null

$registryPath = "HKLM:\SOFTWARE\Policies\Xink\Xink Client AD\ADConfig"
$Name = "DomainAuthToken"
$value = "INSERT YOUR AUTH DOMAIN TOKEN HERE"
IF(!(Test-Path $registryPath))
{
New-Item -Path $registryPath -Force | Out-Null
}
New-ItemProperty -Path $registryPath -Name $name -Value $value `
-PropertyType String -Force | Out-Null


Adding MSI installer command on your Powershell script

You may be using your standard templates and ways to deploy your package but you may also add the MSIEXEC command at the top of the above Powershell script.

Ex.

msiexec /I "Server1\Installers\xinkClientSetupAD.msi" /q

Once you have saved the .PS1(Example file name: Add_Xink_Reg.ps1), you may use the below script to create a .BAT file that you save in the same folder as the .PS1.

SET location=%~dp0%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe -noprofile -executionpolicy bypass -file "%location%Add_Xink_Reg.ps1"

Then you can just use .BAT file as your deployment package.





Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.