Automatic client push installation not working

I created one secondary server and replication with CAS is active. Boundary also configured and enabled automatic client push installation.
Daily i am checking some machines, but agents are not getting installing automatically . But manual client installation is working fine without any issue. Anyone can help on this to find outwhy automatic clients push installation is not running on client
machines

Which site code is showing, for your secondary or for your primary?
If secondary, then as Joyce pointed out, you need to check ccm.log on the secondary site server needs to be checked because that's where the client will be pushed from.
Jason | http://blog.configmgrftw.com | @jasonsandys

Similar Messages

Automatic Client Push not working - Site System Servers

Having an issue getting automatic site-wise client push to work when only
having "Configuration Manager site system servers" selected. This was turned on after discovery was enabled and fully executed.
SCCM 2012 R2 CU1, Single Primary Site Server, 2 Management Points (one on primary and second is standalone), with 5 DP's (currently), SQL is standalone.
The site systems are within the IP range boundaries and show as assigned (i.e. site code showing in console of object). The boundaries are in a boundary group with site assignment selected, and a DP added. When I view the object properties I
see its returning the correct IP that does fall withing the IP range boundary.
Nothing in the ccm.log indicating its ever trying to install the client and the ccr and ccrretry folders are empty. I can do a manual client push without issue to a site server object or a discovered desktop/laptop object.
Is there something I may be missing here? And does anyone know the interval in which SCCM should be creating ccr records for discovered objects that don't have a client?

Thanks or the quick replies everyone. To answer Idan's questions, no errors in log or component status and SQL is not clustered.
John, I hope this isn't the case. If it were wouldn't that effectively mean you would not be able to enabled discovery until you are ready to turn on auto client push? And if you did that you would have no way to control the client roll out.
Maybe I am missing something in that equation. I'll test that theory regardless but if that ends up being the case that is alarming! :-)
Jason, thanks for the tip on the potential bug. Was really more so hoping to validate automatic client push rather than actually needing it for my site system servers. So if it is the issue you reference above hopefully its just contained to
the site system servers. Would be nice to be able to select automatic client push to just a collection of devices prior to turning it on for site wide deployment.
I guess I could always just turn off discovery temporarily and delete all but some test clients, enable client push for workstations, then once validated, turn it back off and re-enable discovery. (wouldn't turn push back on until most clients are
deployed on the roll out schedule)

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

Enable Automatic site-wide client push installation

Hi,
We are configuring sccm 2012 next to sccm 2007. We want to push SCCM 2007 clients automatically to pc's in a certain OU. Can this be done via "Enable Automatic site-wide client push installation".
So will it deploy to only the discovered devices in this OU we configured to discover or really install site wide (probably not but need to be sure)?
J.
Jan Hoedt

Automatic client push will initiate a push to all devices that are discovered (where client = 0) and that are assigned to the site (-> boundaries).
Torsten Meringer | http://www.mssccmfaq.de

Flash play installation not work - The exe file deelete automaticly and the process is still running

Flash play installation not work - The exe file deelete automaticly and the process is still running

Why i get no answer?

Best practise for installing patches for SCCM Client 2012 (Both x86 and x64)) - OSD and Client Push Installation

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

Automatic Client Push

We recently migrated from SCCM 2007 to SCCM 2012 R2. I did the migration by manually pushing out clients, and now that a majority are migrated, I enabled Automatic Client Push. However, resources that were already discovered without the client
installed aren't receiving the client. Checking CCM.log on the primary site server, I don't see SCCM even attempting to push the client.
Any ideas?

