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

Similar Messages

  • SCCM 2012 SP1 to SCCM 2012 R2 - Side by Side

    Hi Friends,
    Currently our SCCM infrastructure is running with a CAS site, 2 Primary Sites and 8 Secondary sites with SCCM 2012 SP1. Now we want to update this infrastructure from SCCM 2012 SP1 to 2012 R2. But we want remove CAS site and to keep only single Primary Site.
    Can this be done in Side by Side migration from SCCM 2012 SP1 to SCCM 2012 R2 ? If yes then please suggest how to migrate all data (Packages/Clients) from SCCM 2012 SP1 to new infra on SCCM 2012 R2.
    Thanks in advance.

    You don't have many (supported) options here. Detaching a site is not possible, so indeed your only option left is to migrate. Problem here is that the supported scenario is from a ConfigMgr 2012 R2 site to a ConfigMgr 2012 R2 site (see:
    http://technet.microsoft.com/en-us/library/gg682006.aspx). That means you should first upgrade your old environment before you can start with your migration.
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • Migration of SCCM 2012 SP1 to SCCM 2012 R2 in a new domain.

    I am wondering if it is possible to migrate objects from a SCCM 2012 SP1 server in one domain to a new SCCM 2012 R2 server in another domain ?
    I read this article, but it does not state this particular combination.
    http://technet.microsoft.com/en-us/library/gg682006.aspx
    Thx
    Thomas

    For Migrate from SCCM 2012 SP1 to SCCM 2012 R2 in same environment/Domain, it's support and applicable.
    But migrate to new domain, it's not support. Also you can't migrate database for new domain or object. you will need to rebuild it.
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Mai Ali | My blog: Technical | Twitter:
    Mai Ali

  • Difference between scom 2012 sp1 and SCOM 2012 R2

    what is the difference between scom 2012 sp1 and SCOM 2012 R2 ?

    What's New in System Center 2012 R2 Operations Manager:
    https://technet.microsoft.com/en-us/library/dn249700.aspx

  • Required Ports to connect remote SQL named Instance for SCCM 2012 R2

    Hi,
      I have allowed the TCP 1433,1434,135 and 80 but still unable to connect the remote SQL named instance DB for the SCCM 2012 R2... and getting below error..can you please suggest if any other port required for the same, i have turned off the windows
    firewall and RPC service is running ob Remote SQL and SCCM 2012 R2 server..
    CCMsetuplog
    Shailendra Dev

    During the installation you need more ports. You would also need the (dynamic) RPC ports. See for a complete list (section Site Server --> SQL Server):
    https://technet.microsoft.com/en-us/library/hh427328.aspx
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • 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

  • IIS and SCCM 2012 R2

    Hi
    I have 2 forest (Forest A only root domain (Server C=MP/DP)), (Forest B, 1 root domain(Server A=SCCM Primary) and 1 child domain (Server B=MP/DP)). I root domain forest A i have Windows 2012 R2 with SCCM 2012 R2 CU4 and another server with SQL 2012
    R2.
    I child domain i have MP and DP
    Another forest (not trusted) i have a MP and DP. i use untrusted forest in SCCM 2012.
    When i test my IIS i root domain(server A), open Internet Explorer and type:
    http://servername/sms_mp/.sms_aut?mplist (no problem) i view all MP.
    http://servername/sms_mp/.sms_aut?mplist (no problem) i view certificate
    When i test my IIS i child domain (serverB), open Internet Explorer and type:
    http://servername/sms_mp/.sms_aut?mplist (no problem) i view all MP.
    http://servername/sms_mp/.sms_aut?mplist (no problem) i view certificate
    When i test my IIS i another forest (server C), open Internet Explorer and type:
    http://servername/sms_mp/.sms_aut?mplist (no problem) i view certificate
    http://servername/sms_mp/.sms_aut?mplist
    (The web site cannot display the page ERROR HTTP 500) It's normal? If Yes why?
    Thanks

    Hi,
    I think this is related to IIS authentication, so you may get an answer from IIS forum:
    http://forums.iis.net/
    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]

  • 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

  • A little confused on vPro and SCCM 2012 R2

    Hi folks. I have a question regarding vPro and SCCM, hopefully someone can help.
    Do I need an SCS sever to integrate and provision vPro devices with SCCM 2012 R2?
    I basically just want to be able to remotely provision the devices for vPro (certs ect) and take advantage of the WOL and shutdown functionality for patch management and I would rather avoid setting up an SCS server if possible. Any advice welcome, thanks in
    advance.
    Best,
    Pete

    I really suggest that you take a look at integrating SCS, because ConfigMgr only supports these versions of the AMT (http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigOOB):
    Intel AMT version 3.2 with a minimum revision of 3.2.1
    Intel AMT version 4.0, version 4.1, and version 4.2
    Intel AMT version 5.0 and version 5.2 with a minimum revision of 5.2.10
    Intel AMT version 6.0 and version 6.1
    And all the new PCs come with newer version of AMT.
    Some guides to get you started with vPro:
    http://windowsmasher.wordpress.com/2013/10/05/intel-vpro-the-basics-of-vpro/
    http://blogs.bamits.com.au/2012/09/integrating-sccm-2012-with-scs-81.html

  • SCVMM and SCCM 2012 R2 - Deploying VM's - Which method

    Hi guys,
    Looking at deploying SCCM 2012 R2 and SCVMM 2012 R2. I've used SCCM 2012 quite a lot in a previous environment, but not SCVMM.
    I'm aware SCVMM is for bare-metal Hyper-V (as well as Xen and ESXi), and for managing the virtual environment, but do I create VM templates and create my VM Servers within SCVMM, or just the shell and PXE boot into a SCCM Task Sequence to deploy the OS?
    Will also be running Orchestrator too.... So to deploy a VM would a runbook be used to create a VM shell in SCVMM, and then kick off a TS in SCCM?
    Or should I be building the server templates and basically replicating some of SCCM's OSD capability for VM servers in SCVMM?
    Thanks - Steve

    Thx Stevehoot.
    Yes, you might see that there are some "overlapping" technologies involved, but please remember that SCCM is the general approach, that has been supporting physical servers/computers since day one. This requires PXE boot for the VMs as well, in order to
    deploy the OS, install the agent and then the applications.
    Using VMM for VM deployment, the VMM agent will handle this all for you and you can manage your datacenter from this single console. Currently, Gen2 has lacking support in some areas, like service templates in VMM, VM roles in Azure Pack and replication
    to Azure using Microsoft Azure Site Recovery. 
    Moving forward, it would be smart if you could invest in deployment using VMM if the majority of your workloads will be on virtual machines. What we basically sees in the field is that people are using SCCM to deploy their traditional applications onto these
    servers where service templates may not be the right solution. But again, then SCCM is something that kicks in post the VM deployment. 
    -kn
    Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

  • OS-Deployment to virtual servers with SCVMM 2012 R2 vs SCCM 2012 R2 or integration with both?

    Hi,
    OS-Deployment to virtual servers with SCVMM 2012 R2 vs SCCM 2012 R2 or integration with both?
    Is SCCM just for physical servers, and SCVMM for virtual?
    What are benefits of integrating them?
    /SaiTech

    Hi,
    Please refer to the links below:
    Introduction to Configuration Manager
    http://technet.microsoft.com/en-us/library/gg682140.aspx
    Virtual Machine Manager
    http://technet.microsoft.com/en-us/library/gg610610.aspx
    The System Center 2012 Integration Guide provides information about automating each of the System Center components and integrating them with each other and with other systems and applications.
    For more information, see the
    System Center 2012 Integration Guide.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • SQL version problem during SCCM 2012 sp1 setup

    Hi
    I am trying to install SCCM 2012 sp1 with a remote sql 2012 server.
    during setup when I enter the SQL name i hit next and then I get this error.
    "Configuration Manager requires Microsoft SQL Server 2008 SP2 with Cumulative update 9 or higher, Microsoft SQL Server 2008 SP3 with Cumulative update
    4 or higher, Microsoft SQL Server 2008 R2 SP1 with Cumulative update 6 or higher or Microsoft SQL Server 2012 with Cumulative update 2 or higher,"
    I installed SQL sp1 and CU3 as well. but still the same error.
    please assist
    thanks
    troy

    Hi,
    If you use default instance, please do not fill in the instance name.
    You could use “telnet sqlserver 1433” to verify the connection and port.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • 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

  • SCCM 2012 SP1 and MDT 2012 Task Sequence Templates, MDT File/Settings Packages

    We're setting up SCCM 2012 integrated with MDT 2012 for our OSD. My main issue is finding actual reference material for the MDT task sequence templates when integrated with SCCM. The MDT documentation has a lot of information on variables and task sequences
    outside of SCCM integration. 
    One thing I'd love to find information on is what's actually going on during an MDT Client Task Sequence template. I found this http://social.technet.microsoft.com/Forums/en-US/645a77b2-5be6-431d-818c-57d24b1435cc/understanding-mdt-task-sequence?forum=configmgrosd but
    it doesn't delve into the kind of detail I'm looking for. I can dig up information through the MDT reference material on some things, but I just can't find anything out there that actually walks you through an SCCM/MDT task sequence template. For instance,
    under State Restore what is being referenced in Install Software with base variable name PACKAGES, vs Install Applications and base variable name COALESCED APPS. And, where are you supposed to put these applications? That's just a specific example, I'm hoping
    to find some kind of walkthrough.
    Two things I'm hazy on are the MDT packages. What exactly are the MDT Settings Package, and the MDT Files Package? What are they used for? What benefits do you get out of using them? And, how exactly do you use them? I know one of them has something to do
    with customsettings.ini, but what's the point of using SCCM with MDT if you still have to muck around in the customsettings.ini file?
    Either way, it seems like there are a lot of references to SCCM task sequences, and a lot of references to MDT task sequences. But, not together. Which is a bit annoying since the MDT-integrated task sequence templates are very obviously different than either
    SCCM or MDT by itself. Any help would be appreciated, even just information on where to look. Maybe I'm just really bad at finding reference material for SCCM/MDT. Thanks. 

    When MDT integrated with SCCM, We need the following MDT components to be created:
    MDT Boot image
    MDT Toolkit Files
    MDT Settings
    The MDT boot image (for example) gives you extra abilities over the standard ConfigMgr boot image such as the ability to display a HTA Refer here:
    http://www.windows-noob.com/forums/index.php?/forum/98-frontends-and-web-services/
    MDT Files once created, you will find UDIWizard_Config.Xml file in which you can start User driven Installation OSD using UDI designer.
    Refer these links for better understanding:
    http://www.windows-noob.com/forums/index.php?/topic/5131-using-sccm-2012-rc-in-a-lab-part-16-integrating-mdt-2012-rc1-with-configuration-manager-2012/
    http://www.windows-noob.com/forums/index.php?/topic/5221-using-sccm-2012-rc-in-a-lab-part-17-using-mdt-2012-rc1-within-configuration-manager-2012/
    http://www.windows-noob.com/forums/index.php?/topic/5250-using-sccm-2012-rc-in-a-lab-part-18-deploying-a-udi-client-task-sequence-with-mdt-2012-rc1-integrated-in-configuration-manager-2012/
    Thanks, Prabha G
    Thanks for the quick reply. But, what about the MDT Settings Package? Also, both have a pretty big folder structure for each package. Surely it does more than just provide a couple xml and ini files? I'm not looking for anyone to spoon-feed me the information,
    but at least a pointer in the right direction for finding the reference material. It seems for SCCM/MDT integration you have to go all over the place finding scraps of information to put together. 
    Also, any info on the SCCM/MDT task sequence templates? Thanks. 

  • Exchange 2013 SP1 and SCOM 2012 R2

    Hi there, 
    Hopefully someone can assist me with this issue, if it is one... 
    I am halfway through an Exchange migration, from Exchange 2010 SP3 on Server 2008 R2 to Exchange 2013 SP1 on Server 2012 R2.
    76 users in total, roughly 80GB of Public Folders.
    I have configured the 2013 environment with a cross datacenter DAG, also increased all of the timeouts of the cluster to take this into consideration, and everything appears to function as expected. 
    Added both 2013 machines to SCOM 2012 R2 for at least a week with no active users on it, and all monitoring reported ok, no issues. 
    Exchange 2010 is configured to use webmail.company.com for RPC over HTTP, which is what I have configured 2013 to use as well. 
    Implemented Microsoft ARR for client access to Exchange 2013, as opposed to ISA we've used for Exchange 2010. 
    A week ago, changed the DNS records for webmail.company.com from ISA to ARR, and all clients connected perfect. 
    Thought, ok, now we can start the migration. So far everything "seems" to be going perfect with the mailbox moves, however, SCOM is really noisy. 
    Attempted to reran the probe for EWS and got the error below:
    Is there perhaps anyone that can assist me with these errors?
    Cheers

    FYI... IIS ARR is not supported for Exchange Server.
    Check in event log if you are getting anything related to the issue.
    About Outlook POP UP to end users. Check the event log on 2010/2013 for MRS events.
    Are those mailboxes still moving or in move request?
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://www.exchangeranger.com    Twitter:
      LinkedIn:
       Check out CodeTwo’s tools for Exchange admins
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Maybe you are looking for