[doug]

You can find the change log inside the software under ‘Help > Check for updates > View change log’

Thanks,

Doug

[doug]

I’m actually not certain which setting is controlling what you are seeing there. It might be different depending on which operating system you’re looking at. However, I can tell you that the settings are all generally controlled by group policy or more specifically by the policy’s corresponding registry value (when group policy is applied to a given computer, that computer then updates typically one registry value per applied policy to control the behavior specified by the policy). The location of all the policies in question is:

Computer Configuration > Administrative Templates > Windows Components > Windows Update

You could determine which registry keys/values are associated with the policies that you have in place to control the timing of updates, and then you could use BatchPatch to retrieve the corresponding registry values to determine the settings on the target computers.

However, we recommend that you use group policy (or local policy if the computers are not members of a domain) to prevent automatic updates from automatically installing updates, so there should be *no* schedule set for automatic updates. Then use BatchPatch to install the updates on-demand. This is described in more detail here:

batchpatch-integration-with-wsus-and-group-policy

[doug]

When you say “an update schedule” what exactly do you mean? Please be as specific and detailed as possible.

-Doug

[doug]

How do you currently check if it is disabled? Do you have a command line query that you can run to determine its state? If so, this should be able to be integrated into your BatchPatch remote commands so that it appears in your menu.

how-to-hard-code-your-own-custom-commands-in-the-batchpatch-actions-menu

[doug]

