Re: Client Push keeps failing

By “network access account” do you mean the user account I created to use
with the Client Push?

Where can I find the settings for the “network access account?”

I have checked and rechecked this share and have verified "EVERYONE" should
at least have READ access. Is there something more I should do to make sure
the permissions are correct? Also, once the permissions ARE correct, will
the client be able to finish installing automaitcally? I have been watching
the log on the desktop that has failed and it is dutifully trying every 10
minutes. I'm thinking the log will show a sign of success once I "fix"
whatever the problem is. Is this correct thinking or do I need to
stop/restart this process to get the results I'm looking for?




"Kerwin Medina [MSFT]" wrote:

In this case, ccmsetup.exe is trying to download client.msi from
\\server\smsclient\i386 but has permissions problem. Cccmsetup.exe is
designed to retry every 10 minutes.

What you can try do is to create a network access account which has access
to the client share. Then, you need to redo the push install. This will
cause push install to write a new TCF file on the client machine. The new
TCF file will contain the network access account. Push install will also
re-start ccmsetup. Ccmsetup will then use the network access account to get
to the client share.

"Jon" <Jon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7732F263-C0A5-4AEC-89A6-784FC85A7A84@xxxxxxxxxxxxxxxx
I am continuing to read about this problem and have come across some other
related posts. As a result, I've attempted a couple of other things....

Disabled the MP on the SMS server....Restarted the MP. = No joy.
I saw a post where it was suggested to have the client install using the "
/useronly" switch, but I'm not really sure where/how to use that switch so
I
haven't tried it yet. It might just work because all of the users on
campus
are admins of their local machines.

It seems like having this error is not all that uncommon...

Source \\Server\SMSCLIENT\I386 is inaccessible (5)
Failed to find accessible source. Waiting for retry.
Next retry in 10 minute(s)...

...I just cannot figure out what to do about it.


"Jon" wrote:

OK, now I'm really lost!

Based on the client-side log you pointed me to, I am convinced I have a
permissions problem. I went to the share (referred to in the log) and
verified all of the permissions seem correct. I even added some
"EVERYONE....Read" permissions to make sure everything should be able to
at
least READ the data in the SMSClient share. I know this should be easy
but I
don't see what is wrong.

Ideas?

"Jon" wrote:

It looks like I have a permissions problem! Thanks for the tip, I'll
give
that a look and see if I can have better success after checking the
permissions.

Thanks,

Jon

==========[ ccmsetup started in process 480 ]========== ccmsetup
5/3/2006
2:01:57 AM 484 (0x01E4)
Version: 2.50.4160.2000 ccmsetup 5/3/2006 2:01:57 AM 484 (0x01E4)
Command line: "C:\WINDOWS\system32\ccmsetup\ccmsetup.exe" /runservice
/config:MobileClient.tcf ccmsetup 5/3/2006 2:01:57 AM 484 (0x01E4)
No network access account provided. Ccmsetup will use current
credentials
for network access. ccmsetup 5/3/2006 2:01:57 AM 484 (0x01E4)
Config file:
C:\WINDOWS\system32\ccmsetup\MobileClient.tcf ccmsetup 5/3/2006 2:01:57
AM 484 (0x01E4)
Retry time: 10 minute(s) ccmsetup 5/3/2006 2:01:57 AM 484
(0x01E4)
MSI log file: ccmsetup 5/3/2006 2:01:57 AM 484 (0x01E4)
MSI properties: INSTALL="ALL" SMSSITECODE="AUTO" ccmsetup 5/3/2006
2:01:57 AM 484 (0x01E4)
Source List: ccmsetup 5/3/2006 2:01:57 AM 484 (0x01E4)
\\SMS\SMSClient\I386 ccmsetup 5/3/2006 2:01:57 AM 484
(0x01E4)
Status MPs: ccmsetup 5/3/2006 2:01:57 AM 484 (0x01E4)
SMS ccmsetup 5/3/2006 2:01:57 AM 484 (0x01E4)
Updated security on object C:\WINDOWS\system32\ccmsetup\. ccmsetup
5/3/2006
2:01:57 AM 484 (0x01E4)
Running as user "SYSTEM" ccmsetup 5/3/2006 2:01:57 AM 520 (0x0208)
Downloading file client.msi ccmsetup 5/3/2006 2:01:57 AM 520 (0x0208)
Determining source location... ccmsetup 5/3/2006 2:01:57 AM 520
(0x0208)
Source \\SMS\SMSClient\I386 is inaccessible (5) ccmsetup 5/3/2006
2:02:01
AM 520 (0x0208)
Failed to find accessible source. Waiting for retry. ccmsetup 5/3/2006
2:02:01 AM 520 (0x0208)
Next retry in 10 minute(s)... ccmsetup 5/3/2006 2:02:01 AM 520 (0x0208)




