Very Computer

On many, but not all, of the newer XP Workstations that I've recently
deployed on my LAN, the SMS client installation remains incomplete. In
the SMS Control Panel applet on the client workstation, the Sites tab
lists the site but no time stamp. The Components tab lists the
components but no status. The General tab lists all the normal
information. Advertised Programs and Advertised Programs Monitor applets

do not appear in Control Panel.

Windows Networking Logon discovery is enabled for the site, but when
these workstations log on to the domain, the SMS Logon script doesn't
run. Instead, a generic command prompt opens for awhile, but remains
blank. Attempts to install the client manually fail also.

On some of the affected workstations, ccim.log is never created.
WN_LOGON.LOG includes these entries:

Some Discovery Methods failed~  $$<CliEx32.dll><Fri Jun 13 07:55:27.577
2003><thread=5636 (0x1604)>
 STATUS CALLBACK -  -  $$<C:\WINDOWS\MS\SMS\CORE\BIN\Boot32wn.exe><Fri
Jun 13 07:55:27.577 2003><thread=5636 (0x1604)>
Warning: Unable to resolve server path
"MSWNET:\\MySiteServerName\SMSLOGON\" - The system cannot find the file
specified.~~  $$<CliEx32.dll><Fri Jun 13 07:55:27.593 2003><thread=5636
(0x1604)>
Warning: No NAL support. All file copies will be attempted outside of
NAL

On at least one affected workstation, ccim.log is created and includes
these entries:

** Base Component Installation Thread is starting **  $$<CCIM32><Fri Jun

13 12:30:10.611 2003><thread=1964 (0x7AC)>
Getting ownership of bootstrap mutex...  $$<CCIM32><Fri Jun 13
12:30:10.611 2003><thread=1964 (0x7AC)>
Client core file version (from cliver.exe) is 2.00.1493.4009
$$<CCIM32><Fri Jun 13 12:30:10.611 2003><thread=1964 (0x7AC)>
Abstract export ABEXPRT:\\CAP List for site S00 not accessable
$$<CCIM32><Fri Jun 13 12:30:10.611 2003><thread=1964 (0x7AC)>
Abstract export ABEXPRT:\\CAP List for site S00 not accessable
$$<CCIM32><Fri Jun 13 12:30:11.111 2003><thread=1964 (0x7AC)>
Abstract export ABEXPRT:\\CAP List for site S00 not accessable
$$<CCIM32><Fri Jun 13 12:30:11.611 2003><thread=1964 (0x7AC)>
Abstract export ABEXPRT:\\CAP List for site S00 not accessable
$$<CCIM32><Fri Jun 13 12:30:12.111 2003><thread=1964 (0x7AC)>
Abstract export ABEXPRT:\\CAP List for site S00 not accessable
$$<CCIM32><Fri Jun 13 12:30:12.611 2003><thread=1964 (0x7AC)>
Abstract export ABEXPRT:\\CAP List for site S00 not accessable
$$<CCIM32><Fri Jun 13 12:30:13.111 2003><thread=1964 (0x7AC)>
Abstract export ABEXPRT:\\CAP List for site S00 not accessable
$$<CCIM32><Fri Jun 13 12:30:13.611 2003><thread=1964 (0x7AC)>
Abstract export ABEXPRT:\\CAP List for site S00 not accessable
$$<CCIM32><Fri Jun 13 12:30:14.111 2003><thread=1964 (0x7AC)>
Abstract export ABEXPRT:\\CAP List for site S00 not accessable
$$<CCIM32><Fri Jun 13 12:30:14.611 2003><thread=1964 (0x7AC)>
Abstract export ABEXPRT:\\CAP List for site S00 not accessable
$$<CCIM32><Fri Jun 13 12:30:15.111 2003><thread=1964 (0x7AC)>
ERROR: could not find a client access point to finish installing.
Exitting.   $$<CCIM32><Fri Jun 13 12:30:15.611 2003><thread=1964
(0x7AC)>
** Base Component Installation Thread is finished **  $$<CCIM32><Fri Jun

