Re: I Give Up. Walk Me Through It.

[Evan [MSFT]]

In the All Systems collection, does the right pane show Assigned= yes for
that box? If not, then push will not install the legacy client since the
client would subsequently realize it wasn't assigned and uninstall itself
(you can push to an unassigned advanced client since it won't uninstall
itself if unassigned). If it is assigned, then you can right click it, All
Tasks \ Install Client and install it that way.But first you must set the
options in Site Settings \ Client Installation Methods \ Client Push
Installation (don't check "enable client push installation to assigned
resources" since that would automatically push to all assigned boxes, which
is not what you want for your test). But check "workstations" if your box is
a workstation, and define a push account in the Accounts tab. Check ccm.log
on the site server to follow its progress in pushing to the box.
You can also install it manually by mapping a drive from the client box to
the cap_<site code> share, drilling down to clicomp.box\base\i386\00000409
and running smsman.exe. Judging by your result, below, you must have used
the option to automatically find a server. Instead, select the second option
button and specify the location as \\<cap server>\cap_<site code> and it
should find it and install the client. If you're not an admin when you do
this, it will create a ccr to ask the server to push the client and, again,
you can view the progress in ccm.log on the site server.

--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Wes C Addle" <anon...@discussions.microsoft.com> wrote in message
news:0D308884-1C17-479F...@microsoft.com...
> This is a bit of a strange situation and I can't seem to find any help or
similar problems.
>
> We are part of a large domain XXXX. Our department is an OU in the AD for
XXXX. I have Domain Admin privelages for the entire domain XXXX. SMS 2003 is
installed on a Windows 2003 Server within our department and is inside the
OU for our department. Inside domain XXXX we are part of a subnet,
173.23.xx.xx.
>
> I did NOT extend the AD because this copy of SMS is for our department use
only and we don't want to interfere with the entire AD for our domain.
>
> When I run any discovery I return all the systems in the entire domain? Is
there a way to stop this? I know I can specify specific subnets in network
discovery, but there are 3 locked ones in there. 1 is the main domain XXXX
and 2 of them are completely unreleated subnets that I have never seen
before. All 3 are disabled, but why are they always discovered? Even if I
turn off AD discovery they show up. Can I limit results to a certain OU in
the AD?
>
> That's not my problem however. I cannot seem to push out the standard
client install to any client. I have limited my boundaries to ONE test
machine's IP. This machine is always discovered, but never receives the
client. MP is installed and functional as is IIS. I've tried a manual
install from the client machine running smsman.exe off the server, but it
says it cannot located a Systems Management Server. Is this a WINS issue? If
so, is there a way around it??? I don't believe domain XXXX uses WINS at
all. Just looking for a little help to get 1 client started. Thanks so much
in advance to anyone who helps.

[Wes C Addle]

>> In the All Systems collection, does the right pane show Assigned= yes for
>> that box?

No it does not. Not for any machine. No clients, nothing assigned.

>> Judging by your result, below, you must have used
>> the option to automatically find a server. Instead, select the second option
>> button and specify the location as \\<cap server>\cap_<site code> and it
>> should find it and install the client.

This didn't work either. It still could not find the SMS Server. I know the CAP_ATD exists on the SMS server is shared there.

Actually, I think un-checking the "Enable Push To Assigned Resources" moved me forward a bit. Until then, my ccm.log wasn't doing anything besides resetting whenever I changed anything. Now it looks like it FINALLY contacted the server. Any idea why it got stuck? The machine it tried to install to is not showing up in the All Systems collection or query anymore.