Are you using a local WSUS or are the searches being performed on Windows Update/Microsoft Update? Please try both (you can change the setting under ‘Tools > Settings > Windows Update’ in BatchPatch. I’d like to know if the issue only occurs with one or the other or both.

Please review the following posting about 106G. I don’t believe we have ever seen or heard of your particular HRESULT -2145123271, and I don’t believe we have ever seen 106G occur on Windows 2012R2. However, the 106G we have seen just a handful of times with customers. The 106G indicates that there was an error retrieving the search results from the update server, while the HRESULT value is the reason code. There may be a solution/resolution in this posting:

Error 106G

Also, if you are able to retrieve the relevant lines from your WindowsUpdate.log (C:WindowsWindowsUpdate.log) from the target computer, they might help shed some light. I would suggest searching for 80240439 in the log file to find the appropriate lines. Feel free to share your findings here.

-Doug

[doug]

I would suggest that you start by seeing if you are able to install updates at the control panel of any of these computers *without* using BatchPatch or if you get a similar error when performing the operation directly on the computer. Let me know what happens.

-2145123271 == 0x80240439

Some of these search results might also help: Google 80240439

[doug]

Excellent. Thanks for following up. I’m glad that 2 worked. I also understand that 3 does not scale well. I’ll ask the team to re-work the script so that it can be used for any number of fonts without having to fill in so much code.

-Doug

[doug]

I would suggest a few things to try:

1. Change the ‘remote execution context’ to ‘Elevated token’ and then try again and see if it works.

BatchPatch Remote Execution Context

2. Change the \nasserver path in the script to a local/relative path instead of one that reaches out to a remote server. If your script is made to *not* access a remote path and instead is made to access the files locally (locally on the target computer), I suspect it will work.

Deploying a Script with Relative Instead of Absolute Paths

3. Follow the tutorial linked below that explains another way to deploy fonts:

Remotely Install OpenType (.otf) or TrueType (.ttf) Fonts

Please report back and let us know what you try and what works for you.

Thanks,

Doug

[doug]

Yes.

[doug]

No. Give the free evaluation version of BatchPatch a go and you can see for yourself. If you run into any problems or have any questions, just post back to this thread.

-Doug

[doug]

Hi Scott – There is not currently a way to clear column contents from inside of a job queue, but we understand the need/desire, and we are considering this for a future build.

Thanks,

Doug

[doug]

Scott – You found a bug. We’ll have this fixed for the next release.

Thanks,

Doug

[doug]

Yes – there is a bug when using “remember open tabs” that causes them to not stick. however, for the next release of BP we will be having the column order saved per-tab/per-bps file instead of globally, so it will no longer be an issue.

Thanks,

Doug

[doug]

Yes, you can use the ‘server selection’ setting to choose whether updates are searched for and pulled from your local WSUS or directly from Microsoft. Windows Update Installation Filters

[doug]

This sounds like a filtering/settings issue. It does not sound like anything is broken.

Please review the second question in the BatchPatch FAQ

While the question does not describe the exact issue that you are encountering, the solution section should still give you all of the places to look at to figure out why you are not seeing what you expect to see.

If you continue to have issues, please open a support ticket by emailing us through the contact form

Thanks,

Doug

[doug]

Thanks, Andreas. Let me know how it goes.

-Doug

[doug]

Another option that might work is to use the following setting in BatchPatch:

Tools > Settings > Remote Execution > Use PsExec -r switch to specify remote service name

This setting allows you to modify the remote service name that is used by psexec from psexesvc to BatchPatchExeSvc or any other custom name of your choice. In the case where anti-virus or other security related software is blocking the remote service from running, changing the name of the remote service with this setting can bypass the restriction for some of those applications without having to add psexesvc to a whitelist.

[doug]

This is unexpected because it used to work properly. We will get it fixed for the next release.

Thanks for bringing it to our attention.

-Doug

[doug]

What is the target computer’s operating system?

[doug]

This indicates a problem with Windows Update on the target computer.

This HRESULT translates to:

0x80040154 -2147221164 REGDB_E_CLASSNOTREG

BITS in Windows 2000 is dependent on SENS and EventSystem services.

If COM+ catalog is corrupted, one of these errors was seen.

I would suggest that you start by making sure the target computer has the most recent version of the Windows Update Agent (WUA). You can get it from here:

https://technet.microsoft.com/en-us/library/bb932139.aspx

If you still have problems after that, it might indicate that there is registry corruption or some other system corruption. At that point I would suggest reviewing the following google search results to see if any of them addresses your issue.

[doug]

Currently the column display index is saved globally, not per-tab. While we are considering adding it to the per-tab settings, for now what you need to do if it does not appear to be saving properly is:

1. Close all instances of batchpatch.exe

2. Launch just a single instance of batchpatch.exe with just a single grid visible.

3. Move the columns to the desired locations. NOTE, the actual location of the column will be affected by which columns are visible at the time that you modify the column locations. So to be sure that it goes right next to the host column, you should first make visible the column that is currently next to the host column. Go to ‘Tools > Customize visible columns’ and check the desired boxes so that you can see which columns are actually right next to the hosts column. Then drag the notes column so that it is in between the hosts column and whichever column was previously next to the hosts column.

4. Once you have the desired ordering, close BatchPatch. When you re-open BP the columns should be in the order that they were previously.

-Doug

[doug]

To understand all the possible reasons for a discrepancy, please review item number 2 in the BatchPatch FAQ

[doug]

Hi Simon – I’m sorry to hear that you are having trouble. The issue sounds like maybe psexec is being held up. Sometimes when you run psexec for the first time Windows prompts you to tick a box to allow it to run, which Windows sometimes forces you to do for programs that are downloaded from the internet. I wonder if that is happening but the window is hidden so that you can’t see it and can’t click on it to continue. I would start by trying to run psexec manually at the cmd prompt. Also make sure that you are running it as the same user that BP is running it as, which would be the logged on user account or if you input alternate credentials into BP then you would need to make sure it runs with those alternate credentials. If you continue to have problems after that, I would suggest start by going through the steps in the troubleshooting guide.

Let me know how it goes.

-Doug

[doug]

Regarding Windows Update: Error 1611: 5. Failure

This likely means that PsExec is failing to work properly.

1. If all target computers are affected then first try ‘Tools > Settings > Remote Execution > Use PsExec -r switch…’ and provide a name in that field such as BatchPatchExeSvc.

If the suggestion in 1. works, then it indicates that probably the issue is being caused by anti-virus or HIPS or other security software in your environment that is blocking PsExec from working. If it does not work, then try 2.

2. Try running BatchPatch from a different computer. If this works, then it indicates that PsExec has somehow broken or failed on the original computer. If this does not work try 3.

3. Try substituting PaExec for PsExec by renaming PaExec to PsExec. See if it also fails. Frequently when PsExec “breaks” on a computer, PaExec also breaks, further indicating something is not functioning properly in the system.

4. If you’re still stuck, try the BatchPatch troubleshooting guide to narrow down the source of the problem.

[doug]

In BatchPatch you can use ‘Tools > Export’ and ‘Tools > Import’

Thanks,

Doug

[doug]

I’m not sure I really understand the question. Could you explain exactly what you mean?

Thanks,

Doug

[doug]

Thank you for your suggestions. As a matter of fact, all of these are already on our to-do list, so keep your eye out for them in a future release.

-Doug

[doug]

Excellent. Keep me posted on how things progress!

Thanks,

Doug

[doug]

My trusted root store shows the same CAs as yours. This is so weird. Are you absolutely sure that you have been providing me with the correct error and HRESULT? Is there any possibility that you mixed things up? The -198 error can occur with a number of different HRESULTS, so possibly you saw -198 but assumed the HRESULT was the same when it was not? This might be a stretch, but I want to confirm because it has happened before with other users.

I think the likelihood of being able to disable signature validation is almost nil. I think that you have a couple of more realistic options…

0. Try running the Microsoft Baseline Security Analyzer on the targets. It uses the WsusScn2.cab also (at least it used to, but I have not used it in a very long time) https://www.microsoft.com/en-us/download/details.aspx?id=7558 See if it scans successfully or if it throws a similar certificate error. If it works and gives you the list of available security updates, then you can download these and install them manually or download them and then use BP to deploy them with the ‘Deploy’ feature in BP.

1. If possible, provide temporary internet access to these computers, and then perform the scan in online instead of offline mode.

2. Manually figure out what updates Microsoft has released for these computers in the past few months, and then download all of them manually for installation. Since Microsoft switched to cumulative update model not that long ago, it might not be that challenging or time consuming to do this (unless Windows 7 isn’t using that same cumulative model– I can’t remember off the top of my head if it is or is not). You could still use BP to deploy the standalone updates to the computers using the ‘Deploy’ feature in BP. But you would need to obtain the correct updates from Microsoft manually first.

3. Try uninstalling May’s updates from these computers and see what happens.

Good luck and keep me posted.

[doug]

Ok no worries. Sorry about that. Based on viewing the cert chain on the WsusScn2.cab file I would think that the certificate that needs to be in the trusted root store is the Microsoft Root Certificate Authority. I conclude this based on looking at the ‘certification path’ tab of the certificate for the WsusScn2.cab. The path ends with the Microsoft Root Certificate Authority. And I can confirm that I have this Microsoft Root Certificate Authority listed in my trusted root CAs snap-in. If I were you I would look to see if you have it showing and if you can see that the dates on it are valid. I hope this helps. Let me know what you find.

-Doug

[Author]

Posts