SCCM 2012 - SUP

Hi All,
I have configured SUP point on the SCCM 2012 SP1 server (Server 2008 R2 Sp1) but under product list I cant see
Windows 7 displayed. Do I need to apply any hotfix. Please advice
Regards, Pratap

You need to sync your SUP with Windows Update. To do that Work through the below step:
Right the All Software Updates node under Software Updates
and select Synchronize updates - wait for the sync to complete. You can verify this in the
wsyncmgr.log file.
After the sync has completed go to Administration, Site Configuration,
Sites.
Right-click your site in the details pane and select Configure Site Components
-> Software Update Point
In the Software Update Point Properties window, click the
products tab and select Windows 7. Then click okay.
Repeat the above steps to sync your SUP with Windows 7 updates etc.

Similar Messages

SCCM 2012 SUP locations

What is a best practice for SUP Installation.
I have read that if your SUP goes down , the clients will assign to another SUP and at that time re-scan for entire catalog (a lot of traffic)
So if we keep only one SUP in the primary location and it goes down , Clients will not fallback to other SUP as there in none in hierarchy , but rather fallback to Microsoft Updates.
Does anyone have suggestions for SUP placements in a environment of around 9K clients
PS1 - Clients 2500 (EMEA) --- 40 MB connection with HQ
PS2 - Clients 1800 (EMEA) --- 100 MB connection with HQ
PS3 - Clients 1700 (EMEA) --- HQ Primary location
PS4 - Clients 1400 (EMEA) --- 100 MB connection with HQ
PS5 - Clients 800 (Americas) --- 100 MB connection with HQ
PS6 - Clients 425 (Asia) --- 2 MB connection with HQ
PS7 - Clients 175 (EMEA) --- 100 MB connection with HQ
PS8 - Clients 170 (Africa) --- 4MB Connection with HQ