Can you post a portion of the ccm.log?
I apparently can't post much of it. The workstations that are failing are ones I pushed to manually the day prior. This is from the point of enabling automatic client push, and a bit afterwards:
Waking up for site control file directory change notification $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:33.896+360><thread=17076 (0x42B4)>
The Site Control File has changed, parameters will be reread. $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:33.965+360><thread=17076 (0x42B4)>
Updating Site Parameters $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:33.984+360><thread=17076 (0x42B4)>
~MP Ports: 80 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:33.998+360><thread=17076 (0x42B4)>
~IISPreferedPort: 80 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.012+360><thread=17076 (0x42B4)>
~MP SSL Ports: 443 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.025+360><thread=17076 (0x42B4)>
~IISSSLPreferedPort: 443 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.040+360><thread=17076 (0x42B4)>
~Default MP: SCCM.Domain.com $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.053+360><thread=17076 (0x42B4)>
~Default MP Type: 1 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.067+360><thread=17076 (0x42B4)>
~Default MP: [None] $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.081+360><thread=17076 (0x42B4)>
~Certificate Selection Criteria: $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.094+360><thread=17076 (0x42B4)>
~Certificate Store: $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.107+360><thread=17076 (0x42B4)>
~SSL State: 224 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.120+360><thread=17076 (0x42B4)>
~Select First Certificate: 1 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.134+360><thread=17076 (0x42B4)>
~Certificate Issuers: $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.159+360><thread=17076 (0x42B4)>
Checking configuration information for server: SCCM.Domain.COM.~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.174+360><thread=17076 (0x42B4)>
~No Fallback Status Point installed on the Site $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.187+360><thread=17076 (0x42B4)>
~Install on DC: True $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.200+360><thread=17076 (0x42B4)>
~Option for installing using IP address: 0 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.214+360><thread=17076 (0x42B4)>
Retrieving properties from the site control file. $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.226+360><thread=17076 (0x42B4)>
~Advanced Client Command Line: SMSSITECODE=STE $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.239+360><thread=17076 (0x42B4)>
Ignoring unrecognized property "Advanced Client Command Line Default" $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.253+360><thread=17076 (0x42B4)>
~Security Mode Option - CCR buffering disabled. $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.266+360><thread=17076 (0x42B4)>
~Default Client Type: -1 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.279+360><thread=17076 (0x42B4)>
Sleeping for 981 seconds... $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.300+360><thread=17076 (0x42B4)>
CCM Shutting down (12)~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:11:12.799+360><thread=10212 (0x27E4)>
No request returned from queue $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:11:12.836+360><thread=10212 (0x27E4)>
CCM Shutting down... (4)~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:11:12.850+360><thread=17076 (0x42B4)>
CCM Main thread is exiting...~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:11:12.908+360><thread=17076 (0x42B4)>
SMS_EXECUTIVE started SMS_CLIENT_CONFIG_MANAGER as thread ID 2664 (0xA68). $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.269+360><thread=16000 (0x3E80)>
************** Client Config Manager main thread starting ************** $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.294+360><thread=2664 (0xA68)>
This site: "STE". $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.308+360><thread=2664 (0xA68)>
This site type: "1". $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.324+360><thread=2664 (0xA68)>
This machine: "SCCM.Domain.com". $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.338+360><thread=2664 (0xA68)>
The Site Control File has changed, parameters will be reread. $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.498+360><thread=2664 (0xA68)>
Updating Site Parameters $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.570+360><thread=2664 (0xA68)>
~MP Ports: 80 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.615+360><thread=2664 (0xA68)>
~IISPreferedPort: 80 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.630+360><thread=2664 (0xA68)>
~MP SSL Ports: 443 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.644+360><thread=2664 (0xA68)>
~IISSSLPreferedPort: 443 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.658+360><thread=2664 (0xA68)>
~Default MP: SCCM.Domain.com $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.680+360><thread=2664 (0xA68)>
~Default MP Type: 1 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.693+360><thread=2664 (0xA68)>
~Default MP: [None] $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.705+360><thread=2664 (0xA68)>
~Certificate Selection Criteria: $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.718+360><thread=2664 (0xA68)>
~Certificate Store: $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.732+360><thread=2664 (0xA68)>
~SSL State: 224 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.745+360><thread=2664 (0xA68)>
~Select First Certificate: 1 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.758+360><thread=2664 (0xA68)>
~Certificate Issuers: $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.774+360><thread=2664 (0xA68)>
Checking configuration information for server: SCCM.Domain.COM.~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.788+360><thread=2664 (0xA68)>
~No Fallback Status Point installed on the Site $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.801+360><thread=2664 (0xA68)>
~Install on DC: True $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.819+360><thread=2664 (0xA68)>
~Option for installing using IP address: 0 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.845+360><thread=2664 (0xA68)>
Retrieving properties from the site control file. $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.864+360><thread=2664 (0xA68)>
~Advanced Client Command Line: SMSSITECODE=STE $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.878+360><thread=2664 (0xA68)>
Ignoring unrecognized property "Advanced Client Command Line Default" $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.893+360><thread=2664 (0xA68)>
~Security Mode Option - CCR buffering disabled. $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.914+360><thread=2664 (0xA68)>
~Default Client Type: -1 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.927+360><thread=2664 (0xA68)>
Confirming all required files are available on the site server~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.942+360><thread=2664 (0xA68)>
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.965+360><thread=2664 (0xA68)>
Site Server Name "\\SCCM.Domain.com" $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.980+360><thread=2664 (0xA68)>
Site Code "STE" $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.020+360><thread=2664 (0xA68)>
CCM Account 1 "Domain\clientdeploy" $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.054+360><thread=2664 (0xA68)>
CCM Account 2 "Domain2\clientdeploy" $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.067+360><thread=2664 (0xA68)>
CCM Account 3 "<end of list>" $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.081+360><thread=2664 (0xA68)>
Max CCR Processing Threads 10 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.095+360><thread=2664 (0xA68)>
CCR Processing Thread Timeout 600000 ms $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.108+360><thread=2664 (0xA68)>
Sitewide Travel Mode Switch USE CLIENT SETTING $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.131+360><thread=2664 (0xA68)>
Days Between Account Cleanups 30 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.143+360><thread=2664 (0xA68)>
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.156+360><thread=2664 (0xA68)>
Parameters for queue: "Incoming" $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.168+360><thread=2664 (0xA68)>
Inbox Path "E:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.181+360><thread=2664
(0xA68)>
Read Queue Every DIR CHANGE NOTIFICATION $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.193+360><thread=2664 (0xA68)>
Retry CCR For 168 Hours $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.206+360><thread=2664 (0xA68)>
Report Error After ERROR REPORTING OFF $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.219+360><thread=2664 (0xA68)>
Warn when Queue Exceeds 100 CCRs $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.246+360><thread=2664 (0xA68)>
Delay Between CCRs 100 Millisec $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.259+360><thread=2664 (0xA68)>
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.271+360><thread=2664 (0xA68)>
Parameters for queue: "Retry" $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.284+360><thread=2664 (0xA68)>
Inbox Path "E:\Program Files\Microsoft Configuration Manager\inboxes\ccrretry.box" $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.297+360><thread=2664
(0xA68)>
Read Queue Every 60 Minutes $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.310+360><thread=2664 (0xA68)>
Retry CCR For 168 Hours $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.323+360><thread=2664 (0xA68)>
Report Error After 24 Hours $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.336+360><thread=2664 (0xA68)>
Warn when Queue Exceeds 150 CCRs $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.349+360><thread=2664 (0xA68)>
Delay Between CCRs 100 Millisec $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.361+360><thread=2664 (0xA68)>
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.374+360><thread=2664 (0xA68)>
Parameters for queue: "Processing" $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.387+360><thread=2664 (0xA68)>
Inbox Path "E:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box\InProc" $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.389+360><thread=2664
(0xA68)>
Read Queue Every DIR CHANGE NOTIFICATION $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.415+360><thread=2664 (0xA68)>
Retry CCR For CCR DOESN'T EXPIRE $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.428+360><thread=2664 (0xA68)>
Report Error After ERROR REPORTING OFF $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.440+360><thread=2664 (0xA68)>
Warn when Queue Exceeds 150 CCRs $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.453+360><thread=2664 (0xA68)>
Delay Between CCRs 0 Millisec $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.466+360><thread=2664 (0xA68)>
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.478+360><thread=2664 (0xA68)>
Moving CCRs from processing queue to incoming queue~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.491+360><thread=2664 (0xA68)>
Started Incoming Queue Thread, ThreadId = 2488 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.505+360><thread=2664 (0xA68)>
Started Retry Queue Thread, ThreadId = 1548 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.518+360><thread=2664 (0xA68)>
Sleeping for 300 seconds... $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.531+360><thread=2664 (0xA68)>
THREAD_ProcessQ starting, Input Queue ID is 0. $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.551+360><thread=9352 (0x2488)>
Queue Name is "Incoming". $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.632+360><thread=9352 (0x2488)>
Queue Directory is "E:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box". $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.697+360><thread=9352 (0x2488)>
Sleeping for 300 seconds before processing requests on queue Incoming... $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.711+360><thread=9352 (0x2488)>
THREAD_ProcessQ starting, Input Queue ID is 1. $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.531+360><thread=5448 (0x1548)>
Queue Name is "Retry". $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.773+360><thread=5448 (0x1548)>
Queue Directory is "E:\Program Files\Microsoft Configuration Manager\inboxes\ccrretry.box". $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.785+360><thread=5448 (0x1548)>
Sleeping for 480 seconds before processing requests on queue Retry... $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.804+360><thread=5448 (0x1548)>
~Waking up for site control file directory change notification $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.148+360><thread=2664 (0xA68)>
The Site Control File has not changed since the last parameter update. $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.170+360><thread=2664 (0xA68)>
Updating Site Parameters $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.183+360><thread=2664 (0xA68)>
~MP Ports: 80 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.200+360><thread=2664 (0xA68)>
~IISPreferedPort: 80 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.247+360><thread=2664 (0xA68)>
~MP SSL Ports: 443 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.260+360><thread=2664 (0xA68)>
~IISSSLPreferedPort: 443 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.279+360><thread=2664 (0xA68)>
~Default MP: SCCM.Domain.com $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.298+360><thread=2664 (0xA68)>
~Default MP Type: 1 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.311+360><thread=2664 (0xA68)>
~Default MP: [None] $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.324+360><thread=2664 (0xA68)>
~Certificate Selection Criteria: $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.337+360><thread=2664 (0xA68)>
~Certificate Store: $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.351+360><thread=2664 (0xA68)>
~SSL State: 224 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.364+360><thread=2664 (0xA68)>
~Select First Certificate: 1 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.379+360><thread=2664 (0xA68)>
~Certificate Issuers: $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.392+360><thread=2664 (0xA68)>
Checking configuration information for server: SCCM.Domain.COM.~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.411+360><thread=2664 (0xA68)>
~No Fallback Status Point installed on the Site $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.494+360><thread=2664 (0xA68)>
~Install on DC: True $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.520+360><thread=2664 (0xA68)>
~Option for installing using IP address: 0 $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.535+360><thread=2664 (0xA68)>
Sleeping for 282 seconds... $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.557+360><thread=2664 (0xA68)>
CCR count in queue "Incoming" is 0. $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:18:57.577+360><thread=2664 (0xA68)>
CCR count in queue "Processing" is 0. $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:18:57.590+360><thread=2664 (0xA68)>
Sleeping for 300 seconds... $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:18:57.603+360><thread=2664 (0xA68)>
Getting a new request from queue "Incoming" after 100 millisecond delay. $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:18:57.733+360><thread=9352 (0x2488)>
Waiting for change in directory "E:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:18:57.746+360><thread=9352
(0x2488)>
Getting a new request from queue "Retry" after 100 millisecond delay. $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:57.827+360><thread=5448 (0x1548)>
Execute query exec [sp_CP_GetPushRequestMachine] 2097152351~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:57.944+360><thread=5448 (0x1548)>
Successfully retrieved information for machine workstation2 from DB $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:57.957+360><thread=5448 (0x1548)>
Execute query exec [sp_CP_GetPushRequestMachineIP] 2097152351~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:57.969+360><thread=5448 (0x1548)>
Execute query exec [sp_CP_GetPushRequestMachineResource] 2097152351~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:57.983+360><thread=5448 (0x1548)>
Execute query exec [sp_CP_GetPushMachineName] 2097152351~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:57.996+360><thread=5448 (0x1548)>
Received request: "2097152351" for machine name: "workstation2" on queue: "Retry". $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:58.008+360><thread=5448 (0x1548)>
Stored request "2097152351", machine name "workstation2", in queue "Processing". $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:58.021+360><thread=5448 (0x1548)>
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152351, 1~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:58.036+360><thread=5448 (0x1548)>
----- Started a new CCR processing thread. Thread ID is 0x335c. There are now 1 processing threads $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.061+360><thread=5448 (0x1548)>
Submitted request successfully $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.074+360><thread=5448 (0x1548)>
Getting a new request from queue "Retry" after 100 millisecond delay. $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.087+360><thread=5448 (0x1548)>
Found CCR "2097152396.ccr" in queue "Retry". $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.099+360><thread=5448 (0x1548)>
======>Begin Processing request: "2097152351", machine name: "workstation2" $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.074+360><thread=13148 (0x335C)>
Execute query exec [sp_IsMPAvailable] N'STE'~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.129+360><thread=13148 (0x335C)>
---> Trying each entry in the SMS Client Remote Installation account list~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.142+360><thread=13148 (0x335C)>
---> Attempting to connect to administrative share '\\workstation2\admin$' using account 'Domain\sccmclientdeploy'~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.155+360><thread=13148 (0x335C)>
Execute query exec [sp_CP_GetPushRequestMachine] 2097152396~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.211+360><thread=5448 (0x1548)>
Successfully retrieved information for machine workstation1 from DB $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.230+360><thread=5448 (0x1548)>
Execute query exec [sp_CP_GetPushRequestMachineIP] 2097152396~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.243+360><thread=5448 (0x1548)>
Execute query exec [sp_CP_GetPushRequestMachineResource] 2097152396~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.256+360><thread=5448 (0x1548)>
Execute query exec [sp_CP_GetPushMachineName] 2097152396~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.269+360><thread=5448 (0x1548)>
Received request: "2097152396" for machine name: "workstation1" on queue: "Retry". $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.283+360><thread=5448 (0x1548)>
Stored request "2097152396", machine name "workstation1", in queue "Processing". $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.296+360><thread=5448 (0x1548)>
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152396, 1~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.312+360><thread=5448 (0x1548)>
---> Connected to administrative share on machine workstation2 using account 'Domain\sccmclientdeploy'~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.213+360><thread=13148 (0x335C)>
---> Attempting to make IPC connection to share <\\workstation2\IPC$> ~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.351+360><thread=13148 (0x335C)>
---> Searching for SMSClientInstall.* under '\\workstation2\admin$\'~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.368+360><thread=13148 (0x335C)>
---> Unable to connect to WMI on remote machine "workstation2", error = 0x80041002. $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.457+360><thread=13148 (0x335C)>
---> Deleting SMS Client Install Lock File '\\workstation2\admin$\SMSClientInstall.STE'~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.470+360><thread=13148 (0x335C)>
Execute query exec [sp_CP_SetLastErrorCode] 2097152351, -2147217406~ $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.491+360><thread=13148 (0x335C)>
Stored request "2097152351", machine name "workstation2", in queue "Retry". $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.505+360><thread=13148 (0x335C)>

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

