Re: Client installation frustration.

Kim,

I have more updates and information and more questions.

Tried the ping and it all worked OK from machines in the same subnet and
from servers in different subnets, all had similar network configs. There is
not, apparently, any DNS lookup issues on my network.

As I have nearly a dozen secondary sites that all have the same issues, Iam
working with 4 till I can sort this out. I have two configued one way and two
configured another way.

The first network configuration is the one that you suggested with the radio
button "Append these DNS suffixes (in order)" checked and the data is
"deg.aus" and "aus". I have also filled in the "DNS suffix for this
connection" field as "deg.aus" and checked both the "Register this
connection's addresses in DNS" and "Use this connection's DNS suffix in DNS
registration" checkboxes.

The second network configuration that I have tried is where I have filled in
the "DNS suffix for this connection" field as "deg.aus" and checked both the
"Register this connection's addresses in DNS" and "Use this connection's DNS
suffix in DNS registration" checkboxes, and then checked the radio button and
check box for "Append primary and connection specific DNS suffixes" and "
Append Parent suffixes of the primary DNS suffix"

For both configurations there were no issues pinging machines, doing an
nslookup, or mapping drives to ADMIN$ for client machines that were switched
on.

I have pasted some details below from the ccm.log file. What I care about
below and have questions about is the bits relating to \\GAB-FP01. GAB-FP01
is a file and print server that we have at one of our secondary sites. We can
ignore the \\GAB-NB1157 machine as this is a notebook and is probably not
connected to the network at the moment, which is probably why it is having
dramas. If I look at this portion of the log it seems that SMS has no
problems finding the machine and connecting to the ADMI$ share and trying to
install the client, except that it finds one already installed and the
"Forced Flag" is not turned on so I cannot install over the top. Now if I go
to the Systems Management Control Panel applet on GAB-FP01 and then look at
the Advanced tab there is no site code entered. Past Experience tells me that
if I click the discover button it will fairly quickly show up in the SMS
management console as a client.

What is this "forced flag" and how do I turn it on?

Will it help if I do?

Is there and automated way, either by script or reg hack or somethign to set
the SMS site field in the Advanced Tab of the control panel applet?

Is there any way to cancel all current requests to install clients?

======>Begin Processing request: "MLA8B4QP", machine name: "GAB-FP01"
SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:14 AM 2976 (0x0BA0)
---> Trying the 'best-shot' account which worked for previous CCRs (index =
0x0) SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:14 AM 2976 (0x0BA0)
---> Attempting to connect to administrative share '\\GAB-FP01\admin$' using
account 'DEG\SMS.Installer1' SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:14 AM
2976 (0x0BA0)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account
DEG\SMS.Installer1 (000004b3) SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:15 AM
6128 (0x17F0)
---> WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account
DEG\SMS.Installer1 (000004b3) SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:15 AM
6128 (0x17F0)
---> The 'best-shot' account has now succeeded 5 times and failed 5 times.
SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:15 AM 6128 (0x17F0)
---> Trying each entry in the SMS Client Remote Installation account list
SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:15 AM 6128 (0x17F0)
---> Attempting to connect to administrative share '\\GAB-NB1157\admin$'
using account 'DEG\SMS.Installer1' SMS_CLIENT_CONFIG_MANAGER 5/02/2006
10:34:15 AM 6128 (0x17F0)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account
DEG\SMS.Installer1 (000004b3) SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:15 AM
6128 (0x17F0)
---> WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account
DEG\SMS.Installer1 (000004b3) SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:15 AM
6128 (0x17F0)
---> Attempting to connect to administrative share '\\GAB-NB1157\admin$'
using account 'DEG\SMS.Installer2' SMS_CLIENT_CONFIG_MANAGER 5/02/2006
10:34:15 AM 6128 (0x17F0)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account
DEG\SMS.Installer2 (000004b3) SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:15 AM
6128 (0x17F0)
---> WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account
DEG\SMS.Installer2 (000004b3) SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:15 AM
6128 (0x17F0)
---> The 'best-shot' account has now succeeded 6 times and failed 5 times.
SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:19 AM 2976 (0x0BA0)
---> Connected to administrative share on machine GAB-FP01 using account
'DEG\SMS.Installer1' SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:19 AM 2976
(0x0BA0)
---> Attempting to make IPC connection to share <\\GAB-FP01\IPC$>
SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:19 AM 2976 (0x0BA0)
---> System OS version string "5.2" converted to 5.20
SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:19 AM 2976 (0x0BA0)
---> Could not retrieve the heartbeat time from the client (2)
SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:19 AM 2976 (0x0BA0)
---> Unable to retrieve a sites list from machine "GAB-FP01".
SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:19 AM 2976 (0x0BA0)
---> Unable to retrieve travel mode switch from machine "GAB-FP01".
SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:19 AM 2976 (0x0BA0)
---> Unable to retrieve pending command value for sms client base components
from machine "GAB-FP01". SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:19 AM 2976
(0x0BA0)
---> Could not retrieve the site config timestamp from the client (2)
SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:19 AM 2976 (0x0BA0)
---> Client type to be installed on GAB-FP01: Advanced client
SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:19 AM 2976 (0x0BA0)
Advanced client version detected on target machine GAB-FP01
SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:19 AM 2976 (0x0BA0)
---> Mobile client on the target machine has the same version, and 'forced'
flag is not turned on. Not processing this CCR SMS_CLIENT_CONFIG_MANAGER
5/02/2006 10:34:19 AM 2976 (0x0BA0)
---> Completed request "MLA8B4QP", machine name "GAB-FP01".
SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:19 AM 2976 (0x0BA0)
Deleted request "MLA8B4QP", machine name "GAB-FP01"
SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:19 AM 2976 (0x0BA0)
<======End request: "MLA8B4QP", machine name: "GAB-FP01".
SMS_CLIENT_CONFIG_MANAGER 5/02/2006 10:34:19 AM 2976 (0x0BA0)

