WSUS Keeps failing on SCCM 2012 R2

Hello all
I am hoping I could get some help with this strange issue:
I am trying to install WSUS on my sccm server prior to the software update point. This what I have done so far:<o:p></o:p>
 In server manger I select to install the WSUS role>Click next (I notice there is a feature option to install Windows internal database)
I unchecked this option because I am using my existing sql server for the WSUS instance. I cant seem to find anything that say tells me that when installing sccm 2012 on Windows Server 2012 and you are using the sql database instance for WSUS to do xyz. In
my case as mentioned before  unchecked the Windows Internal Database Feature. Then under Roles Services there are three option: WID Database, WSUS Services, Database. I chose WSUS Services and Database. On the next page I defined my source for the downloads,
then the next page DB Instance I entered the instance of the sql server which in my case is also on my sccm 2012 server VMSCCM is the name> Click Check Connection and that was successfully connected to the server. <o:p></o:p>
So here is where everything goes wrong. I then select to install everything at the confirmation page. reboot the server<o:p></o:p>
once rebooted I open server manager and there is message that says Launch post - installation configuration. I then get the following error "Post-deployment
configuration failed see log below is a image for the log located in c:\users\username\appdata\local\temp\tmpFC3D\
<o:p></o:p>
<o:p></o:p>
Phil Balderos

I had similar issues with the WSUS integration with ConfigMgr 2012 R2. I also have the WSUS DB hosted on the same SQL instance where ConfigMgr 2012 installs it's database.
I found WSUS would not function correctly until I added the SYSTEM account to the WSUS Administrators group under Local Users and Groups:
Hope this helps! :-)
Reference Article -->
http://technet.microsoft.com/en-us/library/gg712696.aspx
Look under Plan for WSUS Installation heading. You can also add
NT AUTHORITY\SYSTEM account as a user for the WSUS database (SUSDB) and configure a minimum of the webService database role membership as an alternative to the above
Hello again,
How would I add this account. When I go into th WSUS admin group on the local machines I cannot search for the this type of account. It returns nothing.
Thanks
Phil Balderos