13 12:30:15.611 2003><thread=1964 (0x7AC)>
Base install DLL finished.  $$<CCIM32><Fri Jun 13 12:30:15.611
2003><thread=1964 (0x7AC)>
Base setup status value not set to installed  $$<CCIM32><Fri Jun 13
12:30:15.611 2003><thread=1964 (0x7AC)>
- CCIM32:  Retry in 60 minutes  $$<CCIM32><Fri Jun 13 12:30:15.611
2003><thread=1964 (0x7AC)>

 This is SMS 2.0 SP4, single site, in single Windows 2000 Active
Directory Domain. Any suggestions would be very gratefully appreciated.

First of all, most client installation problems occur
because of object rights. First thing I would check is
does the SMSService account have sufficient rights to read
and write to the smslogon folder on the site server? Next
I would see if the SMSCliSvcAcct& is created on the client
and it has admin priveleges. Also look in the
administrator console under Site Database, Site
Hierarchy, "Site Code", Site Settings, Connection
Accounts, Client and note the Domain account name listed.
Verify, in AD User and Computers, that the account has not
been locked out.
*****Never change the password on that account*******
There is a pdf available from Microsft that goes into
great detail on sms security. Most importantly it explains
which accounts run which processes and services. To begin
the setup trouble shooting problem start at page 138.
This was a little long but I hope it's helpful.

TechEd MCSA

Quote:

>On some of the affected workstations, ccim.log is never
created.
>WN_LOGON.LOG includes these entries:

>Some Discovery Methods failed~  $$<CliEx32.dll><Fri Jun
13 07:55:27.577
>2003><thread=5636 (0x1604)>
> STATUS CALLBACK -  -  

$$<C:\WINDOWS\MS\SMS\CORE\BIN\Boot32wn.exe><Fri

Quote:>Jun 13 07:55:27.577 2003><thread=5636 (0x1604)>
>Warning: Unable to resolve server path
>"MSWNET:\\MySiteServerName\SMSLOGON\" - The system cannot
find the file
>specified.~~  $$<CliEx32.dll><Fri Jun 13 07:55:27.593
2003><thread=5636
>(0x1604)>
>Warning: No NAL support. All file copies will be

attempted outside of

Quote:>NAL

>On at least one affected workstation, ccim.log is created
and includes
>these entries:

>** Base Component Installation Thread is starting **  
$$<CCIM32><Fri Jun

>13 12:30:10.611 2003><thread=1964 (0x7AC)>
>Getting ownership of bootstrap mutex...  $$<CCIM32><Fri
Jun 13
>12:30:10.611 2003><thread=1964 (0x7AC)>
>Client core file version (from cliver.exe) is
2.00.1493.4009
>$$<CCIM32><Fri Jun 13 12:30:10.611 2003><thread=1964
(0x7AC)>
>Abstract export ABEXPRT:\\CAP List for site S00 not
accessable
>$$<CCIM32><Fri Jun 13 12:30:10.611 2003><thread=1964
(0x7AC)>
>Abstract export ABEXPRT:\\CAP List for site S00 not
accessable
>$$<CCIM32><Fri Jun 13 12:30:11.111 2003><thread=1964
(0x7AC)>
>Abstract export ABEXPRT:\\CAP List for site S00 not
accessable
>$$<CCIM32><Fri Jun 13 12:30:11.611 2003><thread=1964
(0x7AC)>
>Abstract export ABEXPRT:\\CAP List for site S00 not
accessable
>$$<CCIM32><Fri Jun 13 12:30:12.111 2003><thread=1964
(0x7AC)>
>Abstract export ABEXPRT:\\CAP List for site S00 not
accessable
>$$<CCIM32><Fri Jun 13 12:30:12.611 2003><thread=1964
(0x7AC)>
>Abstract export ABEXPRT:\\CAP List for site S00 not
accessable
>$$<CCIM32><Fri Jun 13 12:30:13.111 2003><thread=1964
(0x7AC)>
>Abstract export ABEXPRT:\\CAP List for site S00 not
accessable
>$$<CCIM32><Fri Jun 13 12:30:13.611 2003><thread=1964
(0x7AC)>
>Abstract export ABEXPRT:\\CAP List for site S00 not
accessable
>$$<CCIM32><Fri Jun 13 12:30:14.111 2003><thread=1964
(0x7AC)>
>Abstract export ABEXPRT:\\CAP List for site S00 not
accessable
>$$<CCIM32><Fri Jun 13 12:30:14.611 2003><thread=1964
(0x7AC)>
>Abstract export ABEXPRT:\\CAP List for site S00 not
accessable
>$$<CCIM32><Fri Jun 13 12:30:15.111 2003><thread=1964
(0x7AC)>
>ERROR: could not find a client access point to finish
installing.
>Exitting.   $$<CCIM32><Fri Jun 13 12:30:15.611
2003><thread=1964
>(0x7AC)>
>** Base Component Installation Thread is finished **  
$$<CCIM32><Fri Jun