Sccm 2012 client push installation error 120 & 1350

what i can do to resolve this problem a lot of client push installation skipped and get error 120 & 1305

Hi Alaa,
The problem is when you initiated your client push for these clients you forgot to force it.
The machines you are trying to deploy to already have a CCM client or a failed/corrupt installation.
You must re-initiate the client push install for the failing machines, and remember to tick off the
'Always Install the client software' option. This repairs failed/corrupt installations also.
The error code 120 tells you this way:
120 - Mobile client on the target machine has the same version, and 'forced' flag is not turned on. Not processing this CCR ,target machine already have cm client and no force install selected(always install).
1305 - is just that the client push cannot detect which version that is already installed.
All the best, Jesper Hassing - MCTS SCCM 2012 - MCSA 2012 Server - MCP

Mac Os X lion installation not working.

os x lion installation not working, when the installation bar comes to 99% a pop up widow tells me that the installation has failed and the file could be damaged or something. But i just downloaded it from appstore. Any ideas?

Here's an update on my problem:
Called Apple Support the other day. They basically told me that they can't help, because this is a problem of misconfiguration and that those kinda things weren't covered. Still the person on the line gave me a hint, I should look for leftovers of previously installed software in /Library/LaunchDaemons/ and /Library/LaunchAgents/ .
Well, that did the trick. In one of the folders I found "net.shrew.iked.plist". This file obvioulsy belongs to the ShrewSoft VPN client. I removed it and the built-in client works again.
I reinstalled ShrewSoft one more time to see if it works without the mentioned plist-file...needless to say it wouldn't connect anymore, but that's alright with me - for now.

