Running this command will "prime" the Windows Update engine to submit its most recent status on the next poll.
You're most likely here because you are an IT administrator and you have a network that deploys Windows Updates via Windows Server Update Services or WSUS. I built a lab environment consisting of a domain controller, a WSUS server and a client machine.
Perhaps you're relatively new to WSUS or you're a veteran that has been using the product since its inception. I then proceeded to deep dive with process monitor and packet analyzers to try and find a way to "trick" the WSUS client into thinking it's time to report in.
So below is a function you can add to your profile.ps1 file on your WSUS server to allow you to automatically update any client machines on demand: This has been a life changer in terms of improving my frustration level with managing WSUS. But once it’s run you still have to tell it to actually report its status. COMException Hi Jonathan, The command runs instantly in terms of it’s command line execution as it doesn’t return anything. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Category Info : Operation Stopped: (:) , COMException Fully Qualified Error Id : System. This Power Shell error is due to the inability to communicate with the WSUS server.
Follow up the command above with a wuauclt /reportnow and you should be golden. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Category Info : Operation Stopped: (:) , COMException Fully Qualified Error Id : System. Your issue sounds more fundamental to your WSUS installation. In my case, a system proxy was set and the proxy was blocking the communication.
Yes, the script works regardless if a user is logged in or not as you are logging in yourself via psexec. My WSUS assets are not reporting back to wsus, and I get a time out. The two big things to check are: 1) Open a command prompt and type “Telnet [IP of your WSUS server] 8530”. Once I allowed the IP of the WSUS server in the proxy server, the PS command executed without the error Lord Glacius notes.
Thanks for this, I’ve searching a solution to the report problem for a long time. You’ll need some basic Power Shell scripting experience to do so and you’re environment would need to be configured to allow administrative remoting via psexec. I opened all firewalls on the windows client/server for testing purpose, I can reach the webpage, but in the error message it says it failed to get a HTTP reply.. Exception from HRESULT: 0x80240440 At line:1 char:1 $updates=$update Session. If it returns a blank screen that means the port is open and responding and that’s good. I have tried the command from powershell and get the same error: Exception from HRESULT: 0x80244022 At line:1 char:62 … One little problem: the scalar variable $criteria is not defined. COMException Connecting to MEWROYD01…Starting PSEXESVC service on MEWROYD01…Connecting with Ps Exec service on MEWROYD01…Starting on MEWROYD01… out of 141 connected machine there are only 3 machines found reporting the rest are none.We've been tried on downgrading and still machines are not reporting.I checked web config file each servers the working WSUS is on Windows Server 2012. If it turns out that it is a problem, I'll get someone to move it to the appropriate forum.and the other one which is running on Windows Server 2008, it has only one reported computer. what I've noticed the web config file on Server 2012 has much content than the other one. Got a notification earlier that new updates are available. I was going to do a system restore, but I cannot get to it.In either case, you are mostly frustrated because even in the latest release of WSUS that there is no way to force clients to check in and report their status. After many hours at this, I was just about to give up when I accidentally stumbled upon the magic command I was looking for.