Similar Messages

  • Reporting services keep failing on SCCM 2012 SP1

    I have SCCM 2012 SP1 install with SSRS 2012 install on same server 2008 R2 server.
    Reporting services keep failing with the following message when trying to START the service from the Reporting Services Configuration Manager Console
    System.ServiceProcess.TimeoutException: Time out has expired and the operation has not been completed.
       at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout)
       at ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)
    Thx,
    Joe
    Thx, Joe

    Good advice Garth, but I have opened over 5 cases to try to resolve this and several other issues with my troublesome SCOM 2012 SP1 upgrade. That is why I am also sending it to the community in hope they can provide assistance.
    CSS will only work on one specific issue and in most cases these are targeted bandaid fixes that DO NOT address the underlying or related issues. I a left to opening many tickets and still floundering with a unreliable product.
    It seems to only be with System Center. All other products by Microsoft seem to be reliable and predicable and are easily supported using break fix support model of the current MS teams.
    It is SQL (SSRS) that controls subscriptions not CM12. CM12 only leverages the APIs provided by SQL (SSRS).
    I hate to say this but Why do you think this problem has anything to do with CM12?
    If CSS tell you to re-create the subscription and the problem re-occurs then I would re-open the ticket and tell them that the problem is NOT fixed and to continue working on it.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • Equivalent of WSUS "file information" in SCCM 2012 R2

    In WSUS, you could r-click on an update, select "file information" and see where in WSUSCONTENT an update was actually located. This was helpful; especically if the update was stored there in an executeable format (not a cab), and you could run
    the patch manually. This often works if it won't install through SCCM or WSUS. Does anyone know if it's possible to get this info through SCCM 2012 R2?
    Ben JohnsonWY

    Thanks everyone and I do appreciate all the input, I understand how this works, but...
    This is another case of where something that was quick, simple, and easy in WSUS has been made ridiculously complicated by MicroShaft in SCCM. The Content Info tab isn't what I want, I want to know where it physically is on my server. When you get to
    the content ID you can't stretch the column to read it, you have to mouse over it and the popup with a ridculously long path disappears after a few seconds. In the show members listing you can select the unique ID but not content ID and but in the package
    folders it uses content ID. Geez! Now if the content ID, with package, were selectable in the show members window it'd be easy. And to top if off, you can't tell by looking at the console which package an update is in. This is something else MS really
    needs to work on. It still boggles my mind how they keep removing simple and easy functionality from programs when they come out with new versions. No wonder I couldn't figure this out on my own.
    I don't pull updates from MS. I pull the from another source approved for us. They get dropped onto one of my servers. So.....
    I'm going back to what Peter suggested; I'm going to look them up using "file info" in WSUS because it's far quicker and easier.
    Ben JohnsonWY

  • SQL Connection Failed for SCCM 2012 R2 (Unable to load user-specified certificate)

    We've recently completed an upgrade from SCCM 2012 SP1 to 2012 R2 and have been running in the new environment for about a week. As of this morning, The consoles failed to connect to the CAS' and one of the Primary Site's database. The issue was resolved
    easily enough by addressing a certificate issue in SQL, but I'm left wondering if there's a correlation between the SP1-to-R2 upgrade that would cause the cert to fail. Anyone have experience with this?
    2014-01-21 22:10:11.81 Server      The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: 0x8009030d. Check certificates to make sure they are valid.
    2014-01-21 22:10:11.81 Server      Error: 26014, Severity: 16, State: 1.
    2014-01-21 22:10:11.81 Server      Unable to load user-specified certificate [Cert Hash(sha1) "haaaaassssshhhh"]. The server will not accept a connection. You should verify that the certificate is correctly installed. See
    "Configuring Certificate for Use by SSL" in Books Online.
    2014-01-21 22:10:11.81 Server      Error: 17182, Severity: 16, State: 1.
    2014-01-21 22:10:11.81 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
    2014-01-21 22:10:11.81 Server      Error: 17182, Severity: 16, State: 1.
    2014-01-21 22:10:11.81 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
    2014-01-21 22:10:11.81 Server      Error: 17826, Severity: 18, State: 3.
    2014-01-21 22:10:11.81 Server      Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
    2014-01-21 22:10:11.81 Server      Error: 17120, Severity: 16, State: 1.
    2014-01-21 22:10:11.81 Server      SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

    We got the same certificate related error events after a fresh install of SCCM 2012 R2 on a new server. It happened during the first reboot after SCCM was installed. In the Certificates mmc, I right-clicked on the certificate used by SQL and chose Manage
    Private Keys. Giving the service account that runs the MSSQLSERVER service read rights to the private key allowed SQL to start. However, after a day or so we rebooted the server again, and SQL wouldn't start. Something had removed the service account's read
    permission. Since the SCCM configuration wasn't that far along, we uninstalled SCCM. After giving the service account read rights again, and rebooting several times over a few days, and SQL started every time. We then installed SCCM 2012 R2 again, and checked
    the certificate's permissions before rebooting. The service account still had read permissions when the install completed, but as soon as the server was rebooted, it lost the permissions again.
    The Certificates mmc was then used to request a second computer certificate and then SQL was configured to use that new certificate via SQL Server Configuration Manager. After several days and a number of reboots the SQL services have started normally every
    time so the second certificate seems to have fixed the issue. I have kept the original certificate for fear that removing it will cause whatever part of SCCM 2012 R2 that modifies the original certificate to start removing permissions from the new certificate
    as well.

  • 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

  • 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

  • 0x80004005: app install failed - OSD SCCM 2012 R2 - randomly

                    
    Hi,
    I have visited many forums with this error before posting.
    Problem : During TS New computer OSD, app failed to install randomly on all model Win 7 x86 or x64.
    Information :
    App concerned : Adobe flash, office, chrome...
    Domain integration : OK
    App installation tested across software center : OK
    smsts.log error  :
    Policy Evaluation failed, hr=0x80004005
    Install application action failed: 'Adobe Shockwave Player '. Error Code 0x80004005 InstallApplication
    LocationServices.log error :
    Policy prevents failover to WINS for lookup
    Successfully sent location services HTTP failure message.
    Error sending HEAD request. HTTP code 401, status 'Unauthorized'
    Client is not assigned to a site. Cannot get security settings.
    Client is not assigned to a site. Cannot get site signing cert.
    An idea ?

    Hi, 
    I create another topic and my problem (App install during OSD) is now solved yes:
    http://social.technet.microsoft.com/Forums/en-US/bb10bfc3-f5ec-46a6-9535-ea299266795c/strange-problem-app-install-failed-randomly-osd-sccm-2012-r2?forum=configmanagerosd#f54d0af1-2658-49ee-a57a-1ec9e2b09a3e
    You can Check "Continue on error" inside  "Options" Tab on your TS. Even if App install fail At least the rest ends well...

  • OSD Request User State Storage fails after SCCM 2012 upgrade to R2

    After SCCM upgrade from SP1 to R2 OSD fails on Request User State Storage. Error:
    Task sequence: XXXXX has failed with the error code (0x00004005). For more information, contact your system administrator or helpdesk operator.
    In smsts.log:
    =================================
    <![LOG[Certificate is a self signed certificate. It will not be checked for revocation or expiration.]LOG]!><time="09:27:37.133-120" date="03-14-2014" component="OSDSMPClient" context="" type="0" thread="5984"
    file="smpclientutil.cpp:420">
    <![LOG[Successfuly retrieved public key and verified signature.]LOG]!><time="09:27:37.133-120" date="03-14-2014" component="OSDSMPClient" context="" type="1" thread="5984" file="smpclient.cpp:2604">
    <![LOG[Sending share info request message: <RequestStateStore><ClientID>GUID:BF0F737B-1834-4625-984C-5C9DE2391CFC</ClientID><Reserved2>308202E4308201CCA00302010202103A4DDA5B85D41CAE4D9D220E5006A4FF300D06092A864886F70D01010B050030203110300E0603550403130742313439353230310C300A06035504031303534D533020170D3134303331313038353935385A180F32313134303231363038353935385A30203110300E0603550403130742313439353230310C300A06035504031303534D5330820122300D06092A864886F70D01010105000382010F003082010A0282010100C739D1BFA21BF715C0BCB55FC3B86983AAB9A0AF8BB33977E85CED2225EDAB0635DA31B1864420AD0BECBB947A148C669FA3C3B4EF17F76E2A5F6939FB4390ACA8EA53FE213C487E7DDBBD653963F0DC5F1ED08C20205657902E2EC70881654B7CFFA5C46006F94BCFE6F3C694E4A12A4B70A7F449473F00770660B0721305E2D17856FBE4ECDDEA0EB844E4628CBBCB6CA6859DF935FEF8F2F026D50FD39FFA99833F380F0298EA2A8CD6E023F00B3A008D64BBCCF694A303E5C4A2B9920C5DEDC72D123C4D2B02C429FFC29F80BB792AA05C367490AD5C3FB368D84C4373A7DD0A77A80B1D955E6E34F694B04BB1BF87CD67D697A4BB1FE291150FC8699EB50203010001A318301630140603551D25040D300B06092B0601040182376502300D06092A864886F70D01010B0500038201010031207E781BCF10D96166416C305AADFA53D85343168E5E8A6B41B2B12B53886D1AC75BDFA045598F088AF465853E1261A5D6F0F4DEB2443C0C5F25B4F2746DB52F1B46D5E4D4D7B139CA8281ACA03C37890285BEB721ED186F3D70098EA9D7E61265210B73C18245FE25C16D72E545C9F4544A788632C7A61F6106BAB6A357530241FBB4245F7D5244805BC571F1B024C0825D04C85021E8AC7F94B901F30039C28BAC6DC307F2AC04B9B14A3949697EED015E64611D3427E41537B800D1222CC1FDAF333DE7F59B1A242BBCB65F4D85722A62147CA391684EB6A53D547C78050C341DA0FC99A09842A184842DEE3C5138F2C5AF515DF8D531F850E7A3839E90</Reserved2></RequestStateStore>]LOG]!><time="09:27:37.134-120"
    date="03-14-2014" component="OSDSMPClient" context="" type="1" thread="5984" file="smpclient.cpp:2285">
    <![LOG[Requesting SMP Root share config information from http://server.int.domain.com:0]LOG]!><time="09:27:37.290-120" date="03-14-2014" component="OSDSMPClient" context="" type="1" thread="5984"
    file="smpclient.cpp:2348">
    <![LOG[Received 3963 byte response.]LOG]!><time="09:27:37.333-120" date="03-14-2014" component="OSDSMPClient" context="" type="0" thread="5984" file="smpclient.cpp:2363">
    <![LOG[Adding \\server.int.domain.com\SMPSTORED_39C7CA32$ to list ]LOG]!><time="09:27:37.367-120" date="03-14-2014" component="OSDSMPClient" context="" type="1" thread="5984" file="smpclient.cpp:2403">
    <![LOG[Failed to connect to "\\server.int.domain.com\SMPSTORED_39C7CA32$" (1203).]LOG]!><time="09:27:37.440-120" date="03-14-2014" component="OSDSMPClient" context="" type="2" thread="5984"
    file="tsconnection.cpp:340">
    <![LOG[Failed to connect to "\\server.int.domain.com\SMPSTORED_39C7CA32$" (1203).]LOG]!><time="09:27:37.468-120" date="03-14-2014" component="OSDSMPClient" context="" type="2" thread="5984"
    file="tsconnection.cpp:340">
    <![LOG[Cannot connect to http://server.int.domain.com SMP root share]LOG]!><time="09:27:37.468-120" date="03-14-2014" component="OSDSMPClient" context="" type="3" thread="5984" file="smpclient.cpp:1754">
    <![LOG[ClientRequestToSMP::DoRequest failed. error = (0x80004005).]LOG]!><time="09:27:37.468-120" date="03-14-2014" component="OSDSMPClient" context="" type="3" thread="5984" file="smpclient.cpp:1882">
    <![LOG[Request to SMP 'http://server.int.domain.com' failed with error (Code 0x80004005). Trying next SMP.]LOG]!><time="09:27:37.468-120" date="03-14-2014" component="OSDSMPClient" context="" type="2"
    thread="5984" file="smpclient.cpp:1590">
    <![LOG[Sleeping for 60 seconds before next attempt to locate an SMP.]LOG]!><time="09:27:37.468-120" date="03-14-2014" component="OSDSMPClient" context="" type="1" thread="5984" file="smpclient.cpp:1565">
    =======================
    IIS log:
    =======================
    172.20.0.xx CCM_POST /SMSSMP/.sms_smp op=KeyInfo 80 - 172.20.6.yy SMS+CCM+5.0+TS 200 0 0 2281 2
    172.20.0.xx CCM_POST /SMSSMP/.sms_smp op=RootShareInfo 80 - 172.20.6.yy SMS+CCM+5.0+TS 200 0 0 4088 29
    172.20.0.xx OPTIONS /SMPSTORED_39C7CA32$ - 80 - 172.20.6.yy Microsoft-WebDAV-MiniRedir/6.1.7601 200 0 0 206 19
    172.20.0.xx PROPFIND /SMPSTORED_39C7CA32$ - 80 - 172.20.6.yy Microsoft-WebDAV-MiniRedir/6.1.7601 405 0 0 1496 1
    172.20.0.xx PROPFIND /SMPSTORED_39C7CA32$ - 80 - 172.20.6.yy Microsoft-WebDAV-MiniRedir/6.1.7601 405 0 0 1496 1
    ======================
    Allow clients to connect anonymously enabled on DP
    On SMP file share permissions enabled for everyone
    Any suggestions where to look?

    Hi,
    Please try to access
    \\server.int.domain.com\SMPSTORED_39C7CA32$ using Network Access Account from the workstation you working on.
    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.

  • Endpoint Protection Role fails after SCCM 2012 SP1 upgrade 0x8004ff84

    We have been in the process upgrading our SCCM RTM to SP1 in order to get to R2 in the end. After upgrading the PRimary Site server to SP1 it seems the Endpoint protection update did not succeed. I removed the role and after that tried it to install again,
    results below.
    EPSetup.log
    I<09/26/14 14:24:25> Installing the SMSEP
    <09/26/14 14:24:25> Passed OS version check.
    <09/26/14 14:24:25> File E:\BO\Microsoft Configuration Manager\Client\SCEPInstall.exe version is 4.4.304.0.
    <09/26/14 14:24:25> EP version 2.2.903.0 is already installed.
    <09/26/14 14:24:25> EP 2.2.903.0 is installed, version is lower than expected installer version 4.4.304.0.
    <09/26/14 14:24:25> Invoking process "E:\BO\Microsoft Configuration Manager\Client\SCEPInstall.exe" /s /q /noreplace /policy "E:\BO\Microsoft Configuration Manager\Client\EP_DefaultPolicy.xml" 
    <09/26/14 14:24:25> CreateProcess: E:\BO\Microsoft Configuration Manager, "E:\BO\Microsoft Configuration Manager\Client\SCEPInstall.exe" /s /q /noreplace /policy "E:\BO\Microsoft Configuration Manager\Client\EP_DefaultPolicy.xml" 
    <09/26/14 14:25:00> CreateProcess: -2147156092
    <09/26/14 14:25:01> SCEPInstall.exe returns 0x8004ff84
    <09/26/14 14:25:01> SMSEP could not be installed. The return code was -2147156092
    <09/26/14 14:25:02> ~RoleSetup().
    When I manually try to run the SCEPInstall.exe setup asks for certain msi files it cannot find. Anyone seen this behaviour before? I'm not able to find information on this one.

    It seems the uninstallation of the current SCEP client fails. It uses the new SCEPinstall.exe version to do the uninstall which fails. I copied the old version from another computer and used that to do the uninstall manually scepinstall.exe /u
    It asks a few times for a location to find the msi files used to do the uninstallation. You have to point at a temporary map created at the drive root location. The Uninstall succeeds.
    Now the Endpoint Protection role can be added again and will also succeed.

  • WSUS Update KB2938066 and SCCM 2012 R2

    Looking at the newly release WSUS update KB2938066 and wondering if I need to apply it to my SCCM WSUS component. If so, what type of impact on the SCCM clients should I be aware of?
    Orange County District Attorney

    As the update is about securing and hardening WSUS and also the communication with WU/MU, I would definitely apply this update.
    The client-side is going to be tricky, depending on the configuration of your windows updates. Jason did a very good post about this here:
    http://blog.configmgrftw.com/the-wua-dilemma-in-configmgr/
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • Distribute content failed on sccm 2012

    Hello all,
    As part of OS deployment, I first did a 'build and capture' a Windows 2008 x64 bit image (.wim) and saved it as part of a shared folder (with full permissions). Next, I wanted to create a 'Operating System Images' under 'Software Library' and was successfully
    able to add the .wim image previously created. Next, I wanted to 'Distribute content' to Distribution Point (DP) which happens to be the same server as my Site server and where my 'shared' folder is. 
    As part of this 'Distribute content' when I check the 'content status' under Monitoring, I see the status in 'RED' (Failed). I checked the 'more details' on the error status and found this:
    Can anyone help me understand what is missing and what needs to be done. I'm also going through documentation to troubleshoot this. thanks

    Hi,
    Have you configure the machine account(site server machine) to at least  Read permission?
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • SCCM 2012 using SUP to Windows 2012 R2 WSUS

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

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

  • Remote WSUS integration with SCCM 2012

    Hi,
    We are currently having WSUS already in place for Patching , but not used at all its just installed.
    can remote WSUS be integrated with SCCM 2012 server which is on different server ? what is the best practice ? is it to have WSUS on same server as Primary server?
    or I decommission it and install a new WSUS on same server as SCCM server.
    what steps have to be taken care if remote WSUS is integrated ? any documents or steps to be taken care .
    Thanks in Advance

    When you install SUPs, they automatically configure the underlying WSUS instance to sync from an upstream server based upon your ConfigMgr hierarchy.
    A couple of notes here though:
    - You generally shouldn't use an existing instance of WSUS for ConfigMgr. Once integrated into ConfigMgr, WSUS should no longer manage approvals, update binary downloads, or update binary distribution as these are all handled by ConfigMgr separate from WSUS.
    Using an existing WSUS instance where this was the case can be problematic at best and will cause unexpected behavior and results.
    - Clients do not choose SUPs based upon boundaries or location so using a remote SUP is typically not beneficial and in many cases will cause additional network load. The exception to this is if the SUP is within a secondary site.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • Sccm 2012 collection query for software deployment failed PCs

    Hi,
    Let me know how can we create a collection of PCs which a particular advertisement failed.
    SCCM 2012 sp1 infra
    Midhun.PS

    See
    http://myitforum.com/cs2/blogs/gramsey/archive/2006/10/20/How-To_3A00_-Create-a-Collection-Based-on-an-Advertisement-Status.aspx. This will only work for program deployments, not applications.
    Torsten Meringer | http://www.mssccmfaq.de

  • SCCM 2012 r2 with CU1 - XP Refresh

    Hi Everyone,
    Hoping someone out there can assist with this. I am doing a refresh for XP to win7.  I have read
    http://social.technet.microsoft.com/Forums/en-US/6e934990-999a-4367-860a-3ce4e5eda956/sccm-2012-r2-error-0x800700c1?forum=configmanagerosd
    and
    http://www.windows-noob.com/forums/index.php?/topic/9418-referesh-task-sequence-from-xp-fails-on-sccm-2012-r2/
    none of these work.  I took a look at this and I was able to get pass the staging of the boot image
    http://blogs.technet.com/b/brandonlinton/archive/2013/06/21/how-to-create-and-import-a-winpe-3-1-boot-image-for-use-in-configmgr-2012-sp1-cu2.aspx
    however when the machine rebooted I received this.  I also inject the nic drivers using dism and still the same issue. Any idea of a fix or how to go about refresh for
    XP using sccm 2012 r2?
    thanks all!

    Hi,
    Also ran into this issue, you're encountering this error because some components are missing in your WinPE image.
    Note that this refresh scenario is not supported, however you can get this  to work by manually customizing (especially importing WMI component) your WinPE image
    before importing it ConfigMgr.
    I made the script below, ran in on a base WinPE image from WADK for Windows 8 (a 6.2 version image so) to make it work (sorry for french comments Inside but I'm sure you'll get it :) ):
    #Adapt these variables to you environment
    $ADK = "C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit" #Chemin d'ADK
    $DismArchitecture = "amd64" #archi a utiliser pour DISM
    $CompArchitecture = "x86" #archi a utiliser pour les composants
    $MountDir = "e:\Mount" #point de montage a utiliser
    $Wimdir = "E:\winpe.wim" #chemin du wim a modifier
    $InjectDrivers = $TRUE #Choisir si il faut ajouter des pilotes ou non
    $DriversDir = "E:\Pilotes\WinPE3.1_x86" #chemin contenant les pilotes
    $AddCMTrace = $FALSE #Choisir si il faut ajouter cmtrace ou non
    $CMTraceDir = "E:\Microsoft Configuration Manager\tools\cmtrace.exe" #chemin de cmtrace
    $ChangeLocale = $TRUE #Choisir si il faut modifier les paramètre regionnaux ou non
    $Locale = "fr-FR" #param regionnaux a utiliser
    $DismFolder = "$ADK\Deployment Tools\$DismArchitecture\DISM" #ne pas modifier
    $OptComponents = "$ADK\Windows Preinstallation Environment\$CompArchitecture\WinPE_OCs"; #ne pas modifier
    $AddOPTComponents = $TRUE #Choisir si il faut ajouter des composants ou non
    #liste des composants:
    $ComponentList = @(
    “$OptComponents\WinPE-WMI.cab”
    “$OptComponents\$Locale\WinPE-WMI_$Locale.cab”
    “$OptComponents\en-us\WinPE-WMI_en-us.cab”
    “$OptComponents\WinPE-NetFx4.cab”
    “$OptComponents\$Locale\WinPE-NetFx4_$Locale.cab”
    “$OptComponents\en-us\WinPE-NetFx4_en-us.cab”
    “$OptComponents\WinPE-HTA.cab”
    “$OptComponents\$Locale\WinPE-HTA_$Locale.cab”
    “$OptComponents\en-us\WinPE-HTA_en-us.cab”
    “$OptComponents\WinPE-DismCmdlets.cab”
    “$OptComponents\$Locale\WinPE-DismCmdlets_$Locale.cab”
    “$OptComponents\en-us\WinPE-DismCmdlets_en-us.cab” );
    #Composants pour WinPE 6.3: (a inserer a la place de NetFx4)
    #“$OptComponents\WinPE-NetFx.cab”
    #“$OptComponents\$Locale\WinPE-NetFx_$Locale.cab”
    #“$OptComponents\en-us\WinPE-NetFx_en-us.cab”
    #“$OptComponents\WinPE-PowerShell.cab”
    #“$OptComponents\$Locale\WinPE-PowerShell_$Locale.cab”
    #-----debut du script
    #Creation du point de montage
    New-Item -ItemType Directory -Force -Path $MountDir
    #import de DISM
    import-module $DismFolder
    #montage de l'image
    Write-Host "Mounting WIM file"
    Mount-WindowsImage -ImagePath $Wimdir -Index 1 -Path $MountDir -ErrorAction Stop
    #changement de locale
    if($ChangeLocale -eq $TRUE)
    Write-Host "Changing locale"
    cd $DismFolder
    dism.exe /image:$MountDir /set-syslocale:$Locale
    dism.exe /image:$MountDir /set-userlocale:$Locale
    dism.exe /image:$MountDir /set-inputlocale:$Locale
    #ajout de cmtrace
    if($AddCMTrace -eq $TRUE)
    Write-Host "Adding CMTrace"
    $CMTraceDest = $MountDir + "\Windows\System32"
    Copy-Item -Path $CMTraceDir -Destination $CMTraceDest
    #ajout des pilotes
    if($InjectDrivers -eq $TRUE)
    Write-Host "Injecting Drivers"
    Add-WindowsDriver -Recurse -ForceUnsigned -Driver $DriversDir -Path $MountDir -Verbose -ErrorAction SilentlyContinue
    #ajout des composants
    if($AddOPTComponents -eq $TRUE)
    Write-Host "Adding Optionnal Components"
    foreach ($Component in $ComponentList)
    Write-Host -Object (’Installing component: {0}’ -f $Component);
    Add-WindowsPackage -Path $MountDir -PackagePath $Component -ErrorAction SilentlyContinue;
    #demontage de l'image
    Write-Host "Unmounting WIM file"
    Dismount-WindowsImage -Path $MountDir -Save -Verbose
    Mickael, My technet galleries contributions : ConfigMgr driver injector : http://gallery.technet.microsoft.com/ConfigMgr-Driver-Injector-aae7d17d SCCM Collection splitter : http://gallery.technet.microsoft.com/SCCM-Collection-Splitter-e1c82b06 ConfigMgr
    TS Tools : http://gallery.technet.microsoft.com/TSTools-f9b01357

Maybe you are looking for