SCCM 2012 SP1 - Secondary SUP Sync Source Server Changed without intervention

Hi,
Recently I noticed that some of ours Secondary SUP's have stopped syncing. Looking at the logs I found that they cannot found SUP parent. Name resolution was OK, no firewall blocking traffic flow, SUP at Primary Site working normally, all replica SUP services
online.
Then I went to the Sync Settings at Site Components of the SUP replica and the value of the option "Synchronize from a upstream data source location (URL)" had been changed!
The URL of the upstream server has the correct server name, but the 8530 port is missing! The interesting fact is that I have other SUP replicas working normally with the correct upstream server name and port.
So, my question is: Since I've installed all the replicas SUP's with the same upstream SUP settings, they have been working normally until last week, how the settings are now wrong? The property is greyed out and I cannot change it back to the
correct parameter.
Is there any way to correct it without having to reinstall all the replicas SUPs?
Thanks!! 

Hi Joice,
Thanks for your response! Well, I followed your suggestion but it didn't work. After I removed the parent SUP, the Sync Settings of the SUP replicas were still greyed out.
I forgot to mention in my post that this problem appeared after I moved the SCCM database to another SQL server. I followed the right procedure and everything worked fine but the SUP. After I run the Perform site maintenance or reset this site I noticed
that SCCM removed the port 8530 from the parent SUP. All the replicas stopped syncing. Then I changed back the port through SCCM console - Site Components - and all worked fine. But 2 days later, the majority of my SUP replicas have the port 8530 removed from
Sync Settings and they cannot sync anymore, and here I am.
There's a cmdlet (Set-CMSoftwareUpdatePointComponent) I thought I could use, but it only works with R2.
So, I just reinstalled the Parent SUP, hoping that it could reconfigure replicas SUPs, but I think it's a long shot.

Similar Messages

  • SCCM 2012 SP1 is Running on SQL Server 2012 with NO CU

    I am working in an org that has SCCM 2012 SP1, it is and always has been running on SQL Server 2012 RTM, with NO CU installed it seems (judging by the file versions 11.0.2100.60, which are not the same as as documented here http://support.microsoft.com/kb/2703275).
    sigh..........
    So before I upgrade to R2 I will ensure I installed SP2 and CU3 onto SQL Server.
    However, I am concerned about WHY SCCM 2012 SP1 requires SQL Server 2012 CU2 as a minimum and what damage may have been done as a result of this configuration?
    Are there any actions that can be performed as remediation or health check?
    Can anyone speculate?

    However, I am concerned about WHY SCCM 2012 SP1 requires SQL Server 2012 CU2 as a minimum
    Because the Microsoft product group decided it that way. All supported SQL versions are listed here:
    http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSQLDBconfig
    Damage? Hard (impossible) to tell. You would have seen errors in various components if there were problems.
    Torsten Meringer | http://www.mssccmfaq.de

  • [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 SP1 Secondary Site installation Fails

    Hi.
    I have multiple secondary sites when i am  trying to install  new SCCM 2012 Secondary site server remotely but installation status shows a pending from last few days.
    1) SEC server have privilages on System managent container
    2) Primary site Server account and computer have local admin right on SEC server
    hman logs says the following error message
    Cannot get SQL Certificate from site xxx
    CheckParentSQLServerCertificate: Failed to get SQL certificate for site XXX
    1) Deleted the secondary site and reinstalled the site with different Site code but no luck
    2) Able to telnet 1433 and 4022 from both primary to secondary and vice versa
    3) SQL server Configuration Manager , TCP IP port was set to 1433.
    please let me know if any thing i am missing
    Thanks

    Hi Guys
    Exact same problem as described above:
    Been told to install SQL Express manually first, but even after that, we continued to get the same problem.
    The SQL Communication between the 2 sites doesn't seem to work.
    I noticed that the Primary's SQL Security Account doesn't get created on Primary DB, in the Database replication the link has not yet been created either.
    The "Exec spDrsSendSubscriptionInvalid 'Secondary 3 digit site code','Primary 3 digit site code','configuration data'" worked on 1 Secondary, but fails on all the rest.
    Uninstalling/Installing the Secondary doesn't work either.
    HMAN.LOG:
    Update site server active directory informtion into DB SMS_HIERARCHY_MANAGER 2013/07/28 09:51:12 AM 7964 (0x1F1C)
    CheckSQLServiceRestart : SQL Service hasn't been restart since last time we check, skip it. SMS_HIERARCHY_MANAGER 2013/07/28 09:51:12 AM 7964 (0x1F1C)
       Time to verify if the parent['PRI-SITECODE'] sql server certificate is still valid on site ['SEC-SITECODE'] sql server. SMS_HIERARCHY_MANAGER 2013/07/28 09:51:12 AM 7964 (0x1F1C)
    Cannot get SQL Certificate from Site 'PRI-SITECODE'. SMS_HIERARCHY_MANAGER 2013/07/28 09:51:12 AM 7964 (0x1F1C)
    CheckParentSQLServerCertificate: Failed to get SQL certificate for site PM2 SMS_HIERARCHY_MANAGER 2013/07/28 09:51:12 AM 7964 (0x1F1C)
    Any ideas would be appreciated.

  • SCCM 2012 SP1 with remote WSUS on Server 2012 and SQL Server 2012

    I am rebuilding my SCCM 2012 lab on Server 2012 R2 x64 OS now.
    I have 1 primary site, remote SQL server 2012, and remote WSUS server.
    Is the WSUS console still required on my primary site running server 2012? If so are the below the correct steps to get this working?
    Install Console on primary server:
    Go to Server Manager à Add Roles and features, Navigate to the features section.
    Remote Server Manager tools
    >Role Administration Tools
    --Select Windows Server Update Services Tools Only
    Are there any post hotfixes to install?
    Intalling WSUS full version on remote server:
    Go to Server Manager à Add Roles and features, Server Roles section.
    Windows Server Update Services
    Do I need to select this as well on the remote wsus server? >Role Administration Tools -Select Windows Server Update Services Tools Only
    Since my SQL server is on a remote server do I select the below only?
    Are there any post hotfixes to install?

    Hi,
    One Part of the question is already answered. The second part is: If you want to use a remote SQL Server you need to select exactly what you selected in your screenshot.
    Regards,
    Thomas
    Thomas Hanrath [MCT | Regional Lead Germany] |
    http://www.hanrath.de
    Microsoft Learning Blog |
    http://blog.microsoftlearning.de

  • SCCM 2012 R2 Secondary site server will support the DMZ Zone?

    We are planning for SCCM 2012 Migration, currently we have separate Primary server in DMZ.
    Kindly suggest what is the best method to deploy in the DMZ (separate primary or secondary or DP) because we have only 500 Client in DMZ.

    Hi,
    There is a blog talking about this error. You could try the method in the blog.
    To summarise, when installing SCCM 2012 SP1 secondary site on a pre-configured SQL 2012 instance regardless which SQL edition is being used, “NT AUTHORITY\SYSTEM” account needs to be given
    securityadmin and sysadmin rights. If SQL Express is used, there are few additional steps need to be carried out to configure the SQL TCP connection as documented in my previous blog:
    http://blog.tyang.org/2012/04/09/installing-sccm-2012-rtm-secondary-site-using-a-pre-installed-sql-express-2008-r2-instance/
    Installing SCCM 2012 SP1 Secondary Site with a Pre-Configured SQL 2012 Instance
    Note:
    Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
    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]

  • SCCM 2012 SP1 Beta Site System Roles Installation issues

    My apologies if this isn't the correct place to post this, but I didn't see any SCCM 2012 forums to post this. If there is a better place for this post, please direct me to the proper location. In the meantime this is my scenario:
    I am currently evaluating SCCM 2012 for our company. I have installed SCCM 2012 SP1 Beta on a test server running Server 2012 and SQL 2012. I am testing its ability to manage Windows 8. The server is a member of our company domain. I have enabled Active
    Directory Forest Discovery and CM has detected our forest and domain and set up boundaries automatically.
    I am trying to add the Application Catalog Web Service and Website Roles. When I start the wizard I get exclamation marks next to Active Directory forest and domain fields in the wizard. It shows our proper forest and domain names but won't proceed
    because it insists that the FQDN for my forest/domain is invalid. If I enter any other forest/domain name (e.g. yahoo.com, google.com, help-me.com) the exclamation marks clear and the wizard will proceed. SC seems to recognize our forest/domain name and
    denies it. Adding different suffixes (e.g. .net, .org, .local) changes nothing. I've even flipped our forest-domain name (e.g. "a-b.com" to "b-a.com": we have a "-" in our name) and it STILL denies it. If I add a prefix to the forest/domain name, the
    wizard is happy and lets me proceed (e.g. "domain.a-b.com") Did I miss something in initial setup? If this is a bug in the SP1 beta, how do I let anyone know about this? Any help/suggestions would be appreciated. Thanks.

    Since no one has answer this post, I recommend opening  a support case with CSS as they can work with you to solve this problem.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • 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

  • WSUS SP2; SCCM 2012 SP1; Sync failed: WSUS update source not found

    Hi,
    I have installed the Fresh SCCM 2012 SP1 and WSUS 3.0 SP2 + KB2720211 + KB2734608. However, still the Sync is getting failed. This is what I am getting in the wsyncmgr and WCM logs:
    wsyncmgr:
    Sync failed: WSUS update source not found on site PR1. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource
    SMS_WSUS_SYNC_MANAGER 1/9/2015 12:00:00 PM
    3668 (0x0E54)
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=3668 GMTDATE=Fri Jan 09 18:00:00.537 2015 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found
    on site PR1. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_WSUS_SYNC_MANAGER 1/9/2015 12:00:00 PM
    3668 (0x0E54)
    Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
    1/9/2015 12:00:00 PM 3668 (0x0E54)
    WCM:
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
    SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
    4176 (0x1050)
    Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER
    1/9/2015 11:19:03 AM 4176 (0x1050)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.
    SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
    4176 (0x1050)
    Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER
    1/9/2015 11:19:03 AM 4176 (0x1050)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.
    SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
    4176 (0x1050)
    Supported WSUS version not found SMS_WSUS_CONFIGURATION_MANAGER
    1/9/2015 11:19:03 AM 4176 (0x1050)
    STATMSG: ID=6607 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=4176 GMTDATE=Fri Jan 09 17:19:03.489 2015 ISTR0="DEF.XYZ.net" ISTR1="" ISTR2="" ISTR3=""
    ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
    4176 (0x1050)
    Remote configuration failed on WSUS Server.
    SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
    4176 (0x1050)
    STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=4176 GMTDATE=Fri Jan 09 17:19:03.515 2015 ISTR0="DEF.XYZ.net" ISTR1="" ISTR2="" ISTR3=""
    ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
    4176 (0x1050)
    I have used the default port numbers 80 and 443 still the sync is failing. Please provide your advise to fix this issue.
    Regards,
    Malwinder

    WCM:
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
    It's not only a matter of installing the console, but also those hotfixes on a remote server ...
    Torsten Meringer | http://www.mssccmfaq.de

  • 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

  • Procedure performing a "Retry Secondary Site" Operation in SCCM 2012 R2 Secondary Server

    Dear Brother,
    My SCCM 2012 R2 Secondary Site Server, unfortunately crashed and required to be restored, doing this I end up performing a "Retry Secondary Site Operation.
    One by one I am clearing out the errors but there are few remaining errors on the prerequisite checks:
    1.[Failed]:The logon account for the SQL Server service cannot be a local user account, NT SERVICE\<sql service name> or LOCAL SERVICE.  You must configure the SQL Server service to use a valid domain account, NETWORK SERVICE, or LOCAL SYSTEM.
    Actions Done: SQL Related Services use Logon As Domain Account "Microsoft-Domain\BillAdmin" , but still the above message still appears in the logs.
    Actions Done: None
    2.[Failed]:The collation of the site database does not match the collation of the parent site's database.  All sites in a hierarchy must use the same database collation.
    3.[Failed]:The site server might be unable to publish to Active Directory. The computer account for the site server must have Full Control permissions to the System Management container in its Active Directory domain. You can ignore this warning if you have
    manually verified these permissions. For more information about your options to configure required permissions, see
    http://go.microsoft.com/fwlink/p/?LinkId=233190.
    Actions Done: None, as this machine is previously a working Secondary site for 1 Year already. So I do not suspect anything from the current related configuration.
    4.[Failed]: Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions on the SQL Server instance selected for site database installation, or the SQL Server instance could not be contacted to verify permissions.
    Setup cannot continue.
    Action Taken:  Domain Account "Microsoft-Domain\BillAdmin" has a
    Sysadmin roles and actually all the check boxes are chosen to acquire all SQL account roles" 
    5. [Failed]:Prerequisite checks complete with failure - check ConfigMgrPrereq.log
    in the root of the primary site server system drive.
    6[Failed]:Unable to complete secondary site server installation - check ConfigMgrSetup.log in the root of the secondary site server system drive.
    ConfigMgrPrereq.log-Start
    ?<12-27-2014 23:39:35> ********************************************
    ?<12-27-2014 23:39:35> ******* Start Prerequisite checking. *******
    ?<12-27-2014 23:39:35> ********************************************
    ?<12-27-2014 23:39:35> Commandline :
    "E:\Program Files\Microsoft Configuration Manager\bin\x64\smsexec.exe"
    ?<12-27-2014 23:39:35> Check Type: Secondary site
     Site Server: SecondarySite2.microsoft.com,
     SQL Server: SecondarySite2.microsoft.com,
     SQL Named Instance: MSSQLSERVER,
     Install Folder: E:\Program Files\Microsoft Configuration Manager\,
     Setup Source Folder: E:\Source\SCCM2012-R2
    ?<12-27-2014 23:39:35> INFO: Executing prerequisite functions...
    ?<12-27-2014 23:39:35> ===== INFO: Prerequisite Type & Server: SITE_SEC:SecondarySite2.microsoft.com =====
    ?<12-27-2014 23:39:35> <<<RuleCategory: Access Permissions>>>
    ?<12-27-2014 23:39:35> <<<CategoryDesc: Checking access permissions...>>>
    ?<12-27-2014 23:39:35> INFO: CheckLocalSys is Admin of <SecondarySite2.microsoft.com>.
    ?<12-27-2014 23:39:43> SecondarySite2.microsoft.com;    Site server computer account administrative rights;    Passed
    ?<12-27-2014 23:39:43> <<<RuleCategory: System Requirements>>>
    ?<12-27-2014 23:39:43> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
    ?<12-27-2014 23:39:43> INFO: Check Lanman service: <SecondarySite2.microsoft.com>.
    ?<12-27-2014 23:39:44> SecondarySite2.microsoft.com;    Check Server Service is running;    Passed
    ?<12-27-2014 23:39:45> INFO: OS version:601, ServicePack:1.
    ?<12-27-2014 23:39:46> INFO: Target computer is a Windows server.
    ?<12-27-2014 23:39:46> SecondarySite2.microsoft.com;    Unsupported site server operating system version for Setup;    Passed
    ?<12-27-2014 23:39:46> SecondarySite2.microsoft.com;    Domain membership;    Passed
    ?<12-27-2014 23:39:47> INFO: Free disk space on target
    \\SecondarySite2.microsoft.com\E$\. = 83157 MB
    ?<12-27-2014 23:39:47> SecondarySite2.microsoft.com;    Free disk space on site server;    Passed
    ?<12-27-2014 23:39:47> SecondarySite2.microsoft.com;    Pending system restart;    Passed
    ?<12-27-2014 23:39:48> INFO: The server SecondarySite2.microsoft.com is not read-only domain controller.
    ?<12-27-2014 23:39:48> SecondarySite2.microsoft.com;    Read-Only Domain Controller;    Passed
    ?<12-27-2014 23:39:48> INFO: Check FQDN Length for site server: <SecondarySite2.microsoft.com>.
    ?<12-27-2014 23:39:48> SecondarySite2.microsoft.com;    Site Server FQDN Length;    Passed
    ?<12-27-2014 23:39:48> <<<RuleCategory: Dependent Components>>>
    ?<12-27-2014 23:39:48> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
    ?<12-27-2014 23:39:48> SecondarySite2.microsoft.com;    Microsoft XML Core Services 6.0 (MSXML60);    Passed
    ?<12-27-2014 23:39:49> SecondarySite2.microsoft.com;    Microsoft Remote Differential Compression (RDC) library registered;    Passed
    ?<12-27-2014 23:39:49> INFO: Checking Windows Installer version on SecondarySite2.microsoft.com.
    ?<12-27-2014 23:39:50> INFO: Path of Windows Installer is <\\SecondarySite2.microsoft.com\C$\Windows\system32\msi.dll>.
    ?<12-27-2014 23:39:51> INFO: Msi.dll version is: <5.0.7601.17807> .
    ?<12-27-2014 23:39:51> SecondarySite2.microsoft.com;    Microsoft Windows Installer;    Passed
    ?<12-27-2014 23:39:51> INFO: Start Checking InstallSQLExpress on site server: SecondarySite2.microsoft.com, SQL Server instance MSSQLSERVER
    ?<12-27-2014 23:39:51> INFO: SQL Server Express installation was not selected.
    ?<12-27-2014 23:39:51> SecondarySite2.microsoft.com;    SQL Server Express on Secondary Site;    Passed
    ?<12-27-2014 23:39:52> SecondarySite2.microsoft.com;    Existing Configuration Manager server components on site server;    Passed
    ?<12-27-2014 23:39:52> SecondarySite2.microsoft.com;    Firewall exception for SQL Server (stand-alone primary site);    Passed
    ?<12-27-2014 23:39:52> INFO: SQL Server computer <SecondarySite2.microsoft.com>
    ?<12-27-2014 23:39:52> INFO: SQL Server named instance <MSSQLSERVER>
    ?<12-27-2014 23:39:53> SecondarySite2.microsoft.com;    SQL Server service running account;    Error;    The logon account for the SQL Server service cannot be a local user account, NT SERVICE\<sql service
    name> or LOCAL SERVICE.  You must configure the SQL Server service to use a valid domain account, NETWORK SERVICE, or LOCAL SYSTEM.
    ?<12-27-2014 23:39:53> INFO: SQL Server computer <SecondarySite2.microsoft.com>
    ?<12-27-2014 23:39:53> INFO: SQL Server named instance <MSSQLSERVER>
    ?<12-27-2014 23:39:53> INFO: Cannot connect to registry key.
    ?<12-27-2014 23:39:53> SecondarySite2.microsoft.com;    Dedicated SQL Server instance;    Passed
    ?<12-27-2014 23:39:53> INFO: CheckSQLCollationSecondary
    ?<12-27-2014 23:39:53> INFO: Collation on <PrimarySite2DB.microsoft.com> <SQL_Latin1_General_CP1_CI_AS>
    ?<12-27-2014 23:41:27> ERROR: failed to get collation from secondary site
    ?<12-27-2014 23:41:27> SecondarySite2.microsoft.com;    Parent/child database collation;    Error;    The collation of the site database does not match the collation of the parent site's database.  All
    sites in a hierarchy must use the same database collation.
    ?<12-27-2014 23:41:27> INFO: Checking .NET framework versions 3.5...
    ?<12-27-2014 23:41:28> INFO: .NET is installed
    ?<12-27-2014 23:41:28> SecondarySite2.microsoft.com;    Minimum .NET Framework version for Configuration Manager site server;    Passed
    ?<12-27-2014 23:41:28> INFO: Skipping check for .NET version, user did not select to install SQL Server Express for Secondary Site.
    ?<12-27-2014 23:41:28> SecondarySite2.microsoft.com;    Minimum .NET Framework version for SQL Server Express edition installation for Configuration Manager Secondary Site;    Passed
    ?<12-27-2014 23:41:28> INFO: CheckInstallSourceVersion <E:\Source\SCCM2012-R2>
    ?<12-27-2014 23:41:29> SecondarySite2.microsoft.com;    Setup Source Version;    Passed
    ?<12-27-2014 23:41:29> INFO:CheckInstallSourcePath <SecondarySite2.microsoft.com>
    ?<12-27-2014 23:42:14> SecondarySite2.microsoft.com;    Setup Source Folder;    Passed
    ?<12-27-2014 23:42:14> INFO: Enter CheckSecSiteSqlOnSameMachine.
    ?<12-27-2014 23:42:14> INFO: Target secondary site Machine <SecondarySite2.microsoft.com>
    ?<12-27-2014 23:42:14> INFO: SQL Server computer <SecondarySite2.microsoft.com>
    ?<12-27-2014 23:42:14> SecondarySite2.microsoft.com;    SQL Server on the Secondary Site Computer;    Passed
    ?<12-27-2014 23:42:14> INFO:CheckSupportedFQDNFormat <SecondarySite2.microsoft.com>
    ?<12-27-2014 23:42:15> INFO: NetBIOS <SECONDARYSITE2>
    ?<12-27-2014 23:42:15> SecondarySite2.microsoft.com;    Primary FQDN;    Passed
    ?<12-27-2014 23:42:15> INFO:CheckMachineAccountHasADAccess <SecondarySite2.microsoft.com>
    ?<12-27-2014 23:42:40> ERROR: Site server does not have create child permission on AD 'System Management'
    ?<12-27-2014 23:42:40> WARN: Site server does not have delete child permission on AD 'System Management'
    ?<12-27-2014 23:42:40> SecondarySite2.microsoft.com;    Verify site server permissions to publish to Active Directory.;    Warning;    The site server might be unable to publish to Active Directory. The computer
    account for the site server must have Full Control permissions to the System Management container in its Active Directory domain. You can ignore this warning if you have manually verified these permissions. For more information about your options to configure
    required permissions, see
    http://go.microsoft.com/fwlink/p/?LinkId=233190.
    ?<12-27-2014 23:42:40> INFO:CheckRemoteWMIConnection <SecondarySite2.microsoft.com>
    ?<12-27-2014 23:42:48> SecondarySite2.microsoft.com;    Remote Connection to WMI on Secondary Site;    Passed
    ?<12-27-2014 23:42:48> INFO: Check required collation of Sql Server.
    ?<12-27-2014 23:42:48> INFO: LangID <409>
    ?<12-27-2014 23:42:48> INFO: NOT primary site or CAS install, skipping check for reqired collation of SQL Server.
    ?<12-27-2014 23:42:48> SecondarySite2.microsoft.com;    Required SQL Server Collation;    Passed
    ?<12-27-2014 23:42:48> ===== INFO: Prerequisite Type & Server: SQL:SecondarySite2.microsoft.com =====
    ?<12-27-2014 23:42:48> <<<RuleCategory: Access Permissions>>>
    ?<12-27-2014 23:42:48> <<<CategoryDesc: Checking access permissions...>>>
    ?<12-27-2014 23:42:48> INFO:RemoteCheckAdminOnSQL <SecondarySite2.microsoft.com>, SQL Server <SecondarySite2.microsoft.com>
    ?<12-27-2014 23:44:33> SecondarySite2.microsoft.com;    SQL Server sysadmin rights;    Error;    Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions
    on the SQL Server instance selected for site database installation, or the SQL Server instance could not be contacted to verify permissions. Setup cannot continue.
    ?<12-27-2014 23:44:33> ===== INFO: Prerequisite Type & Server: MP:SecondarySite2.microsoft.com =====
    ?<12-27-2014 23:44:33> <<<RuleCategory: Access Permissions>>>
    ?<12-27-2014 23:44:33> <<<CategoryDesc: Checking access permissions...>>>
    ?<12-27-2014 23:44:33> SecondarySite2.microsoft.com;    Administrative share (Site system);    Passed
    ?<12-27-2014 23:44:33> INFO:CheckSiteSystemtoSQLConnectivity <SecondarySite2.microsoft.com>
    ?<12-27-2014 23:44:33> INFO: Installing secondary site, skipping SQL Server connectivity check.
    ?<12-27-2014 23:44:33> SecondarySite2.microsoft.com;    Site System to SQL Server Communication;    Passed
    ?<12-27-2014 23:44:33> <<<RuleCategory: System Requirements>>>
    ?<12-27-2014 23:44:33> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
    ?<12-27-2014 23:44:33> INFO: The rule 'Check Server Service is running' has been run on server 'SecondarySite2.microsoft.com', skipped.
    ?<12-27-2014 23:44:34> INFO: OS version:601, ServicePack:1.
    ?<12-27-2014 23:44:35> INFO: Target computer is a Windows server.
    ?<12-27-2014 23:44:35> SecondarySite2.microsoft.com;    Unsupported management point operating system version for Setup;    Passed
    ?<12-27-2014 23:44:35> INFO: The rule 'Domain membership' has been run on server 'SecondarySite2.microsoft.com', skipped.
    ?<12-27-2014 23:44:36> INFO: Windows Cluster not found on SecondarySite2.microsoft.com.
    ?<12-27-2014 23:44:36> SecondarySite2.microsoft.com;    Windows Failover Cluster;    Passed
    ?<12-27-2014 23:44:36> INFO: The rule 'Pending system restart' has been run on server 'SecondarySite2.microsoft.com', skipped.
    ?<12-27-2014 23:44:36> <<<RuleCategory: Dependent Components>>>
    ?<12-27-2014 23:44:36> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
    ?<12-27-2014 23:44:36> INFO: The rule 'Microsoft XML Core Services 6.0 (MSXML60)' has been run on server 'SecondarySite2.microsoft.com', skipped.
    ?<12-27-2014 23:44:36> SecondarySite2.microsoft.com;    IIS service running;    Passed
    ?<12-27-2014 23:45:35> INFO: CheckWebSvcExtnRemote, result:<7>.
    ?<12-27-2014 23:45:35> SecondarySite2.microsoft.com;    BITS installed;    Passed
    ?<12-27-2014 23:47:00> INFO: CheckWebSvcExtnRemote, result:<7>.
    ?<12-27-2014 23:47:01> WARN: BITS Service is not running on SecondarySite2.microsoft.com.
    ?<12-27-2014 23:47:01> SecondarySite2.microsoft.com;    BITS enabled;    Passed
    ?<12-27-2014 23:47:01> SecondarySite2.microsoft.com;    IIS HTTPS Configuration for management point;    Passed
    ?<12-27-2014 23:47:01> INFO: Stand-alone primary site or secondary site. Skip checking firewall settings for SQL Server
    ?<12-27-2014 23:47:01> SecondarySite2.microsoft.com;    Firewall exception for SQL Server for management point;    Passed
    ?<12-27-2014 23:47:01> SecondarySite2.microsoft.com;    Administrative rights on management point;    Passed
    ?<12-27-2014 23:47:01> INFO:CheckV4ClientNotInstalled <SecondarySite2.microsoft.com>
    ?<12-27-2014 23:47:45> SecondarySite2.microsoft.com;    Client Version on Management Point Computer;    Passed
    ?<12-27-2014 23:47:45> ===== INFO: Prerequisite Type & Server: DP:SecondarySite2.microsoft.com =====
    ?<12-27-2014 23:47:45> <<<RuleCategory: Access Permissions>>>
    ?<12-27-2014 23:47:45> <<<CategoryDesc: Checking access permissions...>>>
    ?<12-27-2014 23:47:45> <<<RuleCategory: System Requirements>>>
    ?<12-27-2014 23:47:45> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
    ?<12-27-2014 23:47:47> SecondarySite2.microsoft.com;    Unsupported distribution point operating system version for Setup;    Passed
    ?<12-27-2014 23:47:47> INFO: The rule 'Domain membership' has been run on server 'SecondarySite2.microsoft.com', skipped.
    ?<12-27-2014 23:47:47> INFO: The rule 'Windows Failover Cluster' has been run on server 'SecondarySite2.microsoft.com', skipped.
    ?<12-27-2014 23:47:47> INFO: The rule 'Pending system restart' has been run on server 'SecondarySite2.microsoft.com', skipped.
    ?<12-27-2014 23:47:47> <<<RuleCategory: Dependent Components>>>
    ?<12-27-2014 23:47:47> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
    ?<12-27-2014 23:47:47> SecondarySite2.microsoft.com;    Microsoft XML Core Services 6.0 (MSXML60) for distribution point;    Passed
    ?<12-27-2014 23:47:47> INFO: The rule 'IIS service running' has been run on server 'SecondarySite2.microsoft.com', skipped.
    ?<12-27-2014 23:47:47> SecondarySite2.microsoft.com;    IIS HTTPS Configuration for distribution point;    Passed
    ?<12-27-2014 23:47:47> SecondarySite2.microsoft.com;    Administrative rights on distribution point;    Passed
    ?<12-27-2014 23:47:48> ***************************************************
    ?<12-27-2014 23:47:48> ******* Prerequisite checking is completed. *******
    ?<12-27-2014 23:47:48> ***************************************************
    ?<12-27-2014 23:47:48> INFO: Updating Prerequisite checking result into the registry
    ?<12-27-2014 23:47:48> INFO: Connecting to SecondarySite2.microsoft.com registry
    ?<12-27-2014 23:47:50> INFO: Setting registry values
    ConfigMgrPrereq.log-End
    Well my question is what would be the best solutions as it bugs me for days now.
    Regards,

    Hello,
    ?<12-27-2014 23:44:33> SecondarySite2.microsoft.com;   
    SQL Server sysadmin rights;    Error;   
    Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions on the SQL Server instance selected for site database installation, or the SQL Server instance could not be contacted to verify permissions.
    Setup cannot continue.
    Did you install SQL server with a local account?
    ?<12-27-2014 23:41:27> SecondarySite2.microsoft.com;   
    Parent/child database collation;    Error;   
    The collation of the site database does not match the collation of the parent site's database. 
    All sites in a hierarchy must use the same database collation.
    Try this blog:
    http://jthys.wordpress.com/2012/04/02/sccm-2012-required-sql-server-collation/
    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
    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]

  • WSUS 4.0 and SCCM 2012 SP1 Sync Errors

    SCCM 2012 SP1 is installed on a Windows 2012 Std server with the WSUS 4.0 Role installed.
    All other links I have found list a 2008 R2 Server with WSUS 3.0 SP2 hence all the "fixes" revolve around hot fixes and patches/settings for WSUS 3.0 or 2008 R2 systems.
    WSUS is set for port 8530/8531
    SCCM SUP is set for ports 8530/8531
    Both are on same machine (single site SCCM 2012 SP1 System)
    What does Bad Configuration, SUPs present but no default SUP
    mean and how do I fix it?
    Recent entry in my WCM.LOG states:
    SCF change notification triggered.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.401+420><thread=6052 (0x17A4)>
    Populating config from SCF  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.454+420><thread=6052 (0x17A4)>
    Setting new configuration state to 1 (WSUS_CONFIG_PENDING)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.481+420><thread=6052 (0x17A4)>
    Changes in active SUP list detected. New active SUP List is:~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.489+420><thread=6052 (0x17A4)>
        SUP0: SCCM2012.xxdomainnamexx.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

    Here is my WCM Log from this mornings "re-attempt"
    Trigger event array index 0 ended.  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:22.156+420><thread=5540 (0x15A4)>
    SCF change notification triggered.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.179+420><thread=5540 (0x15A4)>
    Populating config from SCF  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.181+420><thread=5540 (0x15A4)>
    Setting new configuration state to 1 (WSUS_CONFIG_PENDING)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.194+420><thread=5540 (0x15A4)>
    No SUPs are present  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.199+420><thread=5540 (0x15A4)>
    Default SUP not specified  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.220+420><thread=5540 (0x15A4)>
    Setting new configuration state to 0 (WSUS_CONFIG_NONE)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.224+420><thread=5540 (0x15A4)>
    Waiting for changes for 24 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.226+420><thread=5540 (0x15A4)>
    Trigger event array index 0 ended.  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:37.356+420><thread=5540 (0x15A4)>
    SCF change notification triggered.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.388+420><thread=5540 (0x15A4)>
    Populating config from SCF  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.493+420><thread=5540 (0x15A4)>
    Setting new configuration state to 1 (WSUS_CONFIG_PENDING)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.541+420><thread=5540 (0x15A4)>
    Changes in active SUP list detected. New active SUP List is:~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.543+420><thread=5540 (0x15A4)>
        SUP0: SCCM2012.MORTONGENERAL.ORG, group = , nlb = ~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.546+420><thread=5540 (0x15A4)>
    Updating active SUP groups...~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.550+420><thread=5540 (0x15A4)>
    Default SUP not specified  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.553+420><thread=5540 (0x15A4)>
    Setting new configuration state to 0 (WSUS_CONFIG_NONE)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.559+420><thread=5540 (0x15A4)>
    Waiting for changes for 24 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.562+420><thread=5540 (0x15A4)>
    Trigger event array index 1 ended.  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.593+420><thread=5540 (0x15A4)>
    File notification triggered.  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.596+420><thread=5540 (0x15A4)>
    File notification triggered WCM Inbox.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:47.611+420><thread=5540 (0x15A4)>
    Waiting for changes for 24 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:47.614+420><thread=5540 (0x15A4)>
    Trigger event array index 1 ended.  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:47.617+420><thread=5540 (0x15A4)>
    File notification triggered.  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:47.620+420><thread=5540 (0x15A4)>
    File notification triggered WCM Inbox.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:52.634+420><thread=5540 (0x15A4)>
    Waiting for changes for 24 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:52.637+420><thread=5540 (0x15A4)>
    Trigger event array index 0 ended.  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:52.640+420><thread=5540 (0x15A4)>
    SCF change notification triggered.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.761+420><thread=5540 (0x15A4)>
    Populating config from SCF  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.798+420><thread=5540 (0x15A4)>
    Waiting for changes for 24 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.813+420><thread=5540 (0x15A4)>
    Trigger event array index 1 ended.  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.823+420><thread=5540 (0x15A4)>
    File notification triggered.  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.826+420><thread=5540 (0x15A4)>
    File notification triggered WCM Inbox.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:02.840+420><thread=5540 (0x15A4)>
    Waiting for changes for 23 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:02.843+420><thread=5540 (0x15A4)>
    Trigger event array index 1 ended.  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:02.846+420><thread=5540 (0x15A4)>
    File notification triggered.  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:02.849+420><thread=5540 (0x15A4)>
    File notification triggered WCM Inbox.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:07.863+420><thread=5540 (0x15A4)>
    Waiting for changes for 23 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:07.866+420><thread=5540 (0x15A4)>
    Wait timed out after 23 minutes while waiting for at least one trigger event.  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 08:15:30.913+420><thread=5540 (0x15A4)>
    Timed Out...~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 08:15:40.917+420><thread=5540 (0x15A4)>
    Default SUP not specified  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 08:15:40.920+420><thread=5540 (0x15A4)>
    Waiting for changes for 60 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 08:15:40.923+420><thread=5540 (0x15A4)>
    Wait timed out after 60 minutes while waiting for at least one trigger event.  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 09:15:31.041+420><thread=5540 (0x15A4)>
    Timed Out...~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 09:15:41.045+420><thread=5540 (0x15A4)>
    Default SUP not specified  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 09:15:41.048+420><thread=5540 (0x15A4)>
    Waiting for changes for 60 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 09:15:41.051+420><thread=5540 (0x15A4)>
    Randall

  • Windows 8.1 system with new Office 2013 install not pulling down any Office 2013 updates from my SCCM 2012 SP1 server

    Hi,
    I've just setup a new Windows 8.1 system and added to my SCCM 2012 SP1 server and all is good and it pulled down all the correct Windows updates and pulls down automatically the FEP updates that are distributed from SCCM 2012 daily. 
    I just installed Office 2013 on this system and have activated it as necessary.  The problem is that the system doesn't seem to be pulling down any of the Office 2013 updates that have distributed thru SCCM.  I have other systems with
    Office 2013 installed and they have pulled down Office 2013 updates in the past when I published them.
    If I look at the Office 2013 updates in the SCCM console software section, I can see that for example it shows that Office 2013 SP1 (x86) is needed by one system and installed on 8 other systems and shows as downloaded and deployed.
    I've restarted the new system multiple times and also tried to force a software update check from the Configuration Manager applet but nothing seems to happen.
    What can I check to try and determine what the problem is?
    Thanks in advance,
    Nick

    Yes, the 8.1 system is a member of collection where the update deployment is targeted.
    Are there any specific logs I should check in the client?  If I check the WindowsUpdate.log I can see messages about the machine pulling down the FEP updates but that's all it appears to be doing.
    in CCM\logs, focus on the updatehandler and updatedeployment, to begin with
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • Service Manager 2012R2 - Hotfix for Service Manager 2012 SP1 secondary Management server

    Can the hotfix for the issue described here -
    http://blogs.technet.com/b/servicemanager/archive/2013/04/22/service-manager-2012-sp1-secondary-management-server-cannot-set-availability-on-a-health-service-that-doesn-t-exist.aspx 
    , be applied to a 2012R2 Service Manager environment? 
    My dilemma; In a Service Manager 2012 SP1 environment, I installed a secondary mgmt server, promoted it, then upgraded to R2. This R2 Primary mgmt server has the error described in the TechNet blog. 
    The reason this was done, the original primary mgmt server (2012 SP1) resided on the same server as the Portal. This original primary is still at 2012 SP1 with the System Center services disabled.
    Again, can the hotfix for Service Manager 2012 SP1 secondary mgmt servers be applied to a Primary mgmt server (or environment, however the hotfix is run) server Service Manager 2012 R2? 
    Thank you,
    Brian VanDam
    BVAN in SoCol

    Hi,
    Hmm, you should probably log a case for this, but my first thought here would be to install a new SCSM 2012 R2 server and promote that one to the new Primary server, then remove the old ones.
    Regards
    //Anders
    Anders Asp | Lumagate | www.lumagate.com | Sweden | My blog: www.scsm.se

Maybe you are looking for