"Michael Zhuo" wrote:

Did you see and check the sysyem32\ccmsetup.log on the client
machine?

Thanks,

Michael [MSFT]

This posting is provided "AS IS" with no warranties, and confers no
rights.

"Jon" <Jon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5B12B36A-6D3D-4334-B25B-624F188EB309@xxxxxxxxxxxxxxxx
Hello Michael,

Thank you for your interest in this case.

I thought that at first too and yet the SMS console still shows
this
computer as "Site Code = <blank>, Client = No, and Assigned = Yes."
Further,
when I go to the machine itself, it doesn't have the "Systems
Management"
option in the control panel. These two things lead me to believe
it is
not
working correctly/completely.

Your thoughts? Things I could/should check?

Thank you for your help in this matter,

Jon




"Michael Zhuo" wrote:

When you said Push keeps failing, what did mean?
I read the ccm.log below, the following messages showed that Push
worked.
================================
---> Created service "ccmsetup" on machine
"HELPDESK01". SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:04 AM 3964
(0x0F7C)
---> Started service "ccmsetup" on machine
"HELPDESK01". SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:04 AM 3964
(0x0F7C)
---> Completed request "KBGCKLWN", machine name
"HELPDESK01". SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:04 AM 3964
(0x0F7C)
Deleted request "KBGCKLWN", machine name
========================

Above messages showed that the ccmsetup ran on the client machine
HELPDESK01. Did you check the ccmsetup.log? Did you see System
Management
icon in the Control Panel?

Thanks,

Michael [MSFT]

This posting is provided "AS IS" with no warranties, and confers
no
rights.


"Jon" <Jon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0623440C-1797-45F0-921D-7C0432C2D59F@xxxxxxxxxxxxxxxx
Hello,

I am trying to get the client push to work and it keeps failing.
I had
it
working perfectly before doing a complete rebuild of my SMS
server and
now
it
hasn't worked since the rebuild.

- I am running W2K3, SMS 2003 SP2 and SQL 2005
- All computers are shoing up in the "All Systems" collection
- They are all assigned to the correct site
- I have already setup a "SMSPUSH" user account and it is added
to the
appropriate group to give it local admin permissions on all
computers.
- For good measure I even added it to the Domain Admins group
- I am able to login to the SMS server using the SMSPUSH user
account
and
connect to the registry of the desktop that I am trying to push
the
client
agent to.
- The SMS Server is setup as the MP and has the correct Site
boundaries.

- I read in someone else's post that there is a certain service
that
should
be running on my SMS server which is not even present on my
server.
- The CCM.log say the following...