ccm.log
--------------
Sleeping for 300 seconds...
Received request: "173_23_235_54" for machine name: "173.23.235.54" on queue: "Retry".
Stored request "173_23_235_54", machine name "173.23.235.54", in queue "Processing".
======>Begin Processing request: "173_23_235_54", machine name: "173.23.235.54"
---> Trying the account stored in the CCR (index = 0x0)~
---> Attempting to connect to administrative share '\\173.23.235.54\admin$' using account 'LABS\admintom'~
---> Connected to administrative share on machine 173.23.235.54 using account 'LABS\admintom'~
---> Attempting to make IPC connection to share <\\173.23.235.54\IPC$> ~
---> System OS version string "5.0" converted to 5.00
---> Could not retrieve the heartbeat time from the client (2)~
---> Unable to retrieve a sites list from machine "173.23.235.54".
---> Unable to retrieve travel mode switch from machine "173.23.235.54".
---> Unable to retrieve pending command value for sms client base components from machine "173.23.235.54".
---> Could not retrieve the site config timestamp from the client (2)~
---> Unable to retrieve the mobile client version from machine "173.23.235.54".
---> Copying client files to \\173.23.235.54\admin$\sms_temp.~
Submitted request successfully
Getting a new request from queue "Retry" after 100 millisecond delay.
Sleeping for 60 minutes for queue "Retry".
Found Remote Connection Called before CreateCCMBootInstallAccount <\\173.23.235.54\admin$>.~
Found Remote Connection Called before CreateCCMBootInstallAccount <\\173.23.235.54\IPC$>.~
Found Remote Connection Called After CreateCCMBootInstallAccount <\\173.23.235.54\admin$>.~
Found Remote Connection Called After CreateCCMBootInstallAccount <\\173.23.235.54\IPC$>.~
---> ERROR: Unable to create service "CCMBoot" on machine "173.23.235.54", error = 1057.
---> Failed to start the CCM Client Bootstrap service on 173.23.235.54 (1057)
---> Cannot remove service "CCMBoot" from machine "173.23.235.54", service does not exist.
---> Failed to install CCM Client Bootstrap component on client (1057)
Stored request "173_23_235_54", machine name "173.23.235.54", in queue "Retry".
<======End request: "173_23_235_54", machine name: "173.23.235.54".
CCR count in queue "Retry" is 1.
Sleeping for 605 seconds...
Thread has been inactive too long. Closing thread~
--- This thread is terminating due to inactivity
----- Terminated CCR processing thread. There are now 0 processing threads
The Site Control File has changed, parameters will be reread.
Updating Site Parameters
~-*- Normal Security Mode detected -*-
Checking configuration information for server: \\SRVATD6\.~
~Install on DC: False
Retrieving properties from the site control file.
Ignoring unrecognized property "Bootstrap Download Timeout"
Ignoring unrecognized property "Bootstrap Retry Interval"
~Security Mode Option - CCR buffering disabled.
~Default Client Type:
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::~
Site Server Name "\\SRVATD6"
Site Code "ATD"
CCM Account 1 "LABS\admintom"
CCM Account 2 ""
SMS Account "LABS\admintom"
Max CCR Processing Threads 10
CCR Processing Thread Timeout 600000 ms
Sitewide Travel Mode Switch USE CLIENT SETTING
Days Between Account Cleanups 30
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::~
Parameters for queue: "Incoming"
Inbox Path "C:\SMS\inboxes\ccr.box"
Read Queue Every DIR CHANGE NOTIFICATION
Retry CCR For 168 Hours
Report Error After ERROR REPORTING OFF
Warn when Queue Exceeds 100 CCRs
Delay Between CCRs 100 Millisec
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::~
Parameters for queue: "Retry"
Inbox Path "C:\SMS\inboxes\ccrretry.box"
Read Queue Every 60 Minutes
Retry CCR For 168 Hours
Report Error After 24 Hours
Warn when Queue Exceeds 150 CCRs
Delay Between CCRs 100 Millisec
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::~
Parameters for queue: "Processing"
Inbox Path "C:\SMS\inboxes\ccr.box\InProc"
Read Queue Every DIR CHANGE NOTIFICATION
Retry CCR For CCR DOESN'T EXIPRE
Report Error After ERROR REPORTING OFF
Warn when Queue Exceeds 150 CCRs
Delay Between CCRs 0 Millisec
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::~
Sleeping for 1200 seconds...
Waiting for change in directory "C:\SMS\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout).

