Contents
| Easy heading | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
If a proxy server is configured, it will be displayed in the command output.
Powershell:
$proxySettings = Get-ItemProperty -Path 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings'
if ($proxySettings.ProxyEnable -eq 1)
{
Write-Output "Proxy Server: $($proxySettings.ProxyServer)"
}
else {
Write-Output "Proxy is not enabled."
}
If proxy is set, this will be the result:
...
Check MSI File Access: Verify that the targeted PCs or servers can access the MSI file URL as specified in the clientUpgrade.json configuration. To test this, copy the URL from the JSON file and paste it into a browser on a non-updated PC or server. If the file cannot be downloaded, ensure that the URL is accurate and accessible through the specified port mentioned in the JSON file.
Event Viewer for 1603 Errors: If you can successfully download the file but the update is still not being applied, investigate the Event Viewer for events related to msiInstalled. Specifically, look for a 1603 error. This error might indicate that there are antivirus (AV) or endpoint detection and response (EDR) solutions blocking the installation.
EDR Exclusions: If you find a 1603 error in the Event Viewer, it's likely due to AV or EDR blocking the update. Check whether your AV or EDR solution has exclusions or rules that might be preventing the MSI file from being installed. Make sure that the paths, URLs, and processes associated with GYTPOL are properly excluded to allow for smooth updates.
| Anchor | ||||
|---|---|---|---|---|
|
...
PDQdeploy etc.)
Occasionally, the MSI installer may fail to run due to missing cached MSI files, often occurring after SCCM deployment. If this issue arises, you may encounter the following error message:
...