Received request: "KBGCKLWN" for machine name: "HELPDESK01" on
queue:
"Incoming". SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:01 AM 2852
(0x0B24)
Stored request "KBGCKLWN", machine name "HELPDESK01", in queue
"Processing". SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:01 AM 2852
(0x0B24)
----- Started a new CCR processing thread. Thread ID is 0xf7c.
There
are
now
1 processing threads SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:03
AM 2852
(0x0B24)
Submitted request successfully SMS_CLIENT_CONFIG_MANAGER
5/1/2006
8:44:03
AM 2852 (0x0B24)
Getting a new request from queue "Incoming" after 100
millisecond
delay. SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:03 AM 2852
(0x0B24)
Waiting for change in directory "D:\SMS\inboxes\ccr.box" for
queue
"Incoming", (30 minute backup timeout).
SMS_CLIENT_CONFIG_MANAGER
5/1/2006
8:44:03 AM 2852 (0x0B24)
======>Begin Processing request: "KBGCKLWN", machine name:
"HELPDESK01" SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:03 AM 3964
(0x0F7C)
---> Trying the 'best-shot' account which worked for previous
CCRs
(index
=
0x0) SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:03 AM 3964 (0x0F7C)
---> Attempting to connect to administrative share
'\\HELPDESK01\admin$'
using account 'accounts\SMSPUSH' SMS_CLIENT_CONFIG_MANAGER
5/1/2006
8:44:03
AM 3964 (0x0F7C)
---> The 'best-shot' account has now succeeded 3 times and
failed 0
times. SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:03 AM 3964
(0x0F7C)
---> Connected to administrative share on machine HELPDESK01
using
account
'accounts\SMSPUSH' SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:03 AM
3964
(0x0F7C)
---> Attempting to make IPC connection to share
<\\HELPDESK01\IPC$> SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:03
AM 3964
(0x0F7C)
---> System OS version string "5.1" converted to
5.10 SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:03 AM 3964 (0x0F7C)
---> Could not retrieve the heartbeat time from the client
(2) SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:03 AM 3964 (0x0F7C)
---> Unable to retrieve a sites list from machine
"HELPDESK01". SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:03 AM 3964
(0x0F7C)
---> Unable to retrieve travel mode switch from machine
"HELPDESK01". SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:03 AM 3964
(0x0F7C)
---> Unable to retrieve pending command value for sms client
base
components
from machine "HELPDESK01". SMS_CLIENT_CONFIG_MANAGER 5/1/2006
8:44:03
AM
3964
(0x0F7C)
---> Could not retrieve the site config timestamp from the
client
(2) SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:03 AM 3964 (0x0F7C)
---> Unable to retrieve the mobile client version from machine
"HELPDESK01". SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:03 AM 3964
(0x0F7C)
---> Client type to be installed on HELPDESK01: Advanced
client SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:03 AM 3964
(0x0F7C)
---> Copying client files to
\\HELPDESK01\admin$\system32\ccmsetup. SMS_CLIENT_CONFIG_MANAGER
5/1/2006
8:44:03 AM 3964 (0x0F7C)
---> Copying file "D:\SMS\bin\I386\MobileClient.tcf" to
"\\HELPDESK01\admin$\system32\ccmsetup\MobileClient.tcf"
SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:03 AM 3964 (0x0F7C)
---> Copying file "D:\SMS\bin\I386\ccmsetup.exe" to
"\\HELPDESK01\admin$\system32\ccmsetup\ccmsetup.exe"
SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:03 AM 3964 (0x0F7C)
---> Created service "ccmsetup" on machine
.

Relevant Pages

  • Re: Client Push keeps failing
    ... verified all of the permissions seem correct. ... No network access account provided. ... I thought that at first too and yet the SMS console still shows this ... I am trying to get the client push to work and it keeps failing. ...
    (microsoft.public.sms.admin)
  • Re: Adv Client Install Problems??
    ... did enable site wide push but since I was testing it I ... not want it to just go through and push the client to all ... what you are refering to as the push account and advanced ... >Did you enable site wide push ir the push installation ...
    (microsoft.public.sms.setup)
  • Re: Client Push keeps failing
    ... cause push install to write a new TCF file on the client machine. ... TCF file will contain the network access account. ... Disabled the MP on the SMS server....Restarted the MP. ... permissions problem. ...
    (microsoft.public.sms.admin)
  • Re: pushing software to non domain servers
    ... access to the machine to push the client. ... network access account defined. ... >> For systems in the workgroup you will need to install the agent manually. ...
    (microsoft.public.sms.misc)
  • Re: failing to connect to Admin$ thru Domain admins account
    ... If you want to use a local machine account, add a push account that looks ... Push install will replace %MACHINENAME% with the actual machine name and use ... > is it possible to push client thru a common local admin account, ... In the Client Push Installation properties, ...
    (microsoft.public.sms.admin)
Loading