Jump to content


bookert2003

Sccm/Wsus Windows 10 servicing - 1607 deployment

Recommended Posts

Hello,

I have some difficulty deploying the windows 10 anniversary update (1607) to my clients via SCCM. I have installed KB3159706 and followed the post installation steps from: https://support.microsoft.com/en-us/kb/3159706

But when I deploy the upgrade via SCCM servicing the clients get this error message:

[AGENT_INSTALLING_FAILED] 101 {C9FA8069-097F-468B-A8AA-D35D74ED9E11} 201 8024200d CcmExec Failure Content Install Installation Failure: Windows failed to install the following update with error 0x8024200d: Feature update to Windows 10 Pro, version 1607, en-us, Retail.

[AGENT_INSTALLING_FAILED] 101 {C9FA8069-097F-468B-A8AA-D35D74ED9E11} 201 c1800118 CcmExec Failure Content Install Installation Failure: Windows failed to install the following update with error 0xc1800118: Feature update to Windows 10 Pro, version 1607, en-us, Retail.

Other deployments like definitions or security updates are working fine when deployed to a client via SCCM. Tried also to delete all the windows 10 upgrade related deployment packages and sync / download everything again but no go.

Is there something I am missing that needs to be done? Or is there something that is different when using SCCM that needs to be done?
My SUSDB is not on the same server that WSUS is installed on, is there also a update that needs to be installed on the SQL server that has the SUSDB?

SCCM is also update to the latest version 1606 and the clients have the latest SCCM client installed

Just to be sure I will provide the change I made to the web.config file incase there is an error here:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<!--For IIS 7 when virtual application is run in integrated mode-->
<system.webServer>
<handlers accessPolicy="Read, Script">
<remove name="WebServiceHandlerFactory-Integrated-4.0"/>
<add name="ClientWebServiceAsmxHandler"
path="*.asmx"
verb="*"
type="System.ServiceModel.Activation.ServiceHttpHandlerFactory, System.ServiceModel.Activation, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
preCondition="integratedMode,runtimeVersionv4.0" />
</handlers>
</system.webServer>

<!--
This section is required for converting an ASMX web service to WCF
-->
<system.web>
<compilation>
<buildProviders>
<remove extension=".asmx" />
<add extension=".asmx"
type="System.ServiceModel.Activation.ServiceBuildProvider, System.ServiceModel.Activation, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
</buildProviders>
</compilation>

<!-- GLOBALIZATION
This section sets the globalization settings of the application.
-->
<globalization
requestEncoding="utf-8"
responseEncoding="utf-8"
/>

<!-- DOCUMENTATION
Turn off documentation by default
-->
<webServices>
<protocols>
<remove name="Documentation"/>
</protocols>

<!-- Run SOAP Header Filter with ClientWebService -->
<soapExtensionTypes>
<add type="Microsoft.UpdateServices.WUShield,WUShield"
priority="1"
group="0" />
</soapExtensionTypes>
</webServices>

<!-- MAXREQUESTLENGTH
Limit the size of incoming requests to 4096 kbytes.
-->
<httpRuntime maxRequestLength="4096" />
</system.web>

<appSettings>
<!-- The maximim number of locales that a client can pass to GetExtendedUpdateInfo.
An InvalidParameters exception is thrown if this limit is exceeded.
-->
<add key="maxLocales" value="100"/>

<!-- The maximim number of update IDs that a client can pass to SyncUpdates,
SyncPrinterCatalogs, or RefreshCache.
An InvalidParameters exception is thrown if this limit is exceeded.
-->
<add key="maxCachedUpdates" value="22000"/>

<!-- The maximim number of installed prerequisites a client can pass to SyncUpdates
or SyncPrinterCatalog.
An InvalidParameters exception is thrown if this limit is exceeded.
-->
<add key="maxInstalledPrerequisites" value="400"/>