I think that with all this help we might be getting close now.

Kind regards,

David Buckley.
Infrastructure Team,
Information Systems Division,
XYZ Company. :)

"Kim Oppalfens <MVP>" wrote:

try pinging one of the clients that doesn't get installed correctly which is
not on the same subnet as the site server.

--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"David Buckley" <DavidBuckley@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B8DECAE0-983B-49D1-9B8E-3DA60E4921F0@xxxxxxxxxxxxxxxx
When I was checking the DNS settings after your last post. I added
"deg.aus"
to the "DNS suffix for this connection" field.

This should have the same effect, (I hope. Please correct me if I am
wrong),
as the radio button "Append primary and connection specific DNS suffixes"
and
the Checkbox "Append parent suffixes of the primary DNS suffix" are both
checked.

DAVE

:)

PS. I really appreciate you help here, this probably seems fairly basic
and
simple, but I am not thinking as clearly as I should be due ot the strange
working hours I have been keeping of late.
"Kim Oppalfens <MVP>" wrote:

At deg.aus as a search path on your network interface at the site server.

--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"David Buckley" <DavidBuckley@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3A2442AF-F63E-4B64-A089-E6872B3908B3@xxxxxxxxxxxxxxxx
OK I have had a look and the machine is quite able to look up that host
from
the command line.

Did a ping WLG-PC1470 - it resolved the ip ok, couldn't find the
machine
on
though.

Had a closer look at the error and it is listing the machine as
WLG-PC1470.deg and not the fully qualified name of WLG-PC1470.deg.aus.
Any
ideas why this might be?

But in answer to your previous question DNS and WINS are confiured all
OK
on
the SMS Server.

:(

"David Buckley" wrote:

cheers will do.

DAVE

:)

"Kim Oppalfens <MVP>" wrote:

Host not found.
Your site server cannot resolve the computer names to ip addresses.
Check dns configuration on the site server.

--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"David Buckley" <DavidBuckley@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:18C3D7C1-FDF3-4743-A9A7-9CA977ED5E11@xxxxxxxxxxxxxxxx
Cheers for the Tip on the ccm.log and for the info on the expected
behaviour.

This is what I found in the logs bucket loads of entries like
this:

---> ERROR: Unable to connect to remote registry for machine name
"WLG-PC1470", error 53. SMS_CLIENT_CONFIG_MANAGER 3/02/2006
3:21:21
AM
2308
(0x0904)
---> ERROR: Unable to access target machine for request:
"WLG-PC1470.DEG",
machine name: "WLG-PC1470", error code:
53 SMS_CLIENT_CONFIG_MANAGER 3/02/2006 3:21:21 AM 2308 (0x0904)
Stored request "WLG-PC1470.DEG", machine name "WLG-PC1470", in
queue
"Retry". SMS_CLIENT_CONFIG_MANAGER 3/02/2006 3:21:21 AM 2308
(0x0904)
<======End request: "WLG-PC1470.DEG", machine name:
"WLG-PC1470". SMS_CLIENT_CONFIG_MANAGER 3/02/2006 3:21:21 AM 2308
(0x0904)


Any ideas on what they mean by error code 53?

Could this be due to the fact that users keep switching off their
PC's at
night?

DAVE

:)

"Kim Oppalfens <MVP>" wrote:

Check the ccm.log on the server for errors.

As for clients turning up with the primary site's sitecode, this
is
normal
behaviour.
By design advanced clients only assign to primary sites.

--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"David Buckley" <DavidBuckley@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:A0337418-A6F0-4049-A251-2F7A5B611179@xxxxxxxxxxxxxxxx
All,

I would like some assistance please. Here is the story of my
frustration.

We have one primary site and several secondary sites. Site
boundaries
have been configured, discoveries have been run. I also have
Advanced
client
push install configured, (correctly I think). I have tons of
non-clients
listed in a query and collection, but have an annoyingly small
number
of
clients, again listed in queries and collections.

Now this should not be the case as I have had one of the
admins
at a
remote site run around to every machine and install the client
from the
Msi
on the secondary site server. At this secondary site there are
nearly
250
machines and only 10 of them have turned up in the clients
collection.
Of
all
the non-clients listed 229 are assigned and 7 are not assigned.

I know that his is not an exceedingly detailed description
but I
hope
that it is enough that someone can start pointing me in the
right
direction
to try and sort this out. I think that if I can figure out why
the
clients
are not turning up as clients then I can probably work out how
to
get
this
fixed across the rest of the organisation.

Sorry I have just realised that I have not really put a
question in
here, so here it goes:

"Why are these non-clients not becoming clients when they have
had
the
client.msi installed on them?"

A second question that I have just thought of is:

"Why are my clients all turning up with Site code of my Primary
site
and
none of them turning up with the site codes from the secondary
sites?"

Kind regards,

David Buckley.
Infrastructure Team,
Information Systems Division,
XYZ Company. :)












.