Rediscover SCCM Client And Rerun Deployment

I deleted a client from the console and waited for it to be rediscovered. I then re-added it to its prior collections some of which were targeted for deployments. Question is should I expect that the client would rerun past deployments that successfully
ran already? I'd guess that the rediscovered client would have a different resource ID but not sure if that would cause the deployments to rerun as the run history would still be in the registry on that client unless I uninstalled it first right?

Ok I think I'm starting to understand. Can you validate the following statements and tell me if they are correct? I've read
http://blogs.catapultsystems.com/jsandys/archive/2011/04/05/configmgr-program-rerun-behavior.aspx as well.
The client is aware of the execution history via the registry/WMI. The server only knows of this by what information is sent back to it from the client (status messages, state messages, etc). So removing the registry value and restarting SMS service
would cause the client to rerun a deployment it has already successfully ran regardless of the deployment settings.
If I successfully installed Office 2013 for example by a mandatory deployment. I delete that client from the console and it is rediscovered when the client heartbeats and a DDR is created. I re-add that client to the "Office 2013" collection for
example. The deadline is in the past and it already successfully ran. The deployment is set to only rerun on failure. Office 2013 will or will not attempt a reinstall?

Similar Messages

  • Report All SCCM clients and Collections

    Hi all
    I'm trying to create report
    All SCCM clients and Collections
    But I can't convert multiple rows (collections) in one row
    I got:
    Name        Collection Name
    ps1             serverDP
    ps1               Adobe
    ps2                CRT
    ps2               Note
    I need:
    Name        Collection Name
    ps1             serverDP ,Adobe
    ps2                 CRT,Note
    Im using following query ....but it doesn't work .Need help!!!  
    select
    v_FullCollectionMembership
    .Name
    as Name,
    CollName
    =
    stuff((SELECT
    + v_Collection.Name
    from
    v_Collection
    where
    v_Collection.CollectionID
    = v_FullCollectionMembership.CollectionID
    FOR
    XML
    PATH('')
    ), 1,
    1,'')
    FROM v_FullCollectionMembership
    Gerkin

    Hi,
    I recommend you use Report Builder to create the report.
    Using Matrix and LookupSet to merge the table.
    =join(LookupSet(Fields!Name.Value, Fields!Name.Value, Fields!CollName.Value, "DataSet_name"), ",")
    For more information, please review the link below:
    Adding a Matrix (Reporting Services)
    http://technet.microsoft.com/en-us/library/ms157334(v=SQL.100).aspx
    LookupSet Function (Report Builder and SSRS)
    http://msdn.microsoft.com/en-IN/library/ee240819.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.

  • SCCM Policies and SCEP Deployment Issues

    I'm having several issues with SCCM 2012 R2.
    I have inherited an existing SCCM 2012 R2 installation.  The company does not want me to rebuild it from the ground using best practices, so I'm doing what I can with it.
    Issue #1: SCEP does not auto deploy to new systems;
    Issue #2: Client policies do not update;
    Issue #3: Anti-malware policies do not update.
    Starting out, I guess I need to look at issue #2 before I look at the others.
    The client is auto-deploying as far as I can tell.  I do not have any GPO’s that push the software to the clients, so it appears that the system wide deployment of the client is working correctly.
    As for the policies not being updated, I have created a new policy that is assigned to newly defined device collections. 
    I have check the membership of the collections and it is populating/selecting the assets correctly. 
    I have picked a handful of computers out of the collection to use for information gathering. 
    Looking at the log files, it shows that it is applying policies, but it does not identify which policy from the SCCM server.
    With the new policies that I’ve created, I’ve enabled ‘Endpoint Proection’, ‘Hardware Inventory’, ‘Power Management’, ‘Remote Tools’, ‘Software Deployment’, ‘Software Metering’, and ‘User and Device Affinity’. 
    After 13 days, the options within the policy have not taken effect as I have check the clients and the settings from the ‘Remote Tools’ and ‘Power Management’ haven’t been applied. I waited this long since several of the settings were set at 7 days before
    re-evaluation.
    I’m not sure where to go next on this issue.
    On the issue #1 & 3, the computers that did get the initial config push and SCEP install, before I came on, are operating and reporting back to the SCCM manager that they are in a managed state, which is fine, but they are not applying any newly defined
    policies.  Checking the logs on the clients show that they are applying the Default Client Settings and not any of the other policies that are set to deploy to All systems or any other collection I’ve defined. 
    Also checking the anti-malware policy logs on the clients, they are also still applying the Default Client Antimalware Policy, not any of the custom policies, just like the SCCM client issue.  In the EndpointProtectionAgent.log, i have several lines
    showing "Deployment WMI is NOT ready."  The same is in several of the other log files, so I've check that all the WMI services are running and I have tested management with the PoshCat utility and all of the commands are working in there and
    the output reports all seem to be reporting correctly.
    Any pointers or starting points would be greatly appreciated.

    For the 'Client Settings', I have 4 listed.  Default Client Settings, EP Settings (existing that I have set to deploy to a group that only has 1 computer left in it), Server Policy, and Workstation Policy (applies to all clients that have 'workstation'
    in the version name).
    For SCEP, just 2.  Default Client  and Custom SCEP.
    The inventory and software distribution... let's look at the inventory function.  I have nothing showing in '\Assets and compliance\Overview\Asset Intelligence\Inventoried Software'.
    As for software distribution, I am not sure how to check that -- I haven't set up any deployed software packages yet... but the SCEP and Windows Updates are the only things showing up.  SCEP is not deploying to any new workstations, but it appears all
    the Windows Updates are deploying correctly to all the workstations.
    I just checked the SrcUpdateMgr.log on a client and I've found several lines of 'Instance of CCM_SourceUpdateClientConfig doesn't exist in WMI'
    Checking the SoftwareCatalogUpdateEndpoint.log file, I have several lines that just repeat...
    Software catalog update endpoint is starting
    Logo event received
    Logon user SID: [...]
    Retrieving URL for software Catalog
    Software Catalog update endpoint is loading
    Received notification for client agent setting or portal information change
    Retrieving URL for Softwware Catalog
    Making call to determin whether catalog Url should be added to the trusted sites zone
    Updating the registry for Software Catalog for user '[...]'
    Notification system applicaton: C:\Windows\CCM\UpdateTrustedSites.exe
    Started UpdateTrustedSites process
    Making call to determine whether keys to enable Silverlight elevated trust should be added
    Enable elevated trust is set to false. Setting the keys to 0
    CSoftwareCatalogUpdateHandler::UpdateSilverlightRegistry: Successfully set elevated trust on this client for Silverlight
    CSoftwareCatalogUpdateHandler::UpdateSilverlightRegistry: Successfully set elevated trust on this client for Silverlight
    CSoftwareCatalogUpdateHandler::UpdateSilverlightRegistry: Successfully set elevated trust on this client for Silverlight
    Received notification for client agent setting or portal information change
    and it does show the Silverlight lines 3 times each time in the repeats. The repeat time stamp looks like it happens alternating 20 minutes, then 2 hours, then 20 minutes, then 2 hours, etc.
    KW

  • Internet based management of SCCM clients and management points ?

    We have an SCCM backend infrastructure which is used to manage what is in affect multiple external organizations over the internet.  Currently each SCCM client is managed by the primary server directly over the internet. 
    Am I right that we could place a configmgr management point on the internal networks and for the clients to talk to this server when connected to the company network instead of all clients getting patched across the internet connection ?  Meaning that
    just the MP would communicate with our backend infrastructure ?

    So your internal clients are now connecting over the internet to the local MP? How does this setup look like exactly? How were the clients installed (parameters)?
    Torsten Meringer | http://www.mssccmfaq.de

  • SCCM Client and SCEP Client Uninstall

    Hi, I have below questions with regard to the SCCM client software and the SCEP client software.
    Does SCCM client uninstallation removes SCEP client as well? If not, how does the Endpoint Protection get the updates after SCCM client is removed? How to remove/uninstall SCEP client?
    If the SCCM client uninstallation removes the SCEP client as well (by running ccmsetup.exe /uninstall), how to make it to NOT uninstall the SCEP client?
    Thanks.
    NM

    Yes, your SCEP client should still be able to update.
    If you're installing the ConfigMgr client again, and have manage SCEP client enabled in the ConfigMgr client settings, it does more then just adding the update source. It allows you to manage the SCEP client configuration (like scan settings, exclusions,
    etc), perform remote actions (like initiating a scan) and report about them.
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • WSDL Web Services Client and EAR deploy problem

    Hi!
    I have allready posted this on "Web AS General", with no result.
    So I hope this forum is a better choise.
    Environment:
    SAP EP / SAP NW04 / SPS14
    NW DevStudio
    I just deployed an ear file (first time ...) with SDM.
    The ear file represents an auto generated web services client on basis of a WSDL file.
    (done from web services perspective in NWDS choosing "New Deployable Proxy Project")
    When running a test I get the following error:
    "Could not find portal application Unknown provider of external application: J2EE::sap.com/NWTPINWSClient"
    .. where NWTPINWSClient is the name of the EAR - file
    The test code contains this:
    The portalapp.xml has the following tag:
    <application-config>
    <property name="SharingReference" value="J2EE::sap.com/NWTPINWSClient">
    </property>
    </application-config>
    I'm new to this, so please feel free to consider newbie misstakes.
    BRGRDS
    Peter M

    Can you/anybody post solution. I have the same problem.
    Thanks
    Srinivas

  • SCCM Client push or manual installation does not complete

    Hi All,
    I have deployed SCCM 2012 R2 in my lab environment. It has been deployed successfully. I have a issue in which the clients are not getting installed both manually and by pushing the agents via the console. 
    My servers are as follows:
    SCCMSVR.labtest.com  - Is the SCCM server and Fail back status point.
    Server.labtest.com - Is the Domain controller, SQL server
    SCCMTEST.labtest.com - A testing machine to push the client and to deploy patches in it.
    Site code is LAB
    I ran the setup using the following command.
    I have shared the ccmsetup in a share so the command is as follows:
    \\sccmsvr\Client\ccmsetup.exe /MP:SCCMSVR /Logon SMSSITECODE=LAB FSP=SCCMSVR
    But when i check the task manager the process of ccmsetup.exe but it does not change to CCMEXEC.exe
    I waited for an hour but still the same issue. (This was done in the DC Server.labtest.com)
    Screen shot of the DC  Machine:
    When i do a client push installation in a testing machine (SCCMTEST.labtest.com)  i still the same issue. I pushed the client still the same issue
    In the task manager the process of ccmsetup.exe but it does not change to CCMEXEC.exe.
    Screen shot of the second machine:
    Also checked the control panel. Dint find the config manager options there on both machines.
    Also turned off firewall on all 3 machines  but still the same issue.
    Analysed the event logs on all the servers. The client machines did not have any relevant events.
    The SCCM server had this event. Not sure if this is causing the issue.
    Event id 2344
    On 9/28/2014 3:26:48 PM, component SMS_DISTRIBUTION_MANAGER on computer SCCMSVR.LABTEST.COM reported:  Failed to create virtual directory on the defined share or volume on distribution point "["Display=\\SCCMSVR.LABTEST.COM\"]MSWNET:["SMS_SITE=LAB"]\\SCCMSVR.LABTEST.COM\".
    Possible cause: Distribution Manager requires that IIS base components be installed on the local Configuration Manager Site Server in order to create the virtual directory.  Distribution Manager also requires that IIS Web Services be installed on the Distribution
    Point Server that needs to support Background Intelligent Transfer Service (BITS).
    Solution: Verify that IIS base components are installed on the local Configuration Manager Site Server, and IIS Web Services are installed on the Distribution Point Server.
    Can any one please help.
    Gautam.75801

    Hi Kashif,
    Thank you for your valuable help. As you mentioned the IIS 6 WMI compatibility Feature was not installed. Once i installed and rebooted the SCCM server and pushed
     both the agents manually and by Pushing it via console and it succeed. How ever i got some errors on both the systems The trace log tool during the installation but it succeed.
    What i would like to know is that is it common to get errors like the below while pushing a agent automatically or manually ?
    1. MSI: Action 1:25:44: CcmRegisterComponentsRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterComponents.
    (Got this multiple times)
    2. MSI: Warning 25702. Failed to uninstall PrepDrvr.Sys for Software Metering Agent.
    3. Failed to load mdmregistration.dll. Continue deployment.
    4. Failed to load mdmregistration.dll with error 0x8007007e
    5. File 'C:\Windows\ccmsetup\WindowsFirewallConfigurationProvider.msi' does not exist. Discovery failed.
    6. File 'C:\Windows\system32\msrdc.dll' does not exist. Discovery failed.
    7. Enumerated all 1 local DP locations but none of them is good. Fallback to MP.
    8. Failed to check url http://SCCMSVR.LABTEST.COM/SMS_DP_SMSPKG$/LAB00002. Error 0x80004005
    9. Failed to correctly receive a WEBDAV HTTP request.. (StatusCode at WinHttpQueryHeaders: 401)
    10. As per the screen shot.
    Gautam.75801

  • WMI issues in VMware based Machine Windows 2008 R2 Servers affecting SCCM Clients

    Dear
    Brothers,<o:p></o:p>
    I came to
    an observation particularly in dealing with Windows 2008R2 Servers Vmware Based
    Virtual Machines with SCCM Clients.<o:p></o:p>
    Observation:<o:p></o:p>
    1. Windows
    2008R2 Virtual Machine with Vmware Tools installed (Also depending in the
    entries of WMI, I supposed). <o:p></o:p>
    When the SCCM Server Pushes the client on this Servers, I found out that the SCCM Client
    seems to be installed perfectly but when I tried to perform a remote WMI Query
    and the response is displayed below (The RPC Server is unavailable).<o:p></o:p>
    Now, I know that this kind of issues is something to do about DCOM Configuration
    for Remote Access right?
    Well, sad to say the settings has been checked, trippled checked actually to make sure it is correct with the correct permissions required and proven correct up to the last settings.
    I even compare the settings to those in some Windows Servers with Working WMI Remote Access.
    =========
    What I have observed is that when we make a VMware Systems and install the
    VMware Tools (see picture below) first before installing the
    SCCM Client and the issue regarding WMI Remote access issues happens (The RPC Server is unavailable).
    I proved it by creating a new VM Machine, then conduct installation in this order
    SCCM Client first and then the
    VMware Tools by this way so far the WMI Remote access works perfectly.
    Now the Question:
    Since we have atleast 70 VM Servers in production with this issue, and I proven that the VMware Tools is something to do with this issue, somehow now I need to resolved this in a logical manner.
    For some of us who can guide me to resolved the issue without uninstalling the VMware Tools and fixing the WMI settings and let the SCCM Client work.
    Regards,

    We also have this issue. Nearly all of our terminal servers. I have to run a script to fix the issue and then reboot. It works, but only for a few days and then it starts all over again...
    ::to fix "not found" wmi error
    ::to fix .net calls to wmi repository
    ::to fix "initialization failure" error
    net stop winmgmt
    c:
    cd c:\windows\system32\wbem
    rd /S /Q repository
    regsvr32 /s %systemroot%\system32\scecli.dll
    regsvr32 /s %systemroot%\system32\userenv.dll
    mofcomp cimwin32.mof
    mofcomp cimwin32.mfl
    mofcomp rsop.mof
    mofcomp rsop.mfl
    for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
    for /f %%s in ('dir /b *.mof') do mofcomp %%s
    for /f %%s in ('dir /b *.mfl') do mofcomp %%s
    mofcomp exwmi.mof
    mofcomp -n:root\cimv2\applications\exchange wbemcons.mof
    mofcomp -n:root\cimv2\applications\exchange smtpcons.mof
    mofcomp exmgmt.mof
    For the Update on this case Microsoft didn't find out direct connection of WMI issue to any contributors, however the clients
    from Microsoft and and 3rd party application such as VMware is highly dependent on WMI for its total function.
    Things that we have learned:
    1. Your script is the primary solution as recommended as well by Microsoft, but this is to restore the WMI to its healthy State.
    Is the error gone?
    no definitely not.
       Note: The WMIDiagnostic tool does not help to isolate at all, not even Microsoft is validating the credibility of its generated Logs from this tool.
    2. You need to apply the Hotfixes recommended by Microsoft to eliminate the WMI repository to increase its capacity which contributes to the Service to stall. Deliver the Patches via SCCM or any means of your patch deployment.
    3. Don't forget to reboot the Affected Server every Hotfix installation, this seems fix the issue. For 3 months now the usual system who got the WMI issue most of the time is no longer encountering the WMI errors. So far this is the solution, what causes
    the issue? according to Microsoft the cause is the absence of the patches.

  • SCCM Client Installation - Options for "Retry" Setting

    Hey Guys - 
    I've got a fairly straightforward question for you.  When the SCCM Client is installed / deployed to a system, successfully downloads locally, but fails, it retries installation by default every 30 minutes.  When creating an Orchestrator runbook
    for Client Health, I'm needing ccmsetup to try only once.
    So basically, I'm trying to find out how to make ccmsetup.exe not retry installation and simply fail.  There is a "Retry" command line switch for ccmsetup (/retry:<Minutes>) where
    minutes may be specified, however, this does not pertain to the actual installation, but the initial download of the setup files.  It does not have an affect on the client installation, itself.
    Yes, a simple script could be created which could kill the process after X, but prefer a native (or at least better) solution.
    Any ideas?  Thanks!
    Ben K.

    Hey - Thanks for the reply...
    I totally understand what you are saying - but - the only reason I thought I'd ask is because it's being used in an Orchestrator Runbook as mentioned and processes which run after it won't start until it completes.  When it loops, it never completes.
    Basically, yes - I understand what you are saying and have done it 100 times, but in this case was wondering if there was a more "supported" method by chance.
    Thanks - 
    Ben K.

  • SCCM Client Push installation comms/ports

    Hi all,
    I've done a bit of reading of articles/resources and I'm not quite clear on communication requirements. I read that ICMP ping is required in addition to various TCP ports for client push installation. Our setup is a hub and spoke design with firewalls which
    we don't administer between premises (convenient how 'site' is a key word in SCCM grrr) :)
    I thought we would be able to have Distribution Points/Management Points on remote premises and have the clients on those premises do all necessary communication with the local server in their same subnet in order to deploy the SCCM client and report status.
    Do I require ping etc through to the main server before it will use the local Distribution Point to deploy and report via the local Management Point?
    We have a few clients manually installed at a couple of remote premises which are reporting but can't push the client and we have many clients at our central premises which have had client push installation and reported back successfully - presumably because
    they are in the same subnet with no firewalls between.
    I also have a couple of manually installed clients at remote premises which are not reporting client activity but I'll look into that further once the main client push feature is working.
    Thanks for any clarification, I'm building my SCCM knowledge!
    R

    Hi Gerry,
    Thanks for your response and the resources on your blog.
    I have looked at the link but I'm still not clear on instances (if any) where direct communication is required between the client and the primary site server.
    Should clients be expected to be able to communicate only with their local distribution point/management point which is in the same subnet if they are firewalled from the primary site server as I have? How does SCCM know to have a remote distribution point
    do the communication to a client that is local to it without knowing the IP address? My servers have exceptions setup between them but the clients are fairly restricted to their own premises.
    My boundaries are configured per AD Site but unless SCCM checks DNS for IP address would it be able to determine the AD Site to have the nearest DP/MP handle all the client interaction?
    My query about ICMP was based on this link https://technet.microsoft.com/en-us/library/gg682180.aspx which says:
    "In addition to the ports listed in the following table, client push installation also uses Internet Control Message Protocol (ICMP) echo request messages from the site server to the client computer to confirm whether the client computer is available on
    the network."
    Edit: I see Jason has partly answered my question above - I spent too long typing this post :)
    Thanks

  • Why the SCCM client always corrupts the WMI repository?

    Hi All,
    I have a Configuration Manager 2012 R2 CU2 installation with hundred of client/servers.
    From the initial deploy of the SCCM client, we seen that many machines had a Windows slow logon process.
    We searched online for a fix and many people had this problem, suggesting to enable a registry key called
    HKLM\Software\Microsoft\CCM\Ccmeval\NotifyOnly.
    From that date, we fixed the slow logon process problem, but still have problems with operating system's updates installed with SCCM.
    In the most cases, when SCCM install updates, it corrupt the WMI database and at the OS reboot, the updates are rolled back.
    On the same machines, if we install updates from Windows Updates, we have no problems.
    Also, with SCCM installation, we see a lot of "DCOM" or "PerfLib" errors.
    Usually, the remote management of a client with SCCM doesn't works because the WMI repository is corrupted, so each time we need to do uninstall the SCCM client and do this:
    1. Disable and stop the WMI service.
         sc config winmgmt start= disabled
         net stop winmgmt
    2. Run the following commands.
         Winmgmt /salvagerepository %windir%\System32\wbem      (I noticed that you have run this command, but I would suggest that you try it again)
         Winmgmt /resetrepository %windir%\System32\wbem
    4. Re-enable the WMI service and then reboot the server to see how it goes.
         sc config winmgmt start= auto
    This is very frustrating.
    Why the SCCM client create all these problems and how to fix this?
    Thanks for your support.

    I think that my case is not isolate.
    There are a lot of posts like this:
    http://www.windows-noob.com/forums/index.php?/topic/8989-wmi-corruption-sccm-2012-win7-sp1/
    http://trevorsullivan.net/2012/11/21/configmgr-2012-ccmeval-exe-causing-client-corruption/
    The strange thing is that the WMI corruptions only happens on machine where the SCCM client is installed, even if the machines is without any additional software (fresh windows installation).
    In the same time, I need to fix a ProfSvc bug (KB2617858) because the PC become unusable.
    Also, why it starts a WMI rebuild if I deploy the client with the "NotifyOnly" option (the registry key is fine)?
    So, basically, on a fresh windows machine, as it joins to the domain:
    1) the SCCM client install itselfs
    2) it starts to install several windows updates
    3) at the first restart, it try to rebuild the WMI and the ProfSvc bug appears
    May be that the problem is not the SCCM client itself, but a windows update deployed via SCCM client?

  • Very slow BITS download on SCCM client

      I have a problem with one Windows 2012 server and SCCM client BITS downloads. Jobs created by SCCM client and under SYSTEm account are extremely slow, some 40-60Kbit/sec only. Link itself between client and SCCM 2007 server is 1..1.5Mbit/sec.
      After a couple days I have exchausted my ideas. BITS GP policies are in place, minimum at workhours is 100kbit/sec but download is always 40-60Kbit/sec. Is it workhours or not. 17Mb file I can download over http manually in seconds. It also downloads
    with seconds when I created schedule task under system account where there was row
    start-bitstransfer -source http://server/test.cab -destination c:\folder\test.cab
    I tried changing permissions on SCCM side, give anonymous user rights to download, put NTAuthenticationProviders to "NTLM" but without any changes on download speed. To download this 17Mb file with SCCM client takes hours. Of course, if I switch
    to CIFS/SMB then it also gets files within seconds but I really don't want to do that.
     Any ideas why BITS jobs created by SCCM client are so slow? How can I tell to it that link is quite good and you can download faster.

    Started yesterday one job and at morning its status was TRANSFERRED.
    18MB and 12h download time
    GUID: {ADD1B985-5FCF-4461-BE8C-196561C283F4} DISPLAY: 'CCMDTS Job'
    TYPE: DOWNLOAD STATE: TRANSFERRED OWNER: NT AUTHORITY\SYSTEM
    PRIORITY: LOW FILES: 1 / 1 BYTES: 18128896 / 18128896
    CREATION TIME: 23.01.2014 18:12:35 MODIFICATION TIME: 24.01.2014 5:31:15
    COMPLETION TIME: 24.01.2014 5:31:15 ACL FLAGS:
    NOTIFY INTERFACE: UNREGISTERED NOTIFICATION FLAGS: 11
    RETRY DELAY: 60 NO PROGRESS TIMEOUT: 2419200 ERROR COUNT: 0
    PROXY USAGE: NO_PROXY PROXY LIST: NULL PROXY BYPASS LIST: NULL
    DESCRIPTION:
    JOB FILES:
            18128896 / 18128896 WORKING
    http://server:80/SMS_DP_SMSPKGE$/PRI0003A/TortoiseSVN-1.6.16.21511-x64-sv
    n-1.6.17.msi -> C:\Windows\SysWOW64\CCM\Cache\PRI0003A.4.System\TortoiseSVN-1.6.16.21511-x64-svn-1.6.17.msi
    NOTIFICATION COMMAND LINE: none
    owner MIC integrity level: SYSTEM
    owner elevated ?           true
    This job is read-only to the current CMD window because the job's mandatory
    integrity level of SYSTEM is higher than the window's level of HIGH.
    Peercaching flags
             Enable download from peers      :false
             Enable serving to peers         :false
    CUSTOM HEADERS: NULL

  • 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

  • Sccm client v4 wont install and install client v5 - SCCM 2012 R2

    Hi, I am coming to the end of a SCCM 2012 R2 client deployment. I have come across 2 machines (so far)that have the SCCM 2007 (v4) client installed, and although the task is set to uninstall from the server the v5 client will not installed. iI have been
    using this an as template:
    http://eskonr.com/2010/11/sccm-client-installation-troubleshooting-steps-check-list/
    I have ran the install seperatelty from the server (boxed ticked - Uninstall existing Config Manager client) - No Install
    The ccmsetup folder is created - c$\Windows\ccmsetup, but only has 3 files, no logs folder
    Other machines on site has the v5 client
    Checked ping from client to server and vice versa (no firewall enabled)
    Boundaries/Schema/DNS - ok
    Checked all local event logs.
    i know you can run the local uninstall command, but as the network is vast i would like to fix to come from the server, rather than having to do this on the client.
    Any tips would be great going forward.
    SCCM 2012 R2 - Windows 7 Enterprise SP1

    Hi,
    I ensured the account used for the install was in the local admins group.
    From the ccm.log on the server, i got these erros, been googling but nothing yet:
    ---> ERROR: Unable to start service "ccmsetup" on machine "LCD12121", error = 1075.    SMS_CLIENT_CONFIG_MANAGER    22/10/2014 12:01:43    1460 (0x05B4)
    ---> Failed to install CCM Client Bootstrap component on client (1075)    SMS_CLIENT_CONFIG_MANAGER    22/10/2014 12:01:43    1460 (0x05B4)
    Execute query exec [sp_CP_SetLastErrorCode] 2097153910, 1075    SMS_CLIENT_CONFIG_MANAGER    22/10/2014 12:01:43    1460 (0x05B4)
    Also, is there a way to run a report on which machines dont have the sccm client/install issues?
    Thanks

  • PKI SCCM Client Certificate Template not viewable by Windows 7 and Server 2008 workgroup machines.

    Hello everyone,
    I’m having issues with workgroup computers, not domain systems when I request a certificate.
    It’s extremely weird. It has something to do with Windows 7 and Windows 2008 machines. In 2003 server I can request a certificate manually with certutil and it see the certificate template. I copy over the exact command
    on windows 7 and it can’t see the certificate template.
    I have the following configuration:
    CA Enterprise
    I have created the SCCM Client Certificate
    I have created the SCCM Web Server Certificate
    I have created the SCCM Distribution Point Certificate
    GPO is configured
    SCCM 2012 R2 CU2 configured to do HTTP and HTTPS
    Installed SCCM Client Certificate
    Installed SCCM Web Server Certificate
    Installed Distribution Point Certificate
    Deployed to a domain computer good on PKI
    Workgroup Computers:
    I’m having issues with deploying certificates
    Windows 7 –
    (ERROR) not successful
    Windows Server 2008 R2 –
    (ERROR) not successful
    Windows Server 2003 - successful
    Windows XP – successful
    How I’m getting the certs for the clients is by utilizing the following scripts from this URL.
    http://www.ithierarchy.com/ITH/node/48
    I did find a couple of errors in the code, but if it’s working on my Server 2003, then it should work on the others. Windows 7 and Windows 2008 R2 seem to have the same issue. The error I’m getting is the following:
    Command line requesting the cert ---- CertReq –new –f testcomputer.home.pvt.inf c:\client\testcomputer.home.pvt.req
    Error --- Template not found.
    SCCMClientCertificate (this is my template)

    Just to give an update on what’s happening with this. I found out this format is unsupported by MS with Windows Vista and newer OS’s.
    Instead you must utilize two other additional roles on the CA to have this work. The caviate is, I’m down to the testing and it’s not working as in the document. I have MS Support
    working with me to resolve this issue since it was written by MSFT.
    http://blogs.technet.com/b/askds/archive/2010/05/25/enabling-cep-and-ces-for-enrolling-non-domain-joined-computers-for-certificates.aspx
    and use this doc for similar workgroup computers for rolling out certs. This was written for RT devices, however, it should work once I get to that point.
    http://blogs.technet.com/b/pki/archive/2012/12/11/certificate-for-winrt-devices-and-non-domain-member-devices.aspx

Maybe you are looking for