>13 12:30:15.611 2003><thread=1964 (0x7AC)>
>Base install DLL finished.  $$<CCIM32><Fri Jun 13
12:30:15.611
>2003><thread=1964 (0x7AC)>
>Base setup status value not set to installed  

$$<CCIM32><Fri Jun 13

Quote:>12:30:15.611 2003><thread=1964 (0x7AC)>
>- CCIM32:  Retry in 60 minutes  $$<CCIM32><Fri Jun 13
12:30:15.611
>2003><thread=1964 (0x7AC)>

> This is SMS 2.0 SP4, single site, in single Windows 2000
Active
>Directory Domain. Any suggestions would be very

gratefully appreciated.

Quote:

>.

Just realized that I didn't provide a link to the pdf from
Microsft. Sorry! Here it is.
http://www.microsoft.com/smserver/docs/secessentials.pdf
TechEd - MCSA

Quote:>-----Original Message-----
>On many, but not all, of the newer XP Workstations that
I've recently
>deployed on my LAN, the SMS client installation remains
incomplete. In
>the SMS Control Panel applet on the client workstation,
the Sites tab
>lists the site but no time stamp. The Components tab
lists the
>components but no status. The General tab lists all the
normal
>information. Advertised Programs and Advertised Programs
Monitor applets

>do not appear in Control Panel.

>Windows Networking Logon discovery is enabled for the
site, but when
>these workstations log on to the domain, the SMS Logon
script doesn't
>run. Instead, a generic command prompt opens for awhile,
but remains
>blank. Attempts to install the client manually fail also.

>On some of the affected workstations, ccim.log is never
created.
>WN_LOGON.LOG includes these entries:

>Some Discovery Methods failed~  $$<CliEx32.dll><Fri Jun
13 07:55:27.577
>2003><thread=5636 (0x1604)>
> STATUS CALLBACK -  -  

$$<C:\WINDOWS\MS\SMS\CORE\BIN\Boot32wn.exe><Fri

Quote:>Jun 13 07:55:27.577 2003><thread=5636 (0x1604)>
>Warning: Unable to resolve server path
>"MSWNET:\\MySiteServerName\SMSLOGON\" - The system cannot
find the file
>specified.~~  $$<CliEx32.dll><Fri Jun 13 07:55:27.593
2003><thread=5636
>(0x1604)>
>Warning: No NAL support. All file copies will be

attempted outside of

Quote:>NAL

>On at least one affected workstation, ccim.log is created
and includes
>these entries:

>** Base Component Installation Thread is starting **  
$$<CCIM32><Fri Jun

