Client Push problems

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

Client Push problems

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> Client Push problems

Page: [1]

Message

<< Older Topic Newer Topic >>

Client Push problems - 6/17/2008 12:25:50 PM

sms help

Posts: 4
Score: 0
Joined: 6/17/2008
Status: offline

Hi

I'm having problems deploying clients assigned to my secondary sites. Mixed Mode. Client installed fine on machines assigned to primary site. Secondary sites have their own site codes and I've configured the client install account on all secondaries. Did not enable client push. Instead tried installing client through the wizard in collections. Checked ccm.log - can see something happening when doing a client push to machines assigned to primary site code; but nothing when doing it on rest of machines on other site codes. What could be the problem? I desperately need help please?

Post #: 1

RE: Client Push problems - 6/18/2008 1:34:03 AM

sms help

Posts: 4
Score: 0
Joined: 6/17/2008
Status: offline

is there nobody who has any idea why the client push doesn't want to work please? there must be something i'm overlooking? are you suppose to specify the install account at the secondary sites as well or just the primary? does the boundaries i've specificied have an impact? anything?

(in reply to sms help)

Post #: 2

RE: Client Push problems - 6/18/2008 2:43:52 AM

iburnell

Posts: 248
Score: 1
Joined: 5/14/2003
From: London, UK
Status: offline

Yes - you must specify the account(s) to be used on the secondary site via the console. The account must have local admin rights on the user's PC. Test by picking a machine or two. Have ccm.log open on your primary site server with trace32 so you can see it in real time. You'll see messages about trying to connect to pcname\admin$ using the account specified. If it connects great good start - of not you'll probably see an error 5 accessed denied. So:

1) If it can connect there's a problem with the install on the client PC. Check ccmsetup.log on the client again using trace32 and check if there are any issues
2) If ccm.log cannot connect then its a simple privilege issue. Try logging on with the account you specified and trying manually to map a drive to that PC's admin$ share. Typical problems include not having the specified account in the local administrator group or firewall preventing access or maybe file and print sharing not enabled (unlikely)

Either way you just have to work through it step by step. Remember that even thought the clients are at secondary site they are still assigned to the parent primary

_____________________________

Ian Burnell
London UK

(in reply to sms help)

Post #: 3

RE: Client Push problems - 6/18/2008 3:08:34 AM

sms help

Posts: 4
Score: 0
Joined: 6/17/2008
Status: offline

Hi Ian

Thank you so much for your feedback. I checked everything as you've mentioned above and you will not believe this; but the problem was actually quite simple...All I did differently was not to set the Include only clients in this site's boundaries option on the Installation Options Page in the wizard. Immediately I checked the ccm.log and could see some activity. I checked the ccmsetup.log and the installation was running. I had that option selected when I deployed the clients assigned to my primary site. So it looks like you have to de-select it when you deploy to clients assigned to your secondaries.

(in reply to iburnell)

Post #: 4