SCCM 2012 R2 - Software Update Point

I have two domains, one where the site server (SCCM) will be installed home office, and then another untrusted domain Management. This server will have site roles, SUP, and some others.
I want to create a site system server with DP, MP in the untrusted domain. In order to push out updates to clients in the untrusted domain, what do I need, in the untrusted domain, to make this work.

Hi,
For the SUP in the untrusted domain the SCCM Site Server you need the proper patch level of the installed WSUS, the correct ports open on Firewall and an account from the Domain where the SCCM Site is installed which has rights on the WSUS on the primary
site. This account has to be configured during the installation of the SUP on the Site System Server.
May this post also give you some hints:
http://social.technet.microsoft.com/Forums/en-US/c3fbf3ab-ca70-48da-90b1-e7322783140c/sup-in-untrusted-forest-using-sccm-2012-sp1?forum=configmanagerdeployment
Cheers
Christoph
PS: Could somebody please move this thread to the correct Configuration Manager Forum :)

Similar Messages

SCCM 2012: configure software update point

Hi,
I installed WSUS, installed the software update point on Windows 2012 (for SCCM 2012) with following commands:
Install-WindowsFeature -Name UpdateServices -IncludeManagementTools
cd 'C:\Program Files\Update Services\Tools\'
.\wsusutil.exe postinstall CONTENT_DIR=E:\WSUS
Add-CMSoftwareUpdatePoint -SiteCode "PRD" -SiteSystemServerName "CM01.contoso.com" -ClientConnectionType Intranet -WsusiisPort 8530 -WsusiissslPort 8531
Now I'm stuck. How do I configure the specific update (f.e. Windows 2012, forefront etc), download them to a certain folder?
Please advise.
J.
Jan Hoedt

It really isn't practical (or possible) to try to do an entire ConfigMgr implementation using PowerShell. I don't believe that you can choose your products using PoSH.
You will find a full list of cmdlets here
http://technet.microsoft.com/en-us/library/jj821831(v=sc.20).aspx
The following cmdlets are available to configure your software update infrastructure but I'm pretty sure none of them will help you with this.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

[SCCM 2012 R2] How SCCM 2012 handles Software Update Revisions?

Hi All,
There are a lot of questions regarding how SCCM 2012 handles Software Update Revisions.
Does anyone know what happened if:
Windows update publish some update with revision #1
Same update downloaded and deployed via SCCM 2012
Windows update publish same update with revision #2 or any newer revision
What is happening with SCCM and already deployed and downloaded revision? How should I know what revision is really on my distribution points?
Thank you in advance.
Regards,

In WSUS Revision History is very simple:
Where I can find revision history in SCCM??? (please do not mention dates):
Possible scenario in SCCM:
Windows update publish revision #1 for one update
SCCM Download and Deploy same update and revision #1
Windows update change revision to #2
What SCCM does after this scenario?
Auto update Distribution Points with new revision of already deployed and downloaded update?
Clearly state in SCCM Console that there is new revision of already deployed and downloaded update and waiting for admin to act?
Just update the revision in SCCM Console and leave old revision od Distribution Points?????

Sccm 2012 R2 Software update problem