[benksu]

Wes,

I had a similar issue. I cannot remember positively what my issue was, but here are a few things I know I did.

1. I am not on a WINS environment and did not extend the schema in AD, so I manaully added the to my LMHOSTS file sms_nlp and sms_<site code> on the clients, which helped get them assigned.

2. I did not have BITS, WebDAV,COM+ or ASP enabled on the SMS Site Server. Whether or not all of them had to be, I'm not 100% sure, but it helped my results. I read a few locations where all of those were mentioned as being required.

3. Also try to manually install a client on one of your test machines. In the Control Panel, you can test to see if the client can make contact with your site server. If not ( as in my case) you might need to check some of your network settings.

Hope it helps you some. I'm only a month into my testing, so I am a beginner at this, but these are some of the tips and tricks I have read about from various resources.

Ben

[Wes C Addle]

The manual install doesn't work for me for whatever reason.

From the ccm.log it appears to be get stuck creating the CCMBoot service. Can't find any info on resolving the issue.

[Wes C Addle]

Specific error in the log:

ERROR: Unable to create service "CCMBoot" on machine "xxx.xxx.xxx.xxx" error = 1057

[Evan [MSFT]]

"error = 1057" is a generic Windows error msg. From a cmd prompt, type "net
helpmsg 1057" and it will tell you it means "the account name is invalid or
does not exist, or the password is invalid for the account name specified".

--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Wes C Addle" <anon...@discussions.microsoft.com> wrote in message

news:2AAB05B3-8C6D-462D...@microsoft.com...
> Bump. Can you please take a look at the log error in my other post? Also,
is there a resource where MS posts all the various error codes? Almost
sounds too useful.

[Evan [MSFT]]

"error = 1057" is a generic Windows error msg. From a cmd prompt, type "net
helpmsg 1057" and it will tell you it means "the account name is invalid or
does not exist, or the password is invalid for the account name specified".

What's strange is that the account was able to connect to the admin$ share,
so it's obviously an admin on that box.

Try defining a SLP so it can determine its assigned site from that.

You say manually running smsman.exe still can't find the sms site. In
winnt\ms\sms\logs, there should be wnmanual.log which logs what happens when
you run smsman. Does it offer any clue about why it can't find it?

--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Wes C Addle" <anon...@discussions.microsoft.com> wrote in message

news:E2B3DF29-B1DF-4650...@microsoft.com...

[Wes C Addle]

FINALLY got the client to accept the bootstrap (or so it seems). In the task manager I can see a bunch of services run and stop, but nothing else happens. Then .ccr file is moved back to the retry box. The CliCore.log on the client system says setup was successful, but the ccm.log says otherwise:

Received request: "ATDC00630" for machine name: "ATDC00630" on queue: "Retry".
Error event time has expired for Request "ATDC00630" for machine "ATDC00630".
STATMSG: ID=3010 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_CLIENT_CONFIG_MANAGER" SYS=SRVATD6 SITE=ATD PID=1848 TID=1676 GMTDATE=Wed Jun 09 17:11:44.591 2004 ISTR0="36" ISTR1="ATDC00630" ISTR2="168" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
Stored request "ATDC00630", machine name "ATDC00630", in queue "Processing".
======>Begin Processing request: "ATDC00630", machine name: "ATDC00630"

---> Trying the account stored in the CCR (index = 0x0)~

---> Attempting to connect to administrative share '\\ATDC00630\admin$' using account 'LABS\admintom'~
---> Connected to administrative share on machine ATDC00630 using account 'LABS\admintom'~
---> Attempting to make IPC connection to share <\\ATDC00630\IPC$> ~

---> System OS version string "5.0" converted to 5.00
---> Could not retrieve the heartbeat time from the client (2)~

