How to manage Forefront Endpoint Prorection Security Client 2010 with SCCM 2012

Hi
I've sucessfully installed System Center Configuration Manager 2012
and now I 'd like to push/deploy Forefront Endpoint Protection Client 2010 on client machines.I also know that Microsoft embedded Forefront Endpoint Protection in SCCM 2012 so that you can manage FEP from single SCCM 2012 console.Now
when I try to push FEP client on client machines using Default Client Settings
then I've found that all Endpoint Protection settings are greyed out !
Do I need to install Forefront Endpoint Protection 2010 or 2012 Server (which is beta) with SCCM 2012, in order to deploy FEP client or is there a workaround or solution to resolve this ?
Thanks
Sohail

Hi,
Endpoint Protection 2012 is builtin in SCCM 2012, you simply add the Site Role called Endpoint Protection either on your CAS if you have one of those or on your Primary site Server. FEP is no longer a standalone installer and it is a released product and
no longer Beta.
Then the Endpoint Protection Client Settings will no longer be greyed out and you can deploy the System Center 2012 Endpoint Protection client.
http://technet.microsoft.com/en-us/library/hh508760.aspx
regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Similar Messages

  • Basic questions regarding installing Forefront EP Client 2010 on Windows 2012 R2

    Hi,
    We have a handful of servers and client machines (although these always seem to be expanding) and as such have previously just installed the Forefront Endpoint 2010 Client manually onto the various endpoints with updates being pushed via WSUS from a Windows
    2008R2 machine, without running to a full installation of SCCM or the Forefront Endpoint Server. However, trying to install the FEP 2010 client directly onto new Windows 2012R2 servers result in a "This OS is not supported" error.
    After checking some articles it appears that FEP 2010 might well be supported on Win 2012R2 (and Windows 8), but only if installed via SCCM. Is this correct?
    We do have access to SCCM 2012, but again I have shied away from this. I had hoped that maybe the SCCM Endpoint client could also be installed manually once more, but trying to install this on a Windows 2012R2 machine results in a "Windows compatibility
    mode is not supported by this program" error.
    Am I barking up the wrong tree and will I now have to finally learn and install SCCM? If so I take it that I can update my 2008R2 WSUS server to firstly Win 2012RS WSUS, then add SCCM 2012?
    Cheers
    Chris

    Hi Joyce,
    Thanks for the feedback.
    Hi,
    >>After checking some articles it appears that FEP 2010 might well be supported on Win 2012R2 (and Windows 8), but only if installed via SCCM. Is this correct?
    According to the blog below, Forefront Endpoint Protection 2010 with Update Rollup 1
    is supported on Windows Server 2012 R2.
    http://blogs.technet.com/b/configmgrteam/archive/2013/09/16/support-questions-about-win-8.1-and-winsvr-2012-r2-for-configmgr-and-endpoint-protection.aspx
    Please make sure you are running FEP 2010 update rollup 1. You could get it from the following link.
    http://support2.microsoft.com/kb/2907566/en-us
    Thanks for the feedback. I should have said that I have indeed tried this. From the initial link you posted I found the "Update Rollup 1 for Forefront Endpoint Protection 2010" (http://support2.microsoft.com/kb/2551095/en-us), however, this update
    itself apparently requires a prerequisite. Whist I have tried to install the prerequisite (http://support2.microsoft.com/kb/2554364/en-us) and the Forefront Update Rollup 1 directly onto a a Windows 2012 R2 machine, I end up with errors:
    Installing the Prerequisite result in a "Error code: 1642" in the log file. Have have tried to chase this error, but have not spent too much time digging as yet, but this appears to be more to do with the FEP server than the client.
    Installing with the FEP Update Rollup (obviously without the prerequisite), give us three folders (FepExt, FepReport and FepUx), none of which seem to be the client per se
    >>Ah, the later problem of trying to install a client from SCCM 2012 onto Windows 2012R2 maybe because I have been using SCCM 2012 SP1, and not SCCM 2012R2??
    In SCCM 2012, Endpoint Protection 2012 is integrated so you cannot install FEP 2010 in it.
    Best Regards,
    Joyce
    No no, What I meant was that I had hoped that I could install the client contained within SCCM 2012 R2 installation material manually onto a vanilla Windows 2012 R2 box (which is what I'm trying to do), in the same way that I could install the FEP 2010 on
    previous Windows OS. The ISO that I have currently from our systems team is that of SCCM 2012 SP1, not SCCM 2012 R2, and the client within the SP1 package does not install in Windows 2012 R2. I'm tyring to get hold of the SCCM 2012 R2 ISO now, which (from
    what I read) should allow me to manually install the client.
    I may well play with SCCM later, but is a little over kill for our estate (read 10's of servers and clients, rather than 1000's), however, we should have a campus licence for SCCM.
    Regards
    Chris

  • AMT 3.2.10 Clients with SCCM 2012 on Windows 2012

    Hey
    I have a couple of HP dc7800 computers with Intel's AMT/vPro that I'd like to provision with SCCM 2012. The installed firmware version is 3.2.10 which is a supported version according to the documentation [1]. Provisioning of newer clients (5.2.x upwards)
    is successful, so I can rule out all the usual suspects like the provisioning certificate from GoDaddy, our internal CA, DHCP options, etc. Provisioning with SCCM 2007 of both 3.2.x and 5.x AMT devices is also still successful. 
    The amtopmgr.log repeatedly shows the following entries:
    Provision target is indicated with SMS resource id. (MachineId = 16777325 WS45.mydomain.ch)
    Found valid basic machine property for machine id = 16777325.
    Warning: Currently we don't support mutual auth. Change to TLS server auth mode.
    The provision mode for device WS45.mydomain.ch is 1.
    The IP addresses of the host WS45.mydomain.ch are x.x.x.x.
    Root hash of provisioning certificate is 2796BAE63F1801E277261BA0D77770028F20EEE4.
    Attempting to establish connection with target device using SOAP.
    Create provisionHelper with (Hash: 74B7792EDBD64EBB01E2E3A0B27FAFA04C2D3BCB)
    Set credential on provisionHelper...
    Try to use provisioning account to connect target machine WS45.mydomain.ch...
    Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.
    **** Error 0x37f2b370 returned by ApplyControlToken
    Fail to connect and get core version of machine WS45.mydomain.ch using provisioning account #0.
    Try to use default factory account to connect target machine WS45.mydomain.ch...
    Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.
    **** Error 0x37f2b370 returned by ApplyControlToken
    Fail to connect and get core version of machine WS45.mydomain.ch using default factory account.
    Try to use provisioned account (random generated password) to connect target machine WS45.mydomain.ch...
    Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.
    **** Error 0x37f2b370 returned by ApplyControlToken
    Fail to connect and get core version of machine WS45.mydomain.ch using provisioned account (random generated password).
    Error: Device internal error. This may be caused by: 1. blabla...
    Error: Can NOT establish connection with target device. (MachineId = 16777325)
    After some investigation with Wireshark, I've found out that SCCM tries connect with TLSv1 to the AMT device. The response from the device is immediately an SSL alert (internal error). Using OpenSSL, I could connect to the device if I explicitly told it
    to use SSLv3. This leads me to believe that the 3.2.x firmware cannot handle TLSv1 correctly and SCCM never tries to connect with SSLv3 after a failure.
    So the question is: How can I get SCCM 2012 to provision these devices?
    Regards,
    Ingo
    [1]
    http://technet.microsoft.com/en-us/library/c1e93ef9-761f-4f60-8372-df9bf5009be0#BKMK_SupConfigOOB

    Since no one has answer this post, I recommend opening  a support case with CSS as they can work with you to solve this problem.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • How to recover deleted systems in "All Systems" collection in SCCM 2012

    Hi Everyone,
     how to recover deleted systems in "All Systems" collection in SCCM 2012  and also I had one system which is by accidentally deleted, I know the system name, but I cannot able to add the system manually to Device Collections,  is
    there any solution for this...
    I had discovered many systems using discovery, I recovered some systems but not all the systems..
    Please suggest...
    saikumar CH

    just a follow up on Torstens reply. You will see the discovery records show up in the console without having the client installed. That will be corrected when clients perform a hardware inventory re-sync. It all happens automatically, no panic and don't
    reinstall the clients.
    Kent Agerlund | My blogs: blog.coretech.dk/kea and
    SCUG.dk/ | Twitter:
    @Agerlund | Linkedin: Kent Agerlund |
    Mastering ConfigMgr 2012 The Fundamentals

  • How to prompt for OU during OSD Task with SCCM 2012 R2?

    How to prompt for OU during OSD Task with SCCM 2012 R2?

    Hi,
    Here is an example on how to do it using a Variable prompt in Configuration Manager, It works the same way in SCCM 2007,
    http://www.the-d-spot.org/wordpress/2013/04/01/dynamically-join-computer-to-ad-ou-during-osd-with-sccm/
    Regards,
    Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • Lync 2013 x64 silent client deployment via SCCM 2012 SP1

    Greetings everyone!
    I ran into a problem with Lync 2013 x64 silent deployment.
    I need to provide every workstation with Lync 2013 client, so i decided to use deployment via SCCM 2012 sp1.
    I created 2 msp files with OCT, one based on x86 Office 2013 Proplus, and other based on x64 Office 2013 Proplus.
    Added them as applications to sccm software library.
    Deployment of Lync 2013 x86 application was a success with over than 80% compliance. 
    But all Lync 2013 x64 automatic installations finish with different errors.
    I created special device collection for workstations with office 2010 x64 and 2013 x64, because i can't install other architecture products once it has x64 product installed.
    My membership query-rules for this collection:
    Office 2013 x64
    select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId
    = SMS_R_System.ResourceId where UPPER(SMS_G_System_INSTALLED_SOFTWARE.SoftwareCode) = "{90150000-0011-0000-1000-0000000FF1CE}"
    Office 2010 x64
    select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId
    = SMS_R_System.ResourceId where UPPER(SMS_G_System_INSTALLED_SOFTWARE.SoftwareCode) = "{90140000-0011-0000-1000-0000000FF1CE}"
    My application deployment type points to setup.exe in office 2013 x64 installation folder, where i created msp file in updates folder via OCT and edited config.xml file in proplus.ww folder.
    So my installation program looks like this setup.exe /adminfile updates\1lync.msp /config proplus.ww\config.xml
    The same configuration works with Lync 2013 x86 deployment, except other setup folders.
    When i try running installation program setup.exe with /adminfile and /config parameters locally, it installs successfully without errors or warnings.
    I'm trying to find out problem source, does anyone have ideas what I am doing wrong?
    Also i'm trying to reduce office 2013 installation folder size, what subfolders are necessary for Office 2013 proplus installation (still installing only lync with common files and tools)? Because now 3.5 GB package is quite hard to distribute to sccm secondary
    sites with deployment point.
    Thanks in advance.

    Hi,
    Here are some tips and tricks for your reference.
    Tips and Tricks: Deploying Lync 2013 client using SCCM 2012 | Lync 2013 Client Customization for SCCM 2012 Deployment Package
    http://zahirshahblog.com/2014/01/08/tips-and-tricks-deploying-lync-2013-client-using-sccm-2012-lync-2013-client-customization-for-sccm-2012-deployment-package/
    Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
    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.

  • How to find using SQL query application deployed on win 7 machines with SCCM 2012 server or user installed manually.

    Hi,
    how to find using SCCM SQL query,  application deployed on win 7 machines with SCCM 2012 server or user/technician installed manually. Please let me know.

    Thanks, is it not possible via any script also?
    Like Torsten said, how can you tell the difference between CM12 installed applications and locally installed? Once you can answer that, then you can write report.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • Automatic Install of Endpoint Protection fails on windows 8.1 clients with SCCM 2012 R2

    Running SCCM 2012 R2 and deploying CM clients and Endpoint Protection via software updates. CM client and EP install fine on Windows 7 clients. CM client installs fine but endpoint protection fails on Windows 8.1 clients with the following from the
    endpoint protection agent log:
    <![LOG[Create Process Command line: "C:\Windows\ccmsetup\SCEPInstall.exe" /s /q /policy "C:\Windows\CCM\EPAMPolicy.xml".]LOG]!><time="12:22:02.560+240" date="08-13-2014" component="EndpointProtectionAgent"
    context="" type="1" thread="4260" file="epagentutil.cpp:607">
    <![LOG[Detail error message is : [EppSetupResult]
    HRESULT=0x80070643
    Description=Cannot complete the System Center Endpoint Protection installation. An error has prevented the System Center Endpoint Protection setup wizard from completing successfully. Please restart your computer and try again. Error code:0x80070643. Fatal
    error during installation.
    So on the win8.1 client I run the above command line manually in a command window and receive Access is denied. Then I run the same command in an elevated command window and EP installs fine. Does this have something to do with why the automatic
    EP client install fails with the 0x80070643 error code? If so, what is the fix?

    Hi,
    Try uninstalling any other security software.
    For more information, please review the link below:
    I‘m getting an error code from my Microsoft security software
    http://www.microsoft.com/security/portal/mmpc/help/errorcodes.aspx
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Endpoint Installation on Clients Computers Through SCCM

    Dears I have deployed clients to install endpoint protection through SCCM 2012 and we have almost 1500 computers, after deploying I found out half of computer didn’t install
    endpoint protection and the rest was successfully done, in our company we have Windows 7, Windows 8 and Windows Server 2008R2, some Windows 7 got the installation and the most of the severs too, I try to know what is the problem even I check firewall and some
    securities I couldn’t find the problem, is there any solutions or idea to fix my problem, thanks.

    Dear Kent, we have kaspersky installed, but in endpoint installed in some of the computers which they have already kaspersky installed too.
    This log is the last part on the computer who didn't installed the endpoint please see below log:
    ]LOG]!><time="14:54:03.640-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="7576" file="epagentutil.cpp:406">
    <![LOG[EP State and Error Code didn't get changed, skip resend state message.]LOG]!><time="14:54:03.640-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="7576"
    file="epagentimpl.cpp:146">
    <![LOG[State 4 is NOT changed. Skip update registry value]LOG]!><time="14:54:03.640-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="7576" file="epagentimpl.cpp:183">
    <![LOG[Failed to install EP client with exit code = 0x80070643.]LOG]!><time="14:54:03.640-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="3" thread="7576" file="epagentimpl.cpp:485">
    <![LOG[Register a timer here to check whether definition get updated in 30 minutes.]LOG]!><time="14:54:03.640-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="7576"
    file="epagentimpl.cpp:1006">
    <![LOG[FW Provider is NOT installed yet.]LOG]!><time="14:54:03.642-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="7576" file="epagentutil.cpp:778">
    <![LOG[File C:\Windows\ccmsetup\WindowsFirewallConfigurationProvider.msi installation failed with error = 0x80070643.]LOG]!><time="14:54:03.994-180" date="03-13-2013" component="EndpointProtectionAgent" context=""
    type="2" thread="7576" file="epagentutil.cpp:845">
    <![LOG[Failed to install FW MSI with error = 0x80070643.]LOG]!><time="14:54:03.994-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="3" thread="7576" file="epagentimpl.cpp:763">
    And This log is for the last part for computer who installed endpontm please see below log:
    <![LOG[Endpoint is triggered by WMI notification.]LOG]!><time="08:44:30.465-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="7164" file="fepsettingendpoint.cpp:125">
    <![LOG[EP State and Error Code didn't get changed, skip resend state message.]LOG]!><time="08:44:30.490-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="7164"
    file="epagentimpl.cpp:146">
    <![LOG[State 1 is NOT changed. Skip update registry value]LOG]!><time="08:44:30.490-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="7164" file="epagentimpl.cpp:183">
    <![LOG[File C:\Windows\ccmsetup\SCEPInstall.exe version is 2.2.903.0.]LOG]!><time="08:44:30.491-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="7164"
    file="epagentutil.cpp:499">
    <![LOG[EP version 2.2.903.0 is already installed.]LOG]!><time="08:44:30.491-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="7164" file="epagentutil.cpp:200">
    <![LOG[Expected Version 2.2.903.0 is exactly same with installed version 2.2.903.0.]LOG]!><time="08:44:30.491-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="7164"
    file="epagentutil.cpp:218">
    <![LOG[AM Policy XML is ready.]LOG]!><time="08:44:30.491-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="7164" file="epagentutil.cpp:314">
    <![LOG[Handle AM Policy.]LOG]!><time="08:44:30.491-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="7164" file="epagentimpl.cpp:844">
    <![LOG[Generate AM Policy XML while EP is disabled.]LOG]!><time="08:44:30.519-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="7164" file="epagentimpl.cpp:884">
    <![LOG[Endpoint is triggered by WMI notification.]LOG]!><time="14:50:39.322-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="6260" file="fepsettingendpoint.cpp:125">
    <![LOG[EP State and Error Code didn't get changed, skip resend state message.]LOG]!><time="14:50:39.362-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="6260"
    file="epagentimpl.cpp:146">
    <![LOG[State 1 is NOT changed. Skip update registry value]LOG]!><time="14:50:39.362-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="6260" file="epagentimpl.cpp:183">
    <![LOG[File C:\Windows\ccmsetup\SCEPInstall.exe version is 2.2.903.0.]LOG]!><time="14:50:39.362-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="6260"
    file="epagentutil.cpp:499">
    <![LOG[EP version 2.2.903.0 is already installed.]LOG]!><time="14:50:39.362-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="6260" file="epagentutil.cpp:200">
    <![LOG[Expected Version 2.2.903.0 is exactly same with installed version 2.2.903.0.]LOG]!><time="14:50:39.362-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="6260"
    file="epagentutil.cpp:218">
    <![LOG[AM Policy XML is ready.]LOG]!><time="14:50:39.363-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="6260" file="epagentutil.cpp:314">
    <![LOG[Handle AM Policy.]LOG]!><time="14:50:39.363-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="6260" file="epagentimpl.cpp:844">
    <![LOG[Generate AM Policy XML while EP is disabled.]LOG]!><time="14:50:39.404-180" date="03-13-2013" component="EndpointProtectionAgent" context="" type="1" thread="6260" file="epagentimpl.cpp:884">

  • Client Install Issue - SCCM 2012 R2 - Manual Deploy Installed ok

    Hello, I have sccm 2012 configured with 2,000 machine approx. It is been used mainly as a Software Deployment tool for now. On checking a recent IE10 upgrade, I noticed that there is a number of machines that do not have the client installed (and thus did
    not upgrade IE). I picked 1 machine, searched in SCCM - had no client. I checked all relevant settings:
    Boundary for Client in question - ok
    Local Client Settings (ip,dns,no firewall, ping sccm ok and vice versa etc).
    Once i right clicked to deploy the client, it installed no problem. I checked the ccmsetup log file and the only info it had was from the time that the client was manually deployed (I will attach the log below anyway). I am really puzzled as to why the client
    did not install and if this is the issue why IE is not upgrading (it is hard to pinpoint as there are 250 sites approx). The automatic install task works no problem on other machines once the machine goes online.
    Any help, would be great. Here is the log (I am fairly new to SCCM btw):
    SCCM 2012 R2 - Windows 7 SP1 32 Bit
    ==========[ ccmsetup started in process 7196 ]==========    ccmsetup    05/02/2015 16:28:39    4100 (0x1004)
    Running on platform X86    ccmsetup    05/02/2015 16:28:39    4100 (0x1004)
    Launch from folder C:\Windows\ccmsetup\    ccmsetup    05/02/2015 16:28:39    4100 (0x1004)
    CcmSetup version: 5.0.7958.1401    ccmsetup    05/02/2015 16:28:39    4100 (0x1004)
    In ServiceMain    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Running on 'Microsoft Windows 7 Enterprise ' (6.1.7601). Service Pack (1.0). SuiteMask = 272. Product Type = 18    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Ccmsetup command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /ForceInstall /config:MobileClient.tcf    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required.    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /ForceInstall /config:MobileClient.tcf    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    SslState value: 224    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    CCMHTTPPORT:    80    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    CCMHTTPSPORT:    443    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    CCMHTTPSSTATE:    224    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    CCMHTTPSCERTNAME:        ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    FSP:    COLSCCM01.LC-UK.ORG    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    CCMFIRSTCERT:    1    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Config file:      C:\Windows\ccmsetup\MobileClientUnicode.tcf    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Retry time:       10 minute(s)    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    MSI log file:     C:\Windows\ccmsetup\Logs\client.msi.log    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    MSI properties:    INSTALL="ALL" SMSSITECODE="COL" FSP="COLSCCM01.LC-UK.ORG" SMSCACHESIZE="10240" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1"  
     ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Source List:    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
                      \\COLSCCM01.lc-uk.org\SMSClient    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
                      \\COLSCCM01.LC-UK.ORG\SMSClient    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    MPs:    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
                      COLSCCM01.lc-uk.org    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    No version of the client is currently detected.    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Folder 'Microsoft\Configuration Manager' not found. Task does not exist.    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Updated security on object C:\Windows\ccmsetup\.    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Sending Fallback Status Point message to 'COLSCCM01.LC-UK.ORG', STATEID='100'.    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Failed to get client version for sending messages to FSP. Error 0x8004100e    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Params to send FSP message '5.0.7958.1401 Deployment '    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    State message with TopicType 800 and TopicId {19607F6A-0C46-488C-B28D-36640FB0DF94} has been sent to the FSP    FSPStateMessage    05/02/2015 16:28:40    500 (0x01F4)
    Running as user "SYSTEM"    ccmsetup    05/02/2015 16:28:40    500 (0x01F4)
    Detected 434753 MB free disk space on system drive.    ccmsetup    05/02/2015 16:28:40    500 (0x01F4)
    Checking Write Filter Status.    ccmsetup    05/02/2015 16:28:40    500 (0x01F4)
    This is not a supported write filter device. We are not in a write filter maintenance mode.    ccmsetup    05/02/2015 16:28:40    500 (0x01F4)
    Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=COL))'    ccmsetup    05/02/2015 16:28:40    500 (0x01F4)
    OperationalXml '<ClientOperationalSettings><Version>5.00.7958.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>224</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers></CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F0308201D8A00302010202104A263F5C34E3AAAA4C178EF33CA94377300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3134303630383134343831315A180F32313134303531363134343831315A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A0282010100A4FF6866BC9622545F811F8008ABDC534E96C9699A3354E990CADB04B1399B29EB80FB844425DEEDD9FE680C57AA0FE05D42CF1D431BB69080D4E7ED91A8255739089A83E4836F28B09331C100B0BAD81AD795EFD01C9ECF8DCE2BE03B52EE3AC35E7003B728E0FA56F145279301189388F3FC90A6C3DA5342C61230550C2B79DECB64AC0958C6DE2D5BF83C3EA29126E231FBEAADBD632F65AF41AC3267DB3986929C46A08AF0BF925A40E15A346B38219CC62C6C0BAC8990C05EA04037458F1853E251D8C16946F845D46CB47884D9EB00543AC8B02A7C099B53F7DE1EBD11AA1272476E5AAF55B2CC38122B62C751D988C81A07D06F87A9F7980D2B3560A90203010001A3383036301E0603551D11041730158213434F4C5343434D30312E6C632D756B2E6F726730140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B05000382010100A0DE29D627EB45EF2D0074AD578B62CE9007918B4316351DB2DBEFF2D0DF52C0FF58B6DE3405C88572ECCFAF2A7B335B234FE7D1E5B0FDA20548FEFE4B9E6AFB45E77627EDB70E2378A3135FB1FC34C2308F0FBD1ADD890DD08D8D6081B73FFF86DE87DBF678A7CAD73AE32BF6EB3B9D1E4E0380D7FBE3E9F9EF49339031636F2B3CC60989B8443B91F9F69F5837025B6CAE64E2D1837FAF712186A02567EA87F9E82FD170C4DEA61DC61C16226450FCBE062948F2219FB5801DF3AF73443349421A7228F5E1372B5CA165D8ABAB9D1B3FEAF22705A473AAAB034C2A289AA7A507550050D6516C2D7BECDE5686F17CC66FBB7D2C439F15644EBF9EF7E8402109</SiteSigningCert></SecurityConfiguration><RootSiteCode>COL</RootSiteCode><CCM>
    <CommandLine>SMSSITECODE=COL FSP=colsccm01.lc-uk.org SMSCACHESIZE=10240</CommandLine> </CCM><FSP> <FSPServer>COLSCCM01.lc-uk.org</FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSLState"
    Value="0" /></Capabilities><Domain Value="lc-uk.org" /><Forest Value="lc-uk.org" /></ClientOperationalSettings>'    ccmsetup    05/02/2015 16:28:41    500
    (0x01F4)
    Unable to open Registry key Software\Microsoft\CCM. Return Code [80070002]. Client HTTPS state is Unknown.    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    The MP name retrieved is 'COLSCCM01.lc-uk.org' with version '7958' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>'    ccmsetup  
     05/02/2015 16:28:41    500 (0x01F4)
    MP 'COLSCCM01.lc-uk.org' is compatible    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    Retrieved 1 MP records from AD for site 'COL'    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    Retrived site version '5.00.7958.1000' from AD for site 'COL'    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    SiteCode:         COL    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    SiteVersion:      5.00.7958.1000    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    Only one MP COLSCCM01.lc-uk.org is specified. Use it.    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    Searching for DP locations from MP(s)...    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    Current AD site of machine is Millbank    LocationServices    05/02/2015 16:28:41    500 (0x01F4)
    Local Machine is joined to an AD domain    LocationServices    05/02/2015 16:28:41    500 (0x01F4)
    Current AD forest name is lc-uk.org, domain name is lc-uk.org    LocationServices    05/02/2015 16:28:41    500 (0x01F4)
    DhcpGetOriginalSubnetMask entry point is supported.    LocationServices    05/02/2015 16:28:41    500 (0x01F4)
    Begin checking Alternate Network Configuration    LocationServices    05/02/2015 16:28:41    500 (0x01F4)
    Finished checking Alternate Network Configuration    LocationServices    05/02/2015 16:28:41    500 (0x01F4)
    Adapter {743579BD-D66A-4BF9-B487-2AAC075B9473} is DHCP enabled. Checking quarantine status.    LocationServices    05/02/2015 16:28:41    500 (0x01F4)
    Adapter {8F25ACE0-AE8A-45DD-BF3D-F1315E2B9974} is DHCP enabled. Checking quarantine status.    LocationServices    05/02/2015 16:28:41    500 (0x01F4)
    Adapter {8AE4D673-90E8-4FCF-AE50-79474ADC6190} is DHCP enabled. Checking quarantine status.    LocationServices    05/02/2015 16:28:41    500 (0x01F4)
    Adapter {9AA2CA9C-0C0A-48E3-B67E-F9E574AE9DB2} is DHCP enabled. Checking quarantine status.    LocationServices    05/02/2015 16:28:41    500 (0x01F4)
    Sending message body '<ContentLocationRequest SchemaVersion="1.00">
      <AssignedSite SiteCode="COL"/>
      <ClientPackage/>
      <ClientLocationInfo LocationType="SMSPACKAGE" DistributeOnDemand="0" UseProtected="0" AllowCaching="0" BranchDPFlags="0" AllowHTTP="1" AllowSMB="0" AllowMulticast="0"
    UseInternetDP="0">
        <ADSite Name="Millbank"/>
        <Forest Name="lc-uk.org"/>
        <Domain Name="lc-uk.org"/>
        <IPAddresses>
    <IPAddress SubnetAddress="10.103.38.0" Address="10.103.38.10"/>
        </IPAddresses>
      </ClientLocationInfo>
    </ContentLocationRequest>
    '    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    Sending message header '<Msg SchemaVersion="1.1"><ID>{57972056-54D4-461F-B818-D3420A0B5C51}</ID><SourceHost>LCD14572</SourceHost><TargetAddress>mp:[http]MP_LocationManager</TargetAddress><ReplyTo>direct:LCD14572:LS_ReplyLocations</ReplyTo><Priority>3</Priority><Timeout>600</Timeout><ReqVersion>5931</ReqVersion><TargetHost>COLSCCM01.lc-uk.org</TargetHost><TargetEndpoint>MP_LocationManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2015-02-05T16:28:41Z</SentTime><Body
    Type="ByteRange" Offset="0" Length="1084"/><Hooks><Hook3 Name="zlib-compress"/></Hooks><Payload Type="inline"/></Msg>'    ccmsetup    05/02/2015
    16:28:41    500 (0x01F4)
    CCM_POST 'HTTP://COLSCCM01.lc-uk.org/ccm_system/request'    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    Content boundary is '--aAbBcCdDv1234567890VxXyYzZ'    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    Received header '<Msg SchemaVersion="1.1">
        <ID>{48D22538-0FEA-44E6-AAD2-1829DDED2223}</ID>
        <SourceID>GUID:A5143C3E-EA22-4B93-BFF5-B8B859F869F5</SourceID>
        <SourceHost>COLSCCM01</SourceHost>
        <TargetAddress>direct:LCD14572:LS_ReplyLocations</TargetAddress>
        <ReplyTo>MP_LocationManager</ReplyTo>
        <CorrelationID>{00000000-0000-0000-0000-000000000000}</CorrelationID>
        <Priority>3</Priority>
        <Timeout>600</Timeout>
        <TargetHost>LCD14572</TargetHost><TargetEndpoint>LS_ReplyLocations</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2015-02-05T16:28:39Z</SentTime><Body
    Type="ByteRange" Offset="0" Length="2378"/><Hooks><Hook3 Name="zlib-compress"/><Hook Name="authenticate"><Property Name="Signature">3082019106092A864886F70D010702A08201823082017E020101310B300906052B0E03021A0500300B06092A864886F70D0107013182015D30820159020101303630223112301006035504031309434F4C5343434D3031310C300A06035504031303534D5302106A638C8D6A89DE904525D14326BE4DB0300906052B0E03021A0500300D06092A864886F70D01010105000482010027BAE95F5B0DD9F75743E1E40A189091900F78F19367C2A8328F823C63F24229608E7CF02FF2FE76FC61C6A61EF0FE8F19AC75755B88124B13964AE58F971DAB67E47B4DDCAA943B4C27F7AF9B5A0AD1DE956A3AACA26965F5FDAC8659E6263DBB55E025FB305C665AC1AA49972CC937A757EC14F1097DA27AB9998D7CAE332EC135A937A80285C87448AD7B4F4ED059063BCB5032920C65CE16FD32475CD395B279021F62E5C3B534697EDCD68A98D2A654379CCA17056F7B4FAB0346242CE56681F405DB9700FD766FDBD584BB69A4AC088BF3B971BE8B05B723701A22B9D76BB5C063F1BD32B56DB7B3BDC6D827E3D90106F3C1145E04B0629528EA24BD37</Property><Property
    Name="AuthSenderMachine">COLSCCM01;COLSCCM01.lc-uk.org;</Property><Property Name="MPSiteCode">COL</Property></Hook></Hooks><Payload Type="inline"/></Msg>'    ccmsetup  
     05/02/2015 16:28:41    500 (0x01F4)
    Received reply body '<ContentLocationReply SchemaVersion="1.00"><ContentInfo PackageFlags="16777216"><ContentHashValues/></ContentInfo><Sites><Site><MPSite SiteCode="COL" MasterSiteCode="COL"
    SiteLocality="LOCAL" IISPreferedPort="80" IISSSLPreferedPort="443"/><LocationRecords><LocationRecord><URL Name="http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002" Signature="http://COLSCCM01.lc-uk.org/SMS_DP_SMSSIG$/COL00002"/><ADSite
    Name="Millbank"/><IPSubnets><IPSubnet Address="10.20.0.0"/><IPSubnet Address=""/></IPSubnets><Metric Value=""/><Version>7958</Version><Capabilities SchemaVersion="1.0"><Property
    Name="SSLState" Value="0"/></Capabilities><ServerRemoteName>COLSCCM01.lc-uk.org</ServerRemoteName><DPType>SERVER</DPType><Windows Trust="1"/><Locality>LOCAL</Locality></LocationRecord></LocationRecords></Site></Sites><ClientPackage
    FullPackageID="COL00002" FullPackageVersion="2" FullPackageHash="DB3D5D115FC93F6275817FB9791864D98D4AF6897339B9D4AB1C0DE456C240A8" MinimumClientVersion="5.00.7958.1000" RandomizeMaxDays="7" ProgramEnabled="false"
    LastModifiedTime="30376953;932870912" SiteVersionMatch="true" SiteVersion="5.00.7958.1000" EnablePeerCache="true"/><RelatedContentIDs/></ContentLocationReply>'    ccmsetup    05/02/2015
    16:28:41    500 (0x01F4)
    Found local location 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002'    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    Discovered 1 local DP locations.    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    PROPFIND 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002'    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    Got 401 challenge Retrying with Windows Auth...    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    PROPFIND 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002'    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    Using DP location http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    GET 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002/ccmsetup.cab'    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Got 401 challenge Retrying with Windows Auth...    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    GET 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002/ccmsetup.cab'    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    C:\Windows\ccmsetup\ccmsetup.cab is Microsoft trusted.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Successfully extracted manifest file C:\Windows\ccmsetup\ccmsetup.xml from file C:\Windows\ccmsetup\ccmsetup.cab.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Retrieved client version '5.00.7958.1000' and minimum assignable site version '5.00.7845.1000' from manifest    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Checking compatibility of site version '5.00.7958.1000', expect newer than '5.00.7845.1000'    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Site version '5.00.7958.1000' is compatible. Client deployment will continue.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Location 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002' passed site version check.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Loading manifest file: C:\Windows\ccmsetup\ccmsetup.xml    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Successfully loaded ccmsetup manifest file.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Checking if manifest version '5.00.7958.1000' is newer than the ccmsetup version '5.0.7958.1401'    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Running from temp downloaded folder or manifest is not newer than ccmsetup.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'i386/vcredist_x86.exe' is applicable. Add to the list.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'x64/vcredist_x64.exe' is not applicable.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'i386/vc50727_x86.exe' is applicable. Add to the list.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'x64/vc50727_x64.exe' is not applicable.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'i386/WindowsUpdateAgent30-x86.exe' is applicable. Add to the list.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'x64/WindowsUpdateAgent30-x64.exe' is not applicable.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'i386/msxml6.msi' is applicable. Add to the list.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'x64/msxml6_x64.msi' is not applicable.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'i386/msrdcoob_x86.exe' is not applicable.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'x64/msrdcoob_amd64.exe' is not applicable.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'pkgmgr.exe' is not applicable.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'dism.exe' is applicable. Add to the list.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'wimgapi.msi' is not applicable.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'i386/MicrosoftPolicyPlatformSetup.msi' is applicable. Add to the list.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'x64/MicrosoftPolicyPlatformSetup.msi' is not applicable.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'i386/WindowsFirewallConfigurationProvider.msi' is applicable. Add to the list.    ccmsetup    05/02/2015 1

    Hi, Yes i had a look at the log yesterday. there are errors initially, but then the install completes. I can copy the whole log here, the machine in question is LCD14572. If you could take a look would be great. Still doesnt explain why i had to manually
    push the client though:
    Execute query exec [sp_CP_GetPushRequestMachineResource] 2097154539    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:05:58    3648 (0x0E40)
    Execute query exec [sp_CP_GetPushMachineName] 2097154539    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:05:58    3648 (0x0E40)
    Received request: "2097154539" for machine name: "LCD15000" on queue: "Retry".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:05:58    3648 (0x0E40)
    Stored request "2097154539", machine name "LCD15000", in queue "Processing".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:05:58    3648 (0x0E40)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154539, 1    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:05:58    3648 (0x0E40)
    ----- Started a new CCR processing thread. Thread ID is 0x12d8. There are now 1 processing threads    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    Submitted request successfully    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    Getting a new request from queue "Retry" after 100 millisecond delay.    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    Found CCR "2097154540.ccr" in queue "Retry".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    ======>Begin Processing request: "2097154539", machine name: "LCD15000"    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    4824 (0x12D8)
    Execute query exec [sp_IsMPAvailable] N'COL'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    4824 (0x12D8)
    ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    4824 (0x12D8)
    ---> Attempting to connect to administrative share '\\LCD15000\admin$' using account 'LC-UK\VAdmin'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    4824 (0x12D8)
    Execute query exec [sp_CP_GetPushRequestMachine] 2097154540    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    Successfully retrieved information for machine LCD14589 from DB    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    Execute query exec [sp_CP_GetPushRequestMachineIP] 2097154540    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    Execute query exec [sp_CP_GetPushRequestMachineResource] 2097154540    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    Execute query exec [sp_CP_GetPushMachineName] 2097154540    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    Received request: "2097154540" for machine name: "LCD14589" on queue: "Retry".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    Stored request "2097154540", machine name "LCD14589", in queue "Processing".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154540, 1    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    ----- Started a new CCR processing thread. Thread ID is 0x1d10. There are now 2 processing threads    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    Submitted request successfully    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    Getting a new request from queue "Retry" after 100 millisecond delay.    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    Found CCR "2097154542.ccr" in queue "Retry".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    ======>Begin Processing request: "2097154540", machine name: "LCD14589"    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    7440 (0x1D10)
    Execute query exec [sp_IsMPAvailable] N'COL'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    7440 (0x1D10)
    ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    7440 (0x1D10)
    ---> Attempting to connect to administrative share '\\LCD14589\admin$' using account 'LC-UK\VAdmin'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    7440 (0x1D10)
    Execute query exec [sp_CP_GetPushRequestMachine] 2097154542    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    Successfully retrieved information for machine LCD14571 from DB    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    Execute query exec [sp_CP_GetPushRequestMachineIP] 2097154542    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    Execute query exec [sp_CP_GetPushRequestMachineResource] 2097154542    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    Execute query exec [sp_CP_GetPushMachineName] 2097154542    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    Received request: "2097154542" for machine name: "LCD14571" on queue: "Retry".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    Stored request "2097154542", machine name "LCD14571", in queue "Processing".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154542, 1    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    ----- Started a new CCR processing thread. Thread ID is 0x1768. There are now 3 processing threads    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:04    3648 (0x0E40)
    Submitted request successfully    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:04    3648 (0x0E40)
    Getting a new request from queue "Retry" after 100 millisecond delay.    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:04    3648 (0x0E40)
    Sleeping for 60 minutes for queue "Retry".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:04    3648 (0x0E40)
    ======>Begin Processing request: "2097154542", machine name: "LCD14571"    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:04    5992 (0x1768)
    Execute query exec [sp_IsMPAvailable] N'COL'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:05    5992 (0x1768)
    ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:05    5992 (0x1768)
    ---> Attempting to connect to administrative share '\\LCD14571\admin$' using account 'LC-UK\VAdmin'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:05    5992 (0x1768)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:21    4824 (0x12D8)
    ---> The device LCD15000 does not exist on the network. Giving up    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:21    4824 (0x12D8)
    ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:21    4824 (0x12D8)
    ---> Attempting to connect to administrative share '\\LCD15000.lc-uk.org\admin$' using account 'LC-UK\VAdmin'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:21    4824 (0x12D8)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:23    7440 (0x1D10)
    ---> The device LCD14589 does not exist on the network. Giving up    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:23    7440 (0x1D10)
    ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:23    7440 (0x1D10)
    ---> Attempting to connect to administrative share '\\LCD14589.lc-uk.org\admin$' using account 'LC-UK\VAdmin'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:23    7440 (0x1D10)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:26    5992 (0x1768)
    ---> The device LCD14571 does not exist on the network. Giving up    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:26    5992 (0x1768)
    ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:26    5992 (0x1768)
    ---> Attempting to connect to administrative share '\\LCD14571.lc-uk.org\admin$' using account 'LC-UK\VAdmin'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:26    5992 (0x1768)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47    4824 (0x12D8)
    ---> The device LCD15000.lc-uk.org does not exist on the network. Giving up    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47    4824 (0x12D8)
    ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47    4824 (0x12D8)
    ---> Attempting to connect to administrative share '\\LCD15000\admin$' using account 'LC-UK\VAdmin'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47    4824 (0x12D8)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47    4824 (0x12D8)
    ---> The device LCD15000 does not exist on the network. Giving up    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47    4824 (0x12D8)
    ---> ERROR: Unable to access target machine for request: "2097154539", machine name: "LCD15000",  access denied or invalid network path.    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47  
     4824 (0x12D8)
    Execute query exec [sp_CP_SetLastErrorCode] 2097154539, 53    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47    4824 (0x12D8)
    Stored request "2097154539", machine name "LCD15000", in queue "Retry".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47    4824 (0x12D8)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154539, 2    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47    4824 (0x12D8)
    Execute query exec [sp_CP_SetLatest] 2097154539, N'02/05/2015 16:06:47', 2    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47    4824 (0x12D8)
    <======End request: "2097154539", machine name: "LCD15000".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47    4824 (0x12D8)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51    7440 (0x1D10)
    ---> The device LCD14589.lc-uk.org does not exist on the network. Giving up    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51    7440 (0x1D10)
    ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51    7440 (0x1D10)
    ---> Attempting to connect to administrative share '\\LCD14589\admin$' using account 'LC-UK\VAdmin'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51    7440 (0x1D10)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51    7440 (0x1D10)
    ---> The device LCD14589 does not exist on the network. Giving up    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51    7440 (0x1D10)
    ---> ERROR: Unable to access target machine for request: "2097154540", machine name: "LCD14589",  access denied or invalid network path.    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51  
     7440 (0x1D10)
    Execute query exec [sp_CP_SetLastErrorCode] 2097154540, 53    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51    7440 (0x1D10)
    Stored request "2097154540", machine name "LCD14589", in queue "Retry".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51    7440 (0x1D10)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154540, 2    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51    7440 (0x1D10)
    Execute query exec [sp_CP_SetLatest] 2097154540, N'02/05/2015 16:06:51', 2    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51    7440 (0x1D10)
    <======End request: "2097154540", machine name: "LCD14589".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51    7440 (0x1D10)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55    5992 (0x1768)
    ---> The device LCD14571.lc-uk.org does not exist on the network. Giving up    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55    5992 (0x1768)
    ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55    5992 (0x1768)
    ---> Attempting to connect to administrative share '\\LCD14571\admin$' using account 'LC-UK\VAdmin'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55    5992 (0x1768)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55    5992 (0x1768)
    ---> The device LCD14571 does not exist on the network. Giving up    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55    5992 (0x1768)
    ---> ERROR: Unable to access target machine for request: "2097154542", machine name: "LCD14571",  access denied or invalid network path.    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55  
     5992 (0x1768)
    Execute query exec [sp_CP_SetLastErrorCode] 2097154542, 53    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55    5992 (0x1768)
    Stored request "2097154542", machine name "LCD14571", in queue "Retry".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55    5992 (0x1768)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154542, 2    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55    5992 (0x1768)
    Execute query exec [sp_CP_SetLatest] 2097154542, N'02/05/2015 16:06:55', 2    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55    5992 (0x1768)
    <======End request: "2097154542", machine name: "LCD14571".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55    5992 (0x1768)
    CCR count in queue "Retry" is 3.    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:07:42    6564 (0x19A4)
    Sleeping for 634 seconds...    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:07:43    6564 (0x19A4)
    Thread has been inactive too long. Closing thread    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:16:47    4824 (0x12D8)
    --- This thread is terminating due to inactivity    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:16:47    4824 (0x12D8)
    ----- Terminated CCR processing thread. There are now 2 processing threads    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:16:47    4824 (0x12D8)
    Thread has been inactive too long. Closing thread    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:16:51    7440 (0x1D10)
    --- This thread is terminating due to inactivity    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:16:51    7440 (0x1D10)
    ----- Terminated CCR processing thread. There are now 1 processing threads    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:16:51    7440 (0x1D10)
    Thread has been inactive too long. Closing thread    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:16:55    5992 (0x1768)
    --- This thread is terminating due to inactivity    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:16:55    5992 (0x1768)
    ----- Terminated CCR processing thread. There are now 0 processing threads    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:16:55    5992 (0x1768)
    Sleeping for 1 seconds...    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:16    6564 (0x19A4)
    The Site Control File has not changed since the last parameter update.    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:17    6564 (0x19A4)
    Updating Site Parameters    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    MP Ports: 80    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    IISPreferedPort: 80    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    MP SSL Ports: 443    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    IISSSLPreferedPort: 443    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Default MP: COLSCCM01.lc-uk.org    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Default MP Type: 1    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Default MP: [None]    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Certificate Selection Criteria:    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Certificate Store:    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    SSL State: 224    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Select First Certificate: 1    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Certificate Issuers:    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Checking configuration information for server: COLSCCM01.LC-UK.ORG.    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Checking configuration information for server: COLSCCM01.LC-UK.ORG.    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Fallback Status Point: COLSCCM01.lc-uk.org    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Install on DC: False    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Option for installing using IP address: 0    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Sleeping for 1200 seconds...    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Waiting for change in directory "D:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout).    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:23:39  
     2876 (0x0B3C)
    Execute query exec [sp_CP_GetNewPushMachines] N'COL'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:28:09    2876 (0x0B3C)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154468, 1    SMS_CLIENT_CONF

  • For Your Consideration: Ultimate Lync 2010 client install with SCCM 2007

    While the subject of my post may be very presumptuous, I submit the following for your consideration to answer the often-asked question about how to deploy Lync 2010 client with SCCM.
    Background:
    I cannot understand why Microsoft made the Lync install so darned confusing, complex, and convoluted.
    After our Lync 2010 FE server was up and running and all users migrated off our OCS server to the Lync environment, I spent about a month and a half trying to figure out how to:
    1.  Uninstall the OCS 2007 R2 client
    2.  Install all prerequisites for the Lync client
    3.  Install Lync on all user workstations silently.
    While researching this, the simple answer I kept seeing given to this question was, "just use the .exe with the right switches according to the TechNet article here: http://technet.microsoft.com/en-us/library/gg425733.aspx".  Well, my response is, I
    tried that and while the program installed itself correctly pushed through SCCM, because I was doing it using an administrative account (i.e. the SYSTEM account) due to our users not having admin rights, when the install was done, Lync would automatically
    start up, but in the SYSTEM context so that the user couldn't see it was running, they go to run it and it won't run for them.  I was unable to find any switch or option to prevent the automatic launch.  I suppose the simple solution to that would
    be to have the user reboot, but that's unnecessarily disruptive and was contrary to the desire to make this a silent install.
    The next simplest answer I saw was, "extract the MSI and use that with the right switches".  Problem with that is that the MSI by itself doesn't remove the OCS client or install the prerequisites, and also either requires a registry change to even allow
    the MSI to be used or a hacked MSI that bypasses the registry key check.  I tried to put a package together to uninstall OCS, install the prereqs, and use a hacked MSI, but I never could get the MSI hacked properly.  The other problem I ran into
    was detecting if the OCS client was running in a predictable way so I could terminate it, properly uninstall it, and then do the rest of the installations.  It was this problem that ultimately led me to the solution that I'm about to detail and that has
    worked marvellously for us.
    Solution:
    As I said before, when I first looked at this problem, I started by building a typical software deployment package (Computer Management -> Software Distribution -> Packages) and then created the programs to do the install.  My first attempt was
    just with the .exe file provided as-is by Microsoft using the switches they document in the link above for IT-Managed Installation of Lync, and...well, the end result wasn't quite as desirable as hoped.  So, my next attempt was to extract all the prerequisite
    files and the Lync install MSI (both for x86 and x64), attempt to hack it to get around the "UseMSIForLyncInstallation" registry key, and make the command-lines to terminate OCS and uninstall it.
    In the past when I had an install to do with SCCM that also required uninstalling an older version of a given application, I typically used the program-chaining technique.  That's where you have, for example, 3 or more programs that run in a package
    in a sequence and you have Program 3 be set to run after Program 2 does and then set Program 2 to run after Program 1 so you get the desired sequence of Programs 1-2-3 running in that order.  So, I created programs to 1) kill Communicator.exe 2) uninstall
    Communicator 2007 R2 by doing an "msiexec /uninstall {GUID}" 3) install Silverlight 4) install Visual C++ x86 5) optionally install Visual C++ x64, and then 6) install the Lync x86 or x64 client.  That final step was always the point of failure because
    I couldn't get the hacked MSI for the Lync Client install to work.  I also realized that if Communicator wasn't running when the deployment started, that step would fail and cause the whole process to bail out with an error.  That's one of the downsides
    of program-chaining, if one step fails, SCCM completely bails on the deployment.  This is what also led me to the key to my solution:  TASK SEQUENCES.
    I'm not sure how many people out there look in the "Operating System Deployment" area of SCCM 2007 where Task Sequences normally live, but I also wonder how many people realize that Task Sequences can be used for more than just Operating System deployments. 
    One of the biggest advantages of a task sequence is you can set a step to ignore an error condition, such as if you try to terminate a process that isn't running.  Another advantage is that task sequences have some very good built-in conditionals that
    you can apply to steps, for example, having the sequence skip a step if a certain application (or specific version of an application) is not installed on the machine.  Both of those advantages factor highly into my solution.
    OK, for those who already think this is "TL;DR", here's the step-by-step of how to do this:
    First, you need to extract all the files from the LyncSetup.exe for your needed architectures.  We have a mix of Windows XP and Windows 7 64-bit, so my solution here will take both possibilities into account.  To extract the files, just start up
    the .exe like you're going to install it, but then when the first dialog comes up, navigate to "%programfiles%\OCSetup" and copy everything there to a new location.  The main files you need are: Silverlight.exe, vcredist.exe (the x64 LyncSetup.exe includes
    both x86 and x64 Visual C++ runtimes, you need them both, just rename them to differentiate), and Lync.msi (this also comes in an x86 and x64 flavor, so if you have a mix of architectures in your environment, get both and either put them into their own directories
    or rename them to reflect the architecture).
    For my setup, I extracted the files for the x86 and x64 clients and just dumped them each into directories named after the architectures.
    Next, move these files into a directory to your SCCM file server, whatever it might be that you deploy from, in our case, it was just another volume on our central site server.  Go to the SCCM console into Computer Management -> Software Distribution
    -> Packages and then create a new package, call it something meaningful, and then point to the directory on your SCCM file server for the source files.
    Now you need to create 3 to 5 programs inside the package:
    1.  Name: Silverlight
       Command Line: x86\Silverlight.exe /q     (remember, inside my main Lync install folder on my distribution point, I have an x86 directory for the files from the x86 installer and an x64 folder for the files from the x64 installer. 
    The fact is the Silverlight installer is the same in both, so you only need one of them.)
       On the Environment tab:  Program can run whether or not a user is logged in, runs with administrative rights, Runs with UNC name
       On the Advanced tab:  Suppress program notifications
       All other options leave default.
    2.  Name:  Visual C++ x86
        Command Line:  x86\vcredist_x86.exe /q
       On the Requirements tab: Click the radio button next to "This program can run only on specified client platforms:" and then check off the desired x86 clients.
       Environment and Advanced tabs:  same as Silverlight
       (If you have only x64 clients in your environment, change all x86 references to x64.  If you have a mixed environment, create another program identical to this one, replacing references to x86 with x64.)
    3.  Name:  Lync x86
        Command Line:  msiexec /qn /i x86\Lync.msi OCSETUPDIR="C:\Program Files\Microsoft Lync"  (The OCSETUPDIR fixes the issue with the Lync client wanting to "reinstall" itself every time it starts up)
        Requirements, Environment, and Advanced tabs:  Same as with Visual C++ and Silverlight
        (Same deal as above if you have all x64 clients or a mix, either change this program to reflect or make a second program if necessary)
    Now you need to make the Task Sequence.  Go to Computer Management -> Operating System Deployment -> Task Sequences.  Under the Actions pane, click New -> Task Sequence.  In the Create a New Task Sequence dialog, choose "create a
    new custom task sequence", Next, enter a meaningful name for the task sequence like "Install Microsoft Lync", Next, Next, Close.
    The task sequence will have up to 12 steps in it.  I'll break the steps down into 3 phases, the prereqs phase, uninstall OCS phase, and then Lync install phase.
    Prereqs Phase:
    These are the easiest of the steps to do.  Highlight the task sequence and then in the Actions pane, click Edit.
    1.  Click Add -> General -> Install Software.  Name: "Install Microsoft Silverlight".  Select "Install a single application", browse to the Lync package created earlier and then select the Silverlight program.
    2.  Add -> General -> Install Software.  Name: "Install Microsoft Visual C++ 2008 x86".  Install Single Application, browse to the Lync package, select the Visual C++ x86 package.
    As before, if you're an all-x64 environment, replace the x86 references with x64.  If you have a mixed environment, repeat step 2, replacing x86 with x64.
    3.  Add -> General -> Run Command Line.  Name: "Enable Lync Installation".  This step gets around the UseMSIForLyncInstallation registry requirement.  The Lync client MSI simply looks for the presence of this key when it runs, so
    we'll inject it into the registry now and it doesn't require a reboot or anything.  It just has to be there before the client MSI starts.
    Command Line: reg add "hklm\Software\Policies\Microsoft\Communicator" /v UseMSIForLyncInstallation /t REG_DWORD /d 1 /f
    Uninstall OCS Phase:
    This part consists of up to 6 Run Command Line steps.  (Add -> General -> Run Command Line)
    4.  Name: "Terminate Communicator".  Command Line: "taskkill /f /im communicator.exe".  On the Options page, check the box next to "Continue on error".  This will terminate the Communicator process if it's running, and if it's not, it'll
    ignore the error.
    5.  Name: "Terminate Outlook".  Command Line: "taskkill /f /im OUTLOOK.exe".  Check the "Continue on error" on the Options page here too.  Communicator 2007 hooks into Outlook, so if you don't kill Outlook, it might prompt for a reboot
    because components are in use.
    (NOTE:  If necessary, you could also add another step that terminates Internet Explorer because Communicator does hook into IE and without killing IE, it might require a restart after uninstalling Communicator in the next steps.  I didn't run into
    this in my environment, though.  Just repeat step 5, but replace OUTLOOK.EXE with IEXPLORE.EXE)
    6.  Name: "Uninstall Microsoft Office Communicator 2007".  Command Line: "msiexec.exe /qn /uninstall {E5BA0430-919F-46DD-B656-0796F8A5ADFF} /norestart" On the Options page:  Add Condition ->  Installed Software -> Browse to the
    Office Communicator 2007 non-R2 MSI -> select "Match this specific product (Product Code and Upgrade Code)".
    7.  Name:  "Uninstall Microsoft Office Communicator 2007 R2".  Command Line:  "msiexec.exe /qn /uninstall {0D1CBBB9-F4A8-45B6-95E7-202BA61D7AF4} /norestart".  On the Options page:  Add Condition -> Installed Software ->
    Browse to the Office Communicator 2007 R2 MSI -> select "Match any version of this product (Upgrade Code Only)".
    SIDEBAR
    OK, I need to stop here and explain steps 6 and 7 in more detail because it was a gotcha that bit me after I'd already started deploying Lync with this task sequence.  I found out after I'd been deploying for a while that a tech in one of our remote
    offices was reinstalling machines and putting the Communicator 2007 non-R2 client on instead of the R2 client, and my task sequence was expecting R2, mostly because I thought we didn't have any non-R2 clients out there.  So, at first I just had our Help
    Desk people do those installs manually, but later on decided to add support for this possibility into my task sequence.  Now, when you normally uninstall something with msiexec, you would use the Product Code GUID in the command, as you see in steps 6
    and 7.  All applications have a Product Code that's unique to a specific version of an application, but applications also have an Upgrade Code GUID that is unique for an application but common across versions.  This is part of how Windows knows that
    Application X version 1.2 is an upgrade to Application X version 1.1, i.e. Application X would have a common Upgrade Code, but the Product Code would differ between versions 1.1 and 1.2.
    The complication comes in that Communicator 2007 and Communicator 2007 R2 have a common Upgrade Code, but different Product Codes and the "MSIEXEC /uninstall" command uses the Product Code, not the Upgrade Code.  This means that if I didn't have step
    6 to catch the non-R2 clients, step 7 would be fine for the R2 clients, but fail on non-R2 clients because the Product Code in the MSIEXEC command would be wrong.  Luckily, we only had one version of the non-R2 client to deal with versus 4 or 5 versions
    of the R2 client.  So, I put the command to remove Communicator 2007 non-R2 first and checked for that specific product and version on the machine.  If it was present, it uninstalled it and then skipped over the R2 step.  If non-R2 was not present,
    it skipped that step and instead uninstalled any version of the R2 client.  It's important that steps 6 and 7 are in the order they are because if you swap them, then you'd have the same outcome as if step 6 wasn't there.  What if neither is on the
    machine?  Well the collection this was targeted to included only machines with any version of Communicator 2007 installed, so this was not a problem.  It was assumed that the machines had some version of Communicator on them.
    8.  Name:  "Uninstall Conferencing Add-In for Outlook".  Command Line:  "msiexec.exe /qn /uninstall {730000A1-6206-4597-966F-953827FC40F7} /norestart".  Check the "Continue on error" on the Options Page and then Add Condition ->
    Installed Software -> Browse to the MSI for this optional component and set it to match any version of the product.  If you don't use this in your environment, you can omit this step.
    9.  Name:  "Uninstall Live Meeting 2007".  Command Line:  "msiexec.exe /qn /uninstall {69CEBEF8-52AA-4436-A3C9-684AF57B0307} /norestart".  Check the "Continue on error" on the Options Page and then Add Condition -> Installed Software
    -> Browse to the MSI for this optional component and set it to match any version of the product.  If you don't use this in your environment, you can omit this step.
    Install Lync phase:
    Now, finally the main event, and it's pretty simple:
    10.  Click Add -> General -> Install Software.  Name: "Install Microsoft Lync 2010 x86".  Select "Install a single application", browse to the Lync package created earlier and then select the "Lync x86" program.  As before, if you
    only have x64 in your environment, replace the x86 with x64, or if you have a mixed environment, copy this step, replacing x86 references with x64.
    And the task sequence is done!  The final thing you need to do now is highlight the task, click Advertise in the Actions pane, and deploy it to a collection like you would with any other software distribution advertisement.  Go get a beer!
    Some final notes to keep in mind:
    1.  You can't make a task sequence totally silent...easily.  Users will get balloon notifications that an application is available to install.  The notifications cannot be suppressed through the GUI.  I've found scripts that supposedly
    hack the advertisement to make it be silent, but neither of them worked for me.  It was OK, though because in the end we wanted users, especially laptop users, to be able to pick a convenient time to do the upgrade.  The task sequence will appear
    in the "Add/Remove Programs" or "Programs and Features" Control Panel.  You can still do mandatory assignments to force the install to happen, you just can't make it totally silent.  On the plus side, the user shouldn't have to reboot at any point
    during or after the install!
    2.  In the advertisement setup, you can optionally show the task sequence progress.  I've configured the individual installs in this process to be silent, however, I did show the user the task sequence progress.  This means instead of seeing
    5 or 6 Installer windows pop up and go away, the user will have a single progress bar with the name of the step that is executing.
    3.  One step that I didn't consider when I actually did this was starting the Lync client as the user when the install was complete.  The user either had to start the client manually or just let it start on its own at the next logon.  However,
    while I was writing this, I realized that I could possibly start the client after installing by making another Program in the Lync Package with a command line that was along the lines of "%programfiles%\Microsoft Lync\communicator.exe" and then in the Environment
    tab, set it to "Run with user's rights" "only when a user is logged on".
    4.  My first revision of this task sequence has the Prereqs phase happening after the OCS uninstall phase, but I kept running into problems where the Silverlight installer would throw some bizarre error that it couldn't open a window or something wacky
    and it would fail.  Problem was, I couldn't re-run the task sequence because now it would fail because OCS had been uninstalled, so that's why the Prereqs happen first.  It ran much more reliably this way.
    5.  For some reason that baffles me, when I'd check the logs on the Site Server to monitor the deployment, I'd frequently see situations where the task sequence would start on a given machine, complete successfully, almost immediately start again, and
    then fail.  I'm not sure what is causing that, but I suspect either users are going to Add/Remove Programs and double-clicking the Add button to start the install instead of just single-clicking it, or the notification that they have software to install
    doesn't go away immediately or Lync doesn't start up right after the install, so they think the first time it didn't take and try it a second time.
    I hope this helps some of you SCCM and Lync admins out there!

    On Step 8 I found multiple product codes for the Conferencing Add-In for Outlook.  Here's a list of the ones I found in the machines on my network:
    {987CAEDE-EB67-4D5A-B0C0-AE0640A17B5F}
    {2BB9B2F5-79E7-4220-B903-22E849100547}
    {13BEAC7C-69C1-4A9E-89A3-D5F311DE2B69}
    {C5586971-E3A9-432A-93B7-D1D0EF076764}
    I'm sure there's others one, just be mindful that this add-in will have numerous product codes.

  • Handling of pending reboot, exclusive updates for patch management with SCCM 2012

    Hello,
    Planning to use SCCM 2012, I would like to understand how smart is SCCM 2012 when dealing with specific patch management situation.
    Assuming I have the following:
    - A given server to be patched is missing a lot of updates, several being mutually exclusive. This typical case will require several reboot / patching to properly obtain a server fully up to date.
    - A given server to be patched is in pending reboot state because the local admin installed new software and has not restarted the server yet as requested
    - Those servers have configured maintenance windows of 2 hours during each night. I scheduled a deployment of missing patches authorizing restart.
    --> when the maintenance window will be reached:
    - will the server first be restarted to clean the pending reboot ?
    - will the the server be patched / restarted several times as required to fully meet the updates to be deployed.
    Another scenario on workstation side:
    - can I enforce deployment of updates at a given time, do not automatically restart the workstation during patch deployment, but after deployment schedule a mandatory restart with a countdown if there is a pending reboot... From end-user perspective, it
    would have the following behavior. For instance:
    - patches are automatically installed on Monday at 10 AM
    - as soon as deployment is done, warning message is displayed to ask users to reboot
    - then user has up to 48h to restart his computer by himself. If he does not do it, it will be automatically done after countdown expires.
    --> Can such a scenario be managed by SCCM 2012 ?
    Regards.

    Hi,
    I have a related question about deploying Microsoft Security Updates to workstations via SCCM 2012.  Is there a way to deploy the MS updates to workstations and only suppress reboots for machines with users logged on or locked?  There seems to
    be only 2 different options for reboots, Suppress them all or don't suppress them at all.  We would like SCCM to reboot the machines that are logged off, but suppress the reboot for those that are logged on, while at the same time, provide the user with
    a notification that their machine needs to be rebooted (at their convenience). 
    We've tried applying the Domain GPO "No auto-restart with logged on users for scheduled automatic updates installations" (Enabled) and "Configure Automatic Updates" (Disabled), but the logged on/locked machines still receive the restart countdown with no
    option to postpone or delay.
    This is a show stopper for us since we have an environment where we are absolutely not allowed to reboot a logged on machine.
    For a little background, we are coming from SMS 2003 and the Distribute Software Updates (ITMU) way of deploying MS Updates, where we could always set the program to run "Only when no user is logged on".
    Please tell me there is a way to achieve our desired result.
    Thanks,
    Dan 

  • Workgroup client cannot discovered SCCM 2012 R2

    Hi,
    I have enabled the Network Discovery in SCCM 2012 R2, and defined the subnet of clients that I want to manage. Then IP subnet boundaries has been created. When I see
    Devices in Assets and Compliance, the workgroup clients cannot discovered.
    Communication between the workgroup clients with SCCM server is no issue in the network, by ping and mapping folder share in both is good. Windows firewall on all workgroup clients has configured to allow port File and Printer Sharing and WMI.
    How I can discovered all Workgroup clients?
    Thanks
    Regards, Bar Waelah

    Hi Bar Waelah,
    I think you need to configure the Maximum hops on the bottom of SNMP Tab.
    For more details, please check the Limiting Network Discovery.
    http://technet.microsoft.com/en-us/library/gg712308.aspx#BKMK_NetworkDisc
    You could also specify the IP Address or NetBIOS name of the device in SNMP Devices.
    Best Regards,
    Joyce 
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Windows 8 Tablet Manage with SCCM 2012

    Hi,
    Does the SCCM 2012 R2 supports managing of Tablet Devices  Windows 8 installed.
    Is there any step-by-step guide or TechNet or MSDN articales ?
    Thanks,

    here's some step by step guides for you, that help you enroll and deploy settings and apps to Windows 8.x devices
    CM12 in a Lab -
    How can I manage modern devices using System Center 2012 R2 Configuration Manager ? - Part 5
    CM12 in a Lab -
    How can I manage modern devices using System Center 2012 R2 Configuration Manager ? - Part 6
    CM12 in a Lab -
    How can I manage modern devices using System Center 2012 R2 Configuration Manager ? - Part 7
    Step by Step Configuration Manager Guides >
    2012 Guides |
    2007 Guides | I'm on Twitter > ncbrady

  • How to deploy Visual Studio 2012 with SCCM 2012

    Hi All,
    Does anyone know how can I deploy Visual Studio 2012 withc SCCM 2012(step by step).
    Best regards
    Nick

    Hi,
    It worked for me,
    http://fearthemonkey.co.uk/how-to-deploy-visual-studio-2012-using-configuration-manager-2012-and-the-application-method/
    Regards,
    Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

Maybe you are looking for