Hi,
I have 3 ADR's ADRWin7-1, ADRWin7-2 and ADRWin7-3
All three Run on Second tuesday of the month and has common Package. All three ADR's create a new group every time they run.
Schedule :
ADRWin7-1 Deployes patches to Phase1 collection on 2nd Tuesday
ADRWin7-2 Deployes Patches to Phase2 collection after 7 days of 2nd Tuesday
ADRWin7-3 Deployes Patches to Phase3 collection after 14 days of 2nd Tuesday.
Problem :
ADRWin7-1 works fine. PC's in Phase1 gets the patches without any problem. But Phase2 and Phase3 PC's are not getting the patches. I have moved PC from Phase1 to Phase2 collection, same problem. When in Phase1 collection it gets the patches and when moved
to Phase2, it does not.
Not much info from logs : (Sample logs)
WUAHangler.log :
Successfully completed scan. WUAHandler 8/15/2014 5:02:43 PM 1336 (0x0538)
Scan results will include superseded updates only when they are superseded by service packs and definition updates. WUAHandler 8/15/2014 5:02:43 PM 4488 (0x1188)
Search Criteria is ((DeploymentAction=* AND Type='Software' AND CategoryIDs contains 'BFE5B177-A086-47A0-B102-097E4FA1F807')) WUAHandler 8/15/2014 5:02:43 PM 4488 (0x1188)
Async searching of updates using WUAgent started. WUAHandler 8/15/2014 5:02:43 PM 4488 (0x1188)
Async searching completed. WUAHandler 8/15/2014 5:02:55 PM 3708 (0x0E7C)
Successfully completed scan. WUAHandler 8/15/2014 5:02:56 PM 1336 (0x0538)
Scan results will include superseded updates only when they are superseded by service packs and definition updates. WUAHandler 8/15/2014 5:02:57 PM 4548 (0x11C4)
Search Criteria is ((DeploymentAction=* AND Type='Software' AND CategoryIDs contains 'BFE5B177-A086-47A0-B102-097E4FA1F807')) WUAHandler 8/15/2014 5:02:57 PM 4548 (0x11C4)
Async searching of updates using WUAgent started. WUAHandler 8/15/2014 5:02:57 PM 4548 (0x11C4)
Async searching completed. WUAHandler 8/15/2014 5:03:04 PM 2608 (0x0A30)
Successfully completed scan. WUAHandler 8/15/2014 5:03:05 PM 968 (0x03C8)
CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3;
for bundles WUAHandler 8/15/2014 5:18:35 PM 4256 (0x10A0)
UpdatesHandler.log
Initiating updates scan for checking applicability. UpdatesHandler 8/15/2014 5:02:22 PM 1336 (0x0538)
Initiating updates scan for checking applicability. UpdatesHandler 8/15/2014 5:02:22 PM 3388 (0x0D3C)
Successfully initiated scan. UpdatesHandler 8/15/2014 5:02:22 PM 1336 (0x0538)
Successfully initiated scan. UpdatesHandler 8/15/2014 5:02:22 PM 3388 (0x0D3C)
Initiating updates scan for checking applicability. UpdatesHandler 8/15/2014 5:02:22 PM 1336 (0x0538)
Successfully initiated scan. UpdatesHandler 8/15/2014 5:02:22 PM 1336 (0x0538)
Initiating updates scan for checking applicability. UpdatesHandler 8/15/2014 5:02:22 PM 1336 (0x0538)
Successfully initiated scan. UpdatesHandler 8/15/2014 5:02:22 PM 1336 (0x0538)
Updates scan completion received, result = 0x0. UpdatesHandler 8/15/2014 5:02:41 PM 3388 (0x0D3C)
Updates scan completion received, result = 0x0. UpdatesHandler 8/15/2014 5:02:42 PM 4488 (0x1188)
Updates scan completion received, result = 0x0. UpdatesHandler 8/15/2014 5:02:43 PM 968 (0x03C8)
Updates scan completion received, result = 0x0. UpdatesHandler 8/15/2014 5:02:57 PM 3388 (0x0D3C)
Updates scan completion received, result = 0x0. UpdatesHandler 8/15/2014 5:03:06 PM 1336 (0x0538)
UpdatesStore.log
Update status from update (f61b102e-ce91-4086-94d0-fb199d7ce5ee) already exists, will modify existing instance. UpdatesStore 8/15/2014 5:03:06 PM 968 (0x03C8)
Update status from update (f6a9dfd6-91f2-449f-aef9-0d7f5f801d03) already exists, will modify existing instance. UpdatesStore 8/15/2014 5:03:06 PM 968 (0x03C8)
Update status from update (f7583494-fffa-4e41-99bc-1e4958f752f9) already exists, will modify existing instance. UpdatesStore 8/15/2014 5:03:06 PM 968 (0x03C8)
Update status from update (f76f5a9c-8325-4256-a632-654f153704b4) already exists, will modify existing instance. UpdatesStore 8/15/2014 5:03:06 PM 968 (0x03C8)
Update status from update (f802bfe3-9553-4542-bd1d-bdca38ff645c) already exists, will modify existing instance. UpdatesStore 8/15/2014 5:03:06 PM 968 (0x03C8)
Update status from update (f90253be-d178-4681-8ca9-71ac186b31f6) already exists, will modify existing instance. UpdatesStore 8/15/2014 5:03:06 PM 968 (0x03C8)
Update status from update (f92c8766-da08-4e0d-841d-1f36d3270cd3) already exists, will modify existing instance. UpdatesStore 8/15/2014 5:03:06 PM 968 (0x03C8)
Update status from update (f9ff6d98-1a01-437e-8728-f29cb8c71b13) already exists, will modify existing instance. UpdatesStore 8/15/2014 5:03:06 PM 968 (0x03C8)
Update status from update (fa090999-3b89-4dd1-82b2-6e16b0841e24) already exists, will modify existing instance. UpdatesStore 8/15/2014 5:03:06 PM 968 (0x03C8)
Update status from update (fbc9a192-a1d6-4008-8ea6-cd497b8b8668) already exists, will modify existing instance. UpdatesStore 8/15/2014 5:03:06 PM 968 (0x03C8)
Update status from update (fc7e731b-f4c9-44af-aaa8-952a614b4a64) already exists, will modify existing instance. UpdatesStore 8/15/2014 5:03:06 PM 968 (0x03C8)
Update status from update (fca3e05e-3bc0-4291-a675-9769042c9594) already exists, will modify existing instance. UpdatesStore 8/15/2014 5:03:06 PM 968 (0x03C8)
Update status from update (fda58512-32f3-4a5d-a5c4-05a193e037d4) already exists, will modify existing instance. UpdatesStore 8/15/2014 5:03:06 PM 968 (0x03C8)
Update status from update (fe2139b2-00f2-4eb3-8b28-d439e762967c) already exists, will modify existing instance. UpdatesStore 8/15/2014 5:03:06 PM 968 (0x03C8)
Update status from update (ff6cd189-1c49-4438-ac4e-34d988330e5f) already exists, will modify existing instance. UpdatesStore 8/15/2014 5:03:06 PM 968 (0x03C8)
Update status from update (ffbb4e7e-0edc-47fe-8c02-65211d2586fb) already exists, will modify existing instance. UpdatesStore 8/15/2014 5:03:06 PM 968 (0x03C8)
Successfully done with SetStatus() operation. UpdatesStore 8/15/2014 5:03:06 PM 968 (0x03C8)
Querying update status of 10 updates. UpdatesStore 8/15/2014 5:03:06 PM 1336 (0x0538)
Querying update status completed successfully. UpdatesStore 8/15/2014 5:03:06 PM 1336 (0x0538)
Querying update status of 14 updates. UpdatesStore 8/15/2014 5:03:06 PM 4548 (0x11C4)
Querying update status completed successfully. UpdatesStore 8/15/2014 5:03:06 PM 4548 (0x11C4)
Querying update status of 22 updates. UpdatesStore 8/15/2014 5:03:06 PM 2372 (0x0944)
Querying update status completed successfully. UpdatesStore 8/15/2014 5:03:06 PM 2372 (0x0944)
Querying update status of 12 updates. UpdatesStore 8/15/2014 5:03:06 PM 4488 (0x1188)
Querying update status completed successfully. UpdatesStore 8/15/2014 5:03:06 PM 4488 (0x1188)
Querying update status of 26 updates. UpdatesStore 8/15/2014 5:03:06 PM 4516 (0x11A4)
Querying update status completed successfully. UpdatesStore 8/15/2014 5:03:06 PM 4516 (0x11A4)
Querying update status of 10 updates. UpdatesStore 8/15/2014 5:03:06 PM 4368 (0x1110)
Querying update status completed successfully. UpdatesStore 8/15/2014 5:03:06 PM 4368 (0x1110)
Querying update status of 12 updates. UpdatesStore 8/15/2014 5:03:06 PM 1984 (0x07C0)
Querying update status completed successfully. UpdatesStore 8/15/2014 5:03:06 PM 1984 (0x07C0)
Querying update status of 1 updates. UpdatesStore 8/15/2014 5:03:06 PM 4296 (0x10C8)
Querying update status completed successfully. UpdatesStore 8/15/2014 5:03:06 PM 4296 (0x10C8)
Querying update status of 10 updates. UpdatesStore 8/15/2014 5:03:07 PM 4516 (0x11A4)
Querying update status completed successfully. UpdatesStore 8/15/2014 5:03:07 PM 4516 (0x11A4)
Windowsupdate.log
2014-08-15 17:03:03:963 924 1024 Agent   * Added update {801E75EC-F4EF-483C-B606-AB930EBF46B3}.202 to search result
2014-08-15 17:03:03:963 924 1024 Agent   * Added update {61BFE3EC-A1DC-4EAB-9481-0D8FD7319AE8}.100 to search result
2014-08-15 17:03:03:963 924 1024 Agent   * Added update {07D8D1ED-1E2A-4696-A20F-9EE6D983B0E6}.100 to search result
2014-08-15 17:03:03:963 924 1024 Agent   * Added update {B0CD9CEE-4C6B-4E2D-B4DA-1F83C4657C18}.104 to search result
2014-08-15 17:03:03:963 924 1024 Agent   * Added update {006666EF-3638-4ADC-8DA0-65F08E31A4C2}.102 to search result
2014-08-15 17:03:03:963 924 1024 Agent   * Added update {0CFB8DEF-9B7E-478C-A746-8F9F91311DB5}.103 to search result
2014-08-15 17:03:03:963 924 1024 Agent   * Added update {2EE7B9F1-22B7-4618-84B1-8F0804A2ED02}.101 to search result
2014-08-15 17:03:03:963 924 1024 Agent   * Added update {99EB2EF3-7266-4488-9A80-A49418A4D1D4}.201 to search result
2014-08-15 17:03:03:963 924 1024 Agent   * Added update {B34E43F5-2F06-4D9D-B147-EE76B076E9C0}.100 to search result
2014-08-15 17:03:03:963 924 1024 Agent   * Added update {AD752FF8-DF05-4532-84B2-FEFF2D98F689}.101 to search result
2014-08-15 17:03:03:963 924 1024 Agent   * Added update {5357F0F8-DC7C-467C-8D8D-EA4D6345260C}.200 to search result
2014-08-15 17:03:03:963 924 1024 Agent   * Added update {77507BF9-6899-47DF-96D0-2FFA53A90470}.101 to search result
2014-08-15 17:03:03:963 924 1024 Agent   * Added update {EFA1E1FA-3CAD-4098-94E7-571D00F5B3BA}.202 to search result
2014-08-15 17:03:03:963 924 1024 Agent   * Added update {ACCDC8FE-BC27-4473-9F35-BD9D0880B4D2}.101 to search result
2014-08-15 17:03:03:966 924 1024 Agent   * Found 192 updates and 8 categories in search; evaluated appl. rules of 313 out of 697 deployed entities
2014-08-15 17:03:03:972 924 1024 Agent *********
2014-08-15 17:03:03:972 924 1024 Agent ** END ** Agent: Finding updates [CallerId = CcmExec]
2014-08-15 17:03:03:972 924 1024 Agent *************
2014-08-15 17:03:03:990 3536 3c8 COMAPI >>-- RESUMED -- COMAPI: Search [ClientId = CcmExec]
2014-08-15 17:03:04:340 3536 3c8 COMAPI   - Updates found = 192
2014-08-15 17:03:04:340 3536 3c8 COMAPI ---------
2014-08-15 17:03:04:340 3536 3c8 COMAPI -- END -- COMAPI: Search [ClientId = CcmExec]
2014-08-15 17:03:04:340 3536 3c8 COMAPI -------------
2014-08-15 17:15:14:576 924 a98 Shutdwn user declined update at shutdown
2014-08-15 17:15:14:576 924 a98 AU Successfully wrote event for AU health state:0
2014-08-15 17:15:14:576 924 a98 AU AU initiates service shutdown
2014-08-15 17:15:14:576 924 a98 AU ########### AU: Uninitializing Automatic Updates ###########
2014-08-15 17:15:14:701 924 a98 Report CWERReporter finishing event handling. (00000000)
2014-08-15 17:15:14:717 924 a98 Service *********
2014-08-15 17:15:14:717 924 a98 Service ** END ** Service: Service exit [Exit code = 0x240001]
2014-08-15 17:15:14:717 924 a98 Service *************
2014-08-15 17:18:22:445 904 230 Misc =========== Logging initialized (build: 7.6.7600.256, tz: +0100) ===========
2014-08-15 17:18:22:445 904 230 Misc   = Process: C:\Windows\system32\svchost.exe
2014-08-15 17:18:22:445 904 230 Misc   = Module: c:\windows\system32\wuaueng.dll
2014-08-15 17:18:22:445 904 230 Service *************
2014-08-15 17:18:22:445 904 230 Service ** START ** Service: Service startup
2014-08-15 17:18:22:461 904 230 Service *********
2014-08-15 17:18:23:256 904 230 Agent   * WU client version 7.6.7600.256
2014-08-15 17:18:23:287 904 230 Agent   * Base directory: C:\Windows\SoftwareDistribution
2014-08-15 17:18:23:428 904 230 Agent   * Access type: No proxy
2014-08-15 17:18:23:521 904 230 Agent   * Network state: Connected
2014-08-15 17:18:36:498 904 e54 Report CWERReporter::Init succeeded
2014-08-15 17:18:36:514 904 e54 Agent *********** Agent: Initializing Windows Update Agent ***********
2014-08-15 17:18:36:514 904 e54 Agent *********** Agent: Initializing global settings cache ***********
2014-08-15 17:18:36:514 904 e54 Agent   * WSUS server:
http://SCCMserver.com:8530
2014-08-15 17:18:36:514 904 e54 Agent   * WSUS status server:
http://SCCMserver.com:8530
2014-08-15 17:18:36:514 904 e54 Agent   * Target group: (Unassigned Computers)
2014-08-15 17:18:36:514 904 e54 Agent   * Windows Update access disabled: No
2014-08-15 17:18:36:514 904 e54 DnldMgr Download manager restoring 0 downloads
2014-08-15 17:18:37:886 904 230 Report *********** Report: Initializing static reporting data ***********
2014-08-15 17:18:37:886 904 230 Report   * OS Version = 6.1.7600.0.0.65792
2014-08-15 17:18:37:886 904 230 Report   * OS Product Type = 0x00000004
2014-08-15 17:18:37:886 904 230 Report   * Computer Brand = VMware, Inc.
2014-08-15 17:18:37:886 904 230 Report   * Computer Model = VMware Virtual Platform
2014-08-15 17:18:37:886 904 230 Report   * Bios Revision = 6.00
2014-08-15 17:18:37:886 904 230 Report   * Bios Name = PhoenixBIOS 4.0 Release 6.0
2014-08-15 17:18:37:886 904 230 Report   * Bios Release Date = 2012-07-02T00:00:00
2014-08-15 17:18:37:886 904 230 Report   * Locale ID = 1033
2014-08-15 17:18:43:049 904 10f4 Report CWERReporter finishing event handling. (00000000)
2014-08-15 17:19:22:199 904 230 AU ########### AU: Initializing Automatic Updates ###########
2014-08-15 17:19:22:199 904 230 AU   # WSUS server:
http://SCCMserver.com:8530
2014-08-15 17:19:22:199 904 230 AU   # Detection frequency: 10
2014-08-15 17:19:22:199 904 230 AU   # Approval type: Pre-install notify (Policy)
2014-08-15 17:19:22:199 904 230 AU   # Auto-install minor updates: Yes (Policy)
2014-08-15 17:19:22:199 904 230 AU Successfully wrote event for AU health state:0
2014-08-15 17:19:22:199 904 230 AU Initializing featured updates
2014-08-15 17:19:22:199 904 230 AU Found 0 cached featured updates
2014-08-15 17:19:22:199 904 230 AU Successfully wrote event for AU health state:0
2014-08-15 17:19:22:199 904 230 AU Successfully wrote event for AU health state:0
2014-08-15 17:19:22:199 904 230 AU AU finished delayed initialization
2014-08-15 17:19:22:199 904 230 AU #############
2014-08-15 17:19:22:199 904 230 AU ## START ## AU: Search for updates
2014-08-15 17:19:22:199 904 230 AU #########
2014-08-15 17:19:22:199 904 230 AU <<## SUBMITTED ## AU: Search for updates [CallId = {081DAF36-6F30-4383-9B4F-3439B1869B38}]
2014-08-15 17:19:22:199 904 10f4 Agent *************
2014-08-15 17:19:22:199 904 10f4 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-08-15 17:19:22:199 904 10f4 Agent *********
2014-08-15 17:19:22:199 904 10f4 Agent   * Online = No; Ignore download priority = No
2014-08-15 17:19:22:199 904 10f4 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-08-15 17:19:22:199 904 10f4 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-08-15 17:19:22:199 904 10f4 Agent   * Search Scope = {Machine}
2014-08-15 17:19:29:982 904 10f4 Agent   * Found 0 updates and 171 categories in search; evaluated appl. rules of 337 out of 2240 deployed entities
2014-08-15 17:19:29:982 904 10f4 Agent *********
2014-08-15 17:19:29:982 904 10f4 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-08-15 17:19:29:982 904 10f4 Agent *************
2014-08-15 17:19:29:998 904 10f4 Report REPORT EVENT: {CD4756C6-2116-4B99-B2AD-C970D24DE94F} 2014-08-15 17:19:22:199+0100 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Reboot completed.
2014-08-15 17:19:29:998 904 1108 AU >>## RESUMED ## AU: Search for updates [CallId = {081DAF36-6F30-4383-9B4F-3439B1869B38}]
2014-08-15 17:19:29:998 904 1108 AU   # 0 updates detected
2014-08-15 17:19:30:013 904 1108 AU #########
2014-08-15 17:19:30:013 904 1108 AU ## END ## AU: Search for updates [CallId = {081DAF36-6F30-4383-9B4F-3439B1869B38}]
2014-08-15 17:19:30:013 904 1108 AU #############
2014-08-15 17:19:30:013 904 1108 AU Featured notifications is disabled.
2014-08-15 17:19:30:013 904 1108 AU Successfully wrote event for AU health state:0
2014-08-15 17:19:30:013 904 1108 AU Successfully wrote event for AU health state:0
2014-08-15 17:19:30:029 904 10f4 Report CWERReporter finishing event handling. (00000000)
2014-08-15 17:19:35:020 904 10f4 Report CWERReporter finishing event handling. (00000000)
2014-08-15 17:22:35:006 904 10f4 Report Uploading 1 events using cached cookie, reporting URL =
http://SCCMserver.com:8530/ReportingWebService/ReportingWebService.asmx
2014-08-15 17:22:35:255 904 10f4 Report Reporter successfully uploaded 1 events.
Not sure whats going wrong??????????
When I checked the Deployment Monitoring Tool for the perticular test PC, the contents for the Patch deployments are blank (Have attached the image)
Thanks.

