Re: SMS SP3 client problems

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hey Kim,

I appreicate your help, but all I'm getting for responces from you are
copies of what I wrote you. I noticed the same was happening for other post
that you replied.

"Kim Oppalfens [MVP]" <""Kim dot Oppalfen" wrote:

Dave B wrote:
I'm using a domain account that has access to just about everything on the
domain.

"Kim Oppalfens [MVP]" <""Kim dot Oppalfen" wrote:

Dave B wrote:
Kim,

THanks for all your help.

I went through an re-entered all the data for all the access account (even
though they had worked before, but hey I was deperate) and the clients now
install no problem... Sort of... While the clinet does now install on the
client machine it never shows up in the SMS admin console as being installed.

Also all the new machine only have to actions availalbe to them under the
system manager in the control panel. I got the clients to install on Friday
and now on Moday thay are still only these two there with out it showing as
installed in the admin console.

Machine Policy Retrival & Evaluation Cycle
and
User Policy Retrival & Evaluation Cycle






"Kim Oppalfens [MVP]" <""Kim dot Oppalfen" wrote:

What account did you use to access the share?

--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx

Dave B wrote:
oh and yes the client can get to the share.


Thanks again

"Kim Oppalfens [MVP]" <""Kim dot Oppalfen" wrote:

Ok, this means the push from the server to the client actually worked.
Could you try and logon to this client and see whether you can access
the \\IFESDC911\SMSClient\I386 share?

One thing that often fixes issues like this is creating an advanced
client network access account.

Create a normal domain user.
Go to the sms admin console, component configuration, software distribution.
Configure the advanced client network access account.
Try pushing again.


--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx

Dave B wrote:
Hey Kim, (I'm back after a haitus of being sent to an unrealted training
course but my SMS problems continue)

Thanks for your help and yes I did find a log file on the client. To me it
looks like the client can't access somethingon the SMS server, but I've
double checked the shares and it should have access. Unless I'm missing
something.

The log genreates this error over and over again..
<![LOG[Source \\IFESDC911\SMSClient\I386 is inaccessible
(1326)]LOG]!><time="17:43:46.217+240" date="10-16-2007" component="ccmsetup"
context="" type="2" thread="796" file="ccmsetup.cpp:2848">
<![LOG[Failed to find accessible source. Waiting for
retry.]LOG]!><time="17:43:46.217+240" date="10-16-2007" component="ccmsetup"
context="" type="2" thread="796" file="ccmsetup.cpp:2877">
<![LOG[Next retry in 10 minute(s)...]LOG]!><time="17:43:46.217+240"
date="10-16-2007" component="ccmsetup" context="" type="0" thread="796"
file="ccmsetup.cpp:3888">

Can you give me anymore clues I am at loss. Teh SMS account shouldn't be
being blocked at all.

-Thanks!

"Kim Oppalfens [MVP]" <""Kim dot Oppalfen" wrote:

Dave,

If you see the copying message then you should have a ccmsetup.log on
the client.

--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspxDave
B wrote:
Hey Kim thanks for responding.

I looked the ccm.log and think I found something for one of the computers
I'm having trouble installing the client on, but I'm not sure what it means.

I can see that it copies the file and then when it starts the install this
message comes up:

---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account
****\******* (000004be) $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 04
01:13:21.017 2007 Eastern Daylight Time><thread=2136 (0x858)>

I have tow accounts enteres into SMS both og which have more than enough
access to install on the computer and it worked before, so I'm not sure what
to do with this.

Any ideas?

Thanks

"Kim Oppalfens [MVP]" <""Kim dot Oppalfen" wrote:

Dave B wrote:
Hello all and I'm hoping someone can help me.

After someone else (not me but it should have been) performed the upgrade to
SP3 I noticed that my hardware inventory didn't work. I soon realized that
this was bacuse I needed to upgrade the clients on all my machines. THis is
when I realized that my push installation does not seem to be working.
If I install the client manually by navigating from the target computer and
running the client app everything works fine. If however I tell SMS to push
out the client, the client does not upgrade. Furthurmore I no longer seem to
be able to push out clients to new computers.

To add to my frustration I cannot find any errors reported in the
SMS_CLIENT_CONFIG_MANAGER pretating to the machines I am trying to upgrade.


Can anyone help?
Thanks in advance...

check ccm.log and the smsprovider log.

--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx

--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx

This usually means the clients can't find or can't contact their
management point.

--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx

For the clients to connect back? I highly doubt it.
Have you extended your Active directory schema?
Is the data successfully published in Active directory?

--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx

.

Relevant Pages

  • Error Advanced Client setup
    ... I'm having a problem installing the SMS advanced client on certain servers. ... Action start 16:07:53: INSTALL. ...
    (microsoft.public.sms.setup)
  • 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: Advanced client installed on the client, but not displaying as such on the Admin Console?
    ... Heartbeat Discovery interveral being set so short may have had anything to ... the 2.0 client clean utility). ... client components appear to install (the various icons show up in the ... SMS Client Core Components - Installed ...
    (microsoft.public.sms.admin)
  • Re: General Advice on performance
    ... the SMS client installed some go into the collection that applications are ... PCs to run it when they reboot but this is not an ideal solution. ... don't understand is why they don't get added when they start running the SMS ... Novell's unattended install method to remove the client. ...
    (microsoft.public.sms.swdist)
  • Re: Advanced Client Installation Failure - client.msi.log
    ... before calling Install on Server ... SMS Advanced Client does not support per-user installations. ...
    (microsoft.public.sms.admin)