Jump to content


OffColour

Established Members
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About OffColour

  • Rank
    Member
  1. Hi, OK, so we have have some laptops in a multilingual office. They're already out there so I'm not bringing them in for a rebuild. As an example, a PC has language option set to English (United Kingdom). I want a French user to be able to log on, add French in the Language Control panel and download the Language pack. With straight WSUS, this worked as I could approve the pack and Language would display it as available. With SCCM I've tried creating a deploying a package with the needed language packs in the hope that once it was available, the Language panel would now find it available to download. Not working though and it stubbornly stays as "A language pack isn't available" and the SCCM deployment says the PC is compliant. Anyone else achieved this? I've found lots on deployment during OSD, but nothing about deploying afterwards. Thanks
  2. In the Source folder for the package it contains both the x32 and x64 upgrades. As we don't have any x32 installs, do you know of any way of only downloading x64 to avoid wasting disk space?
  3. To finally return to this ggallaway was right, though I went through a bit of a learning process to track down why he was right and why that one on its own wasn't sufficient burg3rmak3r, here's what to do: Turn on verbose logging for WSUS on a client PC http://support.microsoft.com/kb/2545723#letmefixit2 Check for updates Open c:\windows\windowsupdate.log Search for the word "cycle" Get the update ID that has the circuclar reference Find that update in SCUP and expire it (you may want to fix it, but I didn't bother as I don't need the affected updates) Publish the update again Go back to step 2 and keep repeating until Windows Update on the client PC works (I had about 8 with circular references) Turn off verbose logging
  4. Uninstalled and reinstalled WSUS and it started working again, BUT... Published a whole raft of Dell updates from SCUP 2011 and it broke it again. Removed and reinstalled WSUS again. Worked fine Publish the Dell updates again, broke it. Needs more looking at in a lab environment I think.
  5. And here's the full round trip from windowsupdate.log on a Win 8.1 machine 2014-04-04 10:10:45:495 600 2d7c AU Triggering AU detection through DetectNow API 2014-04-04 10:10:45:495 600 2d7c AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Scheduled} added to AU services list 2014-04-04 10:10:45:495 600 2d7c AU Triggering Online detection (interactive) 2014-04-04 10:10:45:496 600 86c AU ############# 2014-04-04 10:10:45:496 600 86c AU ## START ## AU: Search for updates 2014-04-04 10:10:45:496 600 86c AU ######### 2014-04-04 10:10:45:496 600 86c AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Scheduled} added to AU services list 2014-04-04 10:10:45:497 600 86c IdleTmr WU operation (CSearchCall::Init ID 3) started; operation # 116; does use network; is not at background priority 2014-04-04 10:10:45:497 600 86c IdleTmr Incremented PDC RefCount for Network to 1 2014-04-04 10:10:45:497 600 86c IdleTmr Incremented idle timer priority operation counter to 2 2014-04-04 10:10:45:497 600 86c Agent *** START *** Queueing Finding updates [CallerId = AutomaticUpdatesWuApp Id = 3] 2014-04-04 10:10:45:497 600 86c AU <<## SUBMITTED ## AU: Search for updates [CallId = {2165098D-B789-4407-840E-CB8AE6C96545} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}] 2014-04-04 10:10:45:497 600 1ef4 Agent *** END *** Queueing Finding updates [CallerId = AutomaticUpdatesWuApp Id = 3] 2014-04-04 10:10:45:498 600 1ef4 Agent ************* 2014-04-04 10:10:45:498 600 1ef4 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdatesWuApp Id = 3] 2014-04-04 10:10:45:498 600 1ef4 Agent ********* 2014-04-04 10:10:45:498 600 1ef4 Agent * Online = Yes; Ignore download priority = No 2014-04-04 10:10:45:498 600 1ef4 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-04-04 10:10:45:498 600 1ef4 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed 2014-04-04 10:10:45:498 600 1ef4 Agent * Search Scope = {Machine & All Users} 2014-04-04 10:10:45:498 600 1ef4 Agent * Caller SID for Applicability: S-1-5-21-1977413048-354180104-3005836590-3731 2014-04-04 10:10:45:498 600 1ef4 EP Got WSUS Client/Server URL: "http://wsusserver:8530/ClientWebService/client.asmx" 2014-04-04 10:10:45:499 600 1ef4 Setup Checking for agent SelfUpdate 2014-04-04 10:10:45:500 600 1ef4 Setup Client version: Core: 7.9.9600.16422 Aux: 7.9.9600.16384 2014-04-04 10:10:45:500 600 1ef4 EP Got WSUS SelfUpdate URL: "http://wsusserver:8530/selfupdate" 2014-04-04 10:10:45:507 600 1ef4 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\wuident.cab: 2014-04-04 10:10:45:516 600 1ef4 Misc Microsoft signed: Yes 2014-04-04 10:10:45:516 600 1ef4 Misc Infrastructure signed: Yes 2014-04-04 10:10:45:516 600 1ef4 Misc WARNING: Cab does not contain correct inner CAB file. 2014-04-04 10:10:45:516 600 1ef4 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\wuident.cab: 2014-04-04 10:10:45:520 600 1ef4 Misc Microsoft signed: Yes 2014-04-04 10:10:45:520 600 1ef4 Misc Infrastructure signed: Yes 2014-04-04 10:10:45:522 600 1ef4 Setup Wuident for the managed service is valid but not quorum-signed. Skipping selfupdate. 2014-04-04 10:10:45:522 600 1ef4 Setup Skipping SelfUpdate check based on the /SKIP directive in wuident 2014-04-04 10:10:45:522 600 1ef4 Setup SelfUpdate check completed. SelfUpdate is NOT required. 2014-04-04 10:10:46:271 600 1ef4 PT +++++++++++ PT: Synchronizing server updates +++++++++++ 2014-04-04 10:10:46:271 600 1ef4 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsusserver:8530/ClientWebService/client.asmx LOTS OF THESE 2014-04-04 10:10:46:296 600 1ef4 Agent WARNING: Failed to evaluate Installed rule, updateId = {{19B34AFF-FC79-4853-ACB8-363B63EF0D98}.1}, hr = 8004100E 2014-04-04 10:10:47:192 600 1ef4 PT + SyncUpdates round trips: 2 LOTS OF THESE AGAIN 2014-04-04 10:10:47:365 600 1ef4 Agent WARNING: Failed to evaluate Installable rule, updateId = {{100C8845-509B-4DA3-9810-D833D694D0AE}.2}, hr = 8004100E 2014-04-04 10:10:47:368 600 1ef4 Agent * WARNING: Exit code = 0x8024000F 2014-04-04 10:10:47:368 600 1ef4 Agent ********* 2014-04-04 10:10:47:368 600 1ef4 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdatesWuApp Id = 3] 2014-04-04 10:10:47:368 600 1ef4 Agent ************* 2014-04-04 10:10:47:368 600 1ef4 Agent WARNING: WU client failed Searching for update with error 0x8024000f 2014-04-04 10:10:47:368 600 1ef4 IdleTmr WU operation (CSearchCall::Init ID 3, operation # 116) stopped; does use network; is not at background priority 2014-04-04 10:10:47:368 600 1ef4 IdleTmr Decremented PDC RefCount for Network to 0 2014-04-04 10:10:47:368 600 1ef4 IdleTmr Decremented idle timer priority operation counter to 1 2014-04-04 10:10:47:368 600 2f68 AU >>## RESUMED ## AU: Search for updates [CallId = {2165098D-B789-4407-840E-CB8AE6C96545} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}] 2014-04-04 10:10:47:368 600 2f68 AU # WARNING: Search callback failed, result = 0x8024000F 2014-04-04 10:10:47:368 600 2f68 AU ######### 2014-04-04 10:10:47:368 600 2f68 AU ## END ## AU: Search for updates [CallId = {2165098D-B789-4407-840E-CB8AE6C96545} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}] 2014-04-04 10:10:47:368 600 2f68 AU ############# 2014-04-04 10:10:47:368 600 2f68 AU All AU searches complete. 2014-04-04 10:10:47:368 600 2f68 AU # WARNING: Failed to find updates with error code 8024000f 2014-04-04 10:10:47:369 600 2f68 AU AU setting next detection timeout to 2014-04-04 14:10:47 2014-04-04 10:10:47:369 600 2f68 AU # Publishing WNF Per user update count event Count: 0 SID {S-1-5-21-1977413048-354180104-3005836590-3731} Service {7971F918-A847-4430-9279-4A52D1EFE18D} 2014-04-04 10:10:47:369 600 2f68 AU # Publishing WNF Per user update count event Count: 0 SID {S-1-5-21-1977413048-354180104-3005836590-3731} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} 2014-04-04 10:10:47:369 600 2f68 AU # Publishing WNF Per user update count event Count: 0 SID {S-1-5-21-1977413048-354180104-3005836590-3731} Service {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 2014-04-04 10:10:47:369 600 2f68 AU # Publishing WNF Per user update count event Count: 0 SID {S-1-5-21-1977413048-354180104-3005836590-5151} Service {7971F918-A847-4430-9279-4A52D1EFE18D} 2014-04-04 10:10:47:369 600 2f68 AU # Publishing WNF Per user update count event Count: 16 SID {S-1-5-21-1977413048-354180104-3005836590-5151} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} 2014-04-04 10:10:47:369 600 2f68 AU # Publishing WNF Per user update count event Count: 0 SID {S-1-5-21-1977413048-354180104-3005836590-5151} Service {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 2014-04-04 10:10:47:369 600 2f68 AU # Publishing WNF Per user update count event Count: 0 SID {S-1-5-21-869182815-1892558573-2371667495-1004} Service {7971F918-A847-4430-9279-4A52D1EFE18D} 2014-04-04 10:10:47:369 600 2f68 AU # Publishing WNF Per user update count event Count: 17 SID {S-1-5-21-869182815-1892558573-2371667495-1004} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} 2014-04-04 10:10:47:369 600 2f68 AU # Publishing WNF Per user update count event Count: 0 SID {S-1-5-21-869182815-1892558573-2371667495-1004} Service {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
  6. Hi, Urgent help required and appreciated! All my SCCM 2012 R2 clients (win 7, 8 and 8.1) have started failing to update from local WSUS. Local SoftwareDistribution Reportingevents.log are full of the following: {6EE47857-6A6C-4A23-9849-B0F1670EB1F9} 2014-04-03 17:25:39:032+0100 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 8024000f CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x8024000f. If I check for updates directly from Microsoft I get: {FEDA559A-A4F5-4F9D-85A0-B6EA03DF2F3D} 2014-04-03 17:48:55:820+0100 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdatesWuApp Success Software Synchronization Windows Update Client successfully detected 18 updates. I can't see anything obvious that's changed on the WSUS server. GPO is set correctly for http://WSUSServer:8530. Browsing to that address resolves with access denied. I've tried reboots and wsus reset, WSUS and SCCM are on the same Win Server 2012 R2 machine. SCUP 2011 also pushes Dell updates to WSUS. Thanks Gary
  7. Thanks, but haven't got the time or manpower to do that, so think I'll just go with getting everything released in the past month.
  8. No, I'm fine with that and that's what I've done. An example June 12th Patch Tuesday (ADR picks up changes) June 30th MS release a critical patch out of cycle (No ADR job to pick this up) July 12th Patch Tuesday (ADR picks up change) How would we pick up the June 30th release?
  9. Hi, Great guides. Saved me a painful learning curve! Thanks. Back to the patch Tuesday up dates and only getting the last day. Perfectly fine with what that's doing and just picking up the patch tuesday releases. My question goes back to what was asked before: If MS release a patch between the patch Tuesdays, how do we pick that one up? As far as I can tell, just doing last day would miss those. What would you recommend to ensure no patches are missed?
×
×
  • Create New...