Trouble with SCCM Client Push

I am having issues with pushing the SCCM client. I am able to push the client just fine as it installs OK but it will not assign the site code. When I try to manually enter the site code I get the "Failed to Update Site Assignment" error. However,
when I log off of my domain admin account and log on as the local administrator I can manually enter the site code and it accepts it. My domain account is added as a local administrator..
The old Network Admin who setup most of SCCM in not with us anymore so I am in charge of figuring out where he left off at and getting everything working. From what I can put together we have extended AD and the System Management folder is populated. I have
ran a query in AD to ensure we do not have any over lapping boundaries. As far as I know we installed SCCM 2012 fresh and did not upgrade from 2007. I have checked our GPO and have not found any that are trying to push the site code.
I have copy and pasted a couple logs below that may help troubleshoot. I have googled for days now how to fix the issues I see in the logs but haven't found anything. Please Help!!
LocationServices.log:
<![LOG[The MP name retrieved is 'E091SCCM.campbell.ketsds.net' with version '7804' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>']LOG]!><time="14:34:36.365+300"
date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsadcache.cpp:334">
<![LOG[MP 'E091SCCM.campbell.ketsds.net' is compatible]LOG]!><time="14:34:36.365+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsadcache.cpp:339">
<![LOG[Lookup Management Points from AD:]LOG]!><time="14:34:36.365+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsutils.h:205">
<![LOG[Name: 'EDKDECCMP1.KETS.KETSDS.NET' HTTPS: 'N' ForestTrust: 'N']LOG]!><time="14:34:36.365+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsutils.h:211">
<![LOG[Name: 'E091SCCM.campbell.ketsds.net' HTTPS: 'N' ForestTrust: 'N']LOG]!><time="14:34:36.366+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080"
file="lsutils.h:211">
<![LOG[Retrieved lookup MP(s) from AD]LOG]!><time="14:34:36.366+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsad.cpp:2136">
<![LOG[Current AD forest name is ketsds.net, domain name is campbell.ketsds.net]LOG]!><time="14:34:36.376+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080"
file="lsad.cpp:818">
<![LOG[Domain joined client is in Intranet]LOG]!><time="14:34:36.376+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsad.cpp:896">
<![LOG[Site and assignment site code match. Verifying site.]LOG]!><time="14:34:36.383+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsad.cpp:4001">
<![LOG[LSIsSiteCompatible : Verifying Site Compatibility for <PRI>]LOG]!><time="14:34:36.383+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080"
file="lsad.cpp:5061">
<![LOG[Attempting to retrieve lookup MP(s) from AD]LOG]!><time="14:34:36.383+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsad.cpp:2110">
<![LOG[Current AD forest name is ketsds.net, domain name is campbell.ketsds.net]LOG]!><time="14:34:36.385+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080"
file="lsad.cpp:818">
<![LOG[Domain joined client is in Intranet]LOG]!><time="14:34:36.385+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsad.cpp:896">
<![LOG[Lookup Management Points from AD:]LOG]!><time="14:34:36.385+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsutils.h:205">
<![LOG[Name: 'EDKDECCMP1.KETS.KETSDS.NET' HTTPS: 'N' ForestTrust: 'N']LOG]!><time="14:34:36.385+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsutils.h:211">
<![LOG[Name: 'E091SCCM.campbell.ketsds.net' HTTPS: 'N' ForestTrust: 'N']LOG]!><time="14:34:36.385+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080"
file="lsutils.h:211">
<![LOG[Retrieved lookup MP(s) from AD]LOG]!><time="14:34:36.385+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsad.cpp:2136">
<![LOG[Current AD forest name is ketsds.net, domain name is campbell.ketsds.net]LOG]!><time="14:34:36.391+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080"
file="lsad.cpp:818">
<![LOG[Domain joined client is in Intranet]LOG]!><time="14:34:36.391+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsad.cpp:896">
<![LOG[LSGetSiteVersionFromAD : Successfully retrieved version '4.00.6487.0000' for site 'PRI']LOG]!><time="14:34:36.398+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080"
file="lsad.cpp:4960">
<![LOG[LSIsSiteVersionCompatible : Site Version '4.00.6487.0000' is not compatible.]LOG]!><time="14:34:36.399+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080"
file="lsad.cpp:5023">
<![LOG[LSIsSiteCompatible : Site <PRI> Version '4.00.6487.0000' is not compatible.]LOG]!><time="14:34:36.399+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080"
file="lsad.cpp:5126">
<![LOG[LSVerifySiteAssignment : Client cannot be assigned to site <PRI>.]LOG]!><time="14:34:36.399+300" date="01-15-2014" component="LocationServices" context="" type="3" thread="8080"
file="lsad.cpp:5160">
<![LOG[A Fallback Status Point has not been specified.  Message with STATEID='607' will not be sent.]LOG]!><time="14:34:36.399+300" date="01-15-2014" component="LocationServices" context="" type="1"
thread="8080" file="fspclientdeployassign.cpp:55">
ClientLocation.log
<![LOG[Getting Assigned Site]LOG]!><time="14:13:39.330+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="7616" file="smsclientclass.cpp:989">
<![LOG[Assigning client to site 'PRI']LOG]!><time="14:13:41.940+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="7616" file="smsclientclass.cpp:501">
<![LOG[Unable to verify sitecode 'PRI'. Cannot continue site assignment.]LOG]!><time="14:13:42.417+300" date="01-15-2014" component="ClientLocation" context="" type="3" thread="7616" file="smsclientclass.cpp:562">
<![LOG[Assigning client to site 'PRI']LOG]!><time="14:13:47.468+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="7616" file="smsclientclass.cpp:501">
<![LOG[Unable to verify sitecode 'PRI'. Cannot continue site assignment.]LOG]!><time="14:13:47.531+300" date="01-15-2014" component="ClientLocation" context="" type="3" thread="7616" file="smsclientclass.cpp:562">
<![LOG[Getting Assigned Site]LOG]!><time="14:14:34.803+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="3332" file="smsclientclass.cpp:989">
<![LOG[Getting Assigned Site]LOG]!><time="14:14:37.517+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="2520" file="smsclientclass.cpp:989">
<![LOG[Assigning client to site 'PRI']LOG]!><time="14:14:45.167+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="2520" file="smsclientclass.cpp:501">
<![LOG[Unable to verify sitecode 'PRI'. Cannot continue site assignment.]LOG]!><time="14:14:45.424+300" date="01-15-2014" component="ClientLocation" context="" type="3" thread="2520" file="smsclientclass.cpp:562">
<![LOG[Assigning client to site 'PRI']LOG]!><time="14:15:35.577+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="6888" file="smsclientclass.cpp:501">
<![LOG[Unable to verify sitecode 'PRI'. Cannot continue site assignment.]LOG]!><time="14:15:35.627+300" date="01-15-2014" component="ClientLocation" context="" type="3" thread="6888" file="smsclientclass.cpp:562">
<![LOG[Assigning client to site 'PRI']LOG]!><time="14:25:36.861+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="8276" file="smsclientclass.cpp:501">
<![LOG[Unable to verify sitecode 'PRI'. Cannot continue site assignment.]LOG]!><time="14:25:36.930+300" date="01-15-2014" component="ClientLocation" context="" type="3" thread="8276" file="smsclientclass.cpp:562">
<![LOG[Getting Assigned Site]LOG]!><time="14:33:00.123+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="6592" file="smsclientclass.cpp:989">
<![LOG[Getting Assigned Site]LOG]!><time="14:34:31.483+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="8800" file="smsclientclass.cpp:989">
<![LOG[Getting Assigned Site]LOG]!><time="14:34:33.521+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="8080" file="smsclientclass.cpp:989">
<![LOG[Assigning client to site 'PRI']LOG]!><time="14:34:36.145+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="8080" file="smsclientclass.cpp:501">
<![LOG[Unable to verify sitecode 'PRI'. Cannot continue site assignment.]LOG]!><time="14:34:36.399+300" date="01-15-2014" component="ClientLocation" context="" type="3" thread="8080" file="smsclientclass.cpp:562">

Is this 2012 R2?
When I upgraded from SP1 to R2 I had a very similar message. This thread helped me out:
http://www.windows-noob.com/forums/index.php?/topic/7217-client-version-50078041000-is-not-compatible-with-the-site-111-version-50077110000/
Specifically this bit:
DerGali, on 23 Jan 2013 - 08:41 AM, said:
I had the same Problem with the client version thing. I had to do following Steps to fix it:
1. If you made an Extension in the Active Directory for your SCCM Installation just open ADSIedit go To CN System=>CN System Management remove the Object CN=SMS-MP..... (don't worry it will be recreated by
the sccm server hourly. if not check rights on the object (the sccm computer object need to have rights to write into the System Management Object)
2. Just wait until next morning! The Server should updated all Version Numbers by itself!
MCP, MCDST, MCTS x 6, MCITP x 3
Please don't forget to mark this post as an answer if it is the solution to your problem!
If you like trance music, please subscribe to my podcast
Trancendance Podcast
View my MCP Certifications
Follow me on Twitter

Similar Messages

  • SCCM Client Push Installtion

    Hello I am trying to test SCCM client push installation. I used active directory system group discovery as discovery method. All clients(windows 2008 r2) that were on the same subnet reported fine on collection and installed client through client push
    installation. However two clients that are on two different subnets are not reporting nor clients are install through push installation. I have boundaries setup correctly for these two non reporting client. I have all components of SCCM running on same server.
    What firewall ports are needed for active directory system group discovery and client push installation. Between SCCM and SCCM Client ?ad

    In order to successfully use client push to install the Configuration Manager client, you must add the following as exceptions to the Windows Firewall:
    File and Printer Sharing
    Windows Management Instrumentation (WMI)
    TCP Port 135
    TCP Port 445
    Hossam Wael Elmosallamy (IT Support Engineer-ECC Solutions) MCSE - CCNA [email protected] Mobile:(011)-49464671 www.eccsolutions.net "Experience Reliability&quot

  • Issue with sccm client installation

    hi,
    iam facing issue with sccm client 2007 installation on secondary site.please find the logs below,

    Refer for the above error : http://www.myitforum.com/forums/MSI-SMS-Advanced-Client-does-not-support-peruser-installations-m183336.aspx
    Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
    the thread.

  • 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

  • SCCM Client Push Installation Wizard does not install the client. CCMSetup folder - not created

    Hello,
    I have tried running the Client Push wizard for a single computer or a pilot collection of 8 computers, the result is always
    the same - no SCCM client is installed on any computer.
    The computers are running 32-bit Windows XP SP2.
    The Windows firewall is disabled.
    The client push installation account is setup and have domain admin and local admin privileges. Client Push automatic method
    is not enabled.
    The domain is AD WIndows 2000.
    The SCCM server is running Windows 2003 R2 SP2 64bit Standard.
    The AD schema has been extended.
    MP, and SLP are installed and published. (MP is published in DNS as well.)
    FSP is installed.
    MP, SLP and FSP are running on the same server.
    SQL 2005 server is running locally.
    System management container is created and all rights and permissions delegated.
    With the Push installation account I can access C$ share on the client computer from the SCCM server.
    RPC, Remote registry, WMI services are running on the client machines.
    All prerequisites are installed from the client folder on SCCM server- latest BITS 2.5, Windows installer 3.1 and MSXML6.
    All computers are in the same IP subnet which is listed in the boundaries.
    Yet, the client is not being installed.
    No CCMSetup folder is created on the client machines in Windows\System32 folder, so it is really difficult to troubleshoot
    what the is the issue. I do not see anything helpful in the ccm.log on the server.
    I have tried running the CCMSetup.exe manually on one of the workstations and that was successful and reported back to the
    SCCM server / console.
    What else I should check / try? I really want to push agents via the wizard.
    Thank you,
    Peter

    Hi Wally,
    I have changed 2 things:
    1. Enabed automatic push installation (so I am not usign the wizard any more)
    2. Changed the IP subnet to IP ranges in the site boundairies.
    After runnignt the discovery, I was able to see some activities in the ccm.log. A ccmsetup folder is now created but the agent is still not instaleld. Here is the ccmsetup.log
    ==================================
    <![LOG[==========[ ccmsetup started in process 3140 ]==========]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:8853">
    <![LOG[Version: 4.0.5931.0000]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:1913">
    <![LOG[Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required.]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:3937">
    <![LOG[Command line: "C:\WINDOWS\system32\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:3946">
    <![LOG[CCMHTTPPORT:    80]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7851">
    <![LOG[CCMHTTPSPORT:    443]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7866">
    <![LOG[CCMHTTPSSTATE:    0]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7884">
    <![LOG[CCMHTTPSCERTNAME:    ]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7912">
    <![LOG[FSP:    HFXDBSSOM.CORP.EASTLINK.CA]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7927">
    <![LOG[CCMFIRSTCERT:    0]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7969">
    <![LOG[Config file:      C:\WINDOWS\system32\ccmsetup\MobileClient.tcf]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4341">
    <![LOG[Retry time:       10 minute(s)]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4342">
    <![LOG[MSI log file:     ]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4343">
    <![LOG[MSI properties:    INSTALL="ALL" SMSSITECODE="PHX" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" FSP="HFXDBSSOM.CORP.EASTLINK.CA" CCMFIRSTCERT="0"]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4344">
    <![LOG[Source List:]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4352">
    <![LOG[                  \\HFXDBSSOM.corp.eastlink.ca\SMSClient]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4359">
    <![LOG[                  \\HFXDBSSOM\SMSClient]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4368">
    <![LOG[MPs:]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4371">
    <![LOG[                  HFXDBSSOM.corp.eastlink.ca]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4386">
    <![LOG[Updated security on object C:\WINDOWS\system32\ccmsetup\.]LOG]!><time="09:45:07.076+240" date="12-06-2007" component="ccmsetup" context="" type="0" thread="3108" file="ccmsetup.cpp:8692">
    <![LOG[Sending Fallback Status Point message, STATEID='100'.]LOG]!><time="09:45:07.076+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:9169">
    <![LOG[State message with TopicType 800 and TopicId {A450B407-619B-4777-B77E-C3352753B58A} has been sent to the FSP]LOG]!><time="09:45:07.326+240" date="12-06-2007" component="FSPStateMessage" context="" type="1" thread="3108" file="fsputillib.cpp:730">
    <![LOG[Running as user "SYSTEM"]LOG]!><time="09:45:07.326+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:2534">
    <![LOG[Detected 24292 MB free disk space on system drive.]LOG]!><time="09:45:07.326+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:465">
    <![LOG[DetectWindowsEmbeddedFBWF() Detecting OS Version]LOG]!><time="09:45:07.342+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:511">
    <![LOG[Client OS is not Windows XP Embedded]LOG]!><time="09:45:07.342+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:548">
    <![LOG[Successfully ran BITS check.]LOG]!><time="09:45:08.745+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:6948">
    <![LOG[Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 401)]LOG]!><time="09:45:08.745+240" date="12-06-2007" component="ccmsetup" context="" type="3" thread="2600" file="ccmsetup.cpp:5813">
    <![LOG[Sending Fallback Status Point message, STATEID='308'.]LOG]!><time="09:45:08.760+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:9169">
    <![LOG[State message with TopicType 800 and TopicId {3BFABF82-FB74-43FB-8A4A-6DFDEAEAC25C} has been sent to the FSP]LOG]!><time="09:45:08.776+240" date="12-06-2007" component="FSPStateMessage" context="" type="1" thread="2600" file="fsputillib.cpp:730">
    ==============================================================
    There are two red errors I am concerned about:
    "Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 401)
    and
    "Failed to download 'WindwosXP-KB923845-x86-ENU.exe' from http://HFXDBSSOM.corp.eastlink.ca/CCM_Client/i386/BITS25 with error code 0x80004005).
    What should I do to resolve these errors?
    Thanks,
    Peter

  • HTTP 403.13 during SCCM client push

    We have multiple forest connected to a shared SCCM 2012 R2 site.
    The site is in SSL only mode
    With one forest we have problems pushing clients from SCCM.
    Install works fine but soon as the client connects to the MP we get HTTP 403.13 failures.
    RootCA certs have been added to SCCM
    RootCA certs of the remote forest are added both sided to trusted root CA
    CRL can be checked both sides using IE.
    Still IIS logs on the MP show
    2014-08-07 08:14:57 managementpointip CCM_POST /ccm_system_windowsauth/request - 443 - hostip ccmhttp - 403 13 2148081683 34
    ccm messaging logs show
    Post to https://MPFQDN/ccm_system_windowsauth/request failed with 0x87d00231
    The following registry keys have been set to
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL
    ClientauthTrustmode REG_DWORD 2
    sendtrustedissuerlist REG_DWORD 0
    The strange thing is that one forest works and one not. Both are identical configured.
    Firewall ports are open.

    Hi Torsten,
    I have seen that article and yes it is CRL related. The thing is the MP is configured not to check the CRL.
    Now the client push seems to ignore that value. A local install can be configured with /nocrlcheck
    Still it worries me that the CRL can be accessed by the MP using a browser on the MP.
    SSL Certificate bindings:
        IP:port                      : 0.0.0.0:443
        Certificate Hash             : 0317e07bab17b3f16502c1623778c1abeadbfd19
        Application ID               : {4dc3e181-e14b-4a21-b022-59fc669b0914}
        Certificate Store Name       : My
        Verify Client Certificate Revocation : Disabled
        Verify Revocation Using Cached Client Certificate Only : Disabled
        Usage Check                  : Enabled
        Revocation Freshness Time    : 0
        URL Retrieval Timeout        : 0
        Ctl Identifier               : (null)
        Ctl Store Name               : (null)
        DS Mapper Usage              : Disabled
        Negotiate Client Certificate : Disabled
        IP:port                      : 0.0.0.0:8531
        Certificate Hash             : 0317e07bab17b3f16502c1623778c1abeadbfd19
        Application ID               : {4dc3e181-e14b-4a21-b022-59fc669b0914}
        Certificate Store Name       : My
        Verify Client Certificate Revocation : Enabled
        Verify Revocation Using Cached Client Certificate Only : Disabled
        Usage Check                  : Enabled
        Revocation Freshness Time    : 0
        URL Retrieval Timeout        : 0
        Ctl Identifier               : (null)
        Ctl Store Name               : (null)
        DS Mapper Usage              : Disabled
        Negotiate Client Certificate : Disabled

  • 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

  • Problems with SCCM client instalaltion after upgrade to R2 version

    Hi,
    Few days ago, I have upgraded SCCM 2012 Sp1+CU3 to SCCM 2012 R2. I see now manyy issies in component manager with SMS_EXECUTIVE and SMS_MP_CONTROL_MANAGER. Reaon of this is automatically process of installation SCCM client in latest version. This same
    issue apppear when I trying install SCCM manually. In both cases I have got in ccmsetup.log this:
    CcmCreateEmbeddedClientState. Creates the client state file, which is needed for write filter handing.
    CcmCreateEmbeddedClientStateRollback. Rolls back the action of creating the client state file.
    RegisterExtensionInfo. Registering extension servers
    WriteRegistryValues. Writing system registry values
    Could not write value SMSCFGRC to key \SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\Cpls.   Verify that you have sufficient access to that key, or contact your support personnel.
    Rollback. Rolling back action:
    Computer where I want install SCCM client, my adm account, Primary site server or NT SERVICE\TrustedInstaller has full right to this registry key but log file record is always this same. 
    AV and Firewall turned off. 
    What next?

    Hi Torsten,
    I have checked client.msi.log and there is this same:
    Note: 1: 1401 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\Cpls 3: 5 
    Product: Configuration Manager Client -- Error 1406. Could not write value SMSCFGRC to key \SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\Cpls.  System error .  Verify that you have sufficient access to that key, or
    contact your support personnel.
    Error 1406. Could not write value SMSCFGRC to key \SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\Cpls.  System error .  Verify that you have sufficient access to that key, or contact your support personnel.
    User policy value 'DisableRollback' is 0
    Machine policy value 'DisableRollback' is 0
    InstallFinalize. Return value 3.

  • Deploy Images with SCCM Client Installed

    Hi everyone.
    there's one thing I have in mind for a while and haven't got a solution for it
    We use SCCM 2012 to build and create our master image with a Task Sequence
    one task before the syspreping is  "prepare configuration manager client", which from my understanding and from technet - resets all the client's unique configuration.
    conclusion - the SCCM Client is installed and "Syspreped" on our base image
    in that case, assuming we still use the same SCCM client version, is there a way to save time during the Deploy task sequence?
    the "Setup windows and ConfigMgr" step is required and it installs the SCCM Client all over again, even though it is already included in our master image.
    thanks
    Tamir Levy

    First, as noted by Daniel, the Setup Windows and ConfigMgr task does much more than simply installing the ConfigMgr agent. This is clearly indicated by the name of the task (before the "and") "Setup Windows".
    The are no true advantages to having the client agent in the image. If you are building your image with ConfigMgr though, it is unavoidable. Yes having it in the image should save time by not having to reinstall the pre-reqs -- most are pretty trivial though
    but you may gain a bit although I can't say I've ever timed it.
    There is no time savings to be had here, the client agent must be either installed or re-installed during the deployment TS, this is unavoidable. You'll need to look elsewhere if this is a required goal.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • SCCM Client Push

    Hi,
    I have run into a strange issue when setting up SCCM 2012 R2.  I configured the system discovery rule to get machines in the database from AD which was fine but it then did a client push to around half the machines.  I checked the Client Push Installation
    properties and this is not enabled so I am a bit confused to how this happened.   If you could point me to any logs that would help me work out what happened it would be greatly appreciated (only thing I can think is someone did the client push
    but no one is owning up to it)
    Thanks

    You might also want to check out the Status Message Query for All audit messages on your site to see if someone did the change. More on this here:
    http://blog.vdx.com/auditing-events-in-configuration-manager-2012/

  • SCCM Client Push Ports

    Dears,
    I need to understand more on SCCM 2012 Client push ports. I am pushing the client from primary site server.
    As per MS, it’s recommended to have SMB open between site server and client systems.
    My client is accepted to open SMB port (one way) between site servers to client. They are not accepting to open SMB between Clients to Site server.
    I need your suggestion to have below network firewall ports are ok to work on client push.
    Site Server -- > Client
    Description
    UDP
    TCP
    Service Message Blok
    445
    RCP Dynamic
    DYNAMIC
    Hypertext Transfer Protocol (HTTP)
    80
    Client -- > Site Server
    Description
    UDP
    TCP
    Hypertext Transfer Protocol (HTTP)
    80
    Or still we need to open SMB between clients to site server, if yes, please provide the justification.
    Regards,
    Kannan.CS
    Regards, kanna

    https://technet.microsoft.com/en-us/library/hh427328.aspx. SMB from client to server is not needed. 
    Torsten Meringer | http://www.mssccmfaq.de

  • Sccm client push installation problem

    in my company 22000 users and install sccm 2012(1 primary site in main dc  and 4 site system server in branch  )
    i enable automatic site-wide client push installation . only sccm client installed in 11000 computers during 7 month and  increment installation it very slowly 2-10 per month 
    how i install  svvm client in another computers automaticly
    please help me

    Yes. You can also manually create boundaries. Each client must fall under a boundary (eg IP Subnet, IP Range, AD site). You need to check that all are covered. Boundaries have to be added to boundary groups which are configured for site assignment.
    http://www.gerryhampsoncm.blogspot.ie/2013/02/sccm-2012-sp1-step-by-step-guide-part-6.html
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • Trouble with OSX client registering in SCCM

    I am having a weird issue with a OSX client failing to register in SCCM.  Our infrastructure is a CAS and three primary sites.  On one of the primary sites (we will call it "Site 3"), I have a DP with the MP role on it to support HTTP
    clients and a separate DP\MP server strictly for HTTPS (OSX) clients.  It works fine and runs well.  On another site ("Site 1"), we have the same setup however when I try to register a test OSX endpoint it is showing weird behavior. 
    The HTTPS MP has a message about a registration response pending for the GUID displayed in the configuration manger client window in System Preferences and the enrollment status reports Enrolled, but it never appears in the SCCM console. Another thing is if
    I click the "connect now" button in the client applet, a new client GUID is generated and another registration response pending shows up in the dmprp.log file.
    The message "Registration response status is: CCM_REGISTRATIONRESPONSE_PENDING" appears in the DMPRP.log for the HTTPS DP\MP for Site 1 but I don't think that is a normal message for enrollment when things are working.  MP_RegistrationManager.log
    shows DDR processing matching the cert name and client GUID.
    A bit of additional info is that we are using third-party SSL certs for the endpoints and are not going through the typical ADCS PKI/SCCM enrollment point process.  The networking group reports no dropped packets on the hardware firewall everything
    is sitting behind but if you have any ideas of ways a firewall could cause this behavior I would love to hear it.

    Hi,
    Please refer to the link below:
    Enrol Mac OS X Clients in Configuration Manager 2012 SP1
    http://www.jamesbannanit.com/2012/10/enrol-mac-os-x-clients-in-configuration-manager-2012-sp1/
    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.

  • Reports for Apple devices with SCCM client - Mac Addresses and IP information.

    Greetings.
    I've been having an interesting problem.
    I am currently running SCCM 2012R2 with PKI and have clients installed on windows, linux (ubuntu mostly) and apple computers successfully.
    I have created custom report proving me with hardware information for windows and linux machines (Serial numbers, manufacturer, Mac Addresses and IP addresses) successfully.
    So far I wasn't able to create any report or even find what table information about Apple computers MAC and IP addresses is stored.
    If i go to Apple computer in SCCM using resource explorer under hardware I can see network devices, so that information is definitely gathered by SCCM in some way.
    Can anyone help me out with this and maybe I am doing this in a wrong way?

    Nice. Only trouble there seems to be multiple entry for same mac address there for same resource id.
    So when I try to get them as substring i get multiple copies of same mac address.
    But looks like this will work as solution to this problem.
    So far I was doing it this way (And i am sure there is clearer way to do it.)
    SUBSTRING((SELECT ',' + CAST(t2.MACAddress0 AS VARCHAR(40))
                FROM (SELECT DISTINCT ResourceID, MACAddress0 FROM  v_GS_NETWORK_ADAPTER) t2
                WHERE t2.ResourceID = ResourceID
                ORDER BY t2.ResourceID, t2.MACAddress0
                FOR XML PATH ('')
            ), 2, 100) [MACAddresses]

  • Trouble with 10g client

    Hey Folks
    Client Side:
    10.2.0.1
    Windows 2k
    Server Side:
    Several HPUX 11.23
    10.2.0.2 or 9.2.0.6.0
    When I try to connect with the 10g client (or sqlplus) to 9i or 10g there are several errors:
    If the login and password is correct:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-02248: invalid option for ALTER SESSION
    If the login and password is incorrect:
    ORA-01017: invalid username/password; logon denied
    I have an other box with the 9i client there it works perfectly.
    Any ideas?
    Regards

    Thx for replay.
    This is the whole output i get
    F:\>sqlplus "system/password@TEST"
    SQL*Plus: Release 10.2.0.1.0 - Production on Fr Jan 26 13:12:24 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    ERROR:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-02248: invalid option for ALTER SESSION
    Regards

Maybe you are looking for