How to change my client push installation version

I have one primary site server. I have updated it to 5.00.7958.1401 and this is the version shown if i check "about system center configuration manager".
When i push the client to machines by right clicking and choosing "install client"...SCCM installs client version 5.00.7958.1000.
How can I change it so my client push installs the CU3 version 1401?
Thanks

If you were to mess with the files in the client folder of the site server's installation path, you would place your self in an unsupported state, though this is simple...
how about using the PATCH parameter for ccmsetup.exe? You could configure it in the Client Push Installation / Installation Properties tab...
http://thecmadmin.com/2013/08/01/installing-cumulative-update-2-cu2-for-cm12-sp1-during-initial-client-install/
other reference:
http://blogs.technet.com/b/deploymentguys/archive/2012/10/11/automatically-populate-the-patch-property-for-the-configmgr-client-installation-updated-for-configmgr-2012.aspx

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

Client Push Installation over Wi-Fi

Hello Folks,
Is it possible to do Client Push Installation Over the Wi-Fi network.?
Regards,
Vishnu
V I S H N U

A network is a network. It does not matter if wired or wireless. It can be done if all pereqs are met.
Torsten Meringer | http://www.mssccmfaq.de

Question about Client Push Installation configuration

Hello,
I am trying to configure client push installation. Can you please tell me what is needed for the field "Network Share"? I see sample examples listing <server name>\admin$ or server\share. My admin share on my server
is c:\windows. Is there a directory that is needed here such as the client software? If so, I see a directory under C:\program files\Microsoft configuration manager\client. Please advise on the next step. Thanks for any help.

