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
Similar Messages
-
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 ?adIn 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" -
Content Transfer between WSUS and SCCM client on port 8530
Dear All
In my environment from last few days we are facing an strange situtaion where huge contents is getting transferred between WSUS server and SCCM client on port 8530.
I check logs on client and found that client are getting contents from their associated DP's but still weekly network utlisation report showing that data in GB's was transferred between SCCM primary server and clients on port 8530.
Kindly suggest what else need to check in this scenario
Regards SureshThe only other possible traffic from WSUS is actual updates if and only if you have been approving updates directly in WSUS which you should not be doing.
Thus, assuming you are not doing what you should not be doing, the only possibility is the update catalog. 150-200MB sounds excessive but that will be based upon what you all have selected for your catalog. There are also a handful of reasons why a full
catalog resync would be initiated instead of just a delta.
Jason | http://blog.configmgrftw.com -
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!
RHi 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 -
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 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.75801Hi 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,
PeterHi 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 -
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)
ThanksYou 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/ -
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 -
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 meYes. 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 -
Firewall Ports directions for Client Push Installation
Hello,
i take offer a running SCCM 2012 R2 Client Management but there is no Client Push implemented.
So i will now use Client Push and we open the Ports 135 and 445 now i have one Question to use RPC Dynamic Ports,
they are only from Server -to-> Client or both direction?
I read a lot of them but nobody wrote about the directions, my problem is that our SCCM 2012 is installed in a management network and the connect to the clients are controlled with a Firewall and now for a change i must known the direction to change it.
The Port description from MS i read often but not very helpful with direction. :)
with best regards
AndréTo add-on to Torsten. It is also possible to restrict your dynamic RPC ports, as explained at articles like these:
http://www.windowsnetworking.com/kbase/WindowsTips/WindowsServer2008/AdminTips/Admin/DefaultDynamicPortRange.html
http://support.microsoft.com/kb/154596
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude
Have you ever successfully done this? I tried once early in CM07 and it didnt' work. Submitted my findings to MS and a reference from the CM docs to the article you posted was removed from the CM docs.
John Marcum | Microsoft MVP - Enterprise Client Management
My blog: System Center Admin | Twitter:
@SCCM_Marcum | Linkedin:
John Marcum -
Client Push Not Working SCCM 2012
I am new to SCCM and have a test rig SCCM 2012 for testing, problem is the client push fails every time and I am at a loss to explain why. I have tried removing and reading the DP, FSP and MP roles (Both these are on the SCCM core server) I have run IIS
reset, removed all AD configured Boundaries and Groups in favor of IP range but I keep getting the same errors. Any advice here would be greatly appreciated... Below is this mornings logs highlighting the failure.
<![LOG[==========[ ccmsetup started in process 5764 ]==========]LOG]!><time="11:31:48.304-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="7628" file="ccmsetup.cpp:9437">
<![LOG[Running on platform X64]LOG]!><time="11:31:48.305-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="7628" file="util.cpp:1837">
<![LOG[Updated security on object C:\Windows\ccmsetup\cache\.]LOG]!><time="11:31:48.305-120" date="01-12-2014" component="ccmsetup" context="" type="0" thread="7628" file="ccmsetup.cpp:9281">
<![LOG[Launch from folder C:\Windows\ccmsetup\]LOG]!><time="11:31:48.306-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="7628" file="ccmsetup.cpp:721">
<![LOG[CcmSetup version: 5.0.7958.1000]LOG]!><time="11:31:48.306-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="7628" file="ccmsetup.cpp:727">
<![LOG[In ServiceMain]LOG]!><time="11:31:48.308-120" date="01-12-2014" component="ccmsetup" context="" type="0" thread="6436" file="ccmsetup.cpp:3365">
<![LOG[Running on 'Microsoft Windows Server 2012 Standard' (6.2.9200). Service Pack (0.0). SuiteMask = 272. Product Type = 18]LOG]!><time="11:31:48.366-120" date="01-12-2014" component="ccmsetup" context="" type="1"
thread="6436" file="util.cpp:1919">
<![LOG[Ccmsetup command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="11:31:48.366-120" date="01-12-2014" component="ccmsetup" context="" type="1"
thread="6436" file="ccmsetup.cpp:3590">
<![LOG[Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required.]LOG]!><time="11:31:48.366-120" date="01-12-2014" component="ccmsetup" context=""
type="1" thread="6436" file="ccmsetup.cpp:3775">
<![LOG[Command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="11:31:48.366-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436"
file="ccmsetup.cpp:3776">
<![LOG[SslState value: 224]LOG]!><time="11:31:48.368-120" date="01-12-2014" component="ccmsetup" context="" type="0" thread="6436" file="ccmsetup.cpp:4425">
<![LOG[CCMHTTPPORT: 80]LOG]!><time="11:31:48.369-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:8617">
<![LOG[CCMHTTPSPORT: 443]LOG]!><time="11:31:48.369-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:8632">
<![LOG[CCMHTTPSSTATE: 224]LOG]!><time="11:31:48.369-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:8650">
<![LOG[CCMHTTPSCERTNAME: ]LOG]!><time="11:31:48.369-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:8668">
<![LOG[FSP: VKYV-HV01]LOG]!><time="11:31:48.369-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:8720">
<![LOG[CCMFIRSTCERT: 1]LOG]!><time="11:31:48.370-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:8778">
<![LOG[Config file: C:\Windows\ccmsetup\MobileClientUnicode.tcf]LOG]!><time="11:31:48.371-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436"
file="ccmsetup.cpp:4539">
<![LOG[Retry time: 10 minute(s)]LOG]!><time="11:31:48.371-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:4540">
<![LOG[MSI log file: C:\Windows\ccmsetup\Logs\client.msi.log]LOG]!><time="11:31:48.371-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:4541">
<![LOG[MSI properties: INSTALL="ALL" SMSSITECODE="VSI" FSP="VKYV-HV01" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1"]LOG]!><time="11:31:48.371-120"
date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:4542">
<![LOG[Source List:]LOG]!><time="11:31:48.371-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:4550">
<![LOG[ \\VKYV-HV01.VKYV.LAN\SMSClient]LOG]!><time="11:31:48.371-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436"
file="ccmsetup.cpp:4557">
<![LOG[ \\VKYV-HV01.VKYV.LAN\SMSClient]LOG]!><time="11:31:48.371-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436"
file="ccmsetup.cpp:4566">
<![LOG[MPs:]LOG]!><time="11:31:48.371-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:4569">
<![LOG[ VKYV-HV01.VKYV.LAN]LOG]!><time="11:31:48.371-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436"
file="ccmsetup.cpp:4584">
<![LOG[No version of the client is currently detected.]LOG]!><time="11:31:48.374-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:2748">
<![LOG[Updated security on object C:\Windows\ccmsetup\.]LOG]!><time="11:31:48.750-120" date="01-12-2014" component="ccmsetup" context="" type="0" thread="6436" file="ccmsetup.cpp:9281">
<![LOG[Sending Fallback Status Point message to 'VKYV-HV01', STATEID='100'.]LOG]!><time="11:31:48.750-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:9756">
<![LOG[Failed to get client version for sending messages to FSP. Error 0x8004100e]LOG]!><time="11:31:48.752-120" date="01-12-2014" component="ccmsetup" context="" type="2" thread="6436" file="ccmsetup.cpp:9838">
<![LOG[Params to send FSP message '5.0.7958.1000 Deployment ']LOG]!><time="11:31:48.752-120" date="01-12-2014" component="ccmsetup" context="" type="0" thread="6436" file="ccmsetup.cpp:9887">
<![LOG[State message with TopicType 800 and TopicId {037AE2A1-3C8B-482A-A180-04392D0312BA} has been sent to the FSP]LOG]!><time="11:31:49.020-120" date="01-12-2014" component="FSPStateMessage" context="" type="1"
thread="6436" file="fsputillib.cpp:752">
<![LOG[Running as user "SYSTEM"]LOG]!><time="11:31:49.058-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:1995">
<![LOG[Detected 44815 MB free disk space on system drive.]LOG]!><time="11:31:49.059-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="util.cpp:628">
<![LOG[Checking Write Filter Status.]LOG]!><time="11:31:49.059-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:2024">
<![LOG[This is not a supported write filter device. We are not in a write filter maintenance mode.]LOG]!><time="11:31:49.059-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436"
file="ccmsetup.cpp:2051">
<![LOG[Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=VSI))']LOG]!><time="11:31:49.179-120" date="01-12-2014" component="ccmsetup" context="" type="0"
thread="6436" file="lsad.cpp:656">
<![LOG[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>308202EF308201D7A0030201020210518E5B64E54890884666F9411DA2CCB3300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3133313032393130343732365A180F32313133313030363130343732365A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A0282010100B999635F3FFE2F0E7DB66B36407C0ED4FB7DC23A8CD42078325E08E7E553EC2AD1D35A5758268CA497A8023B9F056089BA068ADD84ABDDF74E00B1C402308F287387A8FFA3DBCBFDAC81F8A7F32C959B7CCDCBF5FC0D87434A2907C074675CAA4EA6963D2956EAD43957A831B746E4E5D00C66AAC1F2FE5F71D26D54909EEA0883D780EF46111B124C9C77E3F9D767D36972B9420FEFE291A2A377D958A27C1B24F72E3A870498CF44D8C854214C38F1A50C5CBB3924215F037B0256ACD78B5E32FDFD9BF9760329F523777C16234B560C808F201605774B77B54833D0EA918C44106FF72409876A6D1D4FE75EC9F3A349578577B96BAC62E39D102ACBB401230203010001A3373035301D0603551D11041630148212564B59562D485630312E564B59562E4C414E30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B05000382010100B6B5CDA1A6AA6F712365113F0A81829B596081DB9AF07D5F10DEB0103F158460E9C17B3E1A201A81B9890741F7E2BF5B564058FED25FC724DD4AC948BC9462B1B6A7991AFD159C673B01CE019ABE0A0E0DDD9881AAC751427751C22A43754295DF3F4514EE1BDAD5EF06EE1010E294113B4BB00EB2DF555EE790224E40905E5183E77FF0D87D5EBD98A819DAAE265BA4CD81BA444C226B8B04EF4E80E62ECBF5F3DEDFD2F91822919DBDE529DB043FFAF424A84A0F85A8D0A45F4451F9F5DA48DCADE6603BF106128A36C20F2C52AD69A562BA7834497792D819EAD45DF18BFC6AF1AC60111AC34CF0BF48D9B037064BF41E90E910F36AEAB50C1697C18E800D</SiteSigningCert></SecurityConfiguration><RootSiteCode>VSI</RootSiteCode><CCM>
<CommandLine>SMSSITECODE=VSI FSP=VKYV-HV01</CommandLine> </CCM><FSP> <FSPServer>VKYV-HV01.VKYV.LAN</FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSLState" Value="0"
/></Capabilities><Domain Value="VKYV.LAN" /><Forest Value="VKYV.LAN" /></ClientOperationalSettings>']LOG]!><time="11:31:49.228-120" date="01-12-2014" component="ccmsetup" context=""
type="0" thread="6436" file="lsadcache.cpp:236">
<![LOG[Unable to open Registry key Software\Microsoft\CCM. Return Code [80070002]. Client HTTPS state is Unknown.]LOG]!><time="11:31:49.229-120" date="01-12-2014" component="ccmsetup" context="" type="1"
thread="6436" file="ccmutillib.cpp:373">
<![LOG[The MP name retrieved is 'VKYV-HV01.VKYV.LAN' with version '7958' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>']LOG]!><time="11:31:49.229-120"
date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="lsadcache.cpp:334">
<![LOG[MP 'VKYV-HV01.VKYV.LAN' is compatible]LOG]!><time="11:31:49.229-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="lsadcache.cpp:339">
<![LOG[Retrieved 1 MP records from AD for site 'VSI']LOG]!><time="11:31:49.229-120" date="01-12-2014" component="ccmsetup" context="" type="0" thread="6436" file="lsadcache.cpp:287">
<![LOG[Retrived site version '5.00.7958.1000' from AD for site 'VSI']LOG]!><time="11:31:49.231-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="siteinfo.cpp:575">
<![LOG[SiteCode: VSI]LOG]!><time="11:31:49.231-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:2076">
<![LOG[SiteVersion: 5.00.7958.1000]LOG]!><time="11:31:49.231-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:2077">
<![LOG[Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again.]LOG]!><time="11:31:49.231-120" date="01-12-2014" component="ccmsetup" context="" type="1"
thread="6436" file="ccmsetup.cpp:2111">
<![LOG[Only one MP VKYV-HV01.VKYV.LAN is specified. Use it.]LOG]!><time="11:31:49.232-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:10080">
<![LOG[Searching for DP locations from MP(s)...]LOG]!><time="11:31:49.232-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:11018">
<![LOG[Current AD site of machine is Default-First-Site-Name]LOG]!><time="11:31:49.232-120" date="01-12-2014" component="LocationServices" context="" type="1" thread="6436" file="lsad.cpp:770">
<![LOG[Local Machine is joined to an AD domain]LOG]!><time="11:31:49.232-120" date="01-12-2014" component="LocationServices" context="" type="0" thread="6436" file="lsad.cpp:714">
<![LOG[Current AD forest name is VKYV.LAN, domain name is VKYV.LAN]LOG]!><time="11:31:49.235-120" date="01-12-2014" component="LocationServices" context="" type="1" thread="6436" file="lsad.cpp:842">
<![LOG[DhcpGetOriginalSubnetMask entry point is supported.]LOG]!><time="11:31:49.237-120" date="01-12-2014" component="LocationServices" context="" type="0" thread="6436" file="ccmiputil.cpp:117">
<![LOG[Begin checking Alternate Network Configuration]LOG]!><time="11:31:49.237-120" date="01-12-2014" component="LocationServices" context="" type="0" thread="6436" file="ccmiputil.cpp:1095">
<![LOG[Finished checking Alternate Network Configuration]LOG]!><time="11:31:49.239-120" date="01-12-2014" component="LocationServices" context="" type="0" thread="6436" file="ccmiputil.cpp:1172">
<![LOG[Sending message body '<ContentLocationRequest SchemaVersion="1.00">
<AssignedSite SiteCode="VSI"/>
<ClientPackage/>
<ClientLocationInfo LocationType="SMSPACKAGE" DistributeOnDemand="0" UseProtected="0" AllowCaching="0" BranchDPFlags="0" AllowHTTP="1" AllowSMB="0" AllowMulticast="0"
UseInternetDP="0">
<ADSite Name="Default-First-Site-Name"/>
<Forest Name="VKYV.LAN"/>
<Domain Name="VKYV.LAN"/>
<IPAddresses>
<IPAddress SubnetAddress="10.6.2.0" Address="10.6.2.2"/>
</IPAddresses>
</ClientLocationInfo>
</ContentLocationRequest>
']LOG]!><time="11:31:49.256-120" date="01-12-2014" component="ccmsetup" context="" type="0" thread="6436" file="siteinfo.cpp:96">
<![LOG[Sending message header '<Msg SchemaVersion="1.1"><ID>{CC48E819-7755-4650-83AC-8BC823C06C8C}</ID><SourceHost>VKYV-HV01</SourceHost><TargetAddress>mp:[http]MP_LocationManager</TargetAddress><ReplyTo>direct:VKYV-HV01:LS_ReplyLocations</ReplyTo><Priority>3</Priority><Timeout>600</Timeout><ReqVersion>5931</ReqVersion><TargetHost>VKYV-HV01.VKYV.LAN</TargetHost><TargetEndpoint>MP_LocationManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2014-01-12T09:31:49Z</SentTime><Body
Type="ByteRange" Offset="0" Length="1096"/><Hooks><Hook3 Name="zlib-compress"/></Hooks><Payload Type="inline"/></Msg>']LOG]!><time="11:31:49.256-120" date="01-12-2014"
component="ccmsetup" context="" type="0" thread="6436" file="siteinfo.cpp:177">
<![LOG[CCM_POST 'HTTP://VKYV-HV01.VKYV.LAN/ccm_system/request']LOG]!><time="11:31:49.257-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="httphelper.cpp:807">
<![LOG[Failed to receive ccm message response. Status code = 403]LOG]!><time="11:31:49.434-120" date="01-12-2014" component="ccmsetup" context="" type="2" thread="6436" file="httphelper.cpp:1694">
<![LOG[GetDPLocations failed with error 0x80004005]LOG]!><time="11:31:49.435-120" date="01-12-2014" component="ccmsetup" context="" type="3" thread="6436" file="siteinfo.cpp:532">
<![LOG[Failed to get DP locations as the expected version from MP 'VKYV-HV01.VKYV.LAN'. Error 0x80004005]LOG]!><time="11:31:49.435-120" date="01-12-2014" component="ccmsetup" context="" type="2" thread="6436"
file="ccmsetup.cpp:11261">
<![LOG[Sending Fallback Status Point message to 'VKYV-HV01', STATEID='101'.]LOG]!><time="11:31:49.435-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:9756">
<![LOG[Failed to get client version for sending messages to FSP. Error 0x8004100e]LOG]!><time="11:31:49.437-120" date="01-12-2014" component="ccmsetup" context="" type="2" thread="6436" file="ccmsetup.cpp:9838">
<![LOG[Params to send FSP message '5.0.7958.1000 Deployment ']LOG]!><time="11:31:49.437-120" date="01-12-2014" component="ccmsetup" context="" type="0" thread="6436" file="ccmsetup.cpp:9887">
<![LOG[State message with TopicType 800 and TopicId {1D445639-95B1-4EC5-A65F-FC7A721F8061} has been sent to the FSP]LOG]!><time="11:31:49.455-120" date="01-12-2014" component="FSPStateMessage" context="" type="1"
thread="6436" file="fsputillib.cpp:752">
<![LOG[Next retry in 10 minute(s)...]LOG]!><time="11:31:49.455-120" date="01-12-2014" component="ccmsetup" context="" type="0" thread="6436" file="ccmsetup.cpp:8835">Does you MP/DP use HTTP or HTTPS? I recommend to start with HTTP and when you have successfully installed a few clients, you can switch to HTTPS if desired. HTTPS based communication requires more steps e.g. client certificates.
Have you extended AD schema and do you see objects in \System\System Management container in AD?
Also, you might have DNS name resolution problem or the firewall is blocking the traffic from the client to MP.
The client is having troubles to successfully talk with MP:
Failed to get DP locations as the expected version from MP 'VKYV-HV01.VKYV.LAN'. Error 0x80004005
Panu -
Hi All,
What is best practice for automatic installing of SCCM 2012 client Patches
(using Patch switch) during installation of SCCM 2012 clients? The challenge is that now there are two versions of clients and updates (x86 and x64).
I need information for:
OSD
Client Push Installation
Thank you in advance.
Regards,Not everything that can be or is supported or not supported is documented (or ever can be):
http://technet.microsoft.com/en-us/magazine/jj643252.aspx
Your expectation here needs to be adjusted. No one recommended contacting support. William just mentioned that *if* you have an issue and needed to contact support, they may decline to help you because you've done something explicitly unsupported.
For clientpatch, here's the specific documentation noting it as unsupported:
http://blogs.technet.com/b/configmgrteam/archive/2009/04/08/automatically-applying-hotfixes-to-the-configuration-manager-2007-client-during-installation.aspx
Additionally, I've also been in contact with the sustained engineering folks responsible for the CUs and they've reinforced the statement.
What can happen? Who knows? Microsoft does not test against unsupported configurations and features -- that's the definition of unsupported. It's not tested so no one really knows. They did find a couple of explicit issues (outlined in that post above) so
know that at least those exist and probably more since it is, as mentioned, abandoned code.
Why does it matter what can happen though? If the folks who write and support the code tell you shouldn't do it, you are simply asking for problems by doing it. Ultimately, you're asking a question that has no defined answer (except "bad"/unsupported things)
that really doesn't matter if you follow the explicit guidance. If you don't, as William points out, that's a risk for you take and an answer for you to discover.
Jason | http://blog.configmgrftw.com -
How to install sccm client on bulk collections using push installation
Unfortunately I did something and received the following description:-
How to know/reproduce the following scenario by installing sccm client on bulk collections in SCCM 2012R2?
"User ***** requested that the CCRs will be generated for collection “All Windows Client Systems (P0100015), The SMS Provider did not generate CCRs for all the system resources in this collection.
Possible cause: some system resources are not assigned to the current site, and you chose to insta
Il clients only on system resources that are
assigned to current site.
Another possible cause: Some system resources do not have Microsoft Windows NT operating system
or above installed.
Message ID: 30110"Ok. Some of your clients are not covered under any site assignment boundary, hence you are getting that error. Would recommend you to select "Install the client from a specified site" and select the Primary site. If your boundary groups for content
are configured fine then the client will be installed from the appropriate site for each machine you are pushing the client to.
-RG -
SCCM 2012 R2- Client push not working
Hi,
We have a SCCM 2012 R2 environment in our production. In one of the client machine i am unable to deploy client using Client push method. Below is the error in ccm.log
I am able to access admin$ share from sccm server. Please help!!
Regards
PallaviIt means that it's trying to connect to the Admin$ share, but that it's failing because it's either unavailable or the account has no access.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude
Maybe you are looking for
-
Snow Leopard's Address Book now Requires Full Name to find a Contact
In all previous versions of Address Book, the user could simply type 'T' to instantly go to contacts with last names that start with 'T' (and businesses that start with 'T'). In Snow Leopard, Address Book can no longer search with one letter the way
-
A automatic reset cleared items
Hi, the customer had executing for error with the f.13. i need to reset clearing items for many FI documents. I know there s a t-code fbra but it can use just one document. Is possible or exactly, is there s the Sap standard report can be massive res
-
Switching from "UTF-8" to "ISO-8859-1"
Dear all, I am using Designer 7.0 to create forms, where the content is sent back via eMail and, after review, imported to a wepage. Due to multiple languages on the site, encoding="ISO-8859-1" is mandatory. Unfortunately I am not able to generate a
-
Has anyone found a solution for the error "The iCloud Control Panel did not install properly". I'm using windows 7 prof 64 and outlook 2010 and cant get to cloud to winkd ot my mail, contacts, calendar. Cloud control panel version 2.0.
-
Problem with Dataguard Wizzard in OEM 10
Hi, I've tried to create a physical standby database of a 10gR2 instance on the same host (windows 2003 64 bits) through OEM 10, and I get an error message at the first step. I select "create a physical standby database" and I get this in french : "I