>13 12:30:10.611 2003><thread=1964 (0x7AC)>
>Getting ownership of bootstrap mutex...  $$<CCIM32><Fri
Jun 13
>12:30:10.611 2003><thread=1964 (0x7AC)>
>Client core file version (from cliver.exe) is
2.00.1493.4009
>$$<CCIM32><Fri Jun 13 12:30:10.611 2003><thread=1964
(0x7AC)>
>Abstract export ABEXPRT:\\CAP List for site S00 not
accessable
>$$<CCIM32><Fri Jun 13 12:30:10.611 2003><thread=1964
(0x7AC)>
>Abstract export ABEXPRT:\\CAP List for site S00 not
accessable
>$$<CCIM32><Fri Jun 13 12:30:11.111 2003><thread=1964
(0x7AC)>
>Abstract export ABEXPRT:\\CAP List for site S00 not
accessable
>$$<CCIM32><Fri Jun 13 12:30:11.611 2003><thread=1964
(0x7AC)>
>Abstract export ABEXPRT:\\CAP List for site S00 not
accessable
>$$<CCIM32><Fri Jun 13 12:30:12.111 2003><thread=1964
(0x7AC)>
>Abstract export ABEXPRT:\\CAP List for site S00 not
accessable
>$$<CCIM32><Fri Jun 13 12:30:12.611 2003><thread=1964
(0x7AC)>
>Abstract export ABEXPRT:\\CAP List for site S00 not
accessable
>$$<CCIM32><Fri Jun 13 12:30:13.111 2003><thread=1964
(0x7AC)>
>Abstract export ABEXPRT:\\CAP List for site S00 not
accessable
>$$<CCIM32><Fri Jun 13 12:30:13.611 2003><thread=1964
(0x7AC)>
>Abstract export ABEXPRT:\\CAP List for site S00 not
accessable
>$$<CCIM32><Fri Jun 13 12:30:14.111 2003><thread=1964
(0x7AC)>
>Abstract export ABEXPRT:\\CAP List for site S00 not
accessable
>$$<CCIM32><Fri Jun 13 12:30:14.611 2003><thread=1964
(0x7AC)>
>Abstract export ABEXPRT:\\CAP List for site S00 not
accessable
>$$<CCIM32><Fri Jun 13 12:30:15.111 2003><thread=1964
(0x7AC)>
>ERROR: could not find a client access point to finish
installing.
>Exitting.   $$<CCIM32><Fri Jun 13 12:30:15.611
2003><thread=1964
>(0x7AC)>
>** Base Component Installation Thread is finished **  
$$<CCIM32><Fri Jun

>13 12:30:15.611 2003><thread=1964 (0x7AC)>
>Base install DLL finished.  $$<CCIM32><Fri Jun 13
12:30:15.611
>2003><thread=1964 (0x7AC)>
>Base setup status value not set to installed  

$$<CCIM32><Fri Jun 13

Quote:>12:30:15.611 2003><thread=1964 (0x7AC)>
>- CCIM32:  Retry in 60 minutes  $$<CCIM32><Fri Jun 13
12:30:15.611
>2003><thread=1964 (0x7AC)>

> This is SMS 2.0 SP4, single site, in single Windows 2000
Active
>Directory Domain. Any suggestions would be very

gratefully appreciated.

Quote:

>.

Hi Burr,

your Client cannot access a CAP.
I would suggest to add another cap to your site, so that if your client
cannot access one CAP, it can connect to another one.

--
Martin Santospirito
Support Professional
Microsoft Product Support Services

(Microsoft kann fr die Richtigkeit und Vollst?ndigkeit der Inhalte in
dieser Newsgroup keine Haftung bernehmen.)
This posting is provided "AS IS" with no warranties, and confers no rights.

Quote:> On many, but not all, of the newer XP Workstations that I've recently
> deployed on my LAN, the SMS client installation remains incomplete. In
> the SMS Control Panel applet on the client workstation, the Sites tab
> lists the site but no time stamp. The Components tab lists the
> components but no status. The General tab lists all the normal
> information. Advertised Programs and Advertised Programs Monitor applets

> do not appear in Control Panel.

> Windows Networking Logon discovery is enabled for the site, but when
> these workstations log on to the domain, the SMS Logon script doesn't
> run. Instead, a generic command prompt opens for awhile, but remains
> blank. Attempts to install the client manually fail also.

> On some of the affected workstations, ccim.log is never created.
> WN_LOGON.LOG includes these entries:

> Some Discovery Methods failed~  $$<CliEx32.dll><Fri Jun 13 07:55:27.577
> 2003><thread=5636 (0x1604)>
>  STATUS CALLBACK -  -  $$<C:\WINDOWS\MS\SMS\CORE\BIN\Boot32wn.exe><Fri
> Jun 13 07:55:27.577 2003><thread=5636 (0x1604)>
> Warning: Unable to resolve server path
> "MSWNET:\\MySiteServerName\SMSLOGON\" - The system cannot find the file
> specified.~~  $$<CliEx32.dll><Fri Jun 13 07:55:27.593 2003><thread=5636
> (0x1604)>
> Warning: No NAL support. All file copies will be attempted outside of
> NAL

