Jump to content


kesh

Windows 10 Anniversary Updates

Recommended Posts

I have a servicing plan in place which but it has not downloaded and deployed 1607. I can not see the 'Feature update to Windows 10 Enterprise, version 1607, en-us' update listed any where

 

We are on SCCM Current Branch 1606. I have follwed the manul steps to instal KB3159706. I dont see the patched inistalled though. What else can I check?

Share this post


Link to post
Share on other sites

my current file

 

<?xml version="1.0" encoding="utf-8" ?>
<configuration>

<system.web>

<!-- DYNAMIC DEBUG COMPILATION
Set compilation debug="true" to enable ASPX debugging. Otherwise, setting this value to
false will improve runtime performance of this application.
Set compilation debug="true" to insert debugging symbols (.pdb information)
into the compiled page. Because this creates a larger file that executes
more slowly, you should set this value to true only when debugging and to
false at all other times. For more information, refer to the documentation about
debugging ASP .NET files.
-->
<compilation
defaultLanguage="c#"
debug="false"
/>
<!-- CUSTOM ERROR MESSAGES
Set customError mode values to control the display of user-friendly
error messages to users instead of error details (including a stack trace):

"On" Always display custom (friendly) messages
"Off" Always display detailed ASP.NET error information.
"RemoteOnly" Display custom (friendly) messages only to users not running
on the local Web server. This setting is recommended for security purposes, so
that you do not display application detail information to remote clients.
-->
<customErrors
mode="RemoteOnly"
/>

<!-- AUTHENTICATION
This section sets the authentication policies of the application. Possible modes are "Windows", "Forms",
"Passport" and "None"
-->
<authentication mode="Windows" />

<!--
<authorization>
<deny users="?" />
</authorization>
-->

<!-- APPLICATION-LEVEL TRACE LOGGING
Application-level tracing enables trace log output for every page within an application.
Set trace enabled="true" to enable application trace logging. If pageOutput="true", the
trace information will be displayed at the bottom of each page. Otherwise, you can view the
application trace log by browsing the "trace.axd" page from your web application
root.
-->
<trace
enabled="false"
requestLimit="10"
pageOutput="false"
traceMode="SortByTime"
localOnly="true"
/>

<!-- SESSION STATE SETTINGS
By default ASP .NET uses cookies to identify which requests belong to a particular session.
If cookies are not available, a session can be tracked by adding a session identifier to the URL.
To disable cookies, set sessionState cookieless="true".
-->
<sessionState
mode="Off"
/>

<!-- 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>


</configuration>

Share this post


Link to post
Share on other sites

I followed that now. Only difference was to make the changes to the web.config file. Stil no luck. :(

 

I get this error on wsyncmgr.log

 

SyncBatchMinCreationDate not set, using default 01/01/2001 00:00:00 SMS_WSUS_SYNC_MANAGER 2016-10-07 12:06:34 PM 3128 (0x0C38)
Sync failed: The operation has timed out. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse SMS_WSUS_SYNC_MANAGER 2016-10-07 12:09:34 PM 5788 (0x169C)

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.