That's why you place two SUPs in the central location (avoid the use of the word "primary" unless you are actually talking about a primary site or primary site server other your meaning may be ambiguous) whose underlying WSUS instances use the same
DB. If one goes down, then the rescan penalty is almost nothing because they are using the same DB.
Note that the use of multiple SUPs within a single primary site is for availability only though. Also note that the SUP itself isn't anything the client's know about or use, they use the underlying WSUS instance. Thus, there are ways of controlling which
WSUS instance clients use via Group Policy Preferences but the less micro-management you do, the better things work.
Also, clients will *never* fallback to Microsoft Updates for scanning. That would make no sense because only your WSUS instances have your update catalog to scan against.
And finally, is high availability of update scanning truly something you need to worry about? What's exactly is your SLA for update scanning and isn't simply building a new SUP sufficient?
(Not trying to say it's not valid or that you shouldn't have multiple SUPs, just trying to make you think about what you're doing. Also, "best practice" implies there's only one good way to do something and that everyone should do it that way which means
everyone is the same which is not true. Thus you need to design things specific to your environment based on the knowledge of how the components work. Relying on so-called "best practices" effectively means you're just guessing.)
Jason | http://blog.configmgrftw.com

SCCM 2012 - SUP - updates not showing as downloaded when they actualy are

Hello. I have a strange problem.
I have collected my updates by year to have an overview of what is still updates..
In the console I have 4 updates showing as not downloaded.
If I highlight these and choose to download I get this
So appearantly it works. However these continue to show as not downloaded. R
My WSUS installation uses a SQL database on a proper sql server.
Help needed

Nothing happened in the logfile. I have no clue to what is happening. What I ended up doing was that I recreated the Software Update Group with the exact same updates and downloaded it again. Problem solved. The views in the console are made from SQL
queries. Guess the download process just didnt finish its sql job.
Old log history is of course gone but I will post the logfile here if/when it happens again.

SCCM 2012 Secondary site Client Communication for SUP

Hi,
We have an SCCM 2012 Setup and here is the design CAS-->Primary-->Secondary site servers.
SUP is configured for Secondary site too. Boundaries are defined with IP Address Range and is proper.
Some clients are comminicating to Secondary site for updates. Downloading successfully and installing the software.
But some of the clients are communicating to primary site for updates and retain with the status "Downloading update"
I have checked the locationservices.log and it is fluctuating between Primary and secondary MP.
2 proxy MP errors in the last 10 minutes, threshold is 5. LocationServices 4/5/2013 11:35:59 AM 768 (0x0300)
Executing Task LSSiteRoleCycleTask LocationServices 4/5/2013 11:51:59 AM 4200 (0x1068)
1 proxy MP errors in the last 10 minutes, threshold is 5. LocationServices 4/5/2013 11:51:59 AM 4200 (0x1068)
Executing Task LSSiteRoleCycleTask LocationServices 4/5/2013 11:51:59 AM 5648 (0x1610)
2 proxy MP errors in the last 10 minutes, threshold is 5. LocationServices 4/5/2013 11:51:59 AM 5648 (0x1610)
I have also checed "DataTransferService.log" and found more errors.
Error retrieving manifest (0x800704cf). Will attempt retry 7 in 1920 seconds. DataTransferService 4/5/2013 11:51:59 AM 5576 (0x15C8)
DTSJob {141CB5AE-8EF2-464D-8D8C-68B868EE7F7B} in state 'DownloadingManifest'. DataTransferService 4/5/2013 11:51:59 AM 4200 (0x1068)
Failed to send request to /SMS_DP_SMSPKG$/1fd86ee1-ece0-41ae-a2b8-5a2b305746d4 at host xxxxxxxx.xxxxxxx.com, error 0x2efe DataTransferService 4/5/2013 11:51:59 AM 4200 (0x1068)
[CCMHTTP] ERROR: URL=https://xxxxxxxx.xxxxxxx.com:443/SMS_DP_SMSPKG$/1fd86ee1-ece0-41ae-a2b8-5a2b305746d4, Port=443, Options=192, Code=12030, Text=ERROR_WINHTTP_CONNECTION_ERROR DataTransferService 4/5/2013 11:51:59 AM 4200 (0x1068)
Raising event:
instance of CCM_CcmHttp_Status
ClientID = "GUID:0DA907D5-1709-4B10-B627-61E289FD7149";
DateTime = "20130405062159.643000+000";
HostName = "xxxxxxxx.xxxxxxx.com";
HRESULT = "0x80072efe";
ProcessID = 4260;
StatusCode = 600;
ThreadID = 4200;
DataTransferService 4/5/2013 11:51:59 AM 4200 (0x1068)
Successfully sent location services HTTPS failure message. DataTransferService 4/5/2013 11:51:59 AM 4200 (0x1068)
Error sending DAV request. HTTP code 600, status '' DataTransferService 4/5/2013 11:51:59 AM 4200 (0x1068)
GetDirectoryList_HTTP mapping original error 0x80072efe to 0x800704cf. DataTransferService 4/5/2013 11:51:59 AM 4200 (0x1068)
GetDirectoryList_HTTP('https://xxxxxxxx.xxxxxxx.com:443/SMS_DP_SMSPKG$/1fd86ee1-ece0-41ae-a2b8-5a2b305746d4') failed with code 0x800704cf. DataTransferService 4/5/2013 11:51:59 AM 4200 (0x1068)
Error retrieving manifest (0x800704cf). Will attempt retry 7 in 1920 seconds. DataTransferService 4/5/2013 11:51:59 AM 4200 (0x1068)
my query is how some of the clients are communicating primary site server for updates even though the boundary details are properly configured and Secondary site is configured with sup. Also need to know (as per the log "DataTransferService.log")how
come the clients are communicating SSL port for updates. Plz help in resolving the issue.

Hi Kent,
Thanks for the reply.
Primary and secondary sites are connected over WAN and we have around 2000 clients which are reporting to Secondary site.
Considering the WAN bandwidth utiliztaion and number of clients on secondary site we have configured the SUP role.
Not all the clients are with the above error message around 40%-50% of the clients are with above stated error message.
Plz let me know what is the error message indicates and do we need to reffer any other logs for indepth analysis.
Locationservices.log is with fluctuating connectivity
2 proxy MP errors in the last 10 minutes, threshold is 5. LocationServices 4/5/2013 11:35:59 AM 768 (0x0300)
Executing Task LSSiteRoleCycleTask LocationServices 4/5/2013 11:51:59 AM 4200 (0x1068)
1 proxy MP errors in the last 10 minutes, threshold is 5. LocationServices 4/5/2013 11:51:59 AM 4200 (0x1068)
Executing Task LSSiteRoleCycleTask LocationServices 4/5/2013 11:51:59 AM 5648 (0x1610)
2 proxy MP errors in the last 10 minutes, threshold is 5. LocationServices 4/5/2013 11:51:59 AM 5648 (0x1610)
how come the clients are communicating SSL port for updates. Plz help in resolving the issue.

SCCM 2012 SP1 - SUP Error

Hi guys,
i upgraded my SCCM 2012 test Environment to SP1. I have only one Primary Site Server which holds all Roles. Everything seems to work fine except the SUP Role. If i try to synchronize the latest Updates it says that it cannot find a WSUS Server
and i should check WCM.LOG.
Within WCM.LOG i can find the following Messages:
Waiting for changes for 58 minutes SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 08:56:44 3620 (0x0E24)
Trigger event array index 0 ended. SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:07:56 3620 (0x0E24)
SCF change notification triggered. SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:04 3620 (0x0E24)
Populating config from SCF SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:04 3620 (0x0E24)
Setting new configuration state to 1 (WSUS_CONFIG_PENDING) SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:04 3620 (0x0E24)
Changes in active SUP list detected. New active SUP List is: SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:04 3620 (0x0E24)
SUP0: CM01.TEST.LOCAL, group = , nlb = SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
Updating active SUP groups... SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
Bad Configuration, SUPs present but no default SUP SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
Default SUP not specified SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
Setting new configuration state to 0 (WSUS_CONFIG_NONE) SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
Waiting for changes for 47 minutes SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
So in General this tells me that it can find a SUP but this one is not specified as a DEFAULT SUP. How can i tell SCCM that this is my Default SUP? (I only have this one and it is configured to sync from Microsoft Update site). I have never seen
this before so i guess this is related to SP1?
PS: I also installed the 2 necessary WSUS Updates before i upgraded to SCCM SP1.
Thanks in lot in advance.
Stefan

None of your solutions apply to WSUS 4.0 on Server 2012
None of the specified patches applies or will run on a Windows 2012 Std server. They either report that WSUS 3 SP 2 isn't installed OR that the patch isn't applicable to the server version installed.
Here is a excerpt of MY WCM.LOG
I have a fully patched Windows 2012 Standard Server, Fully updated SCCM 2012 SP1 installed, and am connected to a fully patched SQL2012 Server on another fully patched Windows 2012 Std server.
Ports 8530 and 8531 designated on both the WSUS 4.0 Role and SCCM 2012 SP1 system (both are on same server)
SUP0: SCCM2012.xxdomainname.ORG, group = , nlb = ~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.496+420><thread=6052 (0x17A4)>
Updating active SUP groups...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.503+420><thread=6052 (0x17A4)>
Bad Configuration, SUPs present but no default SUP $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.510+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.525+420><thread=6052 (0x17A4)>
Setting new configuration state to 0 (WSUS_CONFIG_NONE)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.535+420><thread=6052 (0x17A4)>
Waiting for changes for 11 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.543+420><thread=6052 (0x17A4)>
Wait timed out after 11 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:04:54.569+420><thread=6052 (0x17A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.577+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.585+420><thread=6052 (0x17A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.592+420><thread=6052 (0x17A4)>
Wait timed out after 60 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:04:54.714+420><thread=6052 (0x17A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.721+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.728+420><thread=6052 (0x17A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.734+420><thread=6052 (0x17A4)>
Randall

SCCM 2012 SP1 SUP on Windows Server 2012

Hi sccm guys,
I'm having Troubles to get the SUP role working on my Windows Server 2012. I'm using SCCM 2012 SP1. I installed (and did not configure) the WSUS role from the Server Manager. I Chose to install the DB on the local SQL instance (no WID instance).
Then I added the SUP role to the Server and configured it with the seperate wsus Administration site (Ports 8530 and 8531).
WSUS gets configured partially (Proxy Settings and "Products and Classification" Options only for Office and Windows)
The folowing error pops up in the wcm.log
Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error
Any clues?
Cheers
Sebastian Bammer

Also did not fix my issue. A round of my logs:
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER
15/01/2013 8:28:59 a.m. 3556 (0x0DE4)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER
15/01/2013 8:28:59 a.m. 3556 (0x0DE4)
Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.16384
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Supported WSUS version found SMS_WSUS_CONFIGURATION_MANAGER
15/01/2013 8:28:59 a.m. 3556 (0x0DE4)
Using DOMAIN\Administrator credentials for network connections
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Attempting connection to WSUS server: SCCM01.domain, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Successfully connected to server: SCCM01.domain, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Verify Upstream Server settings on the Active WSUS Server
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
No changes - WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Done using DOMAIN\Administrator credentials
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER
15/01/2013 8:28:59 a.m. 3556 (0x0DE4)
Using DOMAIN\Administrator credentials for network connections
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Attempting connection to WSUS server: SCCM01.domain, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Successfully connected to server: SCCM01.domain, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Done using DOMAIN\Administrator credentials
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:14 a.m.
3556 (0x0DE4)
Successfully refreshed categories from WSUS server
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:16 a.m.
3556 (0x0DE4)
Using DOMAIN\Administrator credentials for network connections
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:21 a.m.
3556 (0x0DE4)
Attempting connection to WSUS server: SCCM01.domain, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:21 a.m.
3556 (0x0DE4)
Successfully connected to server: SCCM01.domain, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:21 a.m.
3556 (0x0DE4)
Category Product:587f7961-187a-4419-8972-318be1c318af (Microsoft Dynamics CRM 2011 SHS) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:21 a.m.
3556 (0x0DE4)
Starting WSUS category sync from upstream...
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:21 a.m.
3556 (0x0DE4)
Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER
15/01/2013 8:29:26 a.m. 3556 (0x0DE4)
Using DOMAIN\Administrator credentials for network connections
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:26 a.m.
3556 (0x0DE4)
Attempting connection to WSUS server: SCCM01.domain, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:26 a.m.
3556 (0x0DE4)
Successfully connected to server: SCCM01.domain, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:26 a.m.
3556 (0x0DE4)
Done using DOMAIN\Administrator credentials
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:41 a.m.
3556 (0x0DE4)
Successfully refreshed categories from WSUS server
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
3556 (0x0DE4)
Done using DOMAIN\Administrator credentials
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
3556 (0x0DE4)
Using DOMAIN\Administrator credentials for network connections
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
3556 (0x0DE4)
Attempting connection to WSUS server: SCCM01.domain, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
3556 (0x0DE4)
Successfully connected to server: SCCM01.domain, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
3556 (0x0DE4)
Category Product:587f7961-187a-4419-8972-318be1c318af (Microsoft Dynamics CRM 2011 SHS) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
3556 (0x0DE4)
Subscription contains categories unknown to WSUS.
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
3556 (0x0DE4)
Done using DOMAIN\Administrator credentials
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
3556 (0x0DE4)
Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
3556 (0x0DE4)
STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=SCCM01.domain SITE=AKL PID=1544 TID=3556 GMTDATE=Mon Jan 14 19:29:42.723 2013 ISTR0="SCCM01.domain" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8=""
ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER
15/01/2013 8:29:42 a.m. 3556 (0x0DE4)
Waiting for changes for 59 minutes SMS_WSUS_CONFIGURATION_MANAGER
15/01/2013 8:29:42 a.m. 3556 (0x0DE4)
Thanks Christoph

[SCCM 2012 SP1 W2K8R2] SUP not in Sync with WSUS settings (Language)

Hi All,
I have almost identical production and test SCCM environment.
After I setup SUP on both production and test environment SUP Language settings are not replicated to WSUS and cause WSUS/SCCM to Sync all languages.
SCCM 2012:
WSUS:
Any idea how to fix this?
Thank you in advance.
Regards,

Hi,
There is nothing to fix, it looks exactly the same in my environment. The updates are not downloaded using WSUS it is downloaded using either the SCCM console or the SCCM Primary Site server if you use and ADR and when you download the updates the settings
are beeing honoured.
So this is expected behaviour.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

SCCM 2012 SP1 - Multiple SUP - common WSUS DB

Hello,
Is it supported / recommend to share a common WSUS DB for multiple WSUS / SUP roles ?
If yes, how to perform a clean deployment of additional SUP dealing with additional KB requirements.Following article explains the problem but the solution looks very complex: http://scug.be/sccm/2012/10/03/configmgr-2012-sp1-installing-multiple-software-update-points-per-single-primary-site-and-use-a-single-shared-wsus-database-on-your-sql-cluster/
I tried to test this procedure in my test environment but it broken WSUS and now refuse to sync with Microsoft (can't establish SSL connection).
I have not been able to find any official Microsoft setup guide for this ?
As an alternative, is it possible to sync additional SUP as downstream servers with the first one. I ask for this because I use SCUP, and I don't want to maintain multiple WSUS environment.
Regards.

Hi.
We have the same problem with our WSUS 3.0 SP2 installation, when I install WSUS on an SCCM 2012 server in the "Secondary Site".
That server is in a different domain (one way Trust); but I have Logged On to that server with an specific account from the Top Domain that has Owner rights on the excisting DB). The Installation connect's succcesfully to the DB, and on the
Next Window I get the error "The existing DB is not compatible with this version of Windows Server Update Services 3.0 SP2"
The first two Wsus Installations in the "Top" domain worked just fine.
Anyone an idea?

SCCM 2012 R2 SUP and SQL License

I understand that SQL license comes with SCCM 2012 but not sure if it is also free for remote site server that has SUP role only so my question is do I need SQL license for only SUP role that is installed on a remote server (non-primary)?

All SQL licensing is included as long as it is just used for System Center. See here
http://www.micromail.com/files/admin/uploads/W285_Field_2_65090.pdf
License required only for endpoints being managed.
No additional licenses are needed for management servers or SQL Server technology.
It doesn't explicitly say this but, in my opinion, this includes System Center related technologies - eg WSUS, MDT etc.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

WSUS on DMZ for SUP SCCM 2012 R2

Hi all,
We are setting up SCCM 2012 r2 environment for production purpose and we would be having one primary . Due to security reason internet connectivity is not allowed for SCCM primary server , however
we have some DMZ servers that has internet connectivity .
My question here is
Is it possible to have WSUS on DMZ server and SUP role in SCCM primary server ?

Thanks for you reply..
You mean we have to install WSUS and SUP in primary site server and also install WSUS in DMZ server, then primary site server WSUS should get Sync from DMZ WSUS. Am I correct ?
My next question is while installing SUP in SCCM primary site
, do we need give sync from an upstream data sources location as primary site WSUS or DMZ wsus ?

After SUP install event id 1 appearing after installation of SCCM 2012 R2

I've just built a SCCM 2012 R2 environment. All appears ok, there aren't any noticable errors within SCCM. However since installing the SUPs on my CAS and two secondary sites I noticed the following alert appearing in event viewer.
Event ID 1 - Critical
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
Has anyone seen this before? Should I be concerned?
(SQL is installed locally. I've used a named instance.)
Thanks

Sorry - my mistake. We have 1 CAS and 2 Primary Sites. We have already had a discussion about our need for a CAS - see link
http://social.technet.microsoft.com/Forums/en-US/0702f44e-8d8c-47cc-a825-5750d70a4cbd/replication-link-failing-or-degraded?forum=configmanagergeneral
I have checked all the logs above. SUPSetup.log says installation successful and there are no errors in the wsusctrl.log, wsyncmr.log and wcm.log log files.
I haven't yet synchronized the software Updates for one of the Primaries with the CAS, as I was planning to kick this off this evening. The other Primary has sync'd with the CAS no problem.

SCCM 2012 using SUP to Windows 2012 R2 WSUS

I have the following environment setup:
1. Windows Server 2012 R2 with SCCM 2012 SP1
2. Windows Server 2012 R2 with WSUS installed
3. Windows Server 2008 R2 with SQL Server 2012 SP1
I am trying to connect SCCM to the WSUS server as a SUP. I have reinstalled and configured countless times. I've tried Sebastian's steps near the middle-end of this http://social.technet.microsoft.com/Forums/windowsserver/en-US/29135ae5-5f0c-49d9-b7ad-f4d5e9664a33/sccm-2012-sp1-sup-on-windows-server-2012?forum=configmanagerdeployment
I keep seeing an error in the WCM.log that the WSUS version is not supported. The WSUS version on the Windows 2012 R2 server is 6.3.9600.16384
Permissions should not be an issue. I have configured a Domain account and have added as a local administrator and also the WSUS Admin group. Firewall is not an issue as ports are open.
Do I have to switch my WSUS server to 2008 R2? Or remove it entirely and let SCCM install it as a SUP? This is environment is entirely from scratch.

I was finally able to get this to work. My logs were continuously showing that SCCM2012 was looking for WSUS 3.0 SP2 (+ KB). I installed WSUS locally on the SCCM 2012 server and added a SUP there. I was then able to successfully add the
remote WSUS server and it seems to be working now.

SCCM 2012 on Server 2012 and WSUS 3.0 SP2 on Server 2008

We are installing SCCM 2012 SP1 fresh into our development environment - the primary site server and the database (SQL 2012) are both being installed on Server 2012.
We have an existing WSUS box on a Windows 2008 (not R2) server - the WSUS server version is 3.2.7600.256. We have set this up as the software update point.
For the purposes of this discussion, these are the server names (obviously obfuscated):
Primary site server: sccm.domain.local
Database server: sccmdb.domain.local
WSUS server: wsus.domain.local
On the primary SCCM server, I've installed the WSUS user interface (Install-WindowsFeature -Name UpdateServices-UI), in order to work with the remote WSUS server.
Updates synchronization appears to be working fine, but when I try to setup client distribution via SUP, I'm getting the following error in the Application event log:
Log Name:      Application
Source:        SMS Server
Date:          8/6/2013 11:03:11 AM
Event ID:      6613
Task Category: SMS_WSUS_CONFIGURATION_MANAGER
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      sccm.domain.local
Description:
On 8/6/2013 11:03:11 AM, component SMS_WSUS_CONFIGURATION_MANAGER on computer sccm.domain.local reported: WSUS Configuration Manager failed to publish client boot-strapper package "9D5353E5-DA80-48C3-97DE-C9C528F73A2D" with version "5.00.7804.1000"
to the Software Updates Point.
As well as this in the WMC.log:
PublishApplication(9D5353E5-DA80-48C3-97DE-C9C528F73A2D) failed with error System.InvalidOperationException: Publishing operation failed because the console and remote server versions do not match.~~   at Microsoft.UpdateServices.Internal.BaseApi.Publisher.LoadPackageMetadata(String
sdpFile)~~   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetPublisher(String sdpFile)~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.PublishApplication(String sPackageId, String sSDPFile, String sCabFile) $$<SMS_WSUS_CONFIGURATION_MANAGER><08-06-2013
11:03:11.787+240><thread=3704 (0xE78)>
ERROR: Failed to publish sms client to WSUS, error = 0x80131509 $$<SMS_WSUS_CONFIGURATION_MANAGER><08-06-2013 11:03:11.803+240><thread=3704 (0xE78)>
It would seem obvious that this is because of a mismatch in versions between the WSUS server version on wsus.domain.local, compared to the UpdateServices UI on sccm.domain.local.
Is there a way around this, without having to upgrade the WSUS server to Server 2012?
Thanks for any thoughts you may have!

Not really. As mentioned though, even the separate WSUS server is probably overkill. In ConfigMgr, WSUS is used to handle the update catalog and that's it. Clients do *not* report status to the WSUS instance and do *not* download updates from the WSUS instance.
No management is ever done in WSUS.
So, in reality, once a month, clients connect to WSUS to download the delta update catalog (delta compared to what they currently have) which usually comes out to about a few hundred KB (yes KB, not MB) -- this download is done via BITS. The server also
syncs the catalog from the WSUS instance, via the SUP, in a similar fashion. If you are using SCEP, the frequency will be greater, but the deltas will be much smaller.
EULAs, as needed, are also stored in WSUS and accessed by clients -- these are also quite small only a select few updates requires them.
That's it. Standing up a dedicated WSUS instance means having a server sitting there doing almost nothing else.
If you are concerned about load on the site server, then you should create a separate site system that contains the MP, SUP (and WSUS instance), and DP. Then, for HA purposes, you can simply build a second site system with these three roles also and HA will
essentially be automatic (from a client functionality perspective).
Jason | http://blog.configmgrftw.com

SCCM 2012 R2 WSUS wsyncact error 0x8013141A

i have new servers with Server 2012 R2, SCCM 2012 R2, and SQL 2012 SP1 CU6. SCCM will not sync with WSUS. "Synchronize Software Updates" fails and no updates appear and the scheduled sync in "SUP Component Properties"\"Sync
Schedule" runs, the WSUS servers do not sync with their upstream servers. There are no errors in the WCM and WSUSCtrl logs. The wsyncmgr log has these errors:
Sync failed. Could not load file or assembly '5120 bytes loaded from wsyncact, Version 5.0.0.0, Culture=-neutral, PublicKeyToken=(alphanumeric string) or one of its dependencies. Strong name validation failed. ) Exception from HRESULT: )x8013141A). Source:
wsyncact
STATMSG; ID-6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=(servername) SITE=(site code) PID=2704 TID=5516 GMTDATE=(date/time) ISTR1="Could not load file or assembly 'updmgrclr, Version=5.0.7958.1000, Culture=neutral,
PublicKeyToken=(alphanumeric string)" or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)" ITR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8=""
ISTR9="" NUMATTRS=0
Sync failed. Will retry in 60 minues.
Moving the servers to an OU with no policies does not help. Setting registry entries to turn off strong name validation does not help.
I did find one post that said the ports in IIS and in SCCM need to match. My do, IIS and SCCM both have 8530/8531.
Suggestions?
Ben JohnsonWY

SOLVED. FINALLY!
Do an internet search for "Keith McGuinness" and "Strong name Validation Failed (Exception from HRESULT 0x8013141A)"
You need to create these two registry keys:
[HKLM\Software\Microsoft\StrongName\Verification\*,123adf9123]
[HKLM\Software\Wow6432Node\Microsoft\StrongName\Verification\*,123adf9123]
You need to do this key pair for each 0x8013141A error you have that has a unique PublicKeyToken. Note that the "*,123adf9123" is a key, not a DWORD or anything else. Also, you have to change 123adf9123 to the PublicKeyToken(s) showing in your
error messages within WSUS. You can then force a new sync by setting a sync time a couple minutes in the future with configure SUP under Administration\Sites.
Note: I did this on the site server.
Ben JohnsonWY

Patches missing in SCCM 2012

Hi,
We are using SCCM 2012 SP1 to deploy are pathes. Now we want to install kb2797052 but it is not in our Updates Repository in SCCM. When I check our WSUS server, it is in there. I've read a few threads about this issue telling to reinstall the SUP and
that this sometimes solves the problem but...
We have the problem in all of our 4 environments. Also other patches are missing like kb2553091...
All Classifications have been selected (though I see in WSUS drivers are not selected, in SCCM this classification does not exist).
For the products, we did not select everything, but all Windows OS products and Office are selected.
I could also see that in SCCM we have selected English and French, but in WSUS "download updates in all languages" is selected, even though WSUS was configured by SCCM at the time of installation.
Could it be that the language metadata is missing on certain patches and therefore not showing in SCCM? Can the language of a patch be checked in WSUS?
WiM

Hi,
I found this in my Wsyncmgr.log after Isync all the updates. KB2797052 has been superseded.
Skipped update e8b7a0b5-1350-414a-82ca-74b3a11d756b - Security Update for Microsoft Office 2010 (KB2553091), 64-Bit Edition because it was superseded
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 2012 - SUP

Similar Messages

Maybe you are looking for