Re: SMS client and MP problems! please do help me out!
- From: DHS-SMS <Larry.Brown@xxxxxxxxxx>
- Date: Tue, 31 Jul 2007 09:20:49 -0700
On Jul 31, 10:38 am, "sherrylkissin...@xxxxxxxxx"
<sherrylkissin...@xxxxxxxxx> wrote:
I might have missed some things in this post; so if I'm way off base,
please forgive me.
I think I see multiple issues here. First; are you running in
Advanced Security or not? Depending upon your answer, verify the
permissions on the AD node System/System Management. It sounds like
permissions are not set correctly to allow your server to add/change/
publish information regarding the SLP into that AD node. If Advanced
Security, I believe you have to give your servers' computer account
rights to that node. (Someone please correct me if I'm wrong).
The other thing I see is based on MP Troubleshooter, your MP post-
install is not healthy. That can be one of the more difficult things
to troubleshoot. I'd start with verifying you have IIS *with BITS
extensions* installed. The BITS extensions is not enabled by default,
so you may need to go into Add/Remove Programs, Windows Components,
applications, IIS details, and check that box on. Then, from the SMS
Console, remove the MP role (and wait, and monitor the log file sms
\logs\mpsetup.log). Once it shows a successful uninstall, re-add the
MP role (and wait, and monitor the log file sms\logs\mpsetup.log).
Once it shows a successfuly install; re-run the MP Troubleshoot post-
install; and see what you get.
On Jul 31, 7:39 am, Nandan <nandagopalrva...@xxxxxxxxx> wrote:
Hiii,,
Please help me.I have been trying for weeks to get SMS 2003 R2 up and
running on our network.
It's a pretty big network .I discovered the machines using active
directory system and user discovery but not with network discovery or
heartbeat or any other thing.
Well my main problem is that I am not able to push clients to the the
discovered networks. Client=NO Assigned=NO..whta do i do?
My MP seems to be healthy.
and the ccm.log shows error 5 .unable to access remote registry
"admin
$" .the account I use is a super-user account. It Has local
administrative privileges,is a member of schema admins group.
could IIS be the problem.when i checked the IIS administrative snap-
in
and tried to connect to another pc,it said "IIS version 4 or higher
is
required"
Newsgroups: microsoft.public.sms.setup
From: "Garth" <S...@xxxxxxx>
Date: Mon, 23 Jul 2007 10:39:57 -0400
Local: Mon, Jul 23 2007 7:39 pm
Subject: Re: HELP!! SMS clients not assigning
"Nandan" <nandagopalrva...@xxxxxxxxx> wrote in message
Hiii,,
Please help me.I have been trying for weeks to get SMS 2003 R2 up and
running on our network.
It's a pretty big network .I discovered the machines using active
directory system and user discovery but not with network discovery or
heartbeat or any other thing.
Well my main problem is that I am not able to push clients to the the
discovered networks. Client=NO Assigned=NO..whta do i do?
My MP seems to be healthy.
and the ccm.log shows error 5 .unable to access remote registry "admin
$" .the account I use is a super-user account. It Has local
administrative privileges,is a member of schema admins group.
could IIS be the problem.when i checked the IIS administrative snap-in
and tried to connect to another pc,it said "IIS version 4 or higher is
required"
Regrds,
Nandan
Hi garth,
thanks for the reply.well,I used the same account that SMS clinet
access network account uses to map to the admin$ of other clients and
I am able to do the same. But I think the SMS client is not able to
write to the remote registry.
Well I ran the MP troubleshooter and the only thing that failed was
"BITS was not running" .I checked the box for BITS enabling in SMS
admin console as well manually started the BITS service in
administative tools>services .But still the MP trouble shooter says
BITS is not running.
I had uninstalled IIS earlier,could it be that removing IIS without
removing SMS would create problems.
Thanks,
Nandan
Kim Oppalfens [MVP] View profile
More options Jul 25, 12:26 am
Nandan wrote:
Hi garth,
thanks for the reply.well,I used the same account that SMS clinet
access network account uses to map to the admin$ of other clients and
I am able to do the same. But I think the SMS client is not able to
write to the remote registry.
Well I ran the MP troubleshooter and the only thing that failed was
"BITS was not running" .I checked the box for BITS enabling in SMS
admin console as well manually started the BITS service in
administative tools>services .But still the MP trouble shooter says
BITS is not running.
I had uninstalled IIS earlier,could it be that removing IIS without
removing SMS would create problems.
Thanks,
Nandan
Check add/remove programs; Windows components; application server;
IIS
Is the bits checkbox enabled?
--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMShttp://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_manage...
there's a saying "i've heard so Much abt u"..well i haven't heard
anythin abt u BUT I'VE READ SO MANY OF UR POSTS!! LOL..
Yeah,the checkbox is enabled.well I tried that earlier itself,started
up the BITS service in services.msc .
now I checked on the client machines and they all show the clients as
installed,BITS up and running.In the client services SMS agent Host
and WMI are all enabled..
Where's the needle in the haystack!!!
I removed the active directory discovery methods and now am running
only the network discovery and heartbeat methods but nothing seems to
be discovering..I have given the correct DNS servers for it to
discover as well as the subnets..The subnet on which the SMS server
is
on shows a Locked image next to it.what's this.
On a conceptual side what is required for SMS to discover the
resources in a network without the use of active directory.Is that
possible and if so,How? Please help...
I checked the locationservice.log on the client. It says ""Failed to
resolve IP address from WINS; LS:GetSLP:Failed to resolve SLP from
WINS:IS it published; LSGetassignedSitefromSLP :Unable to get the
list of SLP's "" .
I have set up my SMS as an slp under site system roles earlier itself
and the SMS_server locator point service seems to be running.
Exexmgr.log says" The logged on user is RND015\npol ;Software
Distribution site settings for the client are missing from WMI;
ccmsetup.log shows that it connects to the MP and downloads the
client
upto 100% .Searches for available transform.but then in red it shows
up "failed to find resource file "client.mst".
sitecomp.log says " CHNSERVER04 is the Default MP.
Publishing CHNSERVER04 as a Management
Point into Active Directory.
SMS-MP-NST-CHNSERVER04 could not be
created, Win32 error =8202.
SLP configuration for CHNSERVER04 is correct.
Publishing CHNSERVER04 as SLP into Active Directory.
SLP class SMS-SLP-NST-CHNSERVER04 could not be created, Win32 error
=8202 "
I used Mp troubleshooter and checked post installation and pre
installation.POst installation has three failures
1.It fails to queryhttp://chnserver04:80/SMS_MP/.sms_aut?MPCERT
2.http://chnserver04:80/SMS_MP/.sms_aut?MPLIST
3.If the MP is W2k3:Verify that BITS extensions are enabled:cannot
create ActiveX component.
Thanks..
Nandagopal- Hide quoted text -
- Show quoted text -- Hide quoted text -
- Show quoted text -
Also if the system is giving you access denied when trying to push the
client, you have the service account in the schema admins global
group. I have noticed that nested or defualt group sometimes have
problem with SMS as far as trying to install the agent, try add the
service account locally to the administrators group on the pc to see
if this will solved your problem; it did for me.
.
- References:
- SMS client and MP problems! please do help me out!
- From: Nandan
- Re: SMS client and MP problems! please do help me out!
- From: sherrylkissinger@xxxxxxxxx
- SMS client and MP problems! please do help me out!
- Prev by Date: Re: SMS client and MP problems! please do help me out!
- Next by Date: Re: Invalid root in registry key?
- Previous by thread: Re: SMS client and MP problems! please do help me out!
- Index(es):
Relevant Pages
|