Let's start with that I think it's a very tricky method of deploying software updates. There is always a possibility that between phase 1 and 3 some updates are revised or even some complete new updates are available. That could cause differences (in for
example behavior) between your test clients and your other clients.
Back to your issue, it's hard to judge based on the log snippets. It looks like a function client and at the end I see something about 0 updates available.. Make sure that the software update group contains updates, the deployment is targeted to the right
collection and the content is all downloaded and available.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

SCCM 2012 SP1 WSUS/Software Update Point Synchronization error on CAS.

Hi All,
Good day to all you.
I would like to seek all your help on this issue that i have encountering.
My SCCM 2012 SP1 CAS are having a synchronization error in WSUS/Software update point. The CAS have intergrated WSUS role in it. The last good synchronization was on July 16, 2014. No error log found on WCM.log and WSUSctrl.log
Error:
Sync failed: UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall).
Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM 5776 (0x1690)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:05:32.796 2014 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
ISTR1="UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM 5776 (0x1690)
Sync failed. Will retry in 60 minutes
SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
below are wsyncmgr.log:
Setting sync alert to active state on site C01 SMS_WSUS_SYNC_MANAGER (0x1690)
Sync time: 0d00h01m14s SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Wakeup for a polling cycle SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Starting Sync SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Performing sync on retry schedule SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Read SUPs from SCF for MYHQKUL990707S.sdb.com SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
Found 1 SUPs SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Found active SUP MYHQKUL990707S.sdb.com from SCF File.
SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:04:20.750 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:04:20 PM
5776 (0x1690)
Synchronizing WSUS server MYHQKUL990707S.sdb.com SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:04:21.763 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:04:21 PM
5776 (0x1690)
Using account sdb\SCCM-Admin to connect to WSUS Server
SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
Synchronizing WSUS server myhqkul990707s.sdb.com ...
SMS_WSUS_SYNC_MANAGER 440 (0x01B8)
sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER
440 (0x01B8)
Sync failed: UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall). Source:
Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM
5776 (0x1690)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:05:32.796 2014 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
ISTR1="UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM
5776 (0x1690)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
All response is much appreciated
Thank You

