C
CCurious_Juan
Hello, every so often I find myself getting an error 0x80240037 in my windows update log. I use SCCM for managing updates on my servers. The simple fix is to stop SMS agent host, rename c:\windows\system32\grouppolicy\machine\registry.pol, restart sms agent host, and run actions from config man. It's not a big deal considering how few servers I manage and how often it occurs (about every 2 months). I thought about just creating a script to automate this process.
After some research, I found there could be a previously linked GPO with windows update configuration tattoo'd on the server.
Has anyone encountered this before? If so, where in the registry can I make sure windows is only pointing to my DP and not some other update source. I'm only finding this issue on my server 2012's and not my 2008 or 2016.
Any insight or ideas would be appreciated.
Continue reading...
After some research, I found there could be a previously linked GPO with windows update configuration tattoo'd on the server.
Has anyone encountered this before? If so, where in the registry can I make sure windows is only pointing to my DP and not some other update source. I'm only finding this issue on my server 2012's and not my 2008 or 2016.
Any insight or ideas would be appreciated.
Continue reading...