b3976
asked on
Unable to install SCCM client using client push
I am unable to install SCCM client onto computers using client push. All the needed dependencies have been configured properly. Firewall ports, adminshare, GPO, etc.
So i created a test collections consisting of several machines and tried to push the client onto them. Unfortunately, the installation continues to fail. I tried to look at the logs on these machines, but the ccmsetup.exe file is no where to be found. On the SCCM server, all the site and component roles are showing green. No issues there.
Any idea what I am doing wrong?
I can post the logs from the SCCM server if needs be.
Also, would it better to do this via GPO, instead of client push?
Any help would be appreciated.....
thanks
So i created a test collections consisting of several machines and tried to push the client onto them. Unfortunately, the installation continues to fail. I tried to look at the logs on these machines, but the ccmsetup.exe file is no where to be found. On the SCCM server, all the site and component roles are showing green. No issues there.
Any idea what I am doing wrong?
I can post the logs from the SCCM server if needs be.
Also, would it better to do this via GPO, instead of client push?
Any help would be appreciated.....
thanks
ASKER
Thanks for your response. The account does have the right permission. It has domain and local admin rights on the machines.
Looked at event logs and not much there. Also, checked the security software and firewall. All the needed ports are open via GPO and the policy is successfully propagating down to these very machines...
I suspect this might have to do with the VMs running on AWS, security group configuration and all could be problematic......
Looked at event logs and not much there. Also, checked the security software and firewall. All the needed ports are open via GPO and the policy is successfully propagating down to these very machines...
I suspect this might have to do with the VMs running on AWS, security group configuration and all could be problematic......
Hi,
GPO does work well, but yes we need the logs from the server side. Check these steps and the links.
Mike
GPO does work well, but yes we need the logs from the server side. Check these steps and the links.
Mike
ASKER
Have you confirmed you can connect to the admin$ share on the workstation using the account specified in the location I mentioned above?
that would confirm permissions.
Aside from that firewalls / security software would be my next guess.
that would confirm permissions.
Aside from that firewalls / security software would be my next guess.
ASKER
yes, i can connect to the admin share using the client push account. No problem there.
Also, security software isn't an issue. I actually looked into that and even went so far as to temporary disabling it and ran a test.
That didn't make any difference. I suspect this has to do with AWS security grouping or something else. Might just do this via GPO and get it over with.
Also, security software isn't an issue. I actually looked into that and even went so far as to temporary disabling it and ran a test.
That didn't make any difference. I suspect this has to do with AWS security grouping or something else. Might just do this via GPO and get it over with.
ASKER
I finally got the client to install on all machines, the issue appears to be coming from AWS secruity group settings. I suspected that to be the cause from the very beginning. So in order to solve this problem, I AWS, I had to open the same ports that were opened on windows firewall GPO settings and push out the client installations. It is working now, but the install takes several hrs. I guess i can deal with the wait.
ASKER
I finally got the client to install on all machines, the issue appears to be coming from AWS secruity group settings. I suspected that to be the cause from the very beginning. So in order to solve this problem, I AWS, I had to open the same ports that were opened on windows firewall GPO settings and push out the client installations. It is working now, but the install takes several hrs. I guess i can deal with the wait.
Hi - glad you got it working. It ought to only take 10-15 mins to install the client though. I can't even begin to guess what's going on there without further details of various things. I would check your AV and other security technology to see if that is slowing things.
ASKER
@Mike T
Sure will check on those. Thanks
Sure will check on those. Thanks
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
To see the account configured to be used.
go to Administration \Site Configuration\Sites then in the ribbon bar you should see client installation settings click it then select Client Push installation properties and click on the accounts tab.
If it is not even creating the C:\windows\CCMSetup\ folder then it is likely being blocked.
Check the event logs on the client machine for any errors related to the install.
It usually ends up being permissions, firewall or a security software such as Symantec that prevents the install.