Software Updates Deployment Shows "Unknown" Computers, Previously Had Compliant

I'm not sure what is going on, but can anyone tell me why a software updates deployment would all of a sudden show all computers as having an "Unknown" status?  Previously, most computers were "Compliant" and there were a couple
with errors.  When I went to check it (about a week after the original deployment), I found it had reset all to "Unknown" status.  This was yesterday, and now today there are a couple computers showing "Compliant" but most are
still "Unknown".  It is not set up with ADR, so it's not (at least I don't think) looking for newer updates.  Any ideas?

A re-evaluation of the software update deployment, which you configure in the client settings, can cause this behavior. That's why you should always use the reports for compliance checks and not the deployments node.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Similar Messages

  • How to calculate the compliance for an software update deployment

    Hi All,
    I am trying to find as how do we calculate the compliance for an software update deployment.
    Scenario, We have about 4000 machine in the domain. but we have some stale records in the domain which is about 1200. The AD cleanup for the stale records is planned for sometime in March.
    So total number of machines in a collection (including the stale machines) are 5200.
    The current compliance of that deployment shows the following status:
    Complaint : 1156
    In Progress : 1724
    Error : 38
    Unknown : 2462
    And in the unknown, we have :
    Client check failed/Active: 2
    Client check failed/Inactive: 6
    Client check passed/Active: 732
    Client check passed/Inactive: 1722
    Can you please suggest in understanding the formula that should be followed to get the compliance.

    Your Compliancy, should be based solely off of the number of computers within CM12.
     There are no “if”, “and” or “but” able it.  This is the only way to truly and reliably provide numbers to management.
    Again it should be very simple calculation:
     (Total outstanding  Security SU, Total outstanding
     Critical SU, Total outstand Service packs, Total outstand Update Rollups, Total outstand Updates, Total outstand Definition Updates, Total outstand tools, Total outstand Feature packs) Vs Total applied SU (all Classifications)
    Or
    Total # of 100% patched PCs vs Total # of PCs as seen by CM12.
    If you use any other calculation then you MUST include a disclaimer that you are filtering out computers because they might be invalid. Or you MUST define exactly how you are calculating the number. Therefore any compliancy rate that your calculate maybe
    invalid too or at least it will change once you clean up AD.
    I will never hide low compliancy numbers to management, I will always show it to them.
     In many case I will ask to give a presentation to Management to explain why the numbers are so low.
     Provide them with a list of action items that need to be done in order to bring up the number to more reasonable level. I also set their expectation on what a reasonable level is.
    100% is unachievable; there is no exception to this!
    95-99% Very excellent but expect to spend lots of $$$s to obtain these percentages.
    90-95% is really, really, good; expect to spend $$s in this range.
    85-89% is good; expect to set strict procedures
    81-84 is ok but you could do better
    Below 80% is bad
    In your case, I would start by saying AD is dirty and need to be clean up, this has been schedule for March 2015. I would follow up this to say, in order to keep AD clean the follow procedures need to be define / updated / followed. You should also define
    exactly what you are doing to ensure that all computers are management by CM12.
    IMO these is no simple answer of this.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • Windows Update Agent rebooting systems after Software Update deployment

    I have a software update deployment that is configured to install software updates on a collection of servers at 4:00 AM with a suppressed reboot. The updates get deployed and no reboot occurs as expected.  Then ~8 hours later WUA starts up and the
    servers get rebooted.
    There is a maintenance window applied to the collection from 4:00 AM to 6:00 AM to allow the updates to install.
    I've read a few forum and blog posts on this issue and have implemented some settings via GPO, but the reboots are still occurring.  The settings that were applied are referenced in the link below.
    https://support.microsoft.com/kb/2476479?wa=wsignin1.0
    Here is a snippet from the WindowsUpdate.log:
    2014-10-22 12:00:26:153 1428 8a88 AU Received AU Resume timeout
    2014-10-22 12:00:26:153 1428 8a88 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Pre-install notify} added to AU services list
    2014-10-22 12:00:26:153 1428 8a88 AU Can not perform non-interactive scan if AU is interactive-only
    2014-10-22 12:02:08:512 1428 8a88 AU AU received policy change subscription event
    2014-10-22 12:16:43:463 1428 8a88 AU ###########  AU: Uninitializing Automatic Updates  ###########
    2014-10-22 12:16:43:479 1428 8a88 WuTask Uninit WU Task Manager
    2014-10-22 12:16:43:697 1428 8a88 Service *********
    2014-10-22 12:16:43:697 1428 8a88 Service **  END  **  Service: Service exit [Exit code = 0x240001]
    2014-10-22 12:16:43:697 1428 8a88 Service *************
    2014-10-22 12:19:29:728 1428 e584 Misc ===========  Logging initialized (build: 7.8.9200.16604, tz: -0400)  ===========
    2014-10-22 12:19:29:728 1428 e584 Misc   = Process: C:\WINDOWS\system32\svchost.exe
    2014-10-22 12:19:29:728 1428 e584 Misc   = Module: c:\windows\system32\wuaueng.dll
    2014-10-22 12:19:29:728 1428 e584 Service *************
    2014-10-22 12:19:29:728 1428 e584 Service ** START **  Service: Service startup
    2014-10-22 12:19:29:728 1428 e584 Service *********
    2014-10-22 12:19:29:744 1428 e584 Agent   * WU client version 7.8.9200.16604
    2014-10-22 12:19:29:744 1428 e584 Agent   * Base directory: C:\WINDOWS\SoftwareDistribution
    2014-10-22 12:19:29:744 1428 e584 Agent   * Access type: No proxy
    2014-10-22 12:19:29:744 1428 e584 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 2.
    2014-10-22 12:19:29:744 1428 e584 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 2.
    2014-10-22 12:19:29:744 1428 e584 Agent   * Network state: Connected
    2014-10-22 12:19:29:744 1428 e584 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 2.
    2014-10-22 12:19:29:744 1428 e584 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 2.
    2014-10-22 12:19:29:791 1428 e584 Agent ***********  Agent: Initializing global settings cache  ***********
    2014-10-22 12:19:29:791 1428 e584 Agent   * Endpoint Provider: 00000000-0000-0000-0000-000000000000
    2014-10-22 12:19:29:791 1428 e584 Agent   * WSUS server:
    http://Internal-WSUS.Domain:8530
    2014-10-22 12:19:29:791 1428 e584 Agent   * WSUS status server:
    http://Internal-WSUS.Domain:8530
    2014-10-22 12:19:29:791 1428 e584 Agent   * Target group: (Unassigned Computers)
    2014-10-22 12:19:29:791 1428 e584 Agent   * Windows Update access disabled: No
    2014-10-22 12:19:29:791 1428 e584 Misc WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
    2014-10-22 12:19:29:806 1428 e584 WuTask WuTaskManager delay initialize completed successfully..
    2014-10-22 12:19:29:822 1428 e584 Report CWERReporter::Init succeeded
    2014-10-22 12:19:29:822 1428 e584 Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2014-10-22 12:19:29:822 1428 e584 DnldMgr Download manager restoring 0 downloads
    2014-10-22 12:19:29:838 1428 e584 AU ###########  AU: Initializing Automatic Updates  ###########
    2014-10-22 12:19:29:838 1428 e584 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Pre-install notify} added to AU services list
    2014-10-22 12:19:29:838 1428 e584 AU AIR Mode is disabled
    2014-10-22 12:19:29:838 1428 e584 AU   # Policy Driven Provider:
    http://Internal-WSUS.Domain:8530
    2014-10-22 12:19:29:838 1428 e584 AU   # Detection frequency: 22
    2014-10-22 12:19:29:838 1428 e584 AU   # Approval type: Disabled (User preference)
    2014-10-22 12:19:29:838 1428 e584 AU   # Auto-install minor updates: No (User preference)
    2014-10-22 12:19:29:838 1428 e584 AU   # ServiceTypeDefault: Service 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 Approval type: (Pre-install notify)
    2014-10-22 12:19:29:838 1428 e584 AU   # Will interact with non-admins (Non-admins are elevated (User preference))
    2014-10-22 12:19:29:838 1428 e584 AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
    2014-10-22 12:19:29:853 1428 e584 AU AU finished delayed initialization
    2014-10-22 12:19:29:884 1428 e584 AU #############
    2014-10-22 12:19:29:884 1428 e584 AU ## START ##  AU: Search for updates
    2014-10-22 12:19:29:884 1428 e584 AU #########
    2014-10-22 12:19:29:884 1428 e584 Agent SkipSelfUpdateCheck search flag set for serverId: 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782
    2014-10-22 12:19:30:416 1428 e584 Report ***********  Report: Initializing static reporting data  ***********
    2014-10-22 12:19:30:416 1428 e584 Report   * OS Version = 6.2.9200.0.0.197008
    2014-10-22 12:19:30:416 1428 e584 Report   * OS Product Type = 0x00000008
    2014-10-22 12:19:30:416 1428 e584 Report   * Computer Brand = HP
    2014-10-22 12:19:30:416 1428 e584 Report   * Computer Model = ProLiant BL460c Gen8
    2014-10-22 12:19:30:416 1428 e584 Report   * Platform Role = 1
    2014-10-22 12:19:30:416 1428 e584 Report   * AlwaysOn/AlwaysConnected (AOAC) = 0
    2014-10-22 12:19:30:431 1428 e584 Report   * Bios Revision = I31
    2014-10-22 12:19:30:431 1428 e584 Report   * Bios Name = Default System BIOS
    2014-10-22 12:19:30:431 1428 e584 Report   * Bios Release Date = 2014-02-10T00:00:00
    2014-10-22 12:19:30:431 1428 e584 Report   * Bios Sku Number = 641016-B21     
    2014-10-22 12:19:30:431 1428 e584 Report   * Bios Vendor = HP
    2014-10-22 12:19:30:431 1428 e584 Report   * Bios Family = ProLiant
    2014-10-22 12:19:30:431 1428 e584 Report   * Bios Major Release = 255
    2014-10-22 12:19:30:431 1428 e584 Report   * Bios Minor Release = 255
    2014-10-22 12:19:30:431 1428 e584 Report   * Locale ID = 1033
    2014-10-22 12:19:30:431 1428 e584 AU <<## SUBMITTED ## AU: Search for updates  [CallId = {2787252C-D4B8-46B5-BB42-0C616042113C} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
    2014-10-22 12:19:30:431 1428 dae0 Agent *************
    2014-10-22 12:19:30:431 1428 dae0 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-10-22 12:19:30:431 1428 dae0 Agent *********
    2014-10-22 12:19:30:431 1428 dae0 Agent   * Online = No; Ignore download priority = No
    2014-10-22 12:19:30:431 1428 dae0 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1
    or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2014-10-22 12:19:30:431 1428 dae0 Agent   * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
    2014-10-22 12:19:30:431 1428 dae0 Agent   * Search Scope = {Machine & All Users}
    2014-10-22 12:19:30:431 1428 dae0 Agent   * Caller SID for Applicability: S-1-5-18
    2014-10-22 12:19:30:494 1428 dae0 Agent   * Found 0 updates and 0 categories in search; evaluated appl. rules of 0 out of 0 deployed entities
    2014-10-22 12:19:30:494 1428 dae0 Agent *********
    2014-10-22 12:19:30:494 1428 dae0 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-10-22 12:19:30:494 1428 dae0 Agent *************
    2014-10-22 12:19:30:509 1428 d158 AU >>##  RESUMED  ## AU: Search for updates [CallId = {2787252C-D4B8-46B5-BB42-0C616042113C} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
    2014-10-22 12:19:30:509 1428 d158 AU   # 0 updates detected
    2014-10-22 12:19:30:509 1428 d158 AU #########
    2014-10-22 12:19:30:509 1428 d158 AU ##  END  ##  AU: Search for updates  [CallId = {2787252C-D4B8-46B5-BB42-0C616042113C} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
    2014-10-22 12:19:30:509 1428 d158 AU #############
    2014-10-22 12:19:30:509 1428 d158 AU All AU searches complete.
    2014-10-22 12:19:30:525 1428 e584 AU #############
    2014-10-22 12:19:30:525 1428 e584 AU ## START ##  AU: Search for updates
    2014-10-22 12:19:30:525 1428 e584 AU #########
    2014-10-22 12:19:30:525 1428 e584 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Pre-install notify} added to AU services list
    2014-10-22 12:19:30:525 1428 e584 Agent SkipSelfUpdateCheck search flag set for serverId: 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782
    2014-10-22 12:19:30:525 1428 e584 AU <<## SUBMITTED ## AU: Search for updates  [CallId = {A3E41A4C-E9CB-4172-B6B0-99D556FB9102} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
    2014-10-22 12:19:30:525 1428 dae0 Agent *************
    2014-10-22 12:19:30:525 1428 dae0 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-10-22 12:19:30:525 1428 dae0 Agent *********
    2014-10-22 12:19:30:525 1428 dae0 Agent   * Online = Yes; Ignore download priority = No
    2014-10-22 12:19:30:525 1428 dae0 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1
    or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2014-10-22 12:19:30:525 1428 dae0 Agent   * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
    2014-10-22 12:19:30:525 1428 dae0 Agent   * Search Scope = {Machine & All Users}
    2014-10-22 12:19:30:525 1428 dae0 Agent   * Caller SID for Applicability: S-1-5-18
    2014-10-22 12:19:30:525 1428 dae0 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
    2014-10-22 12:19:30:541 1428 dae0 Misc  Microsoft signed: Yes
    2014-10-22 12:19:30:541 1428 dae0 Misc  Infrastructure signed: Yes
    2014-10-22 12:19:30:556 1428 dae0 EP Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL: "http://fe2.ws.microsoft.com/w81/2/redir/v2-storeauth.cab"
    2014-10-22 12:19:30:588 1428 dae0 Agent Checking for updated auth cab for service 117cab2d-82b1-4b5a-a08c-4d62dbee7782 at
    http://fe2.ws.microsoft.com/w81/2/redir/v2-storeauth.cab
    2014-10-22 12:19:30:588 1428 dae0 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\AuthCabs\Downloaded\117cab2d-82b1-4b5a-a08c-4d62dbee7782.cab:
    2014-10-22 12:19:30:603 1428 dae0 Misc  Microsoft signed: Yes
    2014-10-22 12:19:30:603 1428 dae0 Misc  Infrastructure signed: Yes
    2014-10-22 12:19:30:775 1428 dae0 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\AuthCabs\Downloaded\117cab2d-82b1-4b5a-a08c-4d62dbee7782.cab:
    2014-10-22 12:19:30:791 1428 dae0 Misc  Microsoft signed: Yes
    2014-10-22 12:19:30:791 1428 dae0 Misc  Infrastructure signed: Yes
    2014-10-22 12:19:30:791 1428 dae0 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\WuRedir\117CAB2D-82B1-4B5A-A08C-4D62DBEE7782\wuredir.cab:
    2014-10-22 12:19:30:806 1428 dae0 Misc  Microsoft signed: Yes
    2014-10-22 12:19:30:806 1428 dae0 Misc  Infrastructure signed: Yes
    2014-10-22 12:19:30:822 1428 dae0 EP Got 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 redir Client/Server URL: "https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx"
    2014-10-22 12:19:30:978 1428 dae0 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2014-10-22 12:19:30:978 1428 dae0 PT   + ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}, Server URL =
    https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx
    2014-10-22 12:19:31:025 1428 dae0 Agent   * Found 0 updates and 0 categories in search; evaluated appl. rules of 0 out of 0 deployed entities
    2014-10-22 12:19:31:025 1428 dae0 Agent *********
    2014-10-22 12:19:31:025 1428 dae0 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-10-22 12:19:31:025 1428 dae0 Agent *************
    2014-10-22 12:19:31:025 1428 d158 AU >>##  RESUMED  ## AU: Search for updates [CallId = {A3E41A4C-E9CB-4172-B6B0-99D556FB9102} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
    2014-10-22 12:19:31:025 1428 d158 AU   # 0 updates detected
    2014-10-22 12:19:31:025 1428 d158 AU #########
    2014-10-22 12:19:31:025 1428 d158 AU ##  END  ##  AU: Search for updates  [CallId = {A3E41A4C-E9CB-4172-B6B0-99D556FB9102} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
    2014-10-22 12:19:31:025 1428 d158 AU #############
    2014-10-22 12:19:31:025 1428 d158 AU All AU searches complete.
    2014-10-22 12:19:31:025 1428 d158 AU AU setting next detection timeout to 2014-10-23 14:19:28
    2014-10-22 12:19:36:025 1428 e214 Report REPORT EVENT: {E04012FD-8FFD-4259-96D5-A5A34127F0A0} 2014-10-22 12:19:31:025-0400 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
    Synchronization Windows Update Client successfully detected 0 updates.
    2014-10-22 12:19:36:025 1428 e214 Report CWERReporter finishing event handling. (00000000)
    2014-10-22 12:29:29:914 1428 e584 AU AU invoking RebootSystem (OnRebootNow)
    2014-10-22 12:29:30:055 1428 e584 AU Allowing auto firmware installs at next shutdown
    2014-10-22 12:29:30:102 1428 e584 Misc WARNING: SUS Client is rebooting system.
    2014-10-22 12:29:30:102 1428 e584 AU AU invoking RebootSystem (OnRebootRetry)
    2014-10-22 12:29:30:367 1428 e584 Shutdwn Checking to see whether install at shutdown is appropriate
    2014-10-22 12:29:30:367 1428 e584 Shutdwn user declined update at shutdown
    2014-10-22 12:29:30:367 1428 e584 AU AU initiates service shutdown
    2014-10-22 12:29:30:367 1428 e584 AU ###########  AU: Uninitializing Automatic Updates  ###########
    2014-10-22 12:29:30:399 1428 e584 WuTask Uninit WU Task Manager
    2014-10-22 12:29:30:445 1428 e584 Agent Sending shutdown notification to client
    2014-10-22 12:29:30:445 5788 8084 COMAPI WARNING: Received service shutdown/self-update notification.
    2014-10-22 12:29:30:461 1428 e584 Report CWERReporter finishing event handling. (00000000)
    2014-10-22 12:29:30:539 1428 e584 Service *********
    2014-10-22 12:29:30:539 1428 e584 Service **  END  **  Service: Service exit [Exit code = 0x240001]
    2014-10-22 12:29:30:539 1428 e584 Service *************
    Any assistance is appreciated.
    -Tim

    Hi,
    Any update?
    Best Regards,
    Joyce
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • SCCM - software updates deployment.

    Hi All,
    i have adobe acrobat version 10.1.10 installed on my mahcine, when ever i am trying to up deploy an Adobe acrobat 10.1.13 for my machine using but its not gettin updated. Also , one thing that i have seen is even after deployment it is not showing up under
    deployment package.
    Can anyone help on this, Iam using shavlik higher version of SCUP with SCCM to achieve this.
    Rsg,

    Hi,
    You could troubleshoot software updates deployment by checking logs.
    UpdatesDeployment.log
    UpdatesHandler.log
    WUAHandler.log
    %windir%\WindowsUpdate.log
    For more information:https://technet.microsoft.com/en-us/library/hh427342.aspx#BKMK_SU_NAPLog
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Software Updates Deployment Evaluation.

    Hi,
    I would like to get some clarification around the Software Updates Deployment Eval. cycle. (SCCM R2 CU3)
    Example scenario:
    I have a Software Update Group that contains 200 updates. This SUG includes updates that are prerequisites for other updates in the same SUG. So, when scanning occurs. Only one of these updates are at that particular time considered applicable.
    The software update deployment deadline is reached. The update is installed, as expected. The then agent reports  compliance against the update deployment.
    Then comes the Software Update Scan schedule, when a new scan is made against the SUP more updates are now detected as required because of the previously installed update - from the same SUG which are deployed.
    This leaves me in a situation where the agent is compliant against the Software Update deployment and non-compliant in regards to the actual Software Update Group. 
    I can of course just hit the schedule for Software Update Deployment Evaluation manually on the agent or simply do something (adding an update or whatever) that modifies the actual software updates deployment policy. This would in turn cause a new evaluation
    to occur at the client.
    Bottom line. Is my conclusion correct or have i missed something here? 
    If i'm correct, a good thing would be to add scheduling options available for the actual "software update deployment evaluation".
    That would really come in handy in situations like above scenario. 
    Br,
    Chris

    The next scheduled scan cycle will pick up the newly applicable but non-compliant updates in the deployment.
    However, note that update compliance at the client level is done against the entire update catalog as this is actually done by the Windows Update Agent (WUA) which knows nothing about ConfigMgr. Thus, the fact that an update is in a deployment or not is
    completely irrelevant as far as compliance and compliance reporting goes (which is part of the reason why compliance reporting in ConfigMgr is tricky).
    Updating the policy of an update deployment will kick off a scan cycle (just like creating a new deployment will) on the clients which is why you are probably seeing this behavior as addressing the scenario.
    Jason | http://blog.configmgrftw.com | @jasonsandys
    Thanks Jason,
    What you are describing exactly matches the point I’m trying to make here. There is no correlation what so ever between update scans and actual software update deployments. The logic just isn't there. Which is a logic that is lacking
    – in my opinion.
    I really do think there is room for improvement here.
    Case:
    A customer wants to minimize the spread of reboots (a maint. window overnight should be sufficient for the agent to get the server fully up to date). The admin – who also wants to minimize effort in regards to worrying about MS bundling\prereq
    requirements – simply wants it all to be taken care of by the updates deployment agent.
    Example:
    Software update deployment contains required updates as well as updates that will not be detected as required - until the deployment has been run – and a new update scan cycle has taken place.
    The server reboots and updates deployment agent says all is fine – with regards to the deployment in it's current state, of course.
    But it's not.
    The server then issues a new scan (maybe 4 hours later and way behind the end of the maint. window) according to the software updates scan schedule, and suddenly 10 more updates are applicable, but still within the same deployment.
    What happens? Nothing, sadly. Next maint. window? Nothing.
    Not even a (client agent set – and scheduled) software update deployment re-eval takes care of this since – according to my findings – the deployment will never really be evaluated against again without administrative intervention.
    Suggestion:
    Whenever a software update deployment has been run, succeeded and passed the "after reboot" detectjob. Initiate a new evaluation of this deployment in full – of course including a pre-eval software updates scan. Just add
    a few steps to the logic of updates deployment.
    Evaluate.
    Apply.
    Initiate a new scan.
    Re-Evaluate.
    Apply again (if needed)
    Reboot
    Initiate a new scan.
    Re-evaluate
    Isn’t this the way WAUA has always worked? Why shouldn’t this method be adopted here as well? Why should ConfigMgr not honour the procedure?
    Result:
    Administrative relieve. Since I know that a software update deployment will always do the job, in full. No need for manual triggers or policy modifications.
    Caveats:
    I do realize the fact that – if this would be the scenario - the admin sometimes will not be aware of what might happen during the nightly maint. window since he cannot solely rely on compliance data.
    Anyways:
    This should at least be a deployment option in future releases.
    "Force rescan and deployment re-evaluation after first run." Simple.
    Would make life easier and keep the spread of reboots concentrated to one night and to a minimum. (Given the appropriate length of maint. windows of course)
    Consider things like KB2919355 and how WUAU agent handles that against Windows Update.
    Br,
    Chris

  • How to find who modified Software Update deployment in sccm 2012

    Hi,
    How to find who modified(Date & Time) software update deployment in SCCM 2012 ?

    In the Console :
    Monitoring / System Status / Status Message Query
    Right Click : "Deployments Created, Modified, or Deleted" - Show Message and select your period.
    You'll have your information there.
    Benoit Lecours | Blog: System Center Dudes

  • Why is the software update not showing up in general settings?

    Why does my software update not show up in general settings?

    If you have an iPad 1, the max iOS is 5.1.1. For newer iPads, the current iOS is 7.1.1. The Settings>General>Software Update only appears if you have iOS 5.0 or higher currently installed.
    You can no longer update to iOS 6.x, or down grade the iOS.
    iOS 5: Updating your device to iOS 5 or Later
    http://support.apple.com/kb/HT4972
    How to install iOS 6
    http://www.macworld.com/article/2010061/hands-on-with-ios-6-installation.html
    iOS: How to update your iPhone, iPad, or iPod touch
    http://support.apple.com/kb/HT4623
    If you are currently running an iOS lower than 5.0, connect the iPad to the computer, open iTunes. Then select the iPad under the Devices heading on the left, click on the Summary tab and then click on Check for Update.
    Tip - If connected to your computer, you may need to disable your firewall and antivirus software temporarily.  Then download and install the iOS update. Be sure and backup your iPad before the iOS update. After you update an iPad (except iPad 1) to iOS 7.x, the next update can be installed via wifi (i.e., not connected to your computer).
    Tip 2 - If you're updating via wifi, place your iPad close to your router to preclude getting a corrupted download.
    How to Upgrade to iOS 7
    The iOS 7.0 update requires around 2.5 GB of storage space, so if your iPad is almost full, you may need to clear up some space. You can check your available space in Settings -> General -> Usage.
    There are two ways to upgrade to iOS 7: You can use your Wi-Fi connection, or you can connect your iPad to your PC and update through iTunes. We'll go over each method.
    To upgrade using Wi-Fi:
    Note: If your iPad's battery is under 50%, you will want to plug it into your charger while performing the update.
    Go into the iPad's Settings.
    Locate and tap "General" from the menu on the left.
    The second option from the top is "Software Update". Tap this to move into the update settings.
    Tap "Download and Install". This will start the upgrade, which will take several minutes and will reboot your iPad during the process. If the Download and Install button is grayed out, trying clearing up some space. The space required by the update is mostly temporary, so you should gain most of it back after iOS 7 is installed.
    Once the update is installed, you may have to run through the initial steps of setting up your iPad again. This is to account for new features and settings.
    To upgrade using iTunes:
    First, connect your iPad to your PC or Mac using the cable provided when you purchased your device. This will allow iTunes to communicate with your iPad.
    You will also need the latest version of iTunes. Don't worry, you will be prompted to download the latest version when you launch iTunes. Once it installs, you may be asked to setup iCloud by logging into your iTunes account. If you have a Mac, you may be prompted on whether or not you want to enable the Find my Mac feature.
    Now you are ready to begin the process:
    If you upgraded iTunes earlier, go ahead and launch it. (For many, it will launch automatically when you plug in your iPad.)
    Once iTunes is launched, it should automatically detect that a new version of the operating system exists and prompt you to upgrade to it. Choose Cancel. Before updating, you will want to manually sync your iPad to make sure everything is up to date.
    After canceling the dialog box, iTunes should automatically sync with your iPad.
    If iTunes doesn't automatically sync, you can manually do it by selecting your iPad within iTunes, clicking on the File menu and choosing Sync iPad from the list.
    After your iPad has been synced to iTunes, select your iPad within iTunes. You can find it on the left side menu under Devices.
    From the iPad screen, click on the Update button.
    After verifying that you want to update your iPad, the process will begin. It takes a few minutes to update the operating system during which time your iPad may reboot a few times.
    After updating, you may be asked a few questions when your device finally boots back up. This is to account for new settings and features.
     Cheers, Tom

  • How to troubleshoot Software Update Deployment Errors

    Hi Guys,
    Could you guys please help me to troubleshoot 'Software Update Deployment Errors'. I have been trying to troubleshoot the below mentioned errors but I am not sure what step should I take for each different errors.
    Could you guys please help me stating what kind of troubleshooting steps should we take for such update deployment errors.
    Many Thanks,
    Chandan

    You would have to examine client-side logs like UpdatesDeployment.log, U*.log in general, ScanAgent.log, WUAHandler.log, WindowsUpdate.log and CI*.log.
    Torsten Meringer | http://www.mssccmfaq.de

  • Change Software Updates deployment priority

    Hi
    We use SCCM 2012 R2 CU2.
    whenever a new client is being installed and registered it gets its policies and deployments.
    our problem is that there are many software updates that being deployed and it takes a very long time until they finish their installation.
    while what is more important for us is the clients to get software deployments
    before the software updates.
    I know I can change packages priority but as I understand - it only changes the priority between the software packages.
    is there any way to make the software deployments to be installed before the software updates for new clients?
    even if there's no build-in solution, I'd be happy to get a friendly workaround.
    I thought about auto-adding the clients to a software update deployment collection only after all the packages are being deployed, but maybe some of you can come up with something better
    thanks!

    You can't prioritize in policy for a client. The first policy that arrives is the first that's being served..
    If you're talking about the first thing after the OS deployment, then I would try to update my clients completely during the deployment already. That would solve your problem already. In that same scenario, you could also think about installing
    computer or user targetted applications during the task sequence. For examples about both scenario's see:
    Computer-targeted:
    http://www.petervanderwoude.nl/post/install-computer-targeted-application-during-os-deployment-via-powershell-and-configmgr-2012/;
    User-targeted:
    http://www.petervanderwoude.nl/post/install-user-targeted-applications-during-os-deployment-via-powershell-and-configmgr-2012/.
    If you're not talking about an OS deployment, your only option is indeed to add the clients later to the software update collection(s). In that case you could also try to automate it via PowerShell by using the
    Add-CMDeviceCollectionDirectMembershipRule.
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • HT5052 when ever i download an update i.e,iOS 5.0.1 Software Update it shows an error so pls help me or guide through it.....

    when ever i download an update i.e,iOS 5.0.1 Software Update it shows an error so pls help me or guide through it.....the error shown is-3676 timed out

    Most likely computer Anti-Virus and or computer Fire-Wall is interferring with the download of the Firmware. Turn them OFF, so your computer can download the Firmware.

  • TS3694 sirmy iphone 3G was not on due to software update and its not resotre previous software and shown as error 1051 kindly resolve my issue as soon as possible

    sir my iphone 3G was not on due to software update and its not resotre previous software and shown as error 1051 kindly resolve my issue as soon as possible

    The easiest way to fix the hosts file is to restore it from a backup that predates the modification, or to copy the unmodified file from another Mac. If you can't do that, then do as below.
    Triple-click anywhere in the line below on this page to select it:
    open -e /etc/hosts
    Copy the selected text to the Clipboard by pressing the key combination command-C.
    Paste into a Terminal window by pressing command-V. A TextEdit window should open. At the top of the window, you should see this:
    # Host Database
    # localhost is used to configure the loopback interface
    # when the system is booting.  Do not change this entry.
    127.0.0.1                              localhost
    255.255.255.255          broadcasthost
    ::1                                        localhost
    Below that, you may see some other lines. The first 9 lines should be exactly as above, apart from differences in the blank space within lines. Otherwise you can't use this procedure—STOP and ask for guidance.
    If the contents of the TextEdit window are as described, close it, then enter the following command in the Terminal window in the same way as before (by copy and paste):
    sudo sed -i~ '10,$d' /etc/hosts
    You may be prompted for your login password, which won't be displayed when you type it. Type carefully and then press return. If you don’t have a login password, you’ll need to set one before you can run the command. You may get a one-time warning to be careful. Confirm. Quit Terminal.
    If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator. Log in as one and start over.
    That will fix the hosts file. There is now a copy of the old hosts file with the name "hosts~" in the same folder as "hosts". You can delete the copy if you wish. Don't delete the file named "hosts".

  • Anyone come across error 11 while trying to synch or update an IPhone 3GS that previously had not problems synching?  Have reinstalled ITunes but to no avail...?

    anyone come across error 11 while trying to synch or update an IPhone 3GS that previously had not problems synching?  Have reinstalled ITunes but to no avail...?

    Seems that way. I think I am going to have to give in and spend hours on the phone with Apple support. I don't want to, but I am at a loss. I will share any discoveries...

  • Can windows 8 be upgraded to 8.1 through CM 2012 Software Updates deployment?

    Hi,
    Can windows 8 be upgraded to 8.1 through CM 2012 Software Updates deployment rather than having it downloaded through Windows Store?

    The update is not available via software updates. However, if you are doing multiple updates, you can bypass the Windows Store.
    http://www.petri.co.il/upgrade-to-windows-8-1-without-windows-store.htm#
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • Orphaned software update deployment on child site management point

    Hi
    It would appear that we have an orphaned software update deployment still active on our child site management point but is obviously locked due to it's creation on the primary site. It was deleted from the primary site along with package from the DPs
    and these are no longer present. The issue is that the deployment is still active and clients are pulling the selected software updates from it although they are not getting them as they are no longer on the DPs.
    I know that you can take ownership of orphaned packages from the database but can this be done on Software Update deployments?
    If anyone has experienced this issue or knows of a resolve I would be greatly appreciated
    Thanks in advance

    Hi
    It would appear that we have an orphaned software update deployment still active on our child site management point but is obviously locked due to it's creation on the primary site. It was deleted from the primary site along with package from the DPs
    and these are no longer present. The issue is that the deployment is still active and clients are pulling the selected software updates from it although they are not getting them as they are no longer on the DPs.
    I know that you can take ownership of orphaned packages from the database but can this be done on Software Update deployments?
    If anyone has experienced this issue or knows of a resolve I would be greatly appreciated
    Thanks in advance

  • Windows Updates showing Unknown computers

    Hi,
    I am deploying Windows Updates and the Statistics window shows a high number of 'Unknown' computers, how do I find out these machines and what is the best method to have this number as close to zero as possible?
    In the Software Library > Software Updates > Software Update Groups pane the statistics are as below for Windows 7 Updates:

    Hi,
    We could get those machines which shows unknown from reports. Then troubleshoot the process for the software update group installation and the state messages sent to MP on some specific machines.
    Best Regards,
    Joyce Li
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

Maybe you are looking for