I have setup and ran for many months SCCM R2. We use this for Windows updates, future software rollouts and general hardware/software reporting.
Recently with the addition of a new Hardware Based Web Filtering system a WPAD setting has had to be put in place for our non domain clients to redirect them through the new filtering system.
This has somehow had a negative effect on my domain clients scanning for windows updates and reporting back to the SCCM Server. When I run the “Troubleshooting 3 - Computers failing with a specific scan error“ report all domain clients report back as Scan failed with an error code of -2145107941. Needless to say my compliance reports come back as unknown.
If we remove/disable the WPAD then all domain clients scan without fault. I can then update all clients. We tested this a few times to be sure.
The WPAD file has to stay to accommodate the non domain clients.
Does anyone have an idea how I can get round this issue? I don’t want to move away from SCCM windows updating as it’s worked flawlessly until now.
Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat. The purpose of this eBook is to educate the reader about ransomware attacks.
The environment that this is running in is SCCM 2007 R2 running on a Windows 2008 R2 server. The PXE Distribution point is running on its own Windows 2008 R2 box.
This is what Event viewer showed after trying to start the WDS service:
On a regular basis I get questions about slow RDP performance, RDP connection problems, strange errors and even BSOD, remote computers freezing or restarting after initiation of a remote session.
In a lot of this cases the quick solutions made b…
This Micro Tutorial will give you a basic overview how to record your screen with Microsoft Expression Encoder. This program is still free and open for the public to download.
This will be demonstrated using Microsoft Expression Encoder 4.
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online.
The email signature template has been downloaded from: