SCCM 2012 CU3 Server Update

Hello,
I am trying to install the premade programs "SP1 Cumulative Update 3 - Server Update - CM1 - Cumulative Update 3 - server update install" on my servers. I am getting "Error: 0xBBB(3003)" when I try and run the install from the Software
Center. Looking up the error it is "ERROR_SPL_NO_STARTDOC", A StartDocPrinter call was not issued. I guess I don't have a clue what this means and why I am getting this on my servers.
I didn't modify the created packages.

Actually the server package is required for site servers and any computer that runs the SMS provider. Therefore you do not apply it to DPs.
You must have already installed CU3 on the Primary Site Server (if you already have the packages). You do not have to install anything else on your servers.
Just worry about your clients and any computer running the Admin Console..
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Similar Messages

  • SCCM 2012 CU3 / WSUS - Update files are being deleted

    We have been running this configuration since April of last year and haven't had any problems. 
    The problem is a majority of the window/security updates files in the WSUSContent folder are missing.  I have ran wsusutil /reset and it takes a day or so but it will successfully download the 80GB of missing files.  But after a few days they are
    once again missing.  We do run our EPP updates through WSUS and we have no problems with those.
    I have searched endlessly through the log files, I can see where it goes through and skips them due to being superseded. 
    Do not see any database or communication issues between SCCM and WSUS, per the wsyncmgr.log it sees the thousands of that are available from our WSUS server. 
    So, any suggestions as to what might be causing the update files to be deleted from the WSUSContent folder?
    We are running this on:
    Server 2012 / SCCM 2012 CU3 / WSUS for 2012

    So, just to make sure I understand.  Is that we should be deploying updates from the SCCM Configmgr? 
    If you want to use the integrate experience, then yes.
    but the problem is that a majority of updates are showing Downloaded = No when looking under All Software Updates
    You need to either manually initiate the download of updates or set up an Automatic Deployment Rule (ADR). Either will cause ConfigMgr to download the updates placing them into an update package (which in turn gets placed on a DP where the clients can access
    and download the updates).
    wsynclog shows the sync of the update catalog, i.e., the metadata, and not the actual update binaries.
    Jason | http://blog.configmgrftw.com

  • 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!)

  • Is there a way to change an existing SCCM 2012 site server intranet FQDN name to lowercase?

    Does anyone know if there is a way to change the intranet (not internet) FQDN name of an existing SCCM 2012 site server to all lowercase letters?  You used to be able to do this in SCCM 2007.

    I had a problem with WSUS updates not working via SCCM 2012 R2 during an operating system deployment. When examining the c:\Windows\WindowsUpdate.log I found the following errors:
    WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <****:8080;****:8080> Bypass List used : <(null)> Auth Schemes used : <>
    + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
    WARNING: GetConfig failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
    After a LONG time researching this error I found it was related to the fact we were using a WPAD proxy implementation and apparently this doesnt cope well with uppercase characters for the WSUS server URL. I changed our GPO to be using lowercase lettering
    but when examining the WindowsUpdate log again it still showed as being in uppercase. In the end I found that despite what your GPO setting says, this can get over written by the SCCM site server's own published WSUS location. You can check this by entering
    the following command:
    wmic /namespace:"\\root\CCM\SoftwareUpdates\WUAHandler" PATH CCM_UpdateSource
    Unfortunatelty in SCCM 2012 there is no GUI way to amend the intranet FQDN used for the WSUS location so I then turned to directly editing the database (which anyone will tell you is not recommended, but by this point i was DESPERATE!).
    In the end it solved all my troubles so if anyone finds themselves in this situation, you can fix it by going to the SCCM database and within the table 'WSUSServerLocations', change the WSUSServerName to be in lowercase letters.

  • How does WSUS work when an SCCM 2012 R2 server is newly installed? Should WSUS be installed and configured on same server?

    Let me clarify.
    We had a functional WSUS server delivering our updates to ours workstations. The location of the WSUS server was pushed out by Group policies.
    Later, an SCCM 2012 R2 installation was installed. The original WSUS server was removed. Now WSUS type services appear to be broken.
    I tried to start WSUS on the SCCM 2012 R2 server and it does not start. (I assume its not configured).
    I want to get WSUS running again but am not sure how to do this safely in conjunction with our SCCM 2012 R2 installation. Do I just reinstall WSUS on the SCCM server and configure? Or is there other preferred methods?
    I was not involved in SCCM's installation, so I do not know what was done.
    Geoff.

    Update functionality is provided via the Software Update Point
    https://technet.microsoft.com/en-us/library/gg712312.aspx
    ... which requires WSUS to be installed - it basically takes control of WSUS.
    Any existing group policies defining WSUS servers should be removed so that the SCCM client (which I assume is installed on computers already) can configure accordingly. Otherwise you will have group policy and SCCM client over writing one another to configure
    the update server

  • Is the distribution point role required on an SCCM 2012 site server?

    I am wondering if the distribution point role is required on an SCCM 2012 site server. 
    We have an installation of SCCM 2012 SP1 with a site server, and two remote DPs. 
    I would like to remove the DP role from the site server, and stand up another server (2012) at the same location, making it a DP and also have it hold the WSUS content.
    I was successful in creating the DP on the new server.  I distributed all of our packages to the new server. 
    I then removed the packages from the DP on the site server, and removed the DP role from the site server. 
    After making these changes, we lost the ability to deploy packages, either from the new DP server, or from the previously existing DPs that were at other locations. 
    Deployment status in the SCCM console showed that clients were “waiting for content”.
    I found that adding the DP role back to the site server, and distributing packages to it corrected the problem. 
    Deployment resumed after doing that.  Is it necessary to have packages on a DP on the site server? 
    We want to virtualize the server, and would like to make it as small as possible to facility restores.

    Hi,
    Have you checked the log file distmgr.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.

  • Boot an ESX 5.1 VM to my SCCM 2012 (WDS) server?

    Hi folks,
    I just got my SCCM 2012 server installed, configured a distribution point, published new boot.wim to distribution point.
    I am trying to test booting up a 'bare metal' ESXi 5.1 VM to my SCCM 2012 (WDS) server, but fails with attached error.
    Configuration Manager is looking for policy.
    Anyone have a suggestion?
    Thanks, romatlo

    Thank you so much for responding!  I must admit that this is my first install.  :)
    I could not find that option, so I deleted/recreated my task sequence, then found it as part of Deploy option.
    I deployed the task sequence to unknown computers but I still get that message and will not boot up correctly.
    I've pasted last part of my SMSPXE.log in case you see something definitive.
    I did not have my WDS server role installed when enabling PXE on my DP, maybe that messed me up.
    Thanks again, I may snapshot my VM here and start over on install if there is not a clue.
    <![LOG[Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
    ]LOG]!><time="22:34:31.229+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="libsmsmessaging.cpp:6346">
    <![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: device is in the database.]LOG]!><time="22:34:31.229+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
    <![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
    LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
    ]LOG]!><time="22:34:31.273+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="libsmsmessaging.cpp:6544">
    <![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: no advertisements found]LOG]!><time="22:34:31.273+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
    <![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: No boot action. Aborted.]LOG]!><time="22:34:31.319+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
    <![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: Not serviced.]LOG]!><time="22:34:31.319+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
    <![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
    LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
    ]LOG]!><time="22:34:33.422+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="libsmsmessaging.cpp:6544">
    <![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: no advertisements found]LOG]!><time="22:34:33.422+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">

  • [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 secondary server installation failing

    I am trying to install the SCCM 2012 secondary server remotely and when i check the configmgrsetup.log and i see below error. I tried to check the registry at HKLM\software\microsoft\sms and i see a site code as DRW but i had given a site code DFW. 
    I checked the permission on the servers, the OU everything seems to be fine, can someone please suggest:
    INFO: Attempting to load resource DLL... Configuration Manager Setup 8/23/2013 12:51:28 PM 16652 (0x410C)
    ERROR: Connection strings not initialized Configuration Manager Setup 8/23/2013 12:51:28 PM 11464 (0x2CC8)
    CSql Error: Cannot find data for connection type: , cannot get a connection. Configuration Manager Setup 8/23/2013 12:51:28 PM 11464 (0x2CC8)
    ERROR: Failed to connect to SQL Server 'master' db. Configuration Manager Setup 8/23/2013 12:51:28 PM 11464 (0x2CC8)
    INFO: Prerequisite rules for secondary site fresh installation are being run. Configuration Manager Setup 8/23/2013 12:51:28 PM 11464 (0x2CC8)
    INFO: File C:\Windows\smstsvc_test_1.exe does not exist. No zapping needed. Configuration Manager Setup 8/23/2013 12:51:28 PM 11464 (0x2CC8)
    INFO: test loop count:0. Configuration Manager Setup 8/23/2013 12:51:34 PM 11464 (0x2CC8)
    INFO: smstsvc_test_1 Return result <0> Configuration Manager Setup 8/23/2013 12:51:34 PM 11464 (0x2CC8)
    CWmiRegistry::WmiOpen: Failed to read key SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL on FTWEISSCCM12S1.eis.equifax.com Configuration Manager Setup 8/23/2013 12:52:26 PM 11464 (0x2CC8)
    CWmiRegistry::WmiOpen: Failed to read key SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL on FTWEISSCCM12S1.eis.equifax.com Configuration Manager Setup 8/23/2013 12:52:27 PM 11464 (0x2CC8)
    CWmiRegistry::GetValues: Failed to get values from SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL Configuration Manager Setup 8/23/2013 12:52:27 PM 11464 (0x2CC8)
    CWmiRegistry::GetValues: Failed to connect to registry on machine FTWEISSCCM12S1.eis.equifax.com. Error code: 2 Configuration Manager Setup 8/23/2013 12:52:28 PM 11464 (0x2CC8)
    INFO: Checking Installed SMS componants on:FTWEISSCCM12S1.eis.equifax.com. Configuration Manager Setup 8/23/2013 12:52:31 PM 11464 (0x2CC8)
    CWmiRegistry::WmiOpen: Failed to read key SOFTWARE\Microsoft\SMS\Setup on FTWEISSCCM12S1.eis.equifax.com Configuration Manager Setup 8/23/2013 12:52:32 PM 11464 (0x2CC8)
    CWmiRegistry::WmiOpen: Failed to read key SOFTWARE\Microsoft\SMS\Operations Management\SMS Server Role on FTWEISSCCM12S1.eis.equifax.com Configuration Manager Setup 8/23/2013 12:52:32 PM 11464 (0x2CC8)
    CWmiRegistry::WmiOpen: Failed to read key SOFTWARE\Microsoft\SMS\Providers\Sites on FTWEISSCCM12S1.eis.equifax.com Configuration Manager Setup 8/23/2013 12:52:32 PM 11464 (0x2CC8)
    INFO: File
    \\FTWEISSCCM12S1.eis.equifax.com\admin$\smstsvc_test_2.exe does not exist. No zapping needed. Configuration Manager Setup 8/23/2013 12:52:34 PM 11464 (0x2CC8)
    INFO: test loop count:0. Configuration Manager Setup 8/23/2013 12:53:12 PM 11464 (0x2CC8)
    INFO: smstsvc_test_2 Return result <1> Configuration Manager Setup 8/23/2013 12:53:13 PM 11464 (0x2CC8)
    INFO: File C:\Windows\smstsvc_test_3.exe does not exist. No zapping needed. Configuration Manager Setup 8/23/2013 12:53:14 PM 11464 (0x2CC8)
    INFO: test loop count:0. Configuration Manager Setup 8/23/2013 12:53:22 PM 11464 (0x2CC8)
    INFO: smstsvc_test_3 Return result <0> Configuration Manager Setup 8/23/2013 12:53:22 PM 11464 (0x2CC8)
    INFO: This is a local site system. There is no need to check for the Admin$ share. Configuration Manager Setup 8/23/2013 12:53:24 PM 11464 (0x2CC8)
    INFO: Checking Windows Cluster. Configuration Manager Setup 8/23/2013 12:53:27 PM 11464 (0x2CC8)
    CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e Configuration Manager Setup 8/23/2013 12:53:29 PM 11464 (0x2CC8)
    INFO: WMI namespace root\MSCluster not exists on FTWEISSCCM12S1.eis.equifax.com. Configuration Manager Setup 8/23/2013 12:53:29 PM 11464 (0x2CC8)
    INFO: File
    \\FTWEISSCCM12S1.eis.equifax.com\admin$\smstsvc_test_4.exe does not exist. No zapping needed. Configuration Manager Setup 8/23/2013 12:53:30 PM 11464 (0x2CC8)
    INFO: test loop count:0. Configuration Manager Setup 8/23/2013 12:54:08 PM 11464 (0x2CC8)
    INFO: smstsvc_test_4 Return result <7> Configuration Manager Setup 8/23/2013 12:54:08 PM 11464 (0x2CC8)
    INFO: File
    \\FTWEISSCCM12S1.eis.equifax.com\admin$\smstsvc_test_5.exe does not exist. No zapping needed. Configuration Manager Setup 8/23/2013 12:54:10 PM 11464 (0x2CC8)
    INFO: test loop count:0. Configuration Manager Setup 8/23/2013 12:54:48 PM 11464 (0x2CC8)
    INFO: smstsvc_test_5 Return result <7> Configuration Manager Setup 8/23/2013 12:54:48 PM 11464 (0x2CC8)
    INFO: File
    \\FTWEISSCCM12S1.eis.equifax.com\admin$\smstsvc_test_6.exe does not exist. No zapping needed. Configuration Manager Setup 8/23/2013 12:54:52 PM 11464 (0x2CC8)
    INFO: test loop count:0. Configuration Manager Setup 8/23/2013 12:55:30 PM 11464 (0x2CC8)
    INFO: smstsvc_test_6 Return result <0> Configuration Manager Setup 8/23/2013 12:55:30 PM 11464 (0x2CC8)
    INFO: FTWEISSCCM12S1.eis.equifax.com is a 64 bit operating system. Configuration Manager Setup 8/23/2013 12:55:35 PM 11464 (0x2CC8)

    I'm also unable to create Secondary site due above error in configuration setup log.
    INFO: Attempting to load resource DLL...    Configuration Manager Setup    23/Mar/15 3:11:26 PM    5020 (0x139C)
    ERROR: Connection strings not initialized    Configuration Manager Setup    23/Mar/15 3:11:26 PM    8752 (0x2230)
    CSql Error: Cannot find data for connection type: , cannot get a connection.    Configuration Manager Setup    23/Mar/15 3:11:26 PM    8752 (0x2230)
    ERROR: Failed to connect to SQL Server 'master' db.    Configuration Manager Setup    23/Mar/15 3:11:26 PM    8752 (0x2230)
    INFO: Prerequisite rules for secondary site fresh installation are being run.    Configuration Manager Setup    23/Mar/15 3:11:26 PM    8752 (0x2230)
    INFO: File C:\Windows\smstsvc_test_1.exe does not exist. No zapping needed.    Configuration Manager Setup    23/Mar/15 3:11:26 PM    8752 (0x2230)
    INFO: test loop count:0.    Configuration Manager Setup    23/Mar/15 3:11:33 PM    8752 (0x2230)
    INFO: smstsvc_test_1 Return result <0>    Configuration Manager Setup    23/Mar/15 3:11:33 PM    8752 (0x2230)
    CWmiRegistry::WmiOpen: Failed to read key SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL on    Configuration Manager Setup    23/Mar/15 3:11:36 PM    8752 (0x2230)
    CWmiRegistry::WmiOpen: Failed to read key SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL on    Configuration Manager Setup    23/Mar/15 3:11:36 PM    8752 (0x2230)
    CWmiRegistry::GetValues: Failed to get values from SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL    Configuration Manager Setup    23/Mar/15 3:11:36 PM    8752 (0x2230)
    CWmiRegistry::GetValues: Failed to connect to registry on machine  Error code: 2    Configuration Manager Setup    23/Mar/15 3:11:36 PM    8752 (0x2230)

  • Prestage content no longer working after SCCM 2012 R2 CU1 update

    I run SCCM 2012 R2 CU1 on a Windows 2008 R2 server.
    I upgraded to CU1 in June, and today is the first time I've attempted to pre-stage a package since then.  After pre-staging my package and getting the content out to the target DP, I went to properties of the DP, checked the box "Enable this
    distribution point for prestage content", then hit Ok.
    Next I went to distribute the content to the DP, however after going thru the wizard, nothing changes.  There is no pending status, waiting on prestage content, that I had seen in the past when doing this task.  I can go in and run the wizard
    again, and the target DP shows up in the list, like I'd never initiated the push before.
    Normal (non-prestaged) distributions work fine.
    In troubleshooting this, I also noticed that I looking at the site status of the target DP, there are no status message entries for since I upgraded to CU1 (for that matter, none of my DP's have any entries since CU1).  I did see a similar issue like
    this in the forums
    http://social.technet.microsoft.com/Forums/en-US/9491c2b1-37e6-46e3-9bb0-c5d673490d8a/component-status-not-updating-since-upgrade-from-sccm2012-sp1-cu3-to-sccm2012-r2?forum=configmanagergeneral but I don't have a backed up stat.mgr\retry inbox, it's empty.
    I think this is related to why I can no longer prestage content, but I can't seem to find a reason for it.  The fixes for R2 CU2 don't mention my issue here either
    Anyone else seeing this?
    Tony

    Hi,
    Please check SmsAdminUI.log and Smsprov.log after you distribute the content to the DP.
    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.

  • After SCCM 2012 R2 CU4 update Client won't report status message back

    We had SCCM 2012 R2 CU3, just updated it to CU4 (all site servers and clients) last week.
    Right after the clients received the CU4 update (no reboot), I saw these started popping up the event log:
    The ConfigMgr Client encountered a certificate for Management Point SCCM that could not be verified.
    I checked online and it has to do with trusted root key mismatch, but there was no site change. The only thing we did was upgrading from CU3 to CU4. 
    Right now the symptom is that all these clients do not report status messages back to the MP so we have no idea how our deployments would go.

    i am having what i think is a similar issue. i upgraded to CU4 and the only clients to report back in are my SCCM site server and my only DP server. no clients have reported in since. i checked a few clients and they did get the CU4 client update
    and installed it but they are not reporting back
    I have pretty much the same situation.
    A successfully upgrade to SCCM 2012 r2 cu4 on the primary site.
    Deployed the cu4 to a few computers which was successfully. Later I also deployed the cu4 to the primary site server and it turned out to be the only computer reporting back with the proper client version.
    There is no errors or warnings in the event logs which could explain this strange issue. As far as I can tell the clients is operational but they are just not reporting back with the proper client version. A quick look at the sccm client
    logs has also not revealed the root cause.
    Any ideas would be appreciated a lot.
    Per Dahl Christiansen

  • 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

  • Can I have an SCCM 2012 R2 server and a SCCM 2012 SP1 server in the same site?

    We are currently using SCCM 2012 SP1/MDT 2012 Update 1 to deploy Windows 7, and to migrate existing XP installs to Windows 7 (using the offline USMT functionality in MDT).  We are moving forward with Windows 8.1, and understand that
    we need to upgrade our SCCM infrastructure to SCCM 2012 R2/MDT 2013.  We also understand that this will cause us to lose the ability to migrate XP machines, since MDT 2013 uses a newer version of USMT that doesn’t support XP.
    What do we need to do to continue to support our XP migrations, and enable deployments of Windows 8.1?
    Can we have two SCCM servers in the same Site running different versions of SCCM? Do we need a separate site? 

    You don't explicitly need ConfigMgr 2012 R2 to support Win 8.1. SP1 CU3 will suffice although managing a few things like boot images is a little more difficult: http://blogs.technet.com/b/configmgrteam/archive/2013/10/21/how-to-enable-windows-8.1-deployment-in-sc-2012-configmgr-sp1-cu3.aspx
    You could create two separate site hierarchies, but that would be painful and involve tons of duplication. There would be other issues also if the systems are located on the same subnets and in the same AD forest.
    The best option is to get rid of XP. EOL is in less than 30 days!
    Next best is to stay on SP1 CU3 until you get rid of XP. I know that sucks, but keeping XP around is the root cause of this and many other coming issues in any organization wanting to keep it around.
    Jason | http://blog.configmgrftw.com

  • SCCM 2012 R2 CU2 Update - Need to update console or clients as well?

    Hi,
    I am going to be installing the following update onto out SCCM 2012 server:
    http://support.microsoft.com/kb/2970177/en-us
    I am not 100% sure but is there a need to update all installed consoles and/or all sccm clients after the CU2 installation?

    Site server, console and clients needs to be updated.
    Full installation guide : http://www.systemcenterdudes.com/sccm-2012-r2-cu2-installation-guide/

  • SCCM 2012 secondary server

    Hi All,
    I am trying to install secondary site server from primary site server. All the prerequisites like .NET 3.5, 4, RDC, BITS are installed. Primary site server name is added In the local admin on the server. But still the installation is getting failed.
    I got mcafee enabled on the machine. Is it blocking bootstrap file
    Log:
    ********************************************************************************  $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.412+0><thread=1F2C>
    Starting SMS_BOOTSTRAP.  $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.412+0><thread=1F2C>
    Microsoft System Center 2012 Configuration Manager v5.00 (Build 7804)  $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.412+0><thread=1F2C>
    Copyright (C) 2011 Microsoft Corp.  $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.412+0><thread=1F2C>
    Set current directory to E:\.  $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.412+0><thread=1F2C>
    INFO:Action:<Install>.  $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.412+0><thread=1F2C>
    Successfully read E:\SMS_BOOTSTRAP.ini.  $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.427+0><thread=1F2C>
    Started for the first time.  $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.427+0><thread=1F2C>
    Current time: Tue Mar 11 16:56:49 2014  $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.427+0><thread=1F2C>
    Looking for the .PKG file...  $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.427+0><thread=1F2C>
    Found E:\SMS_BOOTSTRAP.pkg.  $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.427+0><thread=1F2C>
    Elapsed time since startup: 0 days, 00 hours, 00 minutes, 00 seconds.  $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.427+0><thread=1F2C>
    Processing the .PKG file...  $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.427+0><thread=1F2C>
    Validating E:\SMS_BOOTSTRAP.pkg...  $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.427+0><thread=1F2C>
    E:\SMS_BOOTSTRAP.pkg passed validation check.  $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.427+0><thread=1F2C>
    There is enough disk space: 1574MB required, 952704MB available.  $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.427+0><thread=1F2C>
    Temp directory is E:\4n9i849i.TMP.  $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.443+0><thread=1F2C>
    Decompressing E:\SMS_BOOTSTRAP.pkg...  $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.443+0><thread=1F2C>
    Decompression successful.  $$<SMS_BOOTSTRAP><03-11-2014 16:57:05.669+0><thread=1F2C>
    Elapsed time since startup: 0 days, 00 hours, 00 minutes, 16 seconds.  $$<SMS_BOOTSTRAP><03-11-2014 16:57:05.669+0><thread=1F2C>
    Running SMS Setup...  $$<SMS_BOOTSTRAP><03-11-2014 16:57:05.669+0><thread=1F2C>
    Successfully parsed E:\4n9i849i.TMP\\SMSSETUP\install.map.  $$<SMS_BOOTSTRAP><03-11-2014 16:57:05.934+0><thread=1F2C>
    E:\4n9i849i.TMP\\SMSSETUP\install.map build number "7804" is correct.  $$<SMS_BOOTSTRAP><03-11-2014 16:57:05.934+0><thread=1F2C>
    Started "E:\4n9i849i.TMP\\SMSSETUP\bin\x64\SetupWPF.exe /script E:\SMS_BOOTSTRAP.ini /nouserinput" as PID 8016.  $$<SMS_BOOTSTRAP><03-11-2014 16:57:05.934+0><thread=1F2C>
    Waiting for PID 8016 to terminate...  $$<SMS_BOOTSTRAP><03-11-2014 16:57:05.934+0><thread=1F2C>
    PID 8016 exited with code 0.  $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.016+0><thread=1F2C>
    FATAL ERROR: SMS_SITE_COMPONENT_MANAGER is not running, setup must have failed, bootstrap procedure aborted! 
    $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.016+0><thread=1F2C>
    Deinstalling myself...  $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.016+0><thread=1F2C>
    Deleted E:\SMS_BOOTSTRAP.pkg.  $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.078+0><thread=1F2C>
    Deleted E:\SMS_BOOTSTRAP.ini.  $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.078+0><thread=1F2C>
    Deleted E:\SMS_BOOTSTRAP.EXE.  $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.078+0><thread=1F2C>
    Deleted temp directory <E:\4n9i849i.TMP>.  $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.359+0><thread=1F2C>
    Deinstalled the SMS_BOOTSTRAP service.  $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.359+0><thread=1F2C>
    Deinstallation complete.  $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.359+0><thread=1F2C>
    Bootstrap procedure unsuccessful.  $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.359+0><thread=1F2C>
    Stopping SMS_BOOTSTRAP...  $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.359+0><thread=1F2C>
    SMS_BOOTSTRAP stopped.  $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.359+0><thread=1F2C>
    ********************************************************************************  $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.359+0><thread=1F2C>
    ********************************************************************************  $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.078+0><thread=DD8>
    Starting SMS_BOOTSTRAP.  $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.093+0><thread=DD8>
    Microsoft System Center 2012 Configuration Manager v5.00 (Build 7804)  $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.093+0><thread=DD8>
    Copyright (C) 2011 Microsoft Corp.  $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.093+0><thread=DD8>
    Set current directory to E:\.  $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.093+0><thread=DD8>
    INFO:Action:<Install>.  $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.109+0><thread=DD8>
    Successfully read E:\SMS_BOOTSTRAP.ini.  $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.109+0><thread=DD8>
    Started for the first time.  $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.109+0><thread=DD8>
    Current time: Fri Mar 14 15:53:13 2014  $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.109+0><thread=DD8>
    Looking for the .PKG file...  $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.109+0><thread=DD8>
    Found E:\SMS_BOOTSTRAP.pkg.  $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.109+0><thread=DD8>
    Elapsed time since startup: 0 days, 00 hours, 00 minutes, 00 seconds.  $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.109+0><thread=DD8>
    Processing the .PKG file...  $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.109+0><thread=DD8>
    Validating E:\SMS_BOOTSTRAP.pkg...  $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.109+0><thread=DD8>
    E:\SMS_BOOTSTRAP.pkg passed validation check.  $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.125+0><thread=DD8>
    There is enough disk space: 1574MB required, 952700MB available.  $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.125+0><thread=DD8>
    Temp directory is E:\s3jvf81y.TMP.  $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.125+0><thread=DD8>
    Decompressing E:\SMS_BOOTSTRAP.pkg...  $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.125+0><thread=DD8>
    Decompression successful.  $$<SMS_BOOTSTRAP><03-14-2014 15:53:29.707+0><thread=DD8>
    Elapsed time since startup: 0 days, 00 hours, 00 minutes, 16 seconds.  $$<SMS_BOOTSTRAP><03-14-2014 15:53:29.816+0><thread=DD8>
    Running SMS Setup...  $$<SMS_BOOTSTRAP><03-14-2014 15:53:29.816+0><thread=DD8>
    Successfully parsed E:\s3jvf81y.TMP\\SMSSETUP\install.map.  $$<SMS_BOOTSTRAP><03-14-2014 15:53:30.066+0><thread=DD8>
    E:\s3jvf81y.TMP\\SMSSETUP\install.map build number "7804" is correct.  $$<SMS_BOOTSTRAP><03-14-2014 15:53:30.097+0><thread=DD8>
    Started "E:\s3jvf81y.TMP\\SMSSETUP\bin\x64\SetupWPF.exe /script E:\SMS_BOOTSTRAP.ini /nouserinput" as PID 5480.  $$<SMS_BOOTSTRAP><03-14-2014 15:53:30.113+0><thread=DD8>
    Waiting for PID 5480 to terminate...  $$<SMS_BOOTSTRAP><03-14-2014 15:53:30.113+0><thread=DD8>
    PID 5480 exited with code 0.  $$<SMS_BOOTSTRAP><03-14-2014 16:14:06.991+0><thread=DD8>
    FATAL ERROR: SMS_SITE_COMPONENT_MANAGER is not running, setup must have failed, bootstrap procedure aborted!  $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.022+0><thread=DD8>
    Deinstalling myself...  $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.022+0><thread=DD8>
    Deleted E:\SMS_BOOTSTRAP.pkg.  $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.084+0><thread=DD8>
    Deleted E:\SMS_BOOTSTRAP.ini.  $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.084+0><thread=DD8>
    Deleted E:\SMS_BOOTSTRAP.EXE.  $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.084+0><thread=DD8>
    Deleted temp directory <E:\s3jvf81y.TMP>.  $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.365+0><thread=DD8>
    Deinstalled the SMS_BOOTSTRAP service.  $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.365+0><thread=DD8>
    Deinstallation complete.  $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.365+0><thread=DD8>
    Bootstrap procedure unsuccessful.  $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.365+0><thread=DD8>
    Stopping SMS_BOOTSTRAP...  $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.365+0><thread=DD8>
    SMS_BOOTSTRAP stopped.  $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.365+0><thread=DD8>
    ********************************************************************************  $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.365+0><thread=DD8>
    Regards, Pratap

    Hi,
    What's the version of your SCCM 2012?
    If it is SCCM 2012 sp1 CU2, please have a look on the following KB.
    http://blogs.technet.com/b/configmgrteam/archive/2013/07/02/known-issue-secondary-site-installation-failure-with-cumulative-update-2.aspx
    Best Regards,
    Joyce Li
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

Maybe you are looking for