Cannot install SCCM 2012 SP1 CU4

Hi,
I just tried to apply CU4 over one of my SCCM 2012 SP1 CU3 deployments and I receive the following message during the initial verification phase:
Server update status: This update applies to product version 5.0.7804. The installed version on this computer is 5.0.7958.1000. This update is not applicable to this computer.
Console update status: No serviceable configuration manager role was found on the local system.
If I engage the verification phase on this installation for CU2 and CU3 there is no problem at all, so this must be a CU4 package specific error.
Anybody experiencing the same behavior ?

The latest CU that I see for SCCM 2012 SP1 is SP1 Cumulative Update 3, are you sure you are working with the proper file?  .
CU4 was released this week:
http://blogs.technet.com/b/configurationmgr/archive/2014/01/29/now-available-cumulative-update-4-for-system-center-2012-configuration-manager-service-pack-1.aspx
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Similar Messages

  • SMS Provider Locations Do Not Match - Problem installing SCCM 2012 R2 CU4

    I have an SCCM 2012R2 CU1 site that has been upgraded from SCCM 2012 non-SP1, so I have gone from 2012 to 2012SP1 through CU5 and then to R2 and then to CU1.
    Over the course of the life of this site, which has more than 10k clients and 10 Site Systems, we have installed roles, removed roles, moved roles and removed Site Systems.
    I have also installed and removed SMS providers . . . which is where my issues begin.
    The site properties in the console list 6 SMS Providers and even lists an SMS provider on a server that was retired and is no longer a Site System.  When I query WMI using the following VBS script it only returns the *ACTUAL* SMS Provider locations,
    2 of the 6 listed in the GUI.
    On Error Resume Next
    Const ForReading = 1, ForWriting = 2, ForAppending = 8
    strComputer = "." 
    Set oFS = CreateObject("Scripting.FileSystemObject")
    Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\sms")
    If Err.Number <> 0 Then
    WScript.Echo "Cannot connect to WMI"
    WScript.Echo vbTab & "Error " & Err.Number & " - " & Err.Description
    End If
    Set oLog = oFS.OpenTextFile("C:\Temp\SMS_ProvList.log",ForAppending, True)
    If Err.Number <> 0 Then
    WScript.Echo "Could not create output file"
    WScript.Echo vbTab & "Error " & Err.Number & " - " & Err.Description
    End If
    Set colItems = objWMIService.ExecQuery("SELECT * FROM SMS_ProviderLocation",,48)
    count = 0
    For Each objItem in colItems
        count = count + 1
        oLog.WriteLine "-----------------------------------"
        oLog.WriteLine Now()
        oLog.WriteLine "Provider instance " & count &  " : " & objItem.Machine
        oLog.WriteLine "NamespacePath : " & objItem.NamespacePath     
        oLog.WriteLine ""
    Next
    I have a test environment which has also gone through some growth over its lifetime and has had the same changes to SMS Providers made.  When I first attempted to install SCCM 2012 R2 CU4 in this test environment the installer continually failed the
    prerequisite checker when querying the CU level of the SMS Providers.  The only way that I could get past that issue was by running a site maintenance task via the CM installer and installing an SMS Provider at the location that had previously been an
    SMS Provider but I had uninstalled that role.
    I do not want to have to do that in my production environment, and would not even be able to do so if I wanted as I have retired one of the servers listed and cannot re-provision that machine.
    Any CM12 gurus out there with suggestions?  This strikes me as a standard MS problem when having multiple development teams working on a product/update and not having a standard location to check for configuration information (This is exactly the problem
    when configuring DNS suffixes via GPO and not manually setting the GUI to match).
    Thanks!
    Josh Gerner
    Cornell University.

    The issue I have is that I cannot find the WMI class that holds the SMS Providers that are returned by the GUI.
    I actually engaged MS Premier for a SCCM 2012 RAAS about 2 years ago and that was when the discrepancy first reared it's head.  The support person that I worked with couldn't give me a way of cleaning those entries at that point which is when I started
    logging the locations to be sure that my maintenance task was really installing or removing the SMS Providers.
    Josh Gerner

  • SCCM 2012 SP1 CU4 migrated DP shows package status "unknown"

    I have a SCCM 2012 SP1 CU4 environment and have shared SCCM 2007 distribution points.
    Today I migrated one of the DP's which seems to work well.
    However all my packages shows now the status "unknown" for this migrated DP.
    This is a problem which should be fixed in CU4 according to the CU4 description. But it is not :-(
    Any idea how to solve this ? R2 install ?

    Some additional information:
    I noticed that the package sources are still available at the "old" ditribution point share abd not on the new sccm 2012 distribution point share. When performing actions described in step 3 below the package becomes available on the distribution point
    share......then i guess i can remove the content from the "old" distribution point share ????
    I noticed that when a package got the status "unknown" for de migrated DP the following action fix the problem:
    --> i remove the DP from the package and immediately add it again, the package status becomes "Successful".....hummm....ok....maybe a script could be created for this
    I noticed that when a package got the status "unknown" and the package is also located on the "distribution point share" then following will fix the issue:
    --> edit the package and remove the migrated DP and remove the checkbox for string on the distribution point share. Then add the DP again, click Apply and then set the checkbox for storing on the distribution point share and Apply again. Then wait and package
    will become available Successful and the package will become available on the distribution point share
    But i have 800 packages and 50 to be migrated DP's.....this is not a solution....but what is ????
    Any help, ideas, tips, hints, recommendations ?
    My overal thoughts are that migrating of a SCCM 2007 DP is not really working at all !!!!!
    Or does someone has other experience with e.g. R2 installed ? If so then I will upgrade first...

  • [Forum FAQ] Management Point fails after installing SCCM 2012 SP1

    Symptom:
    The Management Point might fail to be installed after you install SCCM 2012 sp1 on Windows Server 2012, either fresh install or others.
    You might see some errors in mpMSI.log like listed below.
    “Setup was unable to compile the file CcmExec_Global.mof”
    “The error code is 80041002”
    Cause:
    Reinstall Management Point cannot work. This is because CCM Namespace remains in WMI which prevents SCCM from installing MP. You need clear CCM Namespace from WMI.
    Resolution:
    1. Uninstall Management Point from the console, then wait for the uninstallation to finish in MPSetup.log.
    2. Open Wbemtest -> Connect to root -> Click Enum Classes and choose Recursive -> Double click _NAMESPACE in Query Result dialog -> Click Instances -> Delete  _NAMESPACE.Name=”ccm”
    3. Install Management Point.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Symptom:
    The Management Point might fail to be installed after you install SCCM 2012 sp1 on Windows Server 2012, either fresh install or others.
    You might see some errors in mpMSI.log like listed below.
    “Setup was unable to compile the file CcmExec_Global.mof”
    “The error code is 80041002”
    Cause:
    Reinstall Management Point cannot work. This is because CCM Namespace remains in WMI which prevents SCCM from installing MP. You need clear CCM Namespace from WMI.
    Resolution:
    1. Uninstall Management Point from the console, then wait for the uninstallation to finish in MPSetup.log.
    2. Open Wbemtest -> Connect to root -> Click Enum Classes and choose Recursive -> Double click _NAMESPACE in Query Result dialog -> Click Instances -> Delete  _NAMESPACE.Name=”ccm”
    3. Install Management Point.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

  • After installing SCCM 2012 R2 CU4, I show a Distribution Point warning that won't clear.

    I recently installed SCCM 2012 R2 CU4 on a LAB environment, and nowhere is it more important to wait until all requisite site roles are reinstalled before doing anything else.
    I did, and still do, have an warning/ error on the Site components that shows up on one of the child primary sites after the CU4 installation.
    Distribution Manager has not tried to install IIS component of operating system to distribution point “[“Display=\\SCxxx\”]MSWNET:[“SMS_SITE=xxx”]\\xxx\”. You should install and configure IIS manually. Please ensure RDC is also enabled.
    IIS is installed, RDC is enabled, but I get this error. What could be the real issue?

    Hi,
    So you have tried to reinstall IIS conponents and DP?
    Have you checked the distmgr.log? Anything helpful?
    Best Regards,
    Joyce
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Management Point fails after installing SCCM 2012 SP1

    I'm carrying out an install of SCCM 2012 SP1 with the following hardware (fresh install not an upgrade from 2007)
    1. Newly built Windows Server 2012 box
    2. Site database located on a remote SQL 2012 cluster, both nodes Windows Server 2012, with CU5
    The install went fine but when checking the Site Server Components the Management Point isn't installing. The following both show errors;
    SMS_MP_CONTROL_MANAGER - MP.msi could not install. Checked the MP.msi log file which shows the following errors;
    [19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\CcmExec_Global.mof' (Phase: 3, Object: 5, Lines: 76 - 83, Error: 80041002)
    [19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\PolicyDefaults.mof' (Phase: 3, Object: 4, Lines: 49 - 57, Error: 80041002)
    [19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\StateMsgSchema.mof' (Phase: 3, Object: 6, Lines: 89 - 94, Error: 80041002)
    [19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\DataTransferService.mof' (Phase: 3, Object: 5, Lines: 318 - 323, Error: 80041002)
    [19:53:19] Failed to compile 'C:\Program Files\SMS_CCM\CcmExec_MP.mof' (Phase: 3, Object: 1, Lines: 31 - 36, Error: 80041002)
    MSI (s) (0C!94) [19:53:20:862]: Product: ConfigMgr Management Point -- Error 25140. Setup was unable to compile the file CcmExec_Global.mof
    The error code is 80041002
    Error 25140. Setup was unable to compile the file CcmExec_Global.mof
    The error code is 80041002
    CustomAction CcmRegisterWmiMofFile returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    SMS_NOTIFICATION_SERVER - bgbisapi.msi could not install. Extract from log below;
    [19:53:38] IGNORE: Failed to delete extension 'C:\Program Files\SMS_CCM\bgbisapi.dll'. Return Code = 0x80020009 (The extension might not be registered)
    [19:53:39] WARNING: Failed to remove PerfLib entries for performance application SmsBgb (2)
    [19:53:39] WARNING: Failed to remove configuration for performance application SmsBgb (80070057)
    MSI (s) (0C!80) [19:53:39:540]: Product: BGB http proxy -- Internal Error 25001. 80070057
    Internal Error 25001. 80070057
    CustomAction CcmRegisterPerfCounters returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    I've tried uninstalling MP and reinstalling, triple checked all the right pre-reqs in Roles and Features are enabled, even rebuilt the server from scratch and tried again but same result. 
    Would really appreciate some help if anyone's fixed this issue

    I'm still struggling, I've uninstalled MP
    <04/16/14 08:06:59> SMSMP Setup Started....
    <04/16/14 08:06:59> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /deinstall /siteserver:EICSC001 SMSMP 0
    <04/16/14 08:06:59> Deinstalling the SMSMP
    <04/16/14 08:06:59> No versions of SMSMP are installed.  Returning Success.
    <04/16/14 08:06:59> ~RoleSetup().
    Ran the command, Invoke-Command  {gwmi -query "SELECT * FROM __Namespace WHERE Name='CCM'" -Namespace "root" | Remove-WmiObject}
    Checked Namespace Instances to ensure '= ccm' is not longer there. 
    Rebooted Server and re-installed MP but it still fails
    <04/16/14 08:37:26> ====================================================================
    <04/16/14 08:37:26> SMSMP Setup Started....
    <04/16/14 08:37:26> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:EICSC001 SMSMP 0
    <04/16/14 08:37:26> Installing Pre Reqs for SMSMP
    <04/16/14 08:37:26>         ======== Installing Pre Reqs for Role SMSMP ========
    <04/16/14 08:37:26> Found 2 Pre Reqs for Role SMSMP 
    <04/16/14 08:37:26> Pre Req MSXML60 found.
    <04/16/14 08:37:26> No versions of MSXML60 are installed.  Would install new MSXML60.
    <04/16/14 08:37:26> Enabling MSI logging.  msxml6_x64.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\msxml6_x64MSI.log
    <04/16/14 08:37:26> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\00000409\msxml6_x64.msi 
    <04/16/14 08:37:26> msxml6_x64.msi exited with return code: 0
    <04/16/14 08:37:26> msxml6_x64.msi Installation was successful.
    <04/16/14 08:37:26> Pre Req SqlNativeClient found.
    <04/16/14 08:37:26> SqlNativeClient already installed (Product Code: {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5}). Would not install again.
    <04/16/14 08:37:26> Pre Req SqlNativeClient is already installed. Skipping it.
    <04/16/14 08:37:26>         ======== Completed Installation of Pre Reqs for Role SMSMP ========
    <04/16/14 08:37:26> Installing the SMSMP
    <04/16/14 08:37:26> Passed OS version check.
    <04/16/14 08:37:26> IIS Service is installed.
    <04/16/14 08:37:26> No versions of SMSMP are installed.  Installing new SMSMP.
    <04/16/14 08:37:26> Enabling MSI logging.  mp.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log
    <04/16/14 08:37:26> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi CCMINSTALLDIR="D:\Program Files\SMS_CCM" CCMSERVERDATAROOT="D:\Program Files\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE
    SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
    <04/16/14 08:37:26> mp.msi exited with return code: 1603
    <04/16/14 08:37:26> Backing up D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError
    <04/16/14 08:37:26> Fatal MSI Error - mp.msi could not be installed.
    <04/16/14 08:37:26> ~RoleSetup().
    On checking I don't seem to have anything in IIS, no default web site.
    I've tried reinstalling IIS and reinstalling SCCM 2012 but what ever I do I still hit the same issue with the Management Point.
    Any assistance would be greatly appreciated.
    Thanks

  • Error installing SCCM 2012 SP1 client

    Hi All,
    I am getting the following error, detailed in the client.msi.log, when trying to install the SCCM 2012 SP1 client on a couple of windows 2008 R2 servers.
    Error 1904. Module C:\Windows\CCM\StatusAgentProxy.dll failed to register.  HRESULT -2147010895
    The ccmsetup.log details the same message without Error 1904 indicated.
    I am installing the client using the SUP method, which has worked without any problems on all 180 other windows servers I have done.  ccmsetup starts and downloads all pre reqs required for the client rollout, but it then hits this error and does not
    finish the installation.
    Any help would be much appreciated?
    Regards PowerShell90

    Hi,
    I've seen this issue a couple of times and usually it's related to incorrect Versions of C++ Library installed on the system you try to install the Client. Try and remove any existing installations, reboot and install this version;
    http://www.microsoft.com/en-us/download/details.aspx?id=26368
    Let me know how it goes.

  • SCCM 2012 SP1 CU4 ccmsetup runs with SMS Agent Host on the "Service" mmc after upgrading the client to CU4.

    Dear Brothers,
    I have an issue with two (2) of my Site Servers, I have below scenarioa and explained issue details:
    Scenario:
    1. Server1: Windows 2012 Server, CAS, SCCM 2012 Hierarchy Roles: Management Point, DP, SUP, Component Server.
    2. Server2: Windows 2008 R2 Server, Secondary Site Role, SCCM 2012 Hierarchy Roles: Management Point, DP, Component Server.
    Issue:
    After updating the SCCM 2012 Client to CU4 on the actual Site Server, the "ccmsetup" appears also with "SMS Agent Host"
    at the Service MMC. Which I believed this is very unusual behavior.
      The Client however it seems properly installed and working please see below details:
    Questions: I believed the Client installations are still running on the background, even though the Client tends to look working on the Control Panel.
    1. How can I resolved this issue?
    2. Should I need to perform a total Client uninstallation, even depth till removing entries in the Registry levels?
    3. Or this is a normal behavior for the scenario?
    Advance thanks for your future replies, my brothers in technology.

    Dear Brother,
    2 Weeks since I installed the CU4, it seems a little bit to long isn't it? for both the ccmsetup and the SMS Host Agent Services to exist, for the errors on the ccmsetup.log there are some errors after uninstallation since I am trying to removed
    the issue .
    CCMsetup.log
    ==========[ ccmsetup started in process 5376 ]========== 7/1/2014 7:14:45 PM 4104 (0x1008)
    Running on platform X64 7/1/2014 7:14:45 PM 4104 (0x1008)
    Updated security on object C:\Windows\ccmsetup\cache\. 7/1/2014 7:14:45 PM 4104 (0x1008)
    Launch from folder C:\Windows\ccmsetup\ 7/1/2014 7:14:45 PM 4104 (0x1008)
    CcmSetup version: 5.0.7804.1500 7/1/2014 7:14:45 PM 4104 (0x1008)
    Running on OS (6.2.9200). Service Pack (0.0). SuiteMask = 272. Product Type = 3 7/1/2014 7:14:45 PM 4104 (0x1008)
    Ccmsetup command line: ccmsetup.exe  /uninstall 7/1/2014 7:14:45 PM 4104 (0x1008)
    Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required. 7/1/2014 7:14:45 PM 4104 (0x1008)
    Command line: ccmsetup.exe  /uninstall 7/1/2014 7:14:45 PM 4104 (0x1008)
    SslState value: 224 7/1/2014 7:14:45 PM 4104 (0x1008)
    Detected client version 5.00.7804.1500 from WMI. 7/1/2014 7:14:45 PM 4104 (0x1008)
    Updated security on object C:\Windows\ccmsetup\. 7/1/2014 7:14:45 PM 4104 (0x1008)
    Another instance of ccmsetup is already running. 7/1/2014 7:14:45 PM 4104 (0x1008)
    Task 'Configuration Manager Client Upgrade Task' does not exist 7/1/2014 7:14:45 PM 4104 (0x1008)
    CcmSetup is exiting with return code 3 7/1/2014 7:14:45 PM 4104 (0x1008)
    MSI: Action 19:15:20: SmsRemoveUIEvents. This custom action is no longer used. The custom action used to remove the COM+ event subscriber and publisher used for UI notifications. We no longer use COM+ events for UI notifications. 7/1/2014 7:15:20 PM 5628
    (0x15FC)
    MSI: Action 19:15:20: CcmUnregisterPerfCounters. Removes performance counters gathered in the CcmUnregisterPerfCountersInit action 7/1/2014 7:15:20 PM 5628 (0x15FC)
    MSI: Action 19:15:20: CcmRemoveLanternDocuments. Removing documents from Microsoft Policy Platform that have been submitted by Configuration Manager authority. 7/1/2014 7:15:20 PM 5628 (0x15FC)
    MSI: Action 19:15:30: CcmTypelibRollback. In the event of install failing, this event rolls back the type libraries to the state before install started. 7/1/2014 7:15:30 PM 5628 (0x15FC)
    MSI: Action 19:15:30: SmsDeinstallDesktopClient. This custom action uninstalls the desktop client with following steps-
    1. Makes sure there are no desktop client installations in progress and prevents any new instance of intallation.
    2. Checks the desktop client version and gets the installation direcotry.
    3. Stops remote control and other desktop components.
    4. Kills the following client processes - clisvc1.exe, pea32.exe, smsapm32.exe, smsmon32.exe and sms_reen.exe.
    5. Saves information needed for migration and uninstalls the desktop components followed by clean up. 7/1/2014 7:15:30 PM 5628 (0x15FC)
    MSI: Action 19:15:30: CcmDetectFilesInUseRollback. Rolls back files moved by CcmDetectFilesInUse. 7/1/2014 7:15:30 PM 5628 (0x15FC)
    MSI: Action 19:15:30: CcmDetectFilesInUse. Moves files that are in use so that they will be deleted upon the next reboot. 7/1/2014 7:15:30 PM 5628 (0x15FC)
    MSI: Action 19:15:31: CcmDetectFilesInUseCommit. Commits action of CcmDetectFileInUse. After this we cannot rollback. 7/1/2014 7:15:31 PM 5628 (0x15FC)
    MSI: Action 19:15:31: InstallFiles. Copying new files 7/1/2014 7:15:31 PM 5628 (0x15FC)
    MSI: Internal Error 2902. ixfAssemblyCopy 7/1/2014 7:15:32 PM 5628 (0x15FC)
    MSI: Action 19:15:32: Rollback. Rolling back action: 7/1/2014 7:15:32 PM 5628 (0x15FC)
    File C:\Windows\ccmsetup\configmgr2012ac-sp1-kb2882125-x64.msp installation failed. Error text: ExitCode: 1603
    Action: InstallFiles.
    ErrorMessages:
    Internal Error 2902. ixfAssemblyCopy
     7/1/2014 7:15:33 PM 5628 (0x15FC)
    A Fallback Status Point has not been specified.  Message with STATEID='301' will not be sent. 7/1/2014 7:15:33 PM 5628 (0x15FC)
    Deleted file C:\Windows\ccmsetup\ccmsetup.xml 7/1/2014 7:15:33 PM 5628 (0x15FC)
    Deleted file C:\Windows\ccmsetup\client.msi 7/1/2014 7:15:33 PM 5628 (0x15FC)
    CcmSetup failed with error code 0x80070643 7/1/2014 7:15:33 PM 5628 (0x15FC)
    Regards,

  • Upgrade from SCCM 2012 SP1 CU4 to R2 Fails - Unsupported Upgrade Path

    Hi everybody,
    I'm currently upgrading our SCCM infrastructure to SCCM 2012 R2 after have finished with the upgrade from SCCM 2012 RTM to SP1 CU4, thus far everything works fine, but when I try to update any
    of the site servers, whether CAS or Primary, I'm getting the following error message in the Prerequisites Check:
    I've gone through the system requirements and prerequisites over and over again and I can assure you that every possible update, supported OS, feature set, SQL Server, check list, etc,
    etc, have been followed as per the official documentation available, however I'm stuck in this point, and surely enough I haven't been able to find out a similar case.Additionally I'm adding
    the ConfigMgrPrereq log (the relevant portion of it) in case someone could kindly take a look at it.
    <04-25-2014 02:06:46> ******* Start Prerequisite checking. *******
    <04-25-2014 02:06:47> ********************************************
    <04-25-2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade,
    minimum supported installed build version is [7804].
    <04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;   
    Unsupported upgrade path;    Error;   
    Configuration Manager has detected that one or more sites in the hierarchy are installed with a version of Configuration Manager that is not supported for upgrade.
    <04-25-2014 02:07:00> INFO: This rule only apply to primary site, skip checking.
    <04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;   
    Active Replica MP;    Passed
    <04-25-2014 02:07:00> INFO: This rule only applies to primary or secondary site in hierarchy, skip checking.
    <04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;   
    Parent site replication status;    Passed
    <04-25-2014 02:07:00> <<<RuleCategory: Database Upgrade Requirements>>>
    <04-25-2014 02:07:00> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
    <04-25-2014 02:07:00> ===== INFO: Prerequisite Type & Server: SQL:INFPROSCCMCDB.usersad.everis.int
    =====
    <04-25-2014 02:07:00> <<<RuleCategory: Access Permissions>>>
    <04-25-2014 02:07:00> <<<CategoryDesc: Checking access permissions...>>>
    <04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int;   
    SQL Server sysadmin rights;    Passed
    <04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int;    SQL Server sysadmin rights
    for reference site;    Passed
    <04-25-2014 02:07:00> INFO: CheckLocalSys is Admin of <INFPROSCCMCDB.usersad.everis.int>.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Site server computer account administrative rights;    Passed
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    SQL Server security mode;    Passed
    <04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
    <04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
    <04-25-2014 02:07:09> INFO: OS version:601, ServicePack:1.
    <04-25-2014 02:07:09> INFO: Target computer is a Windows server.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Unsupported site server operating system version for Setup;    Passed
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Domain membership;    Passed
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Pending system restart;    Passed
    <04-25-2014 02:07:09> <<<RuleCategory: Dependent Components>>>
    <04-25-2014 02:07:09> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
    <04-25-2014 02:07:09> INFO: Return code:0, Major:10, Minor:50, BuildNum:4000
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    SQL Server version;    Passed
    <04-25-2014 02:07:09> INFO: Get Sql edition:Enterprise Edition.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    SQL Server Edition;    Passed
    <04-25-2014 02:07:09> INFO: Checking Tcp is enabled to Static port, SQL Server:INFPROSCCMCDB.usersad.everis.int,
    Instance:.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    SQL Server Tcp Port;    Passed
    <04-25-2014 02:07:09> INFO: Checking if SQL Server memory is limited.
    <04-25-2014 02:07:09> INFO: SQL Server memory is limited.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Configuration for SQL Server memory usage;    Passed
    <04-25-2014 02:07:09> INFO: Checking if SQL Server memory is configured to reserve minimum memory.
    <04-25-2014 02:07:09> INFO: Installing the central administration site or primary site, requires SQL
    Server to reserve a minimum of 8 gigabytes (GB) of memory.
    <04-25-2014 02:07:09> WARN: SQL Server minimum memory is 8000 MB.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;    SQL Server process memory allocation;   
    Warning;    Configuration Manager requires SQL Server to reserve a minimum of 8 gigabytes (GB) of memory for the central administration site and primary site and a minimum of 4 gigabytes (GB) for the secondary site. This memory is reserved by
    using the Minimum server memory setting under Server Memory Options and is configured by using SQL Server Management Studio. For more information about how to set a fixed amount of memory, see
    http://go.microsoft.com/fwlink/p/?LinkId=233759.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Case-insensitive collation on SQL Server;    Passed
    <04-25-2014 02:07:09> INFO: Check Machine FQDN: <INFPROSCCMCDB.usersad.everis.int>.
    <04-25-2014 02:07:09> INFO: getaddrinfo returned success.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Validate FQDN of SQL Server Computer;    Passed
    <04-25-2014 02:07:09> INFO:CheckSupportedFQDNFormat <INFPROSCCMCDB.usersad.everis.int>
    <04-25-2014 02:07:09> INFO: NetBIOS <INFPROSCCMCDB>
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Primary FQDN;    Passed
    <04-25-2014 02:07:09> <<<RuleCategory: Site Upgrade Requirements>>>
    <04-25-2014 02:07:09> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
    <04-25-2014 02:07:09> <<<RuleCategory: Database Upgrade Requirements>>>
    <04-25-2014 02:07:09> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
    <04-25-2014 02:07:09> ===== INFO: Prerequisite Type & Server: SDK:INFPROSCCMCMS.usersad.everis.int
    =====
    <04-25-2014 02:07:09> <<<RuleCategory: Access Permissions>>>
    <04-25-2014 02:07:09> <<<CategoryDesc: Checking access permissions...>>>
    <04-25-2014 02:07:09> INFO: The rule 'Administrative rights on site system' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
    skipped.
    <04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
    <04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
    <04-25-2014 02:07:09> INFO: The rule 'Unsupported site server operating system version for Setup' has
    been run on server 'INFPROSCCMCMS.usersad.everis.int', skipped.
    <04-25-2014 02:07:09> INFO: The rule 'Domain membership' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
    skipped.
    <04-25-2014 02:07:09> INFO: Windows Cluster not found on INFPROSCCMCMS.usersad.everis.int.
    <04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;   
    Windows Failover Cluster;    Passed
    <04-25-2014 02:07:10> INFO: The rule 'Pending system restart' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
    skipped.
    <04-25-2014 02:07:10> <<<RuleCategory: Dependent Components>>>
    <04-25-2014 02:07:10> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
    <04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;   
    Windows Deployment Tools installed;    Passed
    <04-25-2014 02:07:10> INFO: CheckAdkWinPeInstalled on INFPROSCCMCMS.usersad.everis.int.
    <04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;    Windows Preinstallation Environment
    installed;    Passed
    <04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;   
    SMS Provider machine has same domain as site server;    Passed
    <04-25-2014 02:07:10> <<<RuleCategory: Site Upgrade Requirements>>>
    <04-25-2014 02:07:10> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
    <04-25-2014 02:07:10> <<<RuleCategory: Database Upgrade Requirements>>>
    <04-25-2014 02:07:10> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
    <04-25-2014 02:07:10> ***************************************************
    <04-25-2014 02:07:10> ******* Prerequisite checking is completed. *******
    <04-25-2014 02:07:10> ******************************************<04-25-2014 02:07:10> INFO: Updating
    Prerequisite checking result into the registry
    <04-25-2014 02:07:10> INFO: Connecting to INFPROSCCMCMS.usersad.everis.int registry
    <04-25-2014 02:07:10> INFO: Setting registry values
    If you wonder whether it might be related to this error:
    -2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade, minimum supported installed build version is [7804].
    I confirm that this one site is a secondary one that's attached to a primary site and this log is from the CAS server, I managed to tall it and delete it from that site, but still appears listed
    on the CAS management console, any idea how to force the removal of a secondary site that's attached to a primary from the CAS site when it has been removed already from said primary?
    I've already tried the
    Preinst /DELSITE XXX  command but it only works when the site to remove it's attached to the local site and certainly not from a CAS
    Finally,  the version, build number and everything is correct, no idea what could be the problem, does anybody know a way to bypass this or force the re-evaluation of this rules, I've got
    the impression that it's being cached somehow.
    Any help would be highly appreciated,
    Thank you.
    Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE

    Hello again everybody,
    I've finally managed to fix this up, in the end I had to delete those entries manually from the database as Garry suggested. After this was done the upgrade has gone through as expected with no further ado and has finalized already, now moving on to the
    primary sites.
    If anybody out there is facing the same issue, what I did was to delete those "stubborn" records executing the following statements over the CAS database:
    DELETE
    FROMServerDataWHERESiteCode='XXX'
    DELETE
    FROMSC_SiteDefinitionWHERESiteCode='XXX'
    And this is pretty much about it. I'd recommend to take a proper backup first though as best practice.
    Thank you all anyways for your answers and comments,
    Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE

  • Previously blocked client computers - now cannot install SCCM 2012 R2 client

    Hello,
    I have a Primary Site on SCCM 2012 R2. New installation of 2012 R2, not upgrade from SCCM 2007. My environment is pretty small for now, having added just few dept computers in the company.
    We are using SCCM for Endpoint Security antivirus deployment. Some time ago I had not configured the Discovery methods correctly and the scep client started to install on few machines on which it was not supposed to be installed. I removed the clients then
    (both remote and local uninstallation) but since the sccm client was getinng installed again - I had to Block these few machines. Now the problem is that I cannot install the scep client on these computers that have previously been blocked. I am sure the previous
    block is the reason because these are about 6-7 machines and only they do not install. All others do install scep client. The installation process goes smooth on these problematic machines, ccmsetup folder gets created in C:\Windows, I follow the ccmsetup.log
    and it says  " <![LOG[CcmSetup is exiting with return code 0]LOG]!><time="12:33:56.415-180" date="10-08-2014" component="ccmsetup" context="" type="1" thread="3992"
    file="ccmsetup.cpp:10875">  "  at the end of the log which is what it is supposed to show when installation goes ok, then Ccmexec.exe process continues running but folder Microsoft Security Client in C:\Program Files never gets
    created and no scep client gets installed.
    I tried deleting the computers from the sccm console and discovering them anew - did not help. Tried even renaming the comp locally, after having it deleted from sccm console, then adding it anew hoping sccm will regard it as a new resource-again no good.
    All these computers have the Approve, Block and Unblock buttons greyed out/inactive in console.
    Has anyone had this same problem?  Any ideas what can be done. Thank you.
    Regards,
    Hristo

    Hi,
    were you ever able to fix this?
    I'm running in a similar issue here.
    One single client was blocked, then deleted, lateron recreated (imported manually name and MAC address).
    Now the client is unable to register itself in SCCM 2012 R2 (no CU yet).
    Tried the usual stuff: uninstalled SCCM client, remove the entries of CCMsetup and SMS from registry, deleted  the SMS certs from the computer personal
    store and deleted  the smscfg.ini from C:\Windows. Then re-installed the SCCM client
    Client logs look fine, except ClientIDManagerStartup.log:
    <![LOG[[RegTask] - Client is not registered. Sending registration request for GUID:F295F120-9C99-4D10-82B7-027FDD86B5F6 ...]LOG]!><time="14:46:11.555-60" date="01-12-2015" component="ClientIDManagerStartup" context=""
    type="1" thread="6320" file="regtask.cpp:1609">
    <![LOG[[RegTask] - Server rejected registration request: 3]LOG]!><time="14:46:12.616-60" date="01-12-2015" component="ClientIDManagerStartup" context="" type="3" thread="6320" file="regtask.cpp:1675">
    On the server:
    Begin validation of Certificate [Thumbprint 12923BCACDAE5B89547A25E54BF11E533163742F] issued to 'SMS'    MP_RegistrationManager    12.01.2015 14:31:10    8600 (0x2198)
    Completed validation of Certificate [Thumbprint 12923BCACDAE5B89547A25E54BF11E533163742F] issued to 'SMS'    MP_RegistrationManager    12.01.2015 14:31:10    8600 (0x2198)
    Encountered database error while verifying headers for client 'GUID:F3063334-69B4-471F-B158-56782E499F4A' (0x87d00238).    MP_RegistrationManager    12.01.2015 14:31:10    8600 (0x2198)
    CCMValidateAuthHeaders failed (0x87d00238) to validate headers for client 'GUID:F3063334-69B4-471F-B158-56782E499F4A'.    MP_RegistrationManager    12.01.2015 14:31:10    8600 (0x2198)
    A client is trying to re-register with an administrator revoked certificate: SMSID='GUID:F295F120-9C99-4D10-82B7-027FDD86B5F6'.    MP_RegistrationManager    12.01.2015 14:31:10    8600 (0x2198)
    MP Reg: Processing completed. Completion state = 0    MP_RegistrationManager    12.01.2015 14:31:10    8600 (0x2198)
    We are using HTTP for client communication.
    Any ideas appreciated.
    Michael

  • Repporting problem after install SCCM 2012 SP1

    Hi there:
    After install SP1, our reporting does not work any more. It pop up following error messages.
    Any helps on this?
    Thanks..................................
    Microsoft.Reporting.WinForms.ReportServerException
    An error has occurred during report processing. (rsProcessingAborted)
    Stack Trace:
       at Microsoft.Reporting.WinForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension)
       at Microsoft.Reporting.WinForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension)
       at Microsoft.Reporting.WinForms.AsyncMainStreamRenderingOperation.RenderServerReport(ServerReport report)
       at Microsoft.Reporting.WinForms.AsyncRenderingOperation.PerformOperation()
       at Microsoft.Reporting.WinForms.ReportViewer.AsyncReportOperationWrapper.PerformOperation()
       at Microsoft.Reporting.WinForms.ProcessingThread.ProcessThreadMain(Object arg)
    Microsoft.Reporting.WinForms.ReportServerException
    Query execution failed for dataset 'DataSet1'. (rsErrorExecutingCommand)
    Stack Trace:
       at Microsoft.Reporting.WinForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension)
       at Microsoft.Reporting.WinForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension)
       at Microsoft.Reporting.WinForms.AsyncMainStreamRenderingOperation.RenderServerReport(ServerReport report)
       at Microsoft.Reporting.WinForms.AsyncRenderingOperation.PerformOperation()
       at Microsoft.Reporting.WinForms.ReportViewer.AsyncReportOperationWrapper.PerformOperation()
       at Microsoft.Reporting.WinForms.ProcessingThread.ProcessThreadMain(Object arg)
    Microsoft.Reporting.WinForms.ReportServerException
    Invalid object name 'fn_rbac_StatusMessagesAlerts'.
    Stack Trace:
       at Microsoft.Reporting.WinForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension)
       at Microsoft.Reporting.WinForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension)
       at Microsoft.Reporting.WinForms.AsyncMainStreamRenderingOperation.RenderServerReport(ServerReport report)
       at Microsoft.Reporting.WinForms.AsyncRenderingOperation.PerformOperation()
       at Microsoft.Reporting.WinForms.ReportViewer.AsyncReportOperationWrapper.PerformOperation()
       at Microsoft.Reporting.WinForms.ProcessingThread.ProcessThreadMain(Object arg)

    Suspiciously similar to my report error after upgrading to SCCM 2012 R2 today:
    Microsoft.Reporting.WinForms.ReportServerException
    An error has occurred during report processing. (rsProcessingAborted)
    Stack Trace:
       at Microsoft.Reporting.WinForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension)
       at Microsoft.Reporting.WinForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension)
       at Microsoft.Reporting.WinForms.AsyncMainStreamRenderingOperation.RenderServerReport(ServerReport report)
       at Microsoft.Reporting.WinForms.AsyncRenderingOperation.PerformOperation()
       at Microsoft.Reporting.WinForms.ReportViewer.AsyncReportOperationWrapper.PerformOperation()
       at Microsoft.Reporting.WinForms.ProcessingThread.ProcessThreadMain(Object arg)
    Microsoft.Reporting.WinForms.ReportServerException
    Query execution failed for dataset 'DataSet1'. (rsErrorExecutingCommand)
    Stack Trace:
       at Microsoft.Reporting.WinForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension)
       at Microsoft.Reporting.WinForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension)
       at Microsoft.Reporting.WinForms.AsyncMainStreamRenderingOperation.RenderServerReport(ServerReport report)
       at Microsoft.Reporting.WinForms.AsyncRenderingOperation.PerformOperation()
       at Microsoft.Reporting.WinForms.ReportViewer.AsyncReportOperationWrapper.PerformOperation()
       at Microsoft.Reporting.WinForms.ProcessingThread.ProcessThreadMain(Object arg)
    Microsoft.Reporting.WinForms.ReportServerException
    Procedure or function 'sp_CP_StatusPercent_All' expects parameter
    '@UserSIDs', which was not supplied.
    Stack Trace:
       at Microsoft.Reporting.WinForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension)
       at Microsoft.Reporting.WinForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension)
       at Microsoft.Reporting.WinForms.AsyncMainStreamRenderingOperation.RenderServerReport(ServerReport report)
       at Microsoft.Reporting.WinForms.AsyncRenderingOperation.PerformOperation()
       at Microsoft.Reporting.WinForms.ReportViewer.AsyncReportOperationWrapper.PerformOperation()
       at Microsoft.Reporting.WinForms.ProcessingThread.ProcessThreadMain(Object arg)
    Any ideas?

  • SQL 2012 SP1 and SCCM 2012 SP1

    Hi,
    I am installing SCCM 2012 SP1 with SQL 2012 SP1 in Stand-Alone mode. But I am receiving error:"the service broker endpoint cannot listen on port 4022 because it is in use by another process"
    I saw in SQL (SQL Server Configuration Manager) that I am using port 4022 without dinamic port.
    Thaks.
    Lessandro Zampieri - http://lezampieri.com

    Thanks for the reply.
    C:\>netstat -ano
    Active Connections
      Proto  Local Address          Foreign Address        State           PID
      TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       780
      TCP    0.0.0.0:443            0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:4022           0.0.0.0:0              LISTENING       4664
      TCP    0.0.0.0:5985           0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:47001          0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING       528
      TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING       836
      TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING       900
      TCP    0.0.0.0:49155          0.0.0.0:0              LISTENING       624
      TCP    0.0.0.0:49156          0.0.0.0:0              LISTENING       624
      TCP    0.0.0.0:49217          0.0.0.0:0              LISTENING       616
      TCP    0.0.0.0:49219          0.0.0.0:0              LISTENING       4184
      TCP    0.0.0.0:49389          0.0.0.0:0              LISTENING       2056
      TCP    0.0.0.0:49627          0.0.0.0:0              LISTENING       5060
      TCP    127.0.0.1:49390        0.0.0.0:0              LISTENING       2056
      TCP    127.0.0.1:49628        0.0.0.0:0              LISTENING       5060
      TCP    127.0.0.1:57593        0.0.0.0:0              LISTENING       4664
      TCP    192.168.100.30:139     0.0.0.0:0              LISTENING       4
      TCP    192.168.100.30:445     192.168.100.20:49420   ESTABLISHED     4
      TCP    192.168.100.30:445     192.168.100.20:49421   ESTABLISHED     4
      TCP    192.168.100.30:445     192.168.100.20:49422   ESTABLISHED     4
      TCP    192.168.100.30:445     192.168.100.20:49423   ESTABLISHED     4
      TCP    192.168.100.30:4022    192.168.100.30:61430   ESTABLISHED     4664
      TCP    192.168.100.30:4022    192.168.100.30:61496   ESTABLISHED     4664
      TCP    192.168.100.30:49627   192.168.100.40:55914   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:55915   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:55921   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:55922   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:55926   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:55927   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:55928   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:55929   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:55930   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:55967   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:55992   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:55998   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:56001   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:56002   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:56009   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:56077   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:56211   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:56656   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:56687   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:56817   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:56891   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:56946   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:56959   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57027   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57072   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57223   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57240   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57248   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57268   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57292   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57293   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57294   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57311   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57312   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57314   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57320   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57340   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57342   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57343   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57369   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57372   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57379   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57385   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57386   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57387   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57388   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57389   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57390   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57391   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57392   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57393   ESTABLISHED     5060
      TCP    192.168.100.30:61430   192.168.100.30:4022    ESTABLISHED     4112
      TCP    192.168.100.30:61496   192.168.100.30:4022    ESTABLISHED     4112
      TCP    192.168.100.30:61537   192.168.100.10:49158   TIME_WAIT       0
      TCP    [::]:80                [::]:0                 LISTENING       4
      TCP    [::]:135               [::]:0                 LISTENING       780
      TCP    [::]:443               [::]:0                 LISTENING       4
      TCP    [::]:445               [::]:0                 LISTENING       4
      TCP    [::]:4022              [::]:0                 LISTENING       4664
      TCP    [::]:5985              [::]:0                 LISTENING       4
      TCP    [::]:47001             [::]:0                 LISTENING       4
      TCP    [::]:49152             [::]:0                 LISTENING       528
      TCP    [::]:49153             [::]:0                 LISTENING       836
      TCP    [::]:49154             [::]:0                 LISTENING       900
      TCP    [::]:49155             [::]:0                 LISTENING       624
      TCP    [::]:49156             [::]:0                 LISTENING       624
      TCP    [::]:49217             [::]:0                 LISTENING       616
      TCP    [::]:49219             [::]:0                 LISTENING       4184
      TCP    [::]:49389             [::]:0                 LISTENING       2056
      TCP    [::]:49627             [::]:0                 LISTENING       5060
      TCP    [::1]:49390            [::]:0                 LISTENING       2056
      TCP    [::1]:49628            [::]:0                 LISTENING       5060
      TCP    [::1]:57593            [::]:0                 LISTENING       4664
      UDP    0.0.0.0:123            *:*                                    948
      UDP    0.0.0.0:500            *:*                                    900
      UDP    0.0.0.0:1434           *:*                                    3000
      UDP    0.0.0.0:4500           *:*                                    900
      UDP    0.0.0.0:5355           *:*                                    124
      UDP    127.0.0.1:51181        *:*                                    4132
      UDP    127.0.0.1:51338        *:*                                    124
      UDP    127.0.0.1:55475        *:*                                    900
      UDP    127.0.0.1:59835        *:*                                    1628
      UDP    127.0.0.1:60840        *:*                                    3596
      UDP    127.0.0.1:62010        *:*                                    1816
      UDP    127.0.0.1:62390        *:*                                    4112
      UDP    127.0.0.1:64129        *:*                                    624
      UDP    192.168.100.30:137     *:*                                    4
      UDP    192.168.100.30:138     *:*                                    4
      UDP    [::]:123               *:*                                    948
      UDP    [::]:500               *:*                                    900
      UDP    [::]:1434              *:*                                    3000
      UDP    [::]:4500              *:*                                    900
    All things are correct?
    Att.,
    Lessandro Zampieri - http://lezampieri.com

  • New SCCM 2012 client machines still getting SCCM 2012 SP1 client not the new SCCM 2012 SP1 CU3 client

    Hi,
    I've successfully (as far as I can tell) deployed SCCM 2012 SP1 CU3 and all my existing clients are showing a client version of 5.00.7804.1400.  But when I setup a new client system recently I noticed that the client version was showing 5.00.7804.1000,
    and not 5.00.7804.1400. 
    For new client systems, do I need to redeploy the packages that were created for SCCM 2012 SP1 CU3 so that the new systems get the new SCCM 2012 SP1 CU3 client? 
    Thanks,
    Nick

    Hi,
    Here's some good information to look over:
    http://sccmfaq.wordpress.com/2013/09/24/sccm-2012-include-cu-in-osd/
    I haven't followed these instructions myself, since I haven't really had any good reason to include CUs during the initial installation process. I use this method instead and I've never run into any problems:
    http://www.ronnipedersen.com/2013/06/installing-sccm-2012-sp1-cu2-quick-start-guide/
    Don't retire TechNet! -
    (Don't give up yet - 12,575+ strong and growing)

  • Windows Updates are not getting download after installation of SCCM 2012 SP1

    I have installed SCCM 2012 SP1 step by step as per microsoft documents, Now I am getting error while downloading windows updates from microsoft site.
    Error by WCM.log : System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport
    connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
    Error By wsyncmgr: DB Server not detected for SUP XYZ.com from SCF File. skipping.
    Sync failed: WSUS update source not found on site KSL. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=KSL-MUM-SCCM01.KSEC.KotakGroup.com SITE=KSL PID=3688 TID=4752 GMTDATE=Tue May 21 10:59:06.745 2013 ISTR0="getSiteUpdateSource" ISTR1="WSUS
    update source not found on site KSL. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    I have reinstall my SUP on site server, i have my WSUS & site server is on same server. I have kept my sup setting as per requirment (8530 & 8531)
    Kindly suggest is any other settings need to be done on server side.

    Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
    From your log snip-it, it looks like the firewall is causing your problem. Temporary turn off the firewall and see if that solves your problem.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • 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

Maybe you are looking for

  • Problem in goods issue

    Hi i have done following steps that lead me to a problem 1. MIGO of a material done with posting date of march 2. I have issued that material using mvt 281 Q to reservation with posting date in april Now, since i have done above step-2 by mistake, be

  • Basic script help for a newbie?!?!

    Need help with a basic script, I need to display 5 input fields in a single dynamic field. And i need them to have a certain order of display, ie: input 1 is displayed on line 1, 2 on the next line, etc. any help would be appreciated I have been tryi

  • Server-side includes in cs5

    have used all previous versions of dw. no prior problem with server-side includes. now, they are not showing up in design view. Yes, I have marked preferences to include hidden items/server side includes. any thoughts anyone?

  • Problems when embedding animations (aka videos) in Captivate 4

    I am still encountering a major problem with embedded videos. I have a main project and within this project I am selecting Insert Animation (a swf file). The problems are many, depending on whether I preview, publish to hard drive, or publish to Conn

  • Missing return statement error! HOW?

    Why would the following code complain that it's missing a return statement, yet there are more than 4 return statements. All the possibilities are captured on the if statements and there are no more possibilities. public static double power(double b,