---> Unable to retrieve a sites list from machine "ATDC00630".
---> Unable to retrieve travel mode switch from machine "ATDC00630".
---> Unable to retrieve pending command value for sms client base components from machine "ATDC00630".

---> Could not retrieve the site config timestamp from the client (2)~

---> Unable to retrieve the mobile client version from machine "ATDC00630".
---> Copying client files to \\ATDC00630\admin$\sms_temp.~
---> Copying file "C:\SMS\inboxes\clicomp.src\base\I386\CCMCore.exe" to "\\ATDC00630\admin$\sms_temp\CCMCore.exe"

Submitted request successfully
Getting a new request from queue "Retry" after 100 millisecond delay.
Sleeping for 60 minutes for queue "Retry".

---> Copying file "C:\SMS\inboxes\clicomp.src\base\compver.ini" to "\\ATDC00630\admin$\sms_temp\compver.ini"
---> Copying file "C:\SMS\inboxes\clidata.src\cli_inst.cfg" to "\\ATDC00630\admin$\sms_temp\cli_inst.cfg"
---> Copying file "C:\SMS\inboxes\clidata.src\caplist.ini" to "\\ATDC00630\admin$\sms_temp\caplist.ini"
---> Copying file "C:\SMS\bin\I386\CCMData.tcf" to "\\ATDC00630\admin$\sms_temp\CCMData.tcf"
---> Copying file "C:\SMS\bin\I386\CCMBtLdr.exe" to "\\ATDC00630\admin$\sms_temp\CCMBtLdr.exe"
---> Copying file "C:\SMS\bin\I386\clilog.dll" to "\\ATDC00630\admin$\sms_temp\clilog.dll"
Found Remote Connection Called before CreateCCMBootInstallAccount <\\ATDC00630\admin$>.~
Found Remote Connection Called before CreateCCMBootInstallAccount <\\ATDC00630\IPC$>.~
Found Remote Connection Called After CreateCCMBootInstallAccount <\\ATDC00630\admin$>.~
Found Remote Connection Called After CreateCCMBootInstallAccount <\\ATDC00630\IPC$>.~
---> Created service "CCMBoot" on machine "ATDC00630".
---> Started service "CCMBoot" on machine "ATDC00630".
---> Waiting for service to stop
---> Service stopped
---> Successfully Started the CCM Client Bootstrap service on ATDC00630
CCR count in queue "Retry" is 0.
Sleeping for 627 seconds...
---> Service "CCMBoot" on machine "ATDC00630" successfully deleted.
---> Moving request to retry queue for verification "ATDC00630", machine name "ATDC00630".
Stored request "ATDC00630", machine name "ATDC00630", in queue "Retry".
<======End request: "ATDC00630", machine name: "ATDC00630".

Why is it not finishing installtion? Thanks.

[Evan [MSFT]]

So whatever the invalid account or pw issue was, it apparently got resolved
and the push proceded ok. The part at the end of your log,
"Moving request to retry queue for verification", is normal. Ccm checks the
client one more time after it installs the client service to verify things
are working (notice it says it's moving it there for verification), then
deletes the ccr. You should see the sms applet on the client with components
installed and the client service running. If this is not the case, check
ccim.log on the client to see what the matter is.

--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Wes C Addle" <anon...@discussions.microsoft.com> wrote in message

news:FC9510D8-43FE-40A6...@microsoft.com...

[Evan [MSFT]]

And regarding the earlier 1057 error when it tried to install the client
service, dev says "For some reason the client service account is invalid -
it may have been deleted or the password is bad. The account may already be
in the process of being deleted from a previous push. Try rebooting the
machine to completely delete the account. Then, push again.".

This would explain why ccm had the rights to connect to the client box but
still couldn't install the client service.

--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Wes C Addle" <anon...@discussions.microsoft.com> wrote in message

news:FC9510D8-43FE-40A6...@microsoft.com...