> On at least one affected workstation, ccim.log is created and includes
> these entries:

> ** Base Component Installation Thread is starting **  $$<CCIM32><Fri Jun

> 13 12:30:10.611 2003><thread=1964 (0x7AC)>
> Getting ownership of bootstrap mutex...  $$<CCIM32><Fri Jun 13
> 12:30:10.611 2003><thread=1964 (0x7AC)>
> Client core file version (from cliver.exe) is 2.00.1493.4009
> $$<CCIM32><Fri Jun 13 12:30:10.611 2003><thread=1964 (0x7AC)>
> Abstract export ABEXPRT:\\CAP List for site S00 not accessable
> $$<CCIM32><Fri Jun 13 12:30:10.611 2003><thread=1964 (0x7AC)>
> Abstract export ABEXPRT:\\CAP List for site S00 not accessable
> $$<CCIM32><Fri Jun 13 12:30:11.111 2003><thread=1964 (0x7AC)>
> Abstract export ABEXPRT:\\CAP List for site S00 not accessable
> $$<CCIM32><Fri Jun 13 12:30:11.611 2003><thread=1964 (0x7AC)>
> Abstract export ABEXPRT:\\CAP List for site S00 not accessable
> $$<CCIM32><Fri Jun 13 12:30:12.111 2003><thread=1964 (0x7AC)>
> Abstract export ABEXPRT:\\CAP List for site S00 not accessable
> $$<CCIM32><Fri Jun 13 12:30:12.611 2003><thread=1964 (0x7AC)>
> Abstract export ABEXPRT:\\CAP List for site S00 not accessable
> $$<CCIM32><Fri Jun 13 12:30:13.111 2003><thread=1964 (0x7AC)>
> Abstract export ABEXPRT:\\CAP List for site S00 not accessable
> $$<CCIM32><Fri Jun 13 12:30:13.611 2003><thread=1964 (0x7AC)>
> Abstract export ABEXPRT:\\CAP List for site S00 not accessable
> $$<CCIM32><Fri Jun 13 12:30:14.111 2003><thread=1964 (0x7AC)>
> Abstract export ABEXPRT:\\CAP List for site S00 not accessable
> $$<CCIM32><Fri Jun 13 12:30:14.611 2003><thread=1964 (0x7AC)>
> Abstract export ABEXPRT:\\CAP List for site S00 not accessable
> $$<CCIM32><Fri Jun 13 12:30:15.111 2003><thread=1964 (0x7AC)>
> ERROR: could not find a client access point to finish installing.
> Exitting.   $$<CCIM32><Fri Jun 13 12:30:15.611 2003><thread=1964
> (0x7AC)>
> ** Base Component Installation Thread is finished **  $$<CCIM32><Fri Jun

> 13 12:30:15.611 2003><thread=1964 (0x7AC)>
> Base install DLL finished.  $$<CCIM32><Fri Jun 13 12:30:15.611
> 2003><thread=1964 (0x7AC)>
> Base setup status value not set to installed  $$<CCIM32><Fri Jun 13
> 12:30:15.611 2003><thread=1964 (0x7AC)>
> - CCIM32:  Retry in 60 minutes  $$<CCIM32><Fri Jun 13 12:30:15.611
> 2003><thread=1964 (0x7AC)>

>  This is SMS 2.0 SP4, single site, in single Windows 2000 Active
> Directory Domain. Any suggestions would be very gratefully appreciated.

Intresting I seem to have the same problem.
Out of ~300 Clients there are 29 installed with Client and assigned Site.
140 Clients have the Client Software installed but no assigned site.

Ive read the conversation. Ive seen that on the Clients with partly
installed SMS Client software, the die local SMS Client Account is missing.
Could that be the reason, and where to fix it? Because I dont see any error
messages on the Server nor on the Clients.

Thanks
A.Paesch