Are you talking about this?
This is optional. You don't need to use this at all. It's just to verify that the account details you have entered are valid (ie test connection).
Note that your client push installation account has to be local administrator on all devices on which you want to install a client.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

MSI installer not working MSI 5.0 Windows 7

Hello I am trying to get MSI installer to work and when I go to install anything that has the Windows Installer Package it opens Notepad in a scrambled message. I have tried numerous avenues to no avail (regedit,copy paste regedit, troubleshooters, sfc/scannow,
command prompt etc.) I tried to choose the file association of MSIexec in System32 and it just opens this
I have tried what is suggested in this forum
https://social.technet.microsoft.com/Forums/windows/en-US/f699e632-54ba-443b-85df-269a7fd6cf1a/windows-installer-not-working?forum=w7itprogeneral and regedit says:
I have tried this http://support.microsoft.com/kb/2438651#reso1 and didn't work
I have tried changing C :\Windows\System32\msiexec.exe /V in regedit and that didn't work
I have searched event viewer and all that's in there is a warning and information of successful installs and uninstalls.
I have tried %windir%\system32\msi.dll version in Command prompt and it says that the system cannot execute the specified program
I am thinking it is just a matter of finding the correct file association that the windows installer can use to install that program but I am unable to find that!
I did a system restore but the only good restore was from earlier today and it still just opens notepad. before I did the restore I went into services and the computer couldn't find the file (windows installer) so I did a restore and now it at least sees
the file and I can start the service.
Can I please get some help fixing this? would uninstalling MSI and re-installing it work? I have been searching forum after forum and nothing has yet worked.
I did a clean install of windows a couple of weeks ago
Microsoft answers gives me thee worst answers a person could come up with.
for a complete list of what my computer is check my bio