Hi,
I recommend you look at the IIS log. Maybe it can give us some clues.
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.

How to remove the parent-child software update point in sccm 2012 sp1

I have a CAS , Primary site server(1) and secondary site servers (7). I have software update point installed on CAS, Primary server and Secondary site servers as well.
I have a situation to reinstall the software update point which is in primary site server.
So, How to reinstall the software update point in primary site server since this is located in the middle between CAS and secondary site servers.
So, please suggest me, do I have to do anything special apart from the normal steps to uninstall and reinstall the SUP point on primary site server?
I have referred few posts on how to remove SUP
https://social.technet.microsoft.com/Forums/en-US/c7258aad-d968-427b-8826-4829916c14c9/remove-and-re-add-software-update-point-sccm-2012?forum=configmanagersdk
and how to install SUP
http://www.windows-noob.com/forums/index.php?/topic/4467-using-sccm-2012-in-a-lab-part-6-deploying-software-updates/

Hi,
>> please suggest me, do I have to do anything special apart from the normal steps to uninstall and reinstall the SUP point on primary site server?
I just tried to reinstall the SUP on the Primary site(only one SUP on Primary site and there is a SUP on Secondary site). The SUP upstream data source of the Secondary site showed empty and greyed out. But the upstream data source resumed after a while.
It seems nothing special needs to be done.
Best Regards,
Joyce
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]

