GPO and SCCM 2012 Shared WSUS installation

Hello
At present I have a scenario where SCCM 2012 and wsus are installed on the same server and serving around 600 desktop clients.  SCCM is configured to deploy windows updates to the client machine via the sccm client, however the member servers in the
domain do not have the sccm client installed so I have directed them to use the the WSUS installation via GPO.  The servers do appear in the wsus console but never report status and never pull down any updates.
Should this setup be possible; to use one wsus instance for both sccm udpate distribution and direct communication from member servers?
windowsupdate.log entries from a member server as follows:
2014-02-04 15:10:01:172
844 1338
Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2014-02-04 15:10:01:172
844 1338
Agent *********
2014-02-04 15:10:01:172
844 1338
Agent  * Online = No; Ignore download priority = No
2014-02-04 15:10:01:172
844 1338
Agent  * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0
and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-02-04 15:10:01:172
844 1338
Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-02-04 15:10:01:172
844 1338
Agent  * Search Scope = {Machine}
2014-02-04 15:10:01:350
844 14d8
AU Getting featured update notifications.  fIncludeDismissed = true
2014-02-04 15:10:01:351
844 14d8
AU No featured updates available.
2014-02-04 15:10:01:364
844 14d8
AU WARNING: Returning due to error from GetDownloadProgressUx, error = 0x8024000C
2014-02-04 15:10:01:364
844 14d8
AU WARNING: GetInteractiveInstallProgress failed, error = 0x8024000C
2014-02-04 15:10:01:364
564 678
WUApp WARNING: Call to GetInteractiveInstallProgress failed, hr=8024000C
2014-02-04 15:10:02:692
844 1338
Agent  * Found 0 updates and 74 categories in search; evaluated appl. rules of 236 out of 825 deployed entities
2014-02-04 15:10:03:234
844 1338
Agent *********
2014-02-04 15:10:03:234
844 1338
Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2014-02-04 15:10:03:234
844 1338
Agent *************
2014-02-04 15:10:03:238
844 1be4
AU >>##  RESUMED  ## AU: Search for updates [CallId = {5C25CEFB-5315-4722-A422-790FBC7303B5}]
2014-02-04 15:10:03:238
844 1be4
AU  # 0 updates detected
2014-02-04 15:10:03:238
844 1be4
AU #########
2014-02-04 15:10:03:238
844 1be4
AU ##  END  ##  AU: Search for updates [CallId = {5C25CEFB-5315-4722-A422-790FBC7303B5}]
2014-02-04 15:10:03:238
844 1be4
AU #############
Thanks in advance...

Should this setup be possible; to use one wsus instance for both sccm udpate distribution and direct communication from member servers?
No.
Torsten Meringer | http://www.mssccmfaq.de

