Forum Replies Created
-
Posts
-
Thanks for the suggestion. We’ll consider this for the next version.
This likely has something to do with SSL config and communication between the target and the WSUS. Have a look at the solutions provided at these two links:
https://faultbucket.ca/2012/08/windows-server-2012-windows-update-error-0x80240440
For other HRESULT values please see: https://batchpatch.com/batchpatch-error-102-failed-to-execute-the-search-hresult-xxxxxxxxxx
For other HRESULT values please see: https://batchpatch.com/batchpatch-error-102-failed-to-execute-the-search-hresult-xxxxxxxxxx
For other HRESULT values please see https://batchpatch.com/batchpatch-error-102-failed-to-execute-the-search-hresult-xxxxxxxxxx
Each sequence must have its own execution row. There is not currently a way to trigger one sequence to start when another has completed, but you can certainly just set it up as a single larger sequence that encompasses both of the smaller ones. If you want the completion of one sequence to trigger the start of another sequence, then it seems to me that’s what you really want anyway… I mean you really just want one larger sequence that encompasses the two individual smaller sequences. Why would you split it into two smaller sequences if the goal would be to have completion of one sequence would trigger the start of the other sequence? How is this different or better than just having a single larger sequence?
Make sure that ‘Tools > Settings > Remote Execution > Use psexec custom filepath‘ is pointing to psexec.exe and not pointing to batchpatch.exe
We have a handful of tutorials on the website:
https://batchpatch.com/advanced-multi-row-queue-sequence-video-tutorial
https://batchpatch.com/advanced-multi-row-queue-sequence
https://batchpatch.com/virtual-machine-guest-host-update-and-reboot-sequence-automation
https://batchpatch.com/patch-and-update-automation-with-multiple-dependent-systemsThe process works as follows:
1. First you must choose the action(s) that will be executed on each host/row when the sequence runs. The actions are assigned by using the regular job queue
configuration screen for each row that you want to include in the sequence. For this process you’ll select ‘Actions > Job Queue > Create/modify job queue.’ In
the Job Queue window you’ll choose your desired queue, and then finally you’ll click ‘Apply queue to row(s) without executing.’2. For all rows that you want to be part of a sequence, you’ll need to choose a sequence name. You’ll apply a particular sequence name to each host that is
included in a given sequence. With the sequence name you’ll also apply a sequence position number. Multiple hosts can have the same position number, if desired.
So, if you need to have one host execute an action, and then when it completes you need five hosts to all execute actions simultaneously, and then when they all
complete you need three other hosts to all execute actions simultaneously, you can do that by applying the following sequence position numbers:host1 YourSequenceName:PositionNumber1
host2 YourSequenceName:PositionNumber2
host3 YourSequenceName:PositionNumber2
host4 YourSequenceName:PositionNumber2
host5 YourSequenceName:PositionNumber2
host6 YourSequenceName:PositionNumber2
host7 YourSequenceName:PositionNumber3
host8 YourSequenceName:PositionNumber3
host9 YourSequenceName:PositionNumber33. For each sequence name you must create a sequence execution row. This is a special row that is designated for launching a particular sequence.
hostX YourSequenceName:ExecutionRow
4. When you’re ready to execute a sequence, highlight the execution row for the sequence you want to execute, and then choose ‘Actions > Job Queue > Execute
advanced multi-row job queue sequence.’ BatchPatch will find all rows that have the same sequence name as the execution row, and then BatchPatch will launch
the job queue for all rows set to position number 1. When all position 1 rows have completed their queues, all position 2 job queues will be executed. When
all position 2 rows have completed their queues, all position 3 job queues will be executed. And so on.————————————-
In your case you asked to make sure that the groups finish rebooting and come back online before the next group begins, so you could configure your job queue something like this:
Download and install updates + reboot always Wait 10 minutes Wait for host to be detected online
In the screenshot above the SQL group will perform its update/reboot/wait actions, followed by the APP group, followed by the WEB group.
————————————-
However, you actually asked specifically about having *only* the reboot portion be staggered, in which case you’d have to actually add all computers to the grid twice, then you’d have to apply two separate job queues, and then you’d have to combine them all into a single sequence, as shown in the screenshot below. However, I would recommend doing what I’ve described above, not what you described (below). That’s because if your goal is to prevent services from being affected and only having certain machines offline at the same time, then you probably should not install updates at the same time on all groups either because there are times where during the update installation process services could be taken offline by Windows. To be safe you should instead install updates on a single group and reboot that single group, then install updates on the next group and reboot the next group, then install updates on the last group and reboot the last group.
Anyway though… if you still want to perform the update on all machines simultaneously followed by staggered reboots, you can do it. For this you’d have two separate job queues. The queue for updating, which occurs in sequence position 1 is simply:
Download and install updatesThe queue for rebooting and waiting, which occurs in sequence position 2, 3, and 4 is:
Reboot (force, if required) Wait 10 minutes Wait for host to be detected online
More recently we’ve learned of two possible causes for this error. 1: If you are trying to apply updates to an operating system that Microsoft is no longer supporting and delivering updates for. If you have not purchased an Extended Security Update (ESU) package from Microsoft, you might need to do this. 2: You have not installed the most recent servicing stack update (SSU). Try manually applying the most recent SSU for the OS in question, and it’s likely this error will go away.
More recently we’ve learned of two possible causes for this error. 1: If you are trying to apply updates to an operating system that Microsoft is no longer supporting and delivering updates for. If you have not purchased an Extended Security Update (ESU) package from Microsoft, you might need to do this. 2: You have not installed the most recent servicing stack update (SSU). Try manually applying the most recent SSU for the OS in question, and it’s likely this error will go away.
I understand what you’re saying. It’s not clear to me why you would see a change after upgrading, as we have not observed that before, and Windows shouldn’t be making modifications that would lock you out. However, with Windows anything is possible. Even including a bug in the particular build of 20H2 that you have installed. Regardless, BatchPatch didn’t change during the upgrade, the target computer changed. And ‘Access Denied’ is always a permissions/authentication issue of some kind. Specifically, the error you are encountering is occurring when BatchPatch attempts to make a WMI connection to the target computer. I would suggest that you try the following things:
1. Log on to the target computer directly/manually with the same logon account that you are using to attempting to connect from BatchPatch. Just make sure that you’re able to log on successfully with the same username/password.
2. Since you are using a local account (not a domain account), check the registry values described in the section titled ‘Using Alternate Credentials with a Local Account’ at https://batchpatch.com/batchpatch-authentication-in-domain-and-workgroup-non-domain-environments Make sure the necessary registry values were not removed/modified during the upgrade process
3. Test out option 1 and option 2 instead of just option 3 at the following link to see if you experience different results: https://batchpatch.com/batchpatch-authentication-in-domain-and-workgroup-non-domain-environments Make sure the necessary registry values were not removed/modified during the upgrade process
4. This link has some further WMI troubleshooting steps to try that are equally relevant for BatchPatch because in both cases it’s just a WMI connection that is being attempted, so it doesn’t matter if that WMI connection is being attempted from BatchPatch or from a different app, it’s still a WMI query being made in all cases: https://community.spiceworks.com/support/inventory/troubleshooting/advanced-wmi-issues
5. If you have any type of anti-virus or HIPS or similar security app running on the target, check that too as a possible culprit. However, generally ‘Access Denied’ is virtually always something specific to Windows permissions/authentication
6. See if you have the latest build of 20H2 or if there is an update available. You can manually/directly check for updates at the Windows Update control panel of the target computer
“Access denied” indicates that there is a permissions or authentication problem of some kind. We have not ever seen nor heard of any issues that are specifically tied to upgrading to 20H2, so I would suggest you simply re-go-over the permissions/requirements, and make sure everything is in place for that particular computer.
https://batchpatch.com/batchpatch-authentication-in-domain-and-workgroup-non-domain-environments
https://batchpatch.com/getting-started-with-batchpatch
https://batchpatch.com/troubleshooting-common-errors-in-batchpatch
https://msdn.microsoft.com/en-us/library/aa394603%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396
-Doug
This link explains everything. Please read carefully through the entire page. The bottom section address registry changes that need to be made when using local accounts: https://batchpatch.com/batchpatch-authentication-in-domain-and-workgroup-non-domain-environments
1. You can use:
‘Actions > Windows updates > Generate consolidated report of available updates’
‘Actions > Windows updates > Generate consolidated report of update history’2. Yes, the filters work as described. I would suggest that you test on a single computer to ensure that the behavior meets your expectations. Once you’re comfortable with it, follow the same procedure for a larger group.
3. Yes. Remotely Deploying Windows Feature Update Version 21H1 to Numerous Computers
0x80240017 -2145124329 SUS_E_NOT_APPLICABLEThe update is not applicable for that target computer
Maybe I misunderstood what you actually tried to do. If you tried to copy the .lnk file from the start, but that’s what you’re saying didn’t work properly, then I’m sorry to say I don’t know why that would be the case. BP performs a standard file copy just like if you do it yourself through Windows Explorer, so if that didn’t work then my guess is it’s due to something about how the shortcut file itself is formed, though I couldn’t say what exactly that would be. Maybe it doesn’t like %windir% and instead wants a full filepath.
However, when you first posted about this issue, I thought you were describing that you somehow had tried to enter this value into the BP copy file/folder interface, which I’m certain will not work properly:
%windir%\System32\rundll32.exe shell32.dll,Control_RunDLL timedate.cpl,,0Thanks for confirming!
BatchPatch is probably not the right tool for you.
You could possibly use *just* PsExec, which is free. However, there are some caveats, and it may or may not work smoothly. If the application is intended to be open and visible to a user on the target computer, then it would have to be executed/launched by that user account remotely. If each target computer is running under a different user account, then each target remote execution would have to be performed under the user account that is specific to each target computer. Additionally, in PsExec you would have to use the ‘Interactive’ option in order for the application to be visible in the target computer desktop session, otherwise it will be hidden and running in the background. But even with the ‘Interactive’ option in PsExec, it’s not guaranteed to work in the way that you want/need. You’ll have to experiment and see.
Please have a look at the resolution described at this page for that particular HRESULT value ( -102: Failed to execute the search. HRESULT: -2147024894 ) : BatchPatch Error: -102: Failed to execute the search. HRESULT -XXXXXXXXXX
The copy file/folder feature in BP is for copying files and folders only, so if you’re trying to copy something that is not a file or folder, it’s not going to work. Shortcuts are stored as .lnk files in Windows. You *might* be able to just copy the .lnk file, though I can’t say for sure. Try it and see if it works or not. If it does, great. If not, then it doesn’t work. If you locate a shortcut on your computer, you can use ‘shift right-click > copy-as-path’ to get the filepath of the .lnk file.
Please contact us directly
No worries. Glad you got it worked out.
Please see here
Thanks for confirming. 🙂
Clear data from your grid or start a fresh grid. Most likely your ‘All Messages’ column content is very large. My guess is your .bps file is prob between 10 and 20 megabytes at this point, which is a lot. You can clear data with ‘Actions > Clear column contents’
It’s not currently possible, but we’re working on it for a future release.
Ok great. Glad it’s working now. Thanks for letting me know. This is very helpful for us to know that you were able to resolve it with the instructions in that link.
You purchased a license without ever testing out the free evaluation version?
Hmmm… it’s tough to figure out what this could be. We’ve only ever had one report of 1611:3 before. Have a look at this link for details, and then let me know what you discover: https://batchpatch.com/forums/x/topic/error-1611-3-failure/