Alert: Synchronization failure alert for software update point ( SCCM 2012 R2)

SCCM 2012 R2
Alert: Synchronization failure alert for software update point: MY.net(MY)
Alert type: Software update synchronization failure
Severity: Critical
Active time (UTC): 13-09-2014 19:37:34
Condition: Generate an alert if software updates synchronization fails for the Software Update Point role at the
MY (MY) site.
Alert Text: Software updates synchronization for the Software Update Point role at the
MY (MY)) site failed.
Please let me know what will be the cause of this Alert, how to resolve it

The reason is stated in the message: "Generate an alert if software updates synchronization fails
for the Software Update Point role at theMY (MY) site"
Examine wsyncmgr.log
Torsten Meringer | http://www.mssccmfaq.de

Software Update Point doesn't show Win 2012 R2 and Windows 8.1 updates

I started deploying Windows 2012 R2 Datacenter servers and some Windows 8.1 workstations. I wanted to make sure that my Software Update Point was downloading updates available to those OS's and after going in to Administration -> Overview -> Site Configuration
-> Sites -> Configure Site Components -> Software Update Point, I notice that those OS's weren't available to select.
I then did some searches on the web and thought my problem was two fold:
1 - I was using SCCM 2012 SP1.
2 - My SCCM 2012 Software Update Point was on a Win 2008 R2 server
So the first thing I did was upgrade from SCCM 2012 SP1 to SCCM 2012 R2. I then created a Windows 2012 R2 Datacenter server and installed WSUS on it. I then added the server as a Site System Server, added the Software Update Point to it and configured it.
Unfortunately, this still didn't help me as you can see from the screen shots below:
What am I doing wrong and what needs to be done to have all the updated Operating Systems and Microsoft Software added to my Product list?
Thanks... Frank