Quote:> First of all, most client installation problems occur
> because of object rights. First thing I would check is
> does the SMSService account have sufficient rights to read
> and write to the smslogon folder on the site server? Next
> I would see if the SMSCliSvcAcct& is created on the client
> and it has admin priveleges. Also look in the
> administrator console under Site Database, Site
> Hierarchy, "Site Code", Site Settings, Connection
> Accounts, Client and note the Domain account name listed.
> Verify, in AD User and Computers, that the account has not
> been locked out.
> *****Never change the password on that account*******
> There is a pdf available from Microsft that goes into
> great detail on sms security. Most importantly it explains
> which accounts run which processes and services. To begin
> the setup trouble shooting problem start at page 138.
> This was a little long but I hope it's helpful.

> TechEd MCSA

> >On some of the affected workstations, ccim.log is never
> created.
> >WN_LOGON.LOG includes these entries:

> >Some Discovery Methods failed~  $$<CliEx32.dll><Fri Jun
> 13 07:55:27.577
> >2003><thread=5636 (0x1604)>
> > STATUS CALLBACK -  -
> $$<C:\WINDOWS\MS\SMS\CORE\BIN\Boot32wn.exe><Fri
> >Jun 13 07:55:27.577 2003><thread=5636 (0x1604)>
> >Warning: Unable to resolve server path
> >"MSWNET:\\MySiteServerName\SMSLOGON\" - The system cannot
> find the file
> >specified.~~  $$<CliEx32.dll><Fri Jun 13 07:55:27.593
> 2003><thread=5636
> >(0x1604)>
> >Warning: No NAL support. All file copies will be
> attempted outside of
> >NAL

> >On at least one affected workstation, ccim.log is created
> and includes
> >these entries:

> >** Base Component Installation Thread is starting **
> $$<CCIM32><Fri Jun

> >13 12:30:10.611 2003><thread=1964 (0x7AC)>
> >Getting ownership of bootstrap mutex...  $$<CCIM32><Fri
> Jun 13
> >12:30:10.611 2003><thread=1964 (0x7AC)>
> >Client core file version (from cliver.exe) is
> 2.00.1493.4009
> >$$<CCIM32><Fri Jun 13 12:30:10.611 2003><thread=1964
> (0x7AC)>
> >Abstract export ABEXPRT:\\CAP List for site S00 not
> accessable
> >$$<CCIM32><Fri Jun 13 12:30:10.611 2003><thread=1964
> (0x7AC)>
> >Abstract export ABEXPRT:\\CAP List for site S00 not
> accessable
> >$$<CCIM32><Fri Jun 13 12:30:11.111 2003><thread=1964
> (0x7AC)>
> >Abstract export ABEXPRT:\\CAP List for site S00 not
> accessable
> >$$<CCIM32><Fri Jun 13 12:30:11.611 2003><thread=1964
> (0x7AC)>
> >Abstract export ABEXPRT:\\CAP List for site S00 not
> accessable
> >$$<CCIM32><Fri Jun 13 12:30:12.111 2003><thread=1964
> (0x7AC)>
> >Abstract export ABEXPRT:\\CAP List for site S00 not
> accessable
> >$$<CCIM32><Fri Jun 13 12:30:12.611 2003><thread=1964
> (0x7AC)>
> >Abstract export ABEXPRT:\\CAP List for site S00 not
> accessable
> >$$<CCIM32><Fri Jun 13 12:30:13.111 2003><thread=1964
> (0x7AC)>
> >Abstract export ABEXPRT:\\CAP List for site S00 not
> accessable
> >$$<CCIM32><Fri Jun 13 12:30:13.611 2003><thread=1964
> (0x7AC)>
> >Abstract export ABEXPRT:\\CAP List for site S00 not
> accessable
> >$$<CCIM32><Fri Jun 13 12:30:14.111 2003><thread=1964
> (0x7AC)>
> >Abstract export ABEXPRT:\\CAP List for site S00 not
> accessable
> >$$<CCIM32><Fri Jun 13 12:30:14.611 2003><thread=1964
> (0x7AC)>
> >Abstract export ABEXPRT:\\CAP List for site S00 not
> accessable
> >$$<CCIM32><Fri Jun 13 12:30:15.111 2003><thread=1964
> (0x7AC)>
> >ERROR: could not find a client access point to finish
> installing.
> >Exitting.   $$<CCIM32><Fri Jun 13 12:30:15.611
> 2003><thread=1964
> >(0x7AC)>
> >** Base Component Installation Thread is finished **
> $$<CCIM32><Fri Jun