<!-- The maximum number of hardware IDs passed to spGetDriver. The web service trims
the system spec against the list of hardware IDs for which a driver exists in
the DB. Typically this results in a trimmed system spec containing only one or
two hardware IDs. Only the first maxPrunedHardwareIDs are submitted to the
driver query.
-->
<add key="maxPrunedHardwareIDs" value="20"/>

<!-- The order prerequisite clauses are sorted in the internal data-structures used by
SyncUpdates.
-->
<add key="detectoidTypes" value="ProductFamily;Product;Application Locale;Windows Locale"/>
<!--
The value of the following key is made part of the SQL connection's
ApplicationName property to improve sql tracing.
-->
<add key="ApplicationNameForDatabaseConnection" value="ClientWS"/>
</appSettings>

<system.serviceModel>
<diagnostics performanceCounters="All">
<messageLogging logEntireMessage="false"
logMalformedMessages="false"
logMessagesAtServiceLevel="false"
logMessagesAtTransportLevel="false"
maxMessagesToLog="30000" />
</diagnostics>
<services>
<!--
NOTE: To configure for both http and https, use full paths for endpoint addresses:
e.g. <endpoint address="https://localhost:8531/ClientWebService/Client.asmx"
-->
<service
name="Microsoft.UpdateServices.Internal.Client"
behaviorConfiguration="ClientWebServiceBehaviour">
<!--
If using SSL, change the bindingConfiguration to "SSL".
Configuration is Defined below in <bindings>...</bindings> section
-->
<endpoint address=""
binding="basicHttpBinding"
bindingConfiguration="SSL"
contract="Microsoft.UpdateServices.Internal.IClientWebService" />
<endpoint address="secured"
binding="basicHttpBinding"
bindingConfiguration="SSL"
contract="Microsoft.UpdateServices.Internal.IClientWebService" />
<endpoint address=""
binding="basicHttpBinding"
bindingConfiguration="ClientWebServiceBinding"
contract="Microsoft.UpdateServices.Internal.IClientWebService" />
<endpoint address="secured"
binding="basicHttpBinding"
bindingConfiguration="ClientWebServiceBinding"
contract="Microsoft.UpdateServices.Internal.IClientWebService" />
</service>
</services>
<behaviors>
<serviceBehaviors>
<behavior name="ClientWebServiceBehaviour" >
<serviceMetadata httpGetEnabled="true" httpsGetEnabled="true" />
<serviceDebug includeExceptionDetailInFaults="true" />
</behavior>
</serviceBehaviors>
</behaviors>
<!--binding configuration schema reference http://msdn.microsoft.com/en-us/library/ms731399.aspx-->
<bindings>
<basicHttpBinding>
<!-- WCF buffer pool settings set to 1MB/128MB to handle RefreshCache load (see 310779) -->
<binding name="ClientWebServiceBinding"
closeTimeout="00:01:00"
openTimeout="00:01:00"
receiveTimeout="00:10:00"
sendTimeout="00:01:00"
maxReceivedMessageSize="1048576"
maxBufferSize="1048576"
maxBufferPoolSize="134217728"
messageEncoding="Text"
textEncoding="utf-8">
<readerQuotas maxDepth="32"
maxStringContentLength="8192"
maxArrayLength="16384"
maxBytesPerRead="4096"
maxNameTableCharCount="16384" />
<!--
The security mode should be Transport only when the service is available over https
-->
</binding>
<binding name="SSL"
closeTimeout="00:01:00"
openTimeout="00:01:00"
receiveTimeout="00:10:00"
sendTimeout="00:01:00"
maxReceivedMessageSize="1048576"
maxBufferSize="1048576"
maxBufferPoolSize="134217728"
messageEncoding="Text"
textEncoding="utf-8">
<readerQuotas maxDepth="32"
maxStringContentLength="8192"
maxArrayLength="16384"
maxBytesPerRead="4096"
maxNameTableCharCount="16384" />
<security mode="Transport">
<transport clientCredentialType="None" />
</security>
</binding>
</basicHttpBinding>
</bindings>
<!-- Requires AspNetCompatibility mode -->
<serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true" />
</system.serviceModel>
</configuration>

Thanks in advance for the help.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.