To follow on to narcoticoo's statement, have you actually initiated a catalog sync from within the ConfigMgr console yet? If so, has it completed successfully (you can check the moniotring workspace or you can watch the wsyncmgr.log).
Jason | http://blog.configmgrftw.com
Jason...
I just ran a Synchronize Software Updates from ConfigMgr Console. I then went Monitoring -> Software Update Point Sync Status. It's showing my new WSUS server ( 2012 R2 ) but it's not showing any updates are being sync'd through it. See this screen shot:
I then went to the wsyncmgr.log file on my site server which is the OLD WSUS server ( Win 2008 R2 ) and say this:
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=PREP-SCCM12.<domain.org> SITE=STA PID=5224 TID=4028 GMTDATE=Wed Feb 26 19:00:40.236 2014 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site STA. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:40.236+300><thread=4028 (0xFBC)>
Sync failed. Will retry in 60 minutes $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:40.279+300><thread=4028 (0xFBC)>
Setting sync alert to active state on site STA $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:40.313+300><thread=4028 (0xFBC)>
Sync time: 0d00h00m00s $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:40.360+300><thread=4028 (0xFBC)>
Deleting file \\?\UNC\prep-dpsccm12\WSUS Updates\Win 7 Updates up to Aug 2012\0048da55-f46f-4452-b4c1-37c0f295333b\IE9-langpack-Windows7-x86-xho.exe, FAILED, Win32 Error = 5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.042+300><thread=4028 (0xFBC)>
Failed to delete orphaned content folder \\prep-dpsccm12\WSUS Updates\Win 7 Updates up to Aug 2012, error 0x5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.067+300><thread=4028 (0xFBC)>
Deleting file \\?\UNC\prep-dpsccm12\WSUS Updates\Win2k8 Updates Until Aug 2012\000f8a0a-825c-457b-a15b-57ade145a09b\windows6.0-kb2653956-x64.cab, FAILED, Win32 Error = 5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.119+300><thread=4028 (0xFBC)>
Failed to delete orphaned content folder \\prep-dpsccm12\WSUS Updates\Win2k8 Updates Until Aug 2012, error 0x5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.144+300><thread=4028 (0xFBC)>
Deleting file \\?\UNC\prep-dpsccm12\WSUS Updates\Win 7 Updates for Sept 2012\10f3ec1c-f096-4a82-ae41-440ba5328467\Windows6.1-RTM-Client-NEUTRAL-X86.EXE, FAILED, Win32 Error = 5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.173+300><thread=4028 (0xFBC)>
Failed to delete orphaned content folder \\prep-dpsccm12\WSUS Updates\Win 7 Updates for Sept 2012, error 0x5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.199+300><thread=4028 (0xFBC)>
Deleting file \\?\UNC\prep-dpsccm12\WSUS Updates\XP Updates Until Sept 30\17165524-99fa-49f7-91e6-457d43d4a48e\Windows-KB890830-V4.12.exe, FAILED, Win32 Error = 5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.228+300><thread=4028 (0xFBC)>
Failed to delete orphaned content folder \\prep-dpsccm12\WSUS Updates\XP Updates Until Sept 30, error 0x5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.254+300><thread=4028 (0xFBC)>
It appears to me that when doing a Sync, it's still trying to use my OLD WSUS server instead of my new one. I removed the Software Update Point from the OLD WSUS server and uninstalled WSUS from it. I'm not sure why it's still trying to sync from the old
server rather than the new one. Any ideas?
Thanks... Frank

SCCM 2012R2 Software Update Point (Old Programs List olny)

hi,
i have sccm 2012R2, today i add to sccm software update point role but there in Products page not showilng latest microsoft products such as Office 2013, Exchange 2013, Windows Server 2012R2,Windows 8.1,
there is only old programs,eg. office 2010, server 2012 (not R2)
i update sccm to latest cumulative update 4 but no change in there,
i need to update client computers, there are all Windows 8.1 systems.
how can i update cients from sccm?
picture link:
https://www.imageupload.co.uk/image/ZZww

This list comes from WSUS which in its default, newly installed state is out of date. The list is however updated every time that WSUS in synced and the catalog is updated in ConfigMgr. Thus, you simple need to initiate an update catalog sync from within
the ConfigMgr console by going to the Software Updates -> All Software Updates node and choosing Synchronize Software Updates from the ribbon bar or right-click context menu.
Jason | http://blog.configmgrftw.com | @jasonsandys

Use SCCM as a standard WSUS server as well as a Software Update point?

Is it possible to use SCCM as a standard WSUS server as well as a Software Update point? I have 2 scenarios:
1) create software update packages and deploy them via software update groups in Configuration Manager
2) configure a group policy to set internal WSUS server to the SCCM server with SUP role, and allow servers to pull updates
- Is this technically possible?
- Do I need to pre-download the updates that i want delivered via method (2) above ?
I am running Systems Center Configuration Manager 2012 R2 with SUP installed.

100% agree with Jason. Sounds like a idea full of hassle and I'd imagine weirdness could creep in. I'd use ConfigMgr to patch the servers for the advanced reporting alone.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Software Update Point Switching is not working for some Clients

Hi there,
I found nothing similar here and I hope this is the right section.
I´m running ConfigMgr 2012 R2 where one of the Site Systems from one of the Primaries is located in an untrusted Forest in a perimeter Network. The Site System there has the MP, SUP and DB Roles. In general it works great. The Systems in that untrusted Forest
get the SCCM Agent pushed, see and can install published Software packages and receive Windows Updates. But there are a few systems where everything works, except Windows Updates.
So I had a deeper look at what is happening and found out that the SUP switching is not working for them. They always try to contact the SUP from the Primary, which they cannot reach (this is intended).
From how I understand SUP switching as described here
http://blogs.technet.com/b/configmgrteam/archive/2013/03/27/software-update-points-in-cm2012sp1.aspx#pi140062=1
the Windows Update Agent tries to connect to a SUP every 30 minutes and after 4 failed attempts he will try to connect to the next one until he finds one which works.
As I said before, this seems to work for most systems in the untrusted forest, but some do not make any intentions to switch the SUP.
So my next step was to find out from where the Update Agent can get the information of the available SUPs. I think they either don´t receive the information that other SUPs exist, or if the Information is there, they don´t realize that there´s an error and
make no attempt to switch.
I used the System Center Support Center to gather all Information from some of the systems with that problems (Log Files, WMI information, registry information, policies etc.) but I cannot find where SCCM or the Update Agent store the information which SUPs
are available in my environment.
I´m sure the problem is on the Systems which fail to connect to the right SUP and not in the SCCM infrastructure itself, because for most of the systems everything is working just perfect. Unfortunately in the Blog Post above there´s also no information
where this information is stored and how it is obtained by the clients. In the comments there´s even one post which describes the same problem I have here, but there was no answer. I hope someone can point me into the right direction, because I´m stuck currently.
Things I tried additionally to all the log file / WMI / registry sniffing:
Removing the Software Distribution Folder and restarting the Windows Update Agent
Removing the WindowsUpdate Registry folder in the HKLM\SOFTWARE\Policies\Windows section in the Registry and restarting the Windows Update Agent.
Tried to reset the WUAgent with wuauclt /Resetauthorization additionally to the steps above.
I also tried to manually set the WUServer and WUStatusServer Keys in the registry to the new Server, but as soon as the next Update Scan cycle runs, the value is set back to the URL of the Primary Sites SUP
Is someone having additional ideas? It seems to me older systems are more affected (which were configured for a standard WSUS before SCCM 2012 was deployed) than newer ones which were installed when SCCM was in place already. But I don´t know what else to
"reset" on those machines without reinstalling them.