> >13 12:30:15.611 2003><thread=1964 (0x7AC)>
> >Base install DLL finished.  $$<CCIM32><Fri Jun 13
> 12:30:15.611
> >2003><thread=1964 (0x7AC)>
> >Base setup status value not set to installed
> $$<CCIM32><Fri Jun 13
> >12:30:15.611 2003><thread=1964 (0x7AC)>
> >- CCIM32:  Retry in 60 minutes  $$<CCIM32><Fri Jun 13
> 12:30:15.611
> >2003><thread=1964 (0x7AC)>

> > This is SMS 2.0 SP4, single site, in single Windows 2000
> Active
> >Directory Domain. Any suggestions would be very
> gratefully appreciated.

> >.

Hi Martin,

Thanks for the response. I had a vague notion that communication with the CAP
was a problem, and so about five days ago I increased the number of CAPS from
one to three. That has not helped so far. Nonetheless, I'm certain that CAP
access remains a key issue wioth these clients. Their logs contain a variety of
entries pointing to this. Can anyone suggest other possible reasons why these
XP machines might be failing to access CAPs?

The perplexing thing about this issue is that client installation fails at a
variety of points. On at least one affected workstation, SMSCliSvcAcct& is not
even created. On most affected workstations, SMSCliSvcAcct& is present and is a
member of the local Administrators group. On some affected workstations, client
installation does not even progress to the point where ccim.log is created; on
others, ccim.log and numerous others are created, but components do not get
installed. Other workstations, seemingly identical to the affected
workstations, install their SMS clients and function perfectly as members of
the site.

The one unifying thread I can find is that all affected workstations fail to
run smsls.bat when they log on to the domain. Instead, a generic command-prompt
window opens briefly. Its title bar reads "C:\Windows\System32\cmd.exe", where
the titile bar of the command prompt of an unaffected workstation will of
course always feature the name of one of our domain controllers followed by
"NETLOGON\smsls.bat"

-Burr Baldwin

I've had a breakthrough here and am homing in on the source of the problem. It
seems to be caused by inadequate access permissions to some registry keys on the
client workstation.

As an experiment, I decided to open up permissions on one affected workstation
and give Full Control of HKLM\Software\Microsoft\NAL,
HKLM\Software\Microsoft\SMS, and all of their subkeys to Everyone. It took some
wrestling around. I had to take ownership of some keys, etc. Once I finished,
though, the client components all installed, and the workstation even proceeded
to run some current adverti*ts!

After I finished opening up permissions on the NAL key and subkeys, the line
that read "Abstract export ABEXPRT:\\CAP List for site S00 not accessable"
stopped appearing in ccim.log. However, the client components did not appear to
install until I opened up permissions on the SMS key and subkeys.

I think that the problem keys were these:
HKLM\Software\Microsoft\NAL\CLIENT\AbExpertDb
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Client\Client Components\Hardware
Inventory Agent\Sites
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Client\Client Components\Software
Inventory Agent\Sites
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Client\Sites
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Client\Client Components\Remote
Control\Wuser32Initialized
These were the keys that I could not initially open or edit, even though I was
logged on with Local Admin/DomainAdmin privileges. Once I gained control of
these keys, I found that several of them had permissions for only two user
accounts: SYSTEM, and a mysterious account identified only by a question-mark
icon and a GUID.

So now I need to learn two things:

1) What are the proper permissions for the SMS and NAL keys and their subkeys? I
don't want to assign Full Control to Everyone as a permanent workaround. Maybe
someone can guide me toward some helpful documentation, or maybe I can figure it
out by examining the registries of my properly-functioning XP clients.

2) What caused some, but only some, of my XP workstations to have inadequate
permissions to these keys? I need to figure this out to prevent it from
happening in the future.

As always, any help that anyone can offer is greatly appreciated.

-Burr Baldwin

Martin,

It appears that my clients' inability to successfully conduct their business with
the CAPs was caused by inadequate permissions to
HKLM\Software\Microsoft\NAL\AbExprtDb. Elsewhere in this thread, I've posted a
longwinded description of what I found.

-Burr Baldwin