Re: Client Push keeps failing

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
"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
"HELPDESK01" SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:04 AM 3964 (0x0F7C)
<======End request: "KBGCKLWN", machine name:
"HELPDESK01". SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:44:04 AM 3964 (0x0F7C)
Thread has been inactive too long. Closing
thread SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:54:04 AM 3964 (0x0F7C)
--- This thread is terminating due to
inactivity SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:54:04 AM 3964 (0x0F7C)
----- Terminated CCR processing thread. There are now 0 processing
threads SMS_CLIENT_CONFIG_MANAGER 5/1/2006 8:54:04 AM 3964 (0x0F7C)
The Site Control File has not changed since the last parameter
update. SMS_CLIENT_CONFIG_MANAGER 5/1/2006 9:00:01 AM 2672 (0x0A70)
Updating Site Parameters SMS_CLIENT_CONFIG_MANAGER 5/1/2006 9:00:01 AM
2672
(0x0A70)
MP Port: 80 SMS_CLIENT_CONFIG_MANAGER 5/1/2006 9:00:01 AM 2672 (0x0A70)
Default MP: SMS SMS_CLIENT_CONFIG_MANAGER 5/1/2006 9:00:01 AM 2672
(0x0A70)


- I tried removing the SMSPUSH account, closing the SMS console,
restarting
the server, and putting the SMSPUSH account back in as the PUSH account.

Now, I get this error message in my SMS_CLIENT_CONFIG_MANAGER...

The SMS Client Remote Installation account list has been reset to a single
account.

Possible cause: A version of the SMS Administrator console earlier than
SMS
2.0 SP2 was used to modify the list. These earlier versions recognize and
retain only the first account in the list.
Solution: To maintain multiple SMS Client Remote Installation accounts for
this site, use the latest version of the SMS Administrator console to
manage
the account list.

NOTE: Before removing the PUSH account and re-adding it, the
SMS_CLIENT_CONFIG_MANAGER showed no error messages and yet I still cannot
us
SMS to PUSH clients agents out to the desktops.

- I am able to pull the client agent down from the Agent Install share by
logging into the desktop and connecting to the share on the SMS Server.

What other information can I provide that might shed light on the answer
to
my dilemma?

Thanks for your help with this question!

Jon



.

Relevant Pages

  • Re: Cannot install client
    ... I have exactly the same errors on my SMS 2003 site where I have about ... Client itself it has the Client installed, ... > - the account has no network priviledges ... There is only one SMS server so I ...
    (microsoft.public.sms.misc)
  • Re: Adv Client with Workgroup Computers
    ... I was trying to use the SMS tools from the SMS server to initiate harware ... Inv for example the account is a domain account but the Client PC is in a ... Is there a procedure for installing the ADV client localy on a workgroup ... I have manually added to the WINS server. ...
    (microsoft.public.sms.admin)
  • Re: Advanced Client install nightmare
    ... I can successfully install manually using the SMS account. ... MS Client Configuration Manager cannot install the Advanced Client to ...
    (microsoft.public.sms.admin)
  • Re: Client Push keeps failing
    ... Try running the mptroubleshooter tool from sms toolkit 2. ... I saw a post where it was suggested to have the client install using the " ... No network access account provided. ... The SMS Server is setup as the MP and has the correct Site ...
    (microsoft.public.sms.admin)
  • Re: Client Push keeps failing
    ... Also if the management point is running - try doing a reset of the management ... Try running the mptroubleshooter tool from sms toolkit 2. ... I saw a post where it was suggested to have the client install using the " ... The SMS Server is setup as the MP and has the correct Site ...
    (microsoft.public.sms.admin)
Loading