Thank you very much for your response. I must have missed that one by looking through numerous Logfiles. In this, there´s indeed a list of all available SUPs. So according to the LocationServices.log the machine should have a choice.
The WMI Key however, contains just one entry and this is the URL of the Primaries SUP which is not reachable in the untrusted forest. Is it OK that the WMI entry includes only one entry? If yes, what process is putting the results from the LocationServices
into WMI? It seems like the Windows Update Agent is feeded from the WMI Key then. If this is the case my problems seems to be the "communication path" between these two components.
Is this the job from the SCCM Agent, the Windows Update Agent or maybe some third component I´m not aware of? I wonder how I can fix this.

Critical Error in Software Update Point

SCCM 2012 Software Update Point is showing error as per picture below.
How can I fix this error?

Hi,
I would start by looking in the log files, Wsyncmgr.log, WsusCtrl.log and WCM.log file for any errors. information about all log files are found here:http://technet.microsoft.com/en-us/library/hh427342.aspx#BKMK_SUPLog
That should give you an error message and more details on the error, post them here and we can assist you, but alittle bit more information would be useful.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Software update point unable to be installed Sccm2012

Hey all,
I have come across a frustrating issue with SCCM 2012 while trying to install Software update point,
Environment: 1 X single site sccm 2012 SP1 5.00.7804.1300
Wsus to install updates - want to enable Service update point to deploy updates.
History: the Wsus server was configured and initialized
doring the original installation, i reinstalled the WSUS without initial config.
Problem:
the SCCM is unable to install the SMS_WSUS_Control_Manager
Event Log Errors:
Event 1016:
On 07/04/13 21:13:56, component SMS_SITE_COMPONENT_MANAGER on computer SCCMSRV.DOMAIN.LOCAL reported: Site Component Manager failed to install this component on this site system.
Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the installation in minutes. To force Site Component Manager to immediately retry the installation, stop and restart
Site Component Manager using the Configuration Manager Service Manager.
Event 6703:
On 04/07/2013 21:10:35, component SMS_WSUS_SYNC_MANAGER on computer SCCMSRV.DOMAIN.LOCAL reported: WSUS Synchronization failed.
Message: WSUS update source not found on site SYN. Please refer to WCM.log for configuration error details..
Source: getSiteUpdateSource.
The operating system reported error 2147500037: Unspecified error
The WCM.log indicated that updates KB2720211 + KB2734608 event though the updates are installed several times.
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.056-180><thread=5972 (0x1754)>
Checking runtime v2.0.50727...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.058-180><thread=5972 (0x1754)>
Did not find supported version of assembly Microsoft.UpdateServices.Administration.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.196-180><thread=5972 (0x1754)>
Checking runtime v4.0.30319...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.197-180><thread=5972 (0x1754)>
Did not find supported version of assembly Microsoft.UpdateServices.Administration.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.210-180><thread=5972 (0x1754)>
Supported WSUS version not found~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.211-180><thread=5972 (0x1754)>
STATMSG: ID=6607 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=SCCMSRV.domain.local SITE=SYN PID=3276 TID=5972 GMTDATE=יום ה יול 04 15:45:57.211 2013 ISTR0="SCCMSRV.domain.local" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.211-180><thread=5972 (0x1754)>
Remote configuration failed on WSUS Server.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.212-180><thread=5972 (0x1754)>
STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=SCCMSRV.domain.local SITE=SYN PID=3276 TID=5972 GMTDATE=יום ה יול 04 15:45:57.212 2013 ISTR0="SCCMSRV.domain.local" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.212-180><thread=5972 (0x1754)>
Setting new configuration state to 3 (WSUS_CONFIG_FAILED)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.214-180><thread=5972 (0x1754)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.214-180><thread=5972 (0x1754)>
Trigger event array index 0 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.215-180><thread=5972 (0x1754)>
SCF change notification triggered.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:46:02.977-180><thread=5972 (0x1754)>
Populating config from SCF $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:46:02.977-180><thread=5972 (0x1754)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:46:02.981-180><thread=5972 (0x1754)>
Shutting down... $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:53:59.991-180><thread=5972 (0x1754)>
Shutting Down...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:53:59.994-180><thread=5972 (0x1754)>
SMS_EXECUTIVE started SMS_WSUS_CONFIGURATION_MANAGER as thread ID 7164 (0x1BFC). $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 19:15:33.486-180><thread=5940 (0x1734)>
This SCCMSRV.domain.local system is the SMS Site Server.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 19:15:33.539-180><thread=7164 (0x1BFC)>
Populating config from SCF $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 19:15:33.551-180><thread=7164 (0x1BFC)>
Setting new configuration state to 1 (WSUS_CONFIG_PENDING)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 19:15:33.554-180><thread=7164 (0x1BFC)>
Changes in active SUP list detected. New active SUP List is:~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 19:15:33.554-180><thread=7164 (0x1BFC)>
SUP0: SCCMSRV.domain.local, group = , nlb = ~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 19:15:33.555-180><thread=7164 (0x1BFC)>
Updating active SUP groups...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 19:15:33.555-180><thread=7164 (0x1BFC)>
Waiting for changes for 1 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 19:15:33.556-180><thread=7164 (0x1BFC)>
Wait timed out after 0 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 19:15:34.560-180><thread=7164 (0x1BFC)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 19:15:44.598-180><thread=7164 (0x1BFC)>
Event 1:
System.NullReferenceException\r\nObject reference not set to an instance of an object.\r\n at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryPropertySingleItem.get_IntegerValue()
at Microsoft.ConfigurationManagement.AdminConsole.SoftwareUpdateHelper.DisplayUtilities.GetSupSyncStatusIcon(Object sender, ScopeNode scopeNode, IResultObject resultObject, AssemblyDescription& resourceAssembly)\r\n
Any ideas?
Reagards
Asaf

