BatchPatch Forums Home › Forums › BatchPatch Support Forum › goodbye wuauclt hello uso client
Tagged: batchpatch features long overdue
- This topic has 1 reply, 2 voices, and was last updated 4 years, 6 months ago by doug.
-
AuthorPosts
-
June 24, 2020 at 4:03 pm #12385TCBParticipant
I noticed some things on batch patch that need to be updated or removed. I shouldn’t have to enter in my own commands for very basic operations of the now, uso client. I thought this was “the ultimate windows update tool”…??
wuauclt.exe and all the commands with it ARE NO longer used at all…unless you are on windows 7 and server 2012r2…server 2012 might be ok…but windows 7…cmon man.
The USO client is new to windows 10 and Server 2016. (only been out a few years now) There are simple commands here to be added to batch patch to speeds things up.
Enter…. powershell…. (windows update commands only)…where are the remote powershell commands on demand? or do I have to type all those in also? lil Help….??
June 24, 2020 at 4:42 pm #12386dougModeratorWe have no plans to remove the wuauclt.exe commands in the near future because we still have many users who use those commands for their older operating systems.
We talk about usoclient for Windows 10/2016/2019 in this blog posting from Nov 2017.
We have a built-in usoclient command under ‘Actions > Windows updates > usoclient.exe startscan‘. This is the only usoclient.exe command that we have found to have any real value, as of yet, so it’s the only one that we have included. You are certainly welcomed to add your own additional ones. And if you think that any other usoclient commands are useful/valuable, we’d love to hear how and why, so please feel free to explain. It’s certainly possible that you know something that we don’t, and we make adjustments to the software all the time based on customer feedback.
However, we also make BatchPatch customizable so that it can be tweaked by the end-user because not all users have the same needs and desires, obviously. If you think there is a particular command that is not currently included out-of-box but should be included, let us know. If we think it’s a command that many users would find valuable, then we will add it. If not, then you can simply add it to your own BP installation.
You can hard-code your own remote commands as explained at the following link. Once you have added a command, it appears in the BatchPatch menu just like out-of-the-box commands do, so you don’t need to add it every time you launch the app: How to Hard-Code Your Own Custom Commands in the BatchPatch Actions Menu
-
AuthorPosts
- You must be logged in to reply to this topic.