[NotABot]

Were you trying to use “opt-in” on the BP computer all along and not on a remote computer?
Nope, these were all remote vm’s

And when you say there is now feedback in the logs, what is the feedback that now appears that was not appearing before?
This is what I did not see before

Remote Command Output Log
The Windows Update service is stopping.
The Windows Update service was stopped successfully.

The Windows Update service is starting.
The Windows Update service was started successfully.

There was also a popup window that informed me of services about to be restarted or something like that.

And what was there previously?
Nothing. I licked on Opt-In and it was like nothing happened. No pop up, no nothing. Now that I ran it as admin, seems to be working as expected

BP is version 2021.4.7.18.55

Thanks

[NotABot]

Your step #3 gave me a clue. When I tried to add itself, I was presented with the following:

When entering *this* computer into a BatchPatch grid, you must run BatchPatch as administrator (right-click on the batchpatch.exe and select ‘Run as administrator’) in order for everything to work properly.

Hmmm, even though I’m logged into the batchpatch box as an administrator, perhaps I should do a run as. Sure enough. When I start up BP with Run As Administrator, then do the Opt-In, I actually then get a dialog about what it’s about to do and there is now feed back in the logs.

Thanks!

[NotABot]

Since WU wasn’t bringing the appropriate update for .net core, I just found the update from MS, downloaded it and just now installed it in our test environment.

I think we might be ok now.

Thanks much for all the help!

[NotABot]

::Begin installation

1> Security Update for Microsoft ASP.NET MVC 4.0 (KB2993928) – Installation Result: Failed. HRESULT: -2147023293. Reboot Required: FALSE

::End installation

Overall Installation Result: Failed
Reboot Required: FALSE

Looks like I’m failing on reading lately. ASP.NET <> .net core. So I guess I’ll need to hunt for the .net core patch individually? Odd since I see that MS did announce it should be available from WU (LINK)

Thanks

[NotABot]

Nice, I’ll be applying that Opt-in on all the systems just to make sure I didn’t miss any.

So there seems to be a new “issue”. The VM that Nessus said that needed .net core updates, I had gone into the console and flipped the switch in it’s WU advanced settings to get all Microsoft product updates. Then I did a rescan in BP and it showed there was a new update for .net core (hooray). Download, install, and reboot if needed. After it completed the reboot, I did another Nessus scan. Same alert came up? Did a rescan in BP, nothing new. I looked at the history in BP and this is what I find:

03/26 10:46:09> Windows Update: No Reboot Required. Overall Installation Result: Failed
03/26 10:44:44> Windows Update: Executing BatchPatchRemoteAgent.exe…
03/26 10:44:44> Windows Update: Applying specific updates filter list…
03/26 10:44:44> Windows Update: Attempting to initiate Windows Update (Action: Download and install updates: ‘SoftwareOnly’ | Server selection: Default / Managed) …
03/26 10:44:44> Windows Update: Establishing connection…
03/26 10:44:44> Windows Update: Initializing…
03/26 10:44:44> Windows Update: Queued… (Download and install updates + reboot if required)
03/26 10:44:20> Windows Update: 2 update(s) found
03/26 10:43:45> Windows Update: Executing BatchPatchRemoteAgent.exe…
03/26 10:43:44> Windows Update: Attempting to initiate Windows Update (Action: Search for updates: ‘SoftwareOnly’ | Server selection: Default / Managed) …
03/26 10:43:44> Windows Update: Establishing connection…
03/26 10:43:44> Windows Update: Initializing…
03/26 10:43:44> Windows Update: Queued… (Check for available updates)

I switched the server selection from the default to “Microsoft Update” mentioned above, did a rescan, still no new updates.

Slightly confused again.

[NotABot]

Wow, lots of great information!

So looking closer at the updates that are coming up. They are indeed CU3 however I didn’t read the whole description closely. They are CU3 “Preview”. Which I’m still a little confused why those are coming up even after the real CU3 was already applied. At least now I know not to do the Check for Updates within WU anymore!

Part of the problem was that I was running a Nessus scan on a VM that I had just updated. It came back with an alert that .net core needed to be patched. Struck me as odd, so then I went in and did a Check for updates within WU and that was when the CU3 “Preview” came up. At that time, I didn’t realize that was a preview and made the assumption that the CU3 would cover that issue. It does not. I had to flip the “Give me updates for other MS products when I update Windows” switch (which I thought I had already done by oh well). Once I flipped that switch, BP was able to then see that there is a new update specific for .net core.

If that switch is not set in WU, is there a way to set it or just look for those updates within BP without going to all the VM’s and manually checking that switch?

Thanks much!

[NotABot]

I don’t know. I was only attempting to send out the remove Flash .msu. This was the first time I tried deploying .msu’s via BP.

Sorry…

[NotABot]

I too had been having the same issues as bweddell. The account I was logged into while running BP was an admin on that system as well as on the remote system trying to run the wusa.exe. Access was always denied. I’ve done reg changes in the past with no issues. I even tried to wrap the wusa.exe blahblah.msu into a .cmd file and try to run it that way.

Fortunately, I found a way to make it work. In the Remote Execution global settings within BP, I changed the Deployment context from Elevated token to SYSTEM. After I made that change, I was then able to deploy .msu’s!

Hope this helps.

[NotABot]

Yeah, I see that now.

Error 1611: 59. Failure

A restart of the VM seems to clear things up and the driver updates are no longer listed. Updating the VMware drivers from within Windows Update on other candidates seems to work ok. I suppose I’ll need to be a bit more careful now when looking at the listed updates. If I see drivers, I’ll need to do it the old fashion way.

Thanks

[NotABot]

Ahh, I had to enable the driver updates checkbox and now they are showing up.

Thanks!

[Author]

Posts