WSUS was installed and configured and work fine a few monthes ago as a part of the first try to install SUP before aplying SP 1 to SCCM.
Both SCCM and WSUS are installed on the same server.
now we want to deploy all updates from SCCM SUP, and the installation failed.
after researching online, uninstalled WSUS completely from the SCCM server, and removed SUP from the Site and rebooted the server.
installed WSUS 3.0 SP2, when initial config of the WSUS popped up i canceled it, the only config i made
is at the installation wizard, set the port to 8530, folders location and internal DB.
>> i am able to open the WSUS console and connect to the "localhost" but no settings
are configured.
installed update 2734608, reboot.
Installed SUP.
and here we are.

New Site Server with Distribution Point & Software Update Point Roles not pulling SUGs

I just set up a new server & installed the DP & SUP roles on it. I am getting the following in the log this is just a small sample as its kind of repetative:
Report state message 0x8000094F to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Report Body: <ReportBody><StateMessage MessageTime="20140328183445.000000+000" SerialNumber="0"><Topic ID="FPP00002" Type="901" IDType="0"/><State ID="2383" Criticality="0"/><UserParameters
Flags="0" Count="2"><Param>FPP00002</Param><Param>["Display=\\FPPSCCM02.FPP.WUCON.WUSTL.EDU\"]MSWNET:["SMS_SITE=FPP"]\\FPPSCCM02.FPP.WUCON.WUSTL.EDU\</Param></UserParameters></StateMessage></ReportBody>
SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Report status message 0x8000094F to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Status message has been successfully sent to MP from remote DP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Retry 10 times SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Start to evaluate all packages ... SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Start to evaluate package 'FPP00002' version 0 ... SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Report status message 0x4000094C to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Status message has been successfully sent to MP from remote DP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Failed to evaluate package FPP00002, Error code 0x80070002 SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Report state message 0x8000094F to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Report Body: <ReportBody><StateMessage MessageTime="20140328183445.000000+000" SerialNumber="0"><Topic ID="FPP00002" Type="901" IDType="0"/><State ID="2383" Criticality="0"/><UserParameters
Flags="0" Count="2"><Param>FPP00002</Param><Param>["Display=\\FPPSCCM02.FPP.WUCON.WUSTL.EDU\"]MSWNET:["SMS_SITE=FPP"]\\FPPSCCM02.FPP.WUCON.WUSTL.EDU\</Param></UserParameters></StateMessage></ReportBody>
SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Report status message 0x8000094F to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Status message has been successfully sent to MP from remote DP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Report status message 0x40000952 to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Status message has been successfully sent to MP from remote DP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
DP monitoring finishes evaluation. SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Failed to evaluate some packages after 10 retry SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
The Console shows for the DP that it's waiting for content and I don't see where I can create a Prestage Package
# When I wrote this script only God & I knew what I was doing. # Now, only God Knows! don't retire technet http://social.technet.microsoft.com/Forums/en-US/e5d501af-d4ea-4c0f-97c0-dfcef0192888/dont-retire-technet?forum=tnfeedback

D:\SMS_DP$\sms\logs\smsdpmon.log
This is the 2nd server in our SCCM 2012 Sp1 Hierarchy. It is set up with the following Site System Roles:
Component Server
Distribution Point
Site System
Software Update Point
It is Prestaged Enabled. My intent is that the client systems @ the location where this DP is located will use it to pull their Microsoft Updates from as well as content for any Applications we push to them rather than going over the WAN to the Primary
Site Server.
IN Distribution Point Configuration Status. the console shows "Failed to update package" & "Packaget Transfer Manager failed to update the package "yxz00040". Version 3 on Distribution Point server.my.domain.com review pkgxfermgr.log for more information
about this failure."
It also goes on toe list 2 possible causes and solutions
Site servers does not have sufficient rights to the source directory.
(Site server account is a member of local Administrators on Primary)
Not enough disk space available
(I have over 1TB of available space and primary site server has only 150GB available for entire content repository, both applications and sofware updates.)
# When I wrote this script only God & I knew what I was doing. # Now, only God Knows! don't retire technet http://social.technet.microsoft.com/Forums/en-US/e5d501af-d4ea-4c0f-97c0-dfcef0192888/dont-retire-technet?forum=tnfeedback

SCCM 2007 R3 Software Updates Sync : 6703 WSUS server not configured

Hi,
We run SCCM 2007 R3 in native mode (Software Update Point and WSUS both reside on SCCM site server). We're having issues running Software Updates Synchronization which have previously worked fine. In SMS_WSUS_Control_Manager the errors appear as follows
MessageID:6703
SMS WSUS Synchronization failed.
Message: WSUS server not configured.
Source: CWSyncMgr::DoSync.
The operating system reported error 2147500037: Unspecified error
I've followed the suggested fixes in
http://technet.micro...y/bb735874.aspx but still we have an issue.
If I open the WSUS console directly and run a manual synchronization from Microsoft this completes successfully. However, I presume this will not be using SSL which is what SCCM will want to use in native mode. I've checked the bindings in IIS on WSUS Administration
site to confirm that the certificate hasn't expired.
Any ideas what else I can try?
Cheers,
Paul

wsyncmgr.log repeatedly contains the following
Performing sync on retry schedule SMS_WSUS_SYNC_MANAGER 13/10/2013 14:02:11 612 (0x0264)
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=CCPSCCM02 SITE=WES PID=8084 TID=612 GMTDATE=Sun Oct 13 13:02:11.288 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 13/10/2013
14:02:11 612 (0x0264)
Sync failed: WSUS server not configured. Source: CWSyncMgr::DoSync SMS_WSUS_SYNC_MANAGER 13/10/2013 14:07:11 612 (0x0264)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=CCPSCCM02 SITE=WES PID=8084 TID=612 GMTDATE=Sun Oct 13 13:07:11.284 2013 ISTR0="CWSyncMgr::DoSync" ISTR1="WSUS server not configured" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6=""
ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 13/10/2013 14:07:11 612 (0x0264)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER 13/10/2013 14:07:11 612 (0x0264)
Sync time: 0d00h05m00s SMS_WSUS_SYNC_MANAGER 13/10/2013 14:07:11 612 (0x0264)

SCCM 2012 R2 - Software Update Point

Similar Messages

Maybe you are looking for