- This topic has 7 replies, 2 voices, and was last updated 5 years, 3 months ago by .
-
Posts
-
1) We just recently purchase batchpatch about 1.5 weeks ago.
2) How do we know batchpatch is searching for patch via local WSUS server or Microsoft site?
When we use the get windows update configuration it show the local WSUS server. However we want batchpatch to use Microsoft site instead. We have set in the tools -> settings -> windows update -> Microsoft Update. The search is very slow. If we use the normal windows update, it is much faster compare to BP. The performance is not acceptable.
3) If we are perform the windows download and install for not joining domain servers, it is not working. When we go the windows update and search for download in the server itself, there is no issue. But BP cannot perform the search. Below is the error.
Windows Update Messages
Error -102: Failed to execute the search. – 11:35:55
Remote Agent Log
WIN2K8R264BIT 06/04/2015 11:27:32
::Begin online search – Server Selection: Microsoft Update
-102: Failed to execute the search. HRESULT: -2147012866
Logon Account
157.165.162.227administrator
All Messages
Thu-11:35:56> Windows Update: END (Cached mode: Download and install updates)
Thu-11:35:55> Windows Update: Error -102: Failed to execute the search.
Thu-11:33:49> Windows Update: Executing BatchPatchRemoteAgent.exe…
Thu-11:33:48> Windows Update: Attempting to initiate Windows Update (Action: Search for updates and retrieve url list. Server selection: Microsoft Update) …
Thu-11:33:48> Windows Update: Establishing connection…
Thu-11:33:43> Windows Update: Initializing…
Thu-11:33:43> Windows Update: BEGIN (Cached mode: Download and install updates)
Thu-11:33:43> Windows Update: Queued…
Thu-11:33:13> Windows Update: END (Cached mode: Download and install updates)
Thu-11:33:13> Windows Update: Error 1601: Failed to retrieve WMI info. Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Thu-11:33:12> Windows Update: Initializing…
Thu-11:33:12> Windows Update: BEGIN (Cached mode: Download and install updates)
Thu-11:33:12> Windows Update: Queued…
4) Also could your forum here be upgraded to allow attachment??
Steven –
“How do we know batchpatch is searching for patch via local WSUS server or Microsoft site?”
Under ‘Tools > Settings > Windows Update’ you can configure where you want the search/download to take place from. You’ll notice that after you set the ‘Server Selection’ to Microsoft Update, your logs will be consistent with that, as you can see in the text you posted:
::Begin online search - Server Selection: Microsoft Updateand
Thu-11:33:48> Windows Update: Attempting to initiate Windows Update (Action: Search for updates and retrieve url list. Server selection: Microsoft Update) ...“When we use the get windows update configuration it show the local WSUS server. However we want batchpatch to use Microsoft site instead. We have set in the tools -> settings -> windows update -> Microsoft Update.”
The ‘Get Windows Update’ configuration tells you where the target computer is configured to search/download. However, when you set the ‘Server Selection’ to Microsoft Update you are *not* changing the target computer’s configuration. You are *bypassing* the target computer’s configuration and connecting to Microsoft Update instead.
“The search is very slow. If we use the normal windows update, it is much faster compare to BP.”
When you use the “normal Windows Update” as you describe, the target computer is searching your local WSUS server, not Microsoft Update. I know this because you indicated that ‘Get Windows Update’ configuration is reporting your local WSUS server. This means that when you perform a search for Windows Updates directly on that target computer using the Control Panel Windows Update GUI, it is searching for updates on your local WSUS. Your local WSUS server is expected to be faster than Microsoft Update because it’s local. However, it also sounds like you are working with limited internet connectivity because under normal circumstances even though Microsoft Update might be slower than your local WSUS server, in most cases it is still reasonably fast.
“If we are perform the windows download and install for not joining domain servers, it is not working.”
You received the following error:
-102: Failed to execute the search. HRESULT: -2147012866-102 indicates that the target computer is having problems with its connectivity to the Microsoft Update servers.
-2147012866 converts to 80072EFE (see http://www.rapidtables.com/convert/number/decimal-to-hex.htm), and when I googled that HEX number 80072EFE I came to the following page, which also indicates/confirms that the problem is related to connectivity from the target computer to the Microsoft servers. Additionally, this is consistent with your earlier description that Microsoft Update was very slow for you. Normally Microsoft Update is not very slow, but if you’re experiencing slowness in some cases or a complete lack of connectivity in other cases, it is an indication that either your internet access is limited connectivity, or perhaps just your connection to Microsoft’s servers is limited:
http://windows.microsoft.com/en-us/windows7/windows-update-error-80072efe-or-80072f76
“I managed to opt-in for microsoft update and perform the download and install for the non domain server. It still fail with the following error.”
This second time you received a different error:
-102: Failed to execute the search. HRESULT: -2145124322In reviewing your log it appears that you executed the ‘Opt-in to Microsoft Update’ action, but you did not wait for it to complete. Before it completed you executed a Windows Update search. While the Windows Update search was taking place, the Windows Update service was restarted by BatchPatch to complete the ‘Opt-in’ process. This is why it generated the new error -2145124322.
“Also could your forum here be upgraded to allow attachment?”
We will consider this. In the meantime if you want to post an image you would have to use a third-party image hosting site such as imgur.
-Doug
Steven – please email me the c:windowswindowsupdate.log file from the target computer that is producing this error.
Thanks,
Doug
To close the loop for anyone else who might read this posting:
After reviewing the WindowsUpdate.log we found many errors, primarily 0x80072ee2, 0x80072efe, and 0x8024a005, all of which indicated connectivity problems from the target computer to Microsoft’s servers. The issue was caused because a proxy is in place but the machine was not configured to use the proxy for Windows Update. More is described at the following link:
https://support.microsoft.com/en-us/kb/900935
Essentially the Windows Update service is not able to use the proxy settings that are configured in IE unless it is invoked by the logged on interactive user. So a manual check by the logged on user for Windows Updates can be successful while the Automatic Updates service or the update service initiated by a third party tool such as BatchPatch fails due to lack of connectivity because the proxy is not used. In order for a proxy to be used in these cases it must be configured using netsh or WPAD.
To configure a proxy server by using the Netsh.exe tool:
For Windows Vista and above, Netsh.exe tool is available in place of proxycfg.exe.
To use the Netsh.exe tool to configure a proxy server, follow these steps:
Click Start, click Run, type cmd, and then click OK. At the command prompt, type netsh winhttp set proxy proxyservername:portnumber, and then press ENTER. In this command, replace proxyservername with the fully qualified domain name of the proxy server. Replace portnumber with the port number for which you want to configure the proxy server. For example, replace proxyservername with proxy.domain.example.com and replace portnumber with 80.
OR
Web Proxy Auto Detect (WPAD) settings are configured in either of the following locations in the network environment:
The Domain Name System (DNS) options
The Dynamic Host Configuration Protocol (DHCP) options
For more information about a related topic, click the following article number to view the article in the Microsoft Knowledge Base:
http://support.microsoft.com/kb/816320
The domains to whitelist are:
http://download.windowsupdate.com
http://*.download.windowsupdate.com
https://*.update.microsoft.com
http://*.windowsupdate.microsoft.com
http://windowsupdate.microsoft.com
https://*.windowsupdate.microsoft.com
http://ntservicepack.microsoft.com
If you are using a wpad.dat file to configure your computers’ proxy settings, you can use the following syntax in the wpad.dat file to whitelist the Microsoft domains:
if ( shExpMatch ( url, “*.download.windowsupdate.com/*”) ) { return “DIRECT”; }
if ( shExpMatch ( url, “*.download.microsoft.com/*”) ) { return “DIRECT”; }
if ( shExpMatch ( url, “*.update.microsoft.com/*”) ) { return “DIRECT”; }
if ( shExpMatch ( url, “*.windowsupdate.com/*”) ) { return “DIRECT”; }
if ( shExpMatch ( url, “*.download.windowsupdate.com/*”) ) { return “DIRECT”; }
if ( shExpMatch ( url, “*.windowsupdate.microsoft.com/*”) ) { return “DIRECT”; }
if ( shExpMatch ( url, “*.ntservicepack.microsoft.com/*”) ) { return “DIRECT”; }
if ( shExpMatch ( url, “*.wustat.windows.com/*”) ) { return “DIRECT”; }
For all other -102 HRESULT values, please see batchpatch-error-102-failed-to-execute-the-search-hresult-xxxxxxxxxx
- You must be logged in to reply to this topic.