Hi ingenuities,
Try importing these reg file under Safe mode.
If you really need this work, I am supposing the only way is to try importing them manually, if any value key is using by process, use process monitor to filter out these processes and shut them down.I monitored values under MSI.package seems like no
value was using by system.
I exported msi.package and patch to text, it is from a clean Windows 7 intallation。
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Msi.Package]
@="Windows Installer Package"
"EditFlags"=hex:00,00,10,00
"FriendlyTypeName"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,\
00,6f,00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,\
32,00,5c,00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,\
00,2d,00,33,00,34,00,00,00
"InfoTip"="prop:System.ItemType;System.Author;System.Title;System.Subject;System.Comment;System.DateModified;System.Size"
"FullDetails"="prop:System.PropGroup.Description;System.Title;System.Subject;System.Category;System.Keywords;System.Comment;System.PropGroup.Origin;System.Author;System.Document.RevisionNumber;System.Document.DateCreated;System.ApplicationName;System.PropGroup.FileSystem;System.ItemNameDisplay;System.ItemType;System.ItemFolderPathDisplay;System.DateCreated;System.DateModified;System.Size;System.FileAttributes;System.OfflineAvailability;System.OfflineStatus;System.SharedWith;System.FileOwner;System.ComputerName"
[HKEY_CLASSES_ROOT\Msi.Package\DefaultIcon]
@="C:\\Windows\\system32\\msiexec.exe,0"
[HKEY_CLASSES_ROOT\Msi.Package\shell]
@="Open,Repair,Uninstall"
[HKEY_CLASSES_ROOT\Msi.Package\shell\Open]
@="&Install"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,36,00,00,00
[HKEY_CLASSES_ROOT\Msi.Package\shell\Open\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,69,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00
[HKEY_CLASSES_ROOT\Msi.Package\shell\Repair]
@="Re&pair"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,37,00,00,00
[HKEY_CLASSES_ROOT\Msi.Package\shell\Repair\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,66,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00
[HKEY_CLASSES_ROOT\Msi.Package\shell\runasuser]
@="@shell32.dll,-50944"
"Extended"=""
"SuppressionPolicyEx"="{F211AA05-D4DF-4370-A2A0-9F19C09756A7}"
[HKEY_CLASSES_ROOT\Msi.Package\shell\runasuser\command]
"DelegateExecute"="{ea72d00e-4960-42fa-ba92-7792a7944c1d}"
[HKEY_CLASSES_ROOT\Msi.Package\shell\Uninstall]
@="&Uninstall"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,38,00,00,00
[HKEY_CLASSES_ROOT\Msi.Package\shell\Uninstall\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,78,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00
[HKEY_CLASSES_ROOT\Msi.Package\shellex]
[HKEY_CLASSES_ROOT\Msi.Package\shellex\ContextMenuHandlers]
@="Compatibility"
[HKEY_CLASSES_ROOT\Msi.Package\shellex\ContextMenuHandlers\Compatibility]
@="{1d27f844-3a1f-4410-85ac-14651078412d}"
[HKEY_CLASSES_ROOT\Msi.Package\shellex\PropertySheetHandlers]
[HKEY_CLASSES_ROOT\Msi.Package\shellex\PropertySheetHandlers\ShimLayer Property Page]
@="{513D916F-2A8E-4F51-AEAB-0CBC76FB1AF8}"
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Msi.Patch]
@="Windows Installer Patch"
"EditFlags"=hex:00,00,10,00
"FriendlyTypeName"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,\
00,6f,00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,\
32,00,5c,00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,\
00,2d,00,33,00,35,00,00,00
"InfoTip"="prop:System.ItemType;System.Author;System.Title;System.Subject;System.Comment;System.DateModified;System.Size"
"FullDetails"="prop:System.PropGroup.Description;System.Title;System.Subject;System.Category;System.Keywords;System.Comment;System.PropGroup.Origin;System.Author;System.Document.RevisionNumber;System.Document.DateCreated;System.ApplicationName;System.PropGroup.FileSystem;System.ItemNameDisplay;System.ItemType;System.ItemFolderPathDisplay;System.DateCreated;System.DateModified;System.Size;System.FileAttributes;System.OfflineAvailability;System.OfflineStatus;System.SharedWith;System.FileOwner;System.ComputerName"
[HKEY_CLASSES_ROOT\Msi.Patch\DefaultIcon]
@="C:\\Windows\\system32\\msiexec.exe,0"
[HKEY_CLASSES_ROOT\Msi.Patch\shell]
@="Open"
[HKEY_CLASSES_ROOT\Msi.Patch\shell\Open]
@="&Apply Patch"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,39,00,00,00
[HKEY_CLASSES_ROOT\Msi.Patch\shell\Open\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,70,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00
Regards
D. Wu

Automatic client push installation not working

Similar Messages

Maybe you are looking for