Similar Messages

  • SCCM 2012 SP1 + WSUS + Server 2012 + SQL Server 2012

    Hi all;
    I installed SCCM 2012 with Sp1 for my site server and everything is going well.. And than i installed the WSUS role on my Windows Server 2012 and SCCM 2012 SP1 it gave an error message which is "Fatal Error: The schema version of the database is from a newer
    version of WSUS than currently installed.  You must either patch your WSUS server to at least that version or drop the database." My database server is SQL Server 2012... Do you know any pathc for WSUS or SQL Server 2012 doesnt support WSUS yet???
    Thank You...
    MCT

    Normally if you are going to install SCCM 2012 SP1 +Windows 2012 with SQL 2012, Then you better use the SQL 2012 sp1.
    also when you are installing the WSUS version 6.2 which come with server 2012 make sure you leave the default settings as it is. it shows in the below article.
    also when you are giving the path to save the WSUS contents make sure the drive you going to create the wsus folder and the place where you going to download the updates is having free disk space and its formatted with the NTFS volume. Also the service account
    you are using for this configuration should have the admin rights to the location of the wsus folder you going to create,
    Thanks
    Hasitha

  • 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

  • Top 4 basic issues that are encountered in SCOM 2012 and SCCM 2012

    HI,
    I need to give a presentation on the basic issues that are encountered in SCOM 2012 and SCCm 2012.
    Can anyone help me out with this?
    Thanks in advance
    Rohith Kumar

    Hi,
    I am not familiar with SCCM, so I will give some issue I encounterred in SCOM:
    1. Not monitored and grey agent, here is an article for your reference:
    http://technet.microsoft.com/en-us/library/hh212723.aspx
    2. Failed to discover and install agents, this may caused by the action account or install account does not have proper permissions to install the agents. Some time maybe the discovery rule is not enabled.
    3. Failed to import Management Pack, this may caused by references MPs are not imported to the management group, or sometime the proper referenced MPs are imported, but there may be incorrect typing in the XML file which defines the management pack.
    4. Runas account and Action account fail. If you change password for action account, you may also need to change the password everywhere the account is used in SCOM. For run as account, if the account does not have enough right to run some tasks, we may
    encounter errors. You may refer to the below link which take SQL mp for example:
    http://blogs.technet.com/b/kevinholman/archive/2010/09/08/configuring-run-as-accounts-and-profiles-in-r2-a-sql-management-pack-example.aspx
    Regards,
    Yan Li
    Regards, Yan Li

  • Cost of Intune and SCCM 2012 r2 vs SCCM 2012 r2 ICBM

    Is there any research/info on pros and cons of SCCM 2012 using intune for internet clinet management vs SCCM 2012 r2 and ICBM?  Things like cost, supportabiliy, etc.  I have seen intune vs sccm not Intune & SCCM vs SCCM and Internet Client
    Based Management. 
    Cyndy

    Hi,
    I think the reason is that you cannot manage Windows clients using the WIndows Intune Agent and integrate it with SCCM 2012. The integration with Intune and SCCM 2012 is for Mobile Device Management only so there is no possibility to install the Windows
    Intune Agent on a client and then manage it through the SCCM Admin Console.
    THe only scenario where that would work is if you manage a Windows 8.1 with the OMA-DM agent and enroll them in Intune as a mobile device with a limited set of features.
    So ICBM is still the way to go if you need all the features in SCCM or you want one console to rule them all.
    Regards,
    Jörgen  
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • WSUS 4.0, SQL server, and SCCM 2012 version help

    I am trying to get to the bottom of a version question.
    We currently have SCCM 2012 R2 up and running, with a DB on a separate server version MSQL 2008 R2. Now we also are using the WSUS integration. I am being told WSUS 4.0 cannot be ran on SQL server 2008 R2, so they could only install and use WSUS version
    3.0.
    Can anyone out there please shed some light on my version items from above?
    Thank you

    I am being told WSUS 4.0 cannot be ran on SQL server 2008 R2, so they could only install and use WSUS version 3.0.
    (Pedantically speaking this is true because there is no such beast as "WSUS 4".)
    However, WSUS v6.2 (Windows Server 2012) and WSUS v6.3 (Windows Server 2012 R2) can most certainly be installed on SQL Server 2008 R2, and the official documentation is at
    http://technet.microsoft.com/en-us/library/hh852344.aspx
    However, the *preferred* installation methodology, unless you've expressly chosen to use a remote SQL Server, is to use the Windows Internal Database feature which is built into Windows Server 2012 and 2012 R2.
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

  • Applocker with Windows Installer rules and SCCM 2012

    Hi,
    We have been running Applocker since two years on Windows 7 Enterprise clients with SCCM 2007 as management and distribution tool.
    This setup was working fine until we migrated to SCCM 2012 and started to encounter problems with msi-packages not being able to self-heal when the source was the sccm client cache.
    We have recreated this scenario in a lab environment.
    Our setup is this:
    Windows 2008 R2 (DC)
    Windows 7 Enterprise SP1 (Client)
    Standard user (not admin)
    SCCM 2012 R2 (upgraded from 2007)
    Applocker with these rules:
    Executable Default rules enabled (Enforced)
    Windows Installer Default rules enabled (Enforced)
    Exception for %WINDIR% (where SCCM cache is located)
    Script Default Rules enabled (Enforced)
    Application msi-package with self-heal (omus) and advertised shortcuts
    We install the application from the sccm cache (%windir%\ccmcache) and then trigger a self-heal (user components being copied to the user profile).
    What we see on the client is: Error 1718. File C:\Windows\ccmcache\54\application.msi was rejected by digital signature policy.
    Event log is showing: Event 1008: The installation of
    C:\Windows\ccmcache\54\application.msi
    is not permitted due to an error in software restriction policy processing. The object cannot be trusted.
    It looks like the file cannot be evaluated by Applocker and therefore is not trusted. We get an Access Denied error when testing AppLocker-policy with the following PS-command,
    Get-AppLockerPolicy -Effective | Test-AppLockerPolicy -Path C:\Windows\ccmcache\54\application.msi. This command works fine when accessing files in the cache-folder on a SCCM2007-client.
    For testing purposes we recreated a similar folder structure: C:\Windows\Folder1\Folder2\application.msi where the user has no permissions on Folder2 and read on the other folders and the File.msi.
    This is how the permissions look like in SCCM 2012 (no user permissions on %Windir%\ccmcache). Applocker cannot evaluate the trust-level of application.msi.
    The GPO setting “Bypass traverse checking” is set to everyone.
    As we can see, the permissions are the same on SCCM 2007 client cache (%Windir%\syswow64\ccm\cache) but we do not have this issue there.
    Has anyone got Applocker (with windows installer rules actived) to work with SCCM 2012 and windows installer self-heal?

    More info. I found some people also encounter this same issue, but specific msi, take a look at
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/2ad92754-f01e-410e-97db-7a9bc81586db/msiinstaller-event-1008-when-trying-to-install-3ds-max-2011-after-group-policies-apply-on-domain?forum=winserverGP
    Juke Chou
    TechNet Community Support

  • Can we re-activate Adobe patches once expired in SCUP and syncronized to WSUS and SCCM 2012 as expired?

    Hi,
    I expired a couple of Adobe patches in SCUP and published them in WSUS. They got synchronized in WSUS and SCCM as expired. After about two weeks those expired patches got cleaned from SCCM ( at least from UI).
    I want to activate them again in SCUP and re-publish as active patches in SCCM. But its not working - I've tried WSUS cleanup and  SCUP cleanup already!
    Is there any way to re-active expired patches published by SCUP in WSUS and SCCM ? & How?
    Excerpt from SCUP.Log:
    PublishItem: Item 'Reader Multi Lingual User Interface 10.1.4 Update (UpdateId:'5c22235f-a3d9-48db-95eb-a60ec1886e8e' Vendor:'Adobe Systems, Inc.' Product:'Adobe Reader')' is on the update server and is expired, no publish actions are possible.

    The key here is knowing WHY those updates were "expired" in the first place.
    Most likely they were expired because they superseded another update. If so, merely duplicating and publishing won't achieve anything, because the duplicated/re-published update will also be superseded and get promptly expired again.
    Ergo, if expired because superseded, the superseding package will need to be customized to remove the supersession references and it also will need to be republished, which also means that certain other considerations may need to be taken as well ... such
    as the fact that you now have multiple packages that will conflict with one another that no longer have the requisite supersession metadata.
    Regarding this scenario. Configuration Manager 2012 introduced the option to NOT EXPIRE superseded updates, or to defer the expiration for a specified number of days. This is not a SCUP thing; it's a ConfigMgr thing.
    Configure the ConfigMgr product to behave the way you desire. Problem solved. :)
    If YOU actually expired them in SCUP... then just UNEXPIRE them and republish. Shouldn't be any need to duplicate and republish. This is what Microsoft does all the time. Expire Update 'A' Rev 100 on Monday; publish Update 'A' Rev 101 on Patch Tuesday.
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

  • 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

  • WSUS and SCCM 2012

    I'm finally getting around to trying to integrate WSUS with SCCM 2012 - i.e., to begin using SCCM 2012 to manage and deploy all Microsoft updates rather than using plain old WSUS as I have in the past.
    My first impression is that it's much more complicated than using WSUS alone. That said, I'm wondering now what are the advantages of using SCCM 2012 to manage Windows Updates rather than using WSUS? So far, I've added all of this complexity to the
    process, but I'm not seeing the added benefits after having gone through all this. Anyone else agree?
    I'm about to just trash the whole thing and go back to doing it the old way. Thoughts?
    Shaun

    Jorgen summed it up nicely here:
    http://ccmexec.com/2012/08/top-11-reasons-why-you-should-use-configmgr-2012-for-managing-software-updates/
    Jason | http://blog.configmgrftw.com

  • SCCM 2012 and SCCM 2007 Shared Distribution Points

    I am building a new SCCM 2012 site (primary and 4 secondaries) besides a SCCM 2007 site (primary, 3 secondaries and 65 DPs).
    I migrated all objects from SCCM 2007 to SCCM 2012 which worked well.
    I migrated a client from SCCM 2007 to my SCCM 2012 environment and that worked well. Then i push some packages from SCCM 2012 to my migrated client which worked as well either.
    Then I switch on the SHARED DISTRIBUTION option in the migration section and now my migrated SCCM 2012 client only can access the SCCM 2007 DPs and packages from SCCM 2012 DP can't be accessed anymore...in Software Center the packages will stay at 0% downloading....
    Is that normal behavior after enabling shared DPs ?

    Did you ever find a solution for this? I am experiencing the same issue.
    I have an IP address range boundary for testing SCCM 2012. After enabling shared distribution option SCCM 2012 migrated boundaries from SCCM 2007. My test IP address range boundary has two boundary groups... One is the SCCM 2012 Boundary group
    pointing towards the SCCM 2012 DPs. The 2nd is the automatically created "Boundary Group for SCCM 2007 distribution point."
    With both of those in there I can only push SCCM 2007 packages to the SCCM 2012 clients. SCCM 2012 packages come back in the logs as "Calling back with empty distribution points list." If I remove the automatically created "Boundary Group for SCCM 2007 distribution
    point" from the test IP boundary then SCCM 2012 clients will properly download from the SCCM 2012 DPs, but now the SCCM 2007 packages fail to download to the SCCM 2012 test clients.
    I assume I have some kind of boundary issue but am at a loss of resolving it. Either that or I have the shared dp concept down incorrectly. Shouldn't I be able to have a boundary that has SCCM 2012 clients that uses the 2012 DP for 2012 content but the 2007
    DP for 2007 content while I am migrating?
    Thanks for any help
    - Ryan

  • SCCM 2012 R2 WSUS db connection error 2146232060

    On a new set of two servers, I have Server 2012 R2, SCCM 2012 R2, and SQL 2012 SP1 CU6. WSUS role is on both servers with WSUS integrated into the SCCM site. Server01 would not connect Server02 with the error "failures were reported on WSUS Server02
    while trying to make WSUS db connection. Error 2146232060".
    We fixed this when we noticed that within Security\Logins "NT Authority\System" on Server01 had the securitymanager and sysadmin rights but such was not the case on Server02. When we set the system account on server02 to match the one on server01
    and rebooted, the problem was fixed.
    Just wanted to let people know in case it helps someone else.
    Ben JohnsonWY

    Hi,
    Thanks for sharing your troubleshooting information here. This could help the others that have the same issue.
    Also, since this is not a question, I will change the type to discussion.
    Juke Chou
    TechNet Community Support

  • SCCM 2012 - Install WSUS Off Box SQL

    Hi all,
    installed SCCM 2012 R2 CAS on a 2012 server. The SQL is off box on a server cluster. I've installed WSUS through the 'Add Roles and Features'. I configured it to have local storage for the content and a remote DB instance
    (called SQL1 on our cluster). All this worked well and the install completed as expected. I checked the SQL cluster and the "SUSDB" database was created ok.
    As a final step, i went to Tools in Server Manager and launched Windows Server Update Services. This brought up the 'Complete WSUS Installation' dialogue box. I entered the exact same DB info as i had done when completing
    the initial install of WSUS:
    Yet when i hit 'run' the following message returns:
    The relevant bit of logging is shown here:
    2015-01-14 16:58:42  Starting service W3SVC
    2015-01-14 16:58:42  Configuring IIS...
    2015-01-14 16:58:42  Start: ConfigureWebsite
    2015-01-14 16:58:42  System.Runtime.InteropServices.COMException (0x80070422): The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
    So i guess i have two question;
    1] is this Post-installation failure something i need to fix? (I presume it is)
    2] If i do need to fix this to get sccm running properly, does anyone have any suggestions as to where i should start?
    Thanks

    (for three forests which have no trust relationships).
    That's not a valid technical reason to have multiple primary sites at all. ConfigMgr does not care about, use, or rely on domain or forest boundaries or client membership in any way for client management. Using multiple primary sites and a CAS will
    significantly increase complexity and latency, will add additional points of failure, and will increase overall operational costs.
    Concur with Jason here. CAS not needed. You can add in untrusted forests to the Configmgr Console so log as you have an account with permissions in the destination forest, extend the schema, create the system management container and open up any firewall
    ports that are need for communication from site server to dc.
    Neil Peterson has a great set of blogs on how to achieve this
    http://blogs.technet.com/b/neilp/archive/2012/08/20/cross-forest-support-in-system-center-2012-configuration-manager-part-1.aspx
    and ports are listed in this TechNet article under site server -- > Domain Controller. Ensure your RPC ports match the OS of the DC.
    http://technet.microsoft.com/en-gb/library/hh427328.aspx
    Final agreement with Jason - push to get that SQL local. 
    Cheers
    Paul | sccmentor.wordpress.com

  • SCCM 2012 Linux Client Installation Error

    Hi guys,
    I had an error when a try to install SCCM 2012 R2 Linux Client on various RedHat Servers.
    This is the error on my Linux Servers:
    Checking Prerequisites...
    Running preinstall validator
    /tmp/cmetc/bin_100/preinstallvalidator: error while loading shared libraries: libssl.so.1.0.0: cannot open
    shared object file: No such file or directory
    Pre-Install validator failed. Please check the version of OpenSSL with CM installation requirements.
    I've seen this is a known error, and probably it could be solved by creating symlinks on the RedHat systems.
    I'm not a Linux expert. How do I create the symlink? What is the exact command?
    Regards,
    Rodrigo

    Excellent Kamil !
    I executed the following commands, and it worked fine:
    ln -s /usr/lib64/libssl.so.1.0.1e /usr/lib64/libssl.so.1.0.0
    ls /usr/lib64/ | grep libssl
    ln -s /usr/lib64/libcrypto.so.1.0.1e /usr/lib64/libcrypto.so.1.0.0
     ls /usr/lib64/ | grep libcrypto
    ./install -mp srv.domain.cl -sitecode NNN ccm-Universalx64.1.0.0.4580.tar
    Thanks a lot.
    Regards,
    Rodrigo

  • ERROR: Failed to update prerequisite results into the registry; error = 1 for sccm 2012 secondary site installation

    Hi,
    We try to install sccm 2012 serondary site in server 2012. It always failed.
    I used the rereqchek tools to check system enviroment locally. All passed.
    The primary site installed in server 2012.  Both server had granted the administrator permission.
    Anyone can help to check the below Configmgrprereq.log
    <01-16-2015 08:47:55> ********************************************
    <01-16-2015 08:47:55> ******* Start Prerequisite checking. *******
    <01-16-2015 08:47:55> ********************************************
    <01-16-2015 08:47:55> Commandline :
    "D:\Microsoft Configuration Manager\bin\x64\smsexec.exe"
    <01-16-2015 08:47:55> Check Type: Secondary site
     Site Server: DPServer.ms.com,
     SQL Server: DPServer.ms.com,
     SQL Named Instance: ,
     Install Folder: d:\Program Files\Microsoft Configuration Manager\,
     Setup Source Folder: D:\SCCM2012\Source
    <01-16-2015 08:47:55> INFO: Executing prerequisite functions...
    <01-16-2015 08:47:55> ===== INFO: Prerequisite Type & Server: SITE_SEC:DPServer.ms.com =====
    <01-16-2015 08:47:55> <<<RuleCategory: Access Permissions>>>
    <01-16-2015 08:47:55> <<<CategoryDesc: Checking access permissions...>>>
    <01-16-2015 08:47:55> INFO: CheckLocalSys is Admin of <DPServer.ms.com>.
    <01-16-2015 08:48:08> DPServer.ms.com;    Site server computer account administrative rights;    Error;    Configuration Manager Setup requires that the site server computer has administrative rights on
    the SQL Server and management point computers.
    <01-16-2015 08:48:08> <<<RuleCategory: System Requirements>>>
    <01-16-2015 08:48:08> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
    <01-16-2015 08:48:08> INFO: Check Lanman service: <DPServer.ms.com>.
    <01-16-2015 08:48:22> DPServer.ms.com;    Check Server Service is running;    Passed
    <01-16-2015 08:48:30> INFO: OS version:0, ServicePack:0.
    <01-16-2015 08:48:30> DPServer.ms.com;    Unsupported site server operating system version for Setup;    Error;    Configuration Manager site systems can only be installed on systems running Windows Server
    2008 SP2 or later.
    <01-16-2015 08:48:34> INFO: Failed to get Active Directory membership information for computer DPServer.ms.com with 0.
    <01-16-2015 08:48:34> DPServer.ms.com;    Domain membership;    Error;    Configuration Manager site server components must be installed on computers that are members of a Windows domain.
    <01-16-2015 08:48:40> INFO: Free disk space on target \\DPServer.ms.com\d$\. = 510158 MB
    <01-16-2015 08:48:40> DPServer.ms.com;    Free disk space on site server;    Passed
    <01-16-2015 08:48:47> DPServer.ms.com;    Pending system restart;    Passed
    <01-16-2015 08:48:50> INFO: The server DPServer.ms.com is not read-only domain controller.
    <01-16-2015 08:48:50> DPServer.ms.com;    Read-Only Domain Controller;    Passed
    <01-16-2015 08:48:50> INFO: Check FQDN Length for site server: <DPServer.ms.com>.
    <01-16-2015 08:48:50> DPServer.ms.com;    Site Server FQDN Length;    Passed
    <01-16-2015 08:48:50> <<<RuleCategory: Dependent Components>>>
    <01-16-2015 08:48:50> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
    <01-16-2015 08:48:57> DPServer.ms.com;    Microsoft XML Core Services 6.0 (MSXML60);    Warning;    MSXML 6.0 or later libraries are required for Configuration Manager console and Configuration Manager site
    server installations. MSXML 6.0 is available for download at http://go.microsoft.com/fwlink/?LinkId=215744
    <01-16-2015 08:49:03> DPServer.ms.com;    Microsoft Remote Differential Compression (RDC) library registered;    Error;    Microsoft Remote Differential Compression (RDC) library must be registered for Configuration
    Manager site server installation. Details at http://technet.microsoft.com/library/cc431377.aspx#RDC_for_Site_Servers.
    <01-16-2015 08:49:03> INFO: Checking Windows Installer version on DPServer.ms.com.
    <01-16-2015 08:49:13> INFO: Path of Windows Installer is <\\DPServer.ms.com\C$\Windows\System32\msi.dll>.
    <01-16-2015 08:49:19> ERROR: Failed to determine Windows Installer version from path:<\\DPServer.ms.com\C$\Windows\System32\msi.dll> .
    <01-16-2015 08:49:19> DPServer.ms.com;    Microsoft Windows Installer;    Error;    Setup failed to verify the Windows Installer version, or the installed version of Windows Installer does not meet the minimum
    requirement.  Configuration Manager requires at least Windows Installer version 4.5.
    <01-16-2015 08:49:19> INFO: Start Checking InstallSQLExpress on site server: DPServer.ms.com, SQL Server instance CONFIGMGRSEC
    <01-16-2015 08:49:28> INFO: SQL Server Instance Names value was not found
    <01-16-2015 08:49:28> INFO: IsPortUsedByAnySqlInstance port 1433.
    <01-16-2015 08:49:39> INFO: TCP port 1433 is not in use by any other SQL Server instances.
    <01-16-2015 08:49:49> INFO: Sql express: OS version:0, ServicePack:0.
    <01-16-2015 08:49:49> ERROR: Cannot install sqlexpress 2012, not meet OS requirement: Windows server 2008 sp2, Windows server 2008 R2 sp1 or higher.
    <01-16-2015 08:49:49> DPServer.ms.com;    SQL Server Express on Secondary Site;    Error;    A SQL Server instance is already installed on the secondary site server using the instance name CONFIGMGRSEC,
    or the specified TCP port is being used by another SQL Server instance, or OS version is not Windows Server 2008 sp2, Windows Server 2008 R2 sp1 or higher. Setup is unable to install SQL Server Express on the secondary site.
    <01-16-2015 08:49:55> ERROR: Failed to connect to registry of DPServer.ms.com
    <01-16-2015 08:49:55> DPServer.ms.com;    Existing Configuration Manager server components on site server;    Error;    A site server or site system role is already installed on the computer selected for
    site server installation. Remove the site or site system role from the computer, or select another computer for site server installation.
    <01-16-2015 08:49:55> DPServer.ms.com;    Firewall exception for SQL Server (stand-alone primary site);    Passed
    <01-16-2015 08:49:55> INFO: SQL Server computer <DPServer.ms.com>
    <01-16-2015 08:49:55> INFO: SQL Server named instance <>
    <01-16-2015 08:49:55> INFO: Install SQL Server Express on secondary site, skip checking.
    <01-16-2015 08:49:55> DPServer.ms.com;    SQL Server service running account;    Passed
    <01-16-2015 08:49:55> INFO: Install SQL Server Express on secondary site, skip checking.
    <01-16-2015 08:49:55> DPServer.ms.com;    Dedicated SQL Server instance;    Passed
    <01-16-2015 08:49:55> INFO: CheckSQLCollationSecondary
    <01-16-2015 08:49:55> INFO: Installing SQL Server Express; skipping
    <01-16-2015 08:49:55> DPServer.ms.com;    Parent/child database collation;    Passed
    <01-16-2015 08:49:55> INFO: Checking .NET framework versions 3.5...
    <01-16-2015 08:50:05> INFO: .NET is installed
    <01-16-2015 08:50:05> DPServer.ms.com;    Minimum .NET Framework version for Configuration Manager site server;    Passed
    <01-16-2015 08:50:05> INFO: Checking .NET version required for installing SQL Server Express for Secondary Site.
    <01-16-2015 08:50:05> INFO: Checking .NET framework versions 4.0...
    <01-16-2015 08:50:10> INFO: .NET is installed
    <01-16-2015 08:50:11> DPServer.ms.com;    Minimum .NET Framework version for SQL Server Express edition installation for Configuration Manager Secondary Site;    Passed
    <01-16-2015 08:50:11> INFO: CheckInstallSourceVersion <D:\SCCM2012\Source>
    <01-16-2015 08:52:29> ERROR: Could not read install map from \\DPServer.ms.com\D$\\SCCM2012\Source\SMSSETUP\install.map (result 2)
    <01-16-2015 08:52:29> DPServer.ms.com;    Setup Source Version;    Error;    The product version in the source folder specified for secondary site installation does not match the version of the primary site.
    <01-16-2015 08:52:29> INFO:CheckInstallSourcePath <DPServer.ms.com>
    <01-16-2015 08:52:55> ERROR: Failed to call GetResultByRunningService
    <01-16-2015 08:52:55> DPServer.ms.com;    Setup Source Folder;    Error;    The computer account for the secondary site must have Read NTFS and share permissions to the Setup source folder and share. We
    recommend that you do not use administrative shares (for example, C$ and D$) because they require the secondary site computer account to be an administrator on the remote computer.
    <01-16-2015 08:52:55> INFO: Enter CheckSecSiteSqlOnSameMachine.
    <01-16-2015 08:52:55> INFO: Installing SQL Server Express, skipping SQL Server check.
    <01-16-2015 08:52:55> DPServer.ms.com;    SQL Server on the Secondary Site Computer;    Passed
    <01-16-2015 08:52:55> INFO:CheckSupportedFQDNFormat <DPServer.ms.com>
    <01-16-2015 08:53:04> INFO: NetBIOS <NZWHKVMAS020>
    <01-16-2015 08:53:04> DPServer.ms.com;    Primary FQDN;    Passed
    <01-16-2015 08:53:04> INFO:CheckMachineAccountHasADAccess <DPServer.ms.com>
    <01-16-2015 08:53:30> ERROR: Failed to call GetResultByRunningService
    <01-16-2015 08:53:30> DPServer.ms.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.
    <01-16-2015 08:53:30> INFO:CheckRemoteWMIConnection <DPServer.ms.com>
    <01-16-2015 08:53:44> DPServer.ms.com;    Remote Connection to WMI on Secondary Site;    Passed
    <01-16-2015 08:53:44> INFO: Check required collation of Sql Server.
    <01-16-2015 08:53:44> INFO: LangID <409>
    <01-16-2015 08:53:44> INFO: NOT primary site or CAS install, skipping check for reqired collation of SQL Server.
    <01-16-2015 08:53:44> DPServer.ms.com;    Required SQL Server Collation;    Passed
    <01-16-2015 08:53:44> ===== INFO: Prerequisite Type & Server: SQL:DPServer.ms.com =====
    <01-16-2015 08:53:44> <<<RuleCategory: Access Permissions>>>
    <01-16-2015 08:53:44> <<<CategoryDesc: Checking access permissions...>>>
    <01-16-2015 08:53:44> INFO: Installing SQL Server Express, skipping check for sysadmin role on SQL Server.
    <01-16-2015 08:53:44> DPServer.ms.com;    SQL Server sysadmin rights;    Passed
    <01-16-2015 08:53:44> INFO: Skip testing, no expand primary site specified.
    <01-16-2015 08:53:44> DPServer.ms.com;    SQL Server sysadmin rights for reference site;    Passed
    <01-16-2015 08:53:44> INFO: The rule 'Site server computer account administrative rights' has been run on server 'DPServer.ms.com', skipped.
    <01-16-2015 08:53:44> INFO: Installing SQL Server Express, skipping Windows integrated security check.
    <01-16-2015 08:53:44> DPServer.ms.com;    SQL Server security mode;    Passed
    <01-16-2015 08:53:44> <<<RuleCategory: System Requirements>>>
    <01-16-2015 08:53:44> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
    <01-16-2015 08:53:44> INFO: The rule 'Unsupported site server operating system version for Setup' has been run on server 'DPServer.ms.com', skipped.
    <01-16-2015 08:53:44> INFO: The rule 'Domain membership' has been run on server 'DPServer.ms.com', skipped.
    <01-16-2015 08:53:44> INFO: The rule 'Pending system restart' has been run on server 'DPServer.ms.com', skipped.
    <01-16-2015 08:53:44> <<<RuleCategory: Dependent Components>>>
    <01-16-2015 08:53:44> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
    <01-16-2015 08:53:44> INFO: Installing SQL Server Express, skipping SQL Server version check.
    <01-16-2015 08:53:44> DPServer.ms.com;    SQL Server version;    Passed
    <01-16-2015 08:53:44> DPServer.ms.com;    SQL Server Edition;    Passed
    <01-16-2015 08:53:44> DPServer.ms.com;    SQL Server Tcp Port;    Passed
    <01-16-2015 08:53:44> INFO: Checking if SQL Server memory is limited.
    <01-16-2015 08:53:44> INFO: Installing SQL Server Express, skipping SQL Server memory check.
    <01-16-2015 08:53:44> DPServer.ms.com;    Configuration for SQL Server memory usage;    Passed
    <01-16-2015 08:53:44> INFO: Checking if SQL Server memory is configured to reserve minimum memory.
    <01-16-2015 08:53:44> INFO: Installing SQL Server Express, skipping SQL Server memory allocation check.
    <01-16-2015 08:53:44> DPServer.ms.com;    SQL Server process memory allocation;    Passed
    <01-16-2015 08:53:44> INFO: Installing SQL Server Express, skipping SQL Server case insensitive validation.
    <01-16-2015 08:53:44> DPServer.ms.com;    Case-insensitive collation on SQL Server;    Passed
    <01-16-2015 08:53:44> INFO: Check Machine FQDN: <DPServer.ms.com>.
    <01-16-2015 08:53:44> INFO: getaddrinfo returned success.
    <01-16-2015 08:53:44> DPServer.ms.com;    Validate FQDN of SQL Server Computer;    Passed
    <01-16-2015 08:53:44> INFO: The rule 'Primary FQDN' has been run on server 'DPServer.ms.com', skipped.
    <01-16-2015 08:53:44> ===== INFO: Prerequisite Type & Server: MP:DPServer.ms.com =====
    <01-16-2015 08:53:44> <<<RuleCategory: Access Permissions>>>
    <01-16-2015 08:53:44> <<<CategoryDesc: Checking access permissions...>>>
    <01-16-2015 08:53:44> DPServer.ms.com;    Administrative share (Site system);    Passed
    <01-16-2015 08:53:44> INFO:CheckSiteSystemtoSQLConnectivity <DPServer.ms.com>
    <01-16-2015 08:53:44> INFO: Installing secondary site, skipping SQL Server connectivity check.
    <01-16-2015 08:53:44> DPServer.ms.com;    Site System to SQL Server Communication;    Passed
    <01-16-2015 08:53:44> <<<RuleCategory: System Requirements>>>
    <01-16-2015 08:53:44> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
    <01-16-2015 08:53:44> INFO: The rule 'Check Server Service is running' has been run on server 'DPServer.ms.com', skipped.
    <01-16-2015 08:53:52> INFO: OS version:0, ServicePack:0.
    <01-16-2015 08:53:52> DPServer.ms.com;    Unsupported management point operating system version for Setup;    Warning;    Configuration Manager site systems can only be installed on systems running Windows
    Server 2008 SP2 or later.
    <01-16-2015 08:53:52> INFO: The rule 'Domain membership' has been run on server 'DPServer.ms.com', skipped.
    <01-16-2015 08:54:05> INFO: Windows Cluster not found on DPServer.ms.com.
    <01-16-2015 08:54:05> DPServer.ms.com;    Windows Failover Cluster;    Passed
    <01-16-2015 08:54:05> INFO: The rule 'Pending system restart' has been run on server 'DPServer.ms.com', skipped.
    <01-16-2015 08:54:05> <<<RuleCategory: Dependent Components>>>
    <01-16-2015 08:54:05> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
    <01-16-2015 08:54:05> INFO: The rule 'Microsoft XML Core Services 6.0 (MSXML60)' has been run on server 'DPServer.ms.com', skipped.
    <01-16-2015 08:54:10> DPServer.ms.com;    IIS service running;    Warning;    Internet Information Services (IIS) is required for some site system roles. You have selected to install a site system role that
    requires IIS. Install IIS on the site system to continue setup.
    <01-16-2015 08:54:39> ERROR: Failed to get WEBSVCEXT from Remote Service on DPServer.ms.com.
    <01-16-2015 08:54:39> INFO: Failed to get IIS BITS Server Extensions state on DPServer.ms.com.
    <01-16-2015 08:54:39> DPServer.ms.com;    BITS installed;    Warning;    Background Intelligent Transfer Service (BITS) is required for the management point and distribution point site system roles. BITS
    is not installed, IIS 6 WMI compatibility component for IIS7 is not installed on this computer or the remote IIS host, or Setup was unable to verify remote IIS settings because IIS common components were not installed on the site server computer. Also, check
    if IIS/BITS services are running properly. Setup cannot continue until BITS is installed and enabled in the IIS settings.
    <01-16-2015 08:55:08> ERROR: Failed to get WEBSVCEXT from Remote Service on DPServer.ms.com.
    <01-16-2015 08:55:08> INFO: Failed to get IIS BITS Server Extensions state on DPServer.ms.com.
    <01-16-2015 08:55:08> DPServer.ms.com;    BITS enabled;    Warning;    Background Intelligent Transfer Service (BITS) is required for the management point and distribution point site system roles. BITS is
    not installed, IIS 6 WMI compatibility component for IIS7 is not installed on this computer or the remote IIS host, or Setup was unable to verify remote IIS settings because IIS common components were not installed on the site server computer. Also, check
    if IIS/BITS services are running properly. Setup cannot continue until BITS is installed and enabled in the IIS settings.
    <01-16-2015 08:55:08> DPServer.ms.com;    IIS HTTPS Configuration for management point;    Passed
    <01-16-2015 08:55:08> INFO: Stand-alone primary site or secondary site. Skip checking firewall settings for SQL Server
    <01-16-2015 08:55:08> DPServer.ms.com;    Firewall exception for SQL Server for management point;    Passed
    <01-16-2015 08:55:08> DPServer.ms.com;    Administrative rights on management point;    Passed
    <01-16-2015 08:55:08> INFO:CheckV4ClientNotInstalled <DPServer.ms.com>
    <01-16-2015 08:55:36> ERROR: Failed to call GetResultByRunningService
    <01-16-2015 08:55:36> DPServer.ms.com;    Client Version on Management Point Computer;    Warning;    You cannot install the management point on a computer with an earlier version of the Configuration Manager
    client installed. Upgrade the client to the current version, remove the client, or select a different computer for the management point installation, and then try again.
    <01-16-2015 08:55:36> ===== INFO: Prerequisite Type & Server: DP:DPServer.ms.com =====
    <01-16-2015 08:55:36> <<<RuleCategory: Access Permissions>>>
    <01-16-2015 08:55:36> <<<CategoryDesc: Checking access permissions...>>>
    <01-16-2015 08:55:36> <<<RuleCategory: System Requirements>>>
    <01-16-2015 08:55:36> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
    <01-16-2015 08:55:49> DPServer.ms.com;    Unsupported distribution point operating system version for Setup;    Warning;    Configuration Manager distribution point can only be installed on systems running
    Windows Server 2003 or later.
    <01-16-2015 08:55:49> INFO: The rule 'Domain membership' has been run on server 'DPServer.ms.com', skipped.
    <01-16-2015 08:55:49> INFO: The rule 'Windows Failover Cluster' has been run on server 'DPServer.ms.com', skipped.
    <01-16-2015 08:55:49> INFO: The rule 'Pending system restart' has been run on server 'DPServer.ms.com', skipped.
    <01-16-2015 08:55:49> <<<RuleCategory: Dependent Components>>>
    <01-16-2015 08:55:49> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
    <01-16-2015 08:55:57> DPServer.ms.com;    Microsoft XML Core Services 6.0 (MSXML60) for distribution point;    Warning;    MSXML 6.0 or later libraries are required for Configuration Manager console and
    Configuration Manager site server installations. MSXML 6.0 is available for download at http://go.microsoft.com/fwlink/?LinkId=215744
    <01-16-2015 08:55:57> INFO: The rule 'IIS service running' has been run on server 'DPServer.ms.com', skipped.
    <01-16-2015 08:55:57> DPServer.ms.com;    IIS HTTPS Configuration for distribution point;    Passed
    <01-16-2015 08:55:57> DPServer.ms.com;    Administrative rights on distribution point;    Passed
    <01-16-2015 08:55:57> ***************************************************
    <01-16-2015 08:55:57> ******* Prerequisite checking is completed. *******
    <01-16-2015 08:55:57> ***************************************************
    <01-16-2015 08:55:57> INFO: Updating Prerequisite checking result into the registry
    <01-16-2015 08:55:57> INFO: Connecting to DPServer.ms.com registry
    <01-16-2015 08:56:09> INFO: Setting registry values
    <01-16-2015 08:56:16> ERROR: Failed to update prerequisite results into the registry; error = 1.

    <01-16-2015 08:48:08> DPServer.ms.com;    Site server computer account administrative rights;    Error;    Configuration Manager Setup requires that the site server computer has administrative rights
    on the SQL Server and management point computers.
    Actually the administrative permission had been granted.

Maybe you are looking for

  • Payment Terms

    Hi, Can anyone explain me how to change the payment terms of the PO. What is the configuration path. what is the impact in changing the payment terms from one to the other . Where in the PO we can see this. Thanks in advance.

  • Pga_aggregate_target  and hash_join cost (anomalies)

    Hi, I've got some performance issues with queries using bind variables (BVP + histograms = evil). I did some test cases in test environment where the only difference with PROD was pga_aggregate_target . And was able to make plan changes w/o changing

  • Customer Group Deletion

    Dear All, In our compnay we are maintaining sales persons as Customer group in sap system (Sales Order & Customer Master).  some of the sales persons has resigned.  so we have deleted their names from customer group. so system showing the serial numb

  • GR processing time can be customer based

    Hi,    Would like to know whether for  GR Processing Time can be customer based instead of setup in Material master?    Please kindly advise. Thanks Regards, shirley

  • Error on Logging in

    Many times when logging in (seems to be manly when I start by clicking 'my questions' - I also have this bookmarked because it's the most sensible place for me to start when visiting these discussion forums) I get an error saying "page not found". Th