No site code Info. and clients are showing as not installed

[gshin8359]

I have sms 2003 configured for a single site with all the discovery methods, as well as client agents configured. Also I have sit boundaries configured for my subnet.

All myclients have been manually installed with the client agents, and are auto detecting the sms site code ok.

In my all systems collections area it has been populated with all my client machine, with no site code entry and the clients are showing as not installed.

I can't use remote tools cause it say remote tool agent not found on client, despite the fact that it is installed.

Also when I open "system management" The "Action" menu, hasn't been populated with any info, except for 2 entries:

Machine policy retrieval
User policy retrieval

Can anyone help?

 

[tbrennans]

Sounds like a MP problem, check out the Mpfdm.log and make sure the mp is talking to the site server, and on the client look at the Clientlocation.log it will show you if your client is assigned to a site and then check out the locationservices.log to see if the client is talking to the MP.


good start anyway...

Tim B

 

[gshin8359]

Tim B, thanks for your reply, this is part the contents of

mpfdm.log:
**ERROR: Cannot find destination inbox for Discovery Data Manager (Trusted) on server WIN23K $$<SMS_MP_FILE_DISPATCH_MANAGER><Mon Sep 12 19:44:31.109 2005 GMT Daylight Time><thread=3520 (0xDC0)>
~Cannot update environment so skiping outbox processing. $$<SMS_MP_FILE_DISPATCH_MANAGER><Mon Sep 12 19:44:31.109 2005 GMT Daylight Time><thread=3520 (0xDC0)>
~Waiting for changes in MP outboxes, max wait = 300 seconds $$<SMS_MP_FILE_DISPATCH_MANAGER><Mon Sep 12 19:44:31.109 2005 GMT Daylight Time><thread=3520 (0xDC0)>
~Waiting for changes in MP outboxes, max wait = 300 seconds $$<SMS_MP_FILE_DISPATCH_MANAGER><Mon Sep 12 19:49:31.187 2005 GMT Daylight Time><thread=3520 (0xDC0)>
~Waiting for changes in MP outboxes, max wait = 300 seconds $$<SMS_MP_FILE_DISPATCH_MANAGER><Mon Sep 12 19:54:31.203 2005 GMT Daylight Time><thread=3520 (0xDC0)>
~Updating environment... $$<SMS_MP_FILE_DISPATCH_MANAGER><Mon Sep 12 19:59:31.203 2005 GMT Daylight Time><thread=3520 (0xDC0)>

LocationServices.log:

locatio<![LOG[Current AD site of machine is Default-First-Site-Name]LOG]!><time="07:11:44.269+-60" date="09-13-2005" component="LocationServices" context="" type="1" thread="596" file="lsad.cpp:215">
<![LOG[Retrieved Proxy Management Point from AD: WIN23K]LOG]!><time="07:11:44.610+-60" date="09-13-2005" component="LocationServices" context="" type="1" thread="596" file="lsproxymp.cpp:835">
<![LOG[Attempting to retrieve local MP from AD]LOG]!><time="07:11:44.770+-60" date="09-13-2005" component="LocationServices" context="" type="1" thread="596" file="lsad.cpp:2504">
<![LOG[Current AD site of machine is Default-First-Site-Name]LOG]!><time="07:11:45.261+-60" date="09-13-2005" component="LocationServices" context="" type="1" thread="596" file="lsad.cpp:215">
<![LOG[Retrieved local Management Point from AD: WIN23K]LOG]!><time="07:11:45.291+-60" date="09-13-2005" component="LocationServices" context="" type="1" thread="596" file="lsad.cpp:2514">nservices.log:


Clientlocation.logs:

<![LOG[Management Point is WIN23K]LOG]!><time="19:56:46.643+-60" date="09-12-2005" component="ClientLocation" context="" type="1" thread="1692" file="smsclientclass.cpp:791">
<![LOG[Getting Assigned Site]LOG]!><time="19:59:33.493+-60" date="09-12-2005" component="ClientLocation" context="" type="1" thread="892" file="smsclientclass.cpp:843">
<![LOG[Assigned Site is A53]LOG]!><time="19:59:33.513+-60" date="09-12-2005" component="ClientLocation" context="" type="1" thread="892" file="smsclientclass.cpp:861">
<![LOG[Getting Assigned Site]LOG]!><time="20:23:48.501+-60" date="09-12-2005" component="ClientLocation" context="" type="1" thread="596" file="smsclientclass.cpp:843">
<![LOG[Assigned Site is A53]LOG]!><time="20:23:48.542+-60" date="09-12-2005" component="ClientLocation" context="" type="1" thread="596" file="smsclientclass.cpp:861">


Will appreciate a diagnosis, and a resolution.

Thanks

 

[tbrennans]

Well, it looks to me like the MP is not communicating with the site server. HAve you extended the schema and gave rights to the systems management container?

 

[tbrennans]

You might also run the MPtroubleshooter from the sms 2003 toolkit 2 and see what that comes up with also.

 

[gshin8359]

Yes schema was succesfully extended, rights have been given to the management container, can you suggest anything pls

 

[tbrennans]

has the management container populated? (at least three objects)

You might also run the MPtroubleshooter from the sms 2003 toolkit 2

is your sql server on a different box?

 

[tbrennans]

meaning sql on a different box than the site server if so it might be a spn problem

 

[tbrennans]

http://support.microsoft.com/default.aspx?scid=kb;en-us;829868

for the spn issue...

 

[gshin8359]

Thanks very much, problem is now resolved, you were right there was no communication, so I uninstalled MP, and IIS following this procedure listed:

http://support.microsoft.com/default.aspx?scid=kb;en-us;883983

The system management is now fully populated and installed.

I have another issue now with distribution points, there is no issue when I have just the one DP on the sms server, but on nominating other distribution points packages are not copied over instead I get this error message in "Component Status": MS Distribution Manager failed to process package "Acrobat Writer" (package ID = A5300001).

 

[tbrennans]

go into that package with the dp wizard, remove all the distribution points then run it again add them all back in and see if that helps.

 

[gshin8359]

I have tried like u suggested removing the dp with distribution point wizard, and adding them back again, but still same errors:

Component status message: SMS Distribution Manager failed to process package "Acrobat Writer" (package ID = A5300001).

Package Status: "State": Install retrying

Will appreciate any more suggestions

 

[gshin8359]

Thanks to everyone who replied to this query, I found out what the problem was, and want to share this info:

Did you make the SMS service account (standard security) or
SiteServerComputer$ account (advanced security) a member of the local admins
group on the remote distribution point?

--
Cathy Moya, CISSP, MCSE: Security
Technical Writer, Windows Enterprise Management Division User Assistance

Check out the SMS Technical FAQ:

http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default.mspx

This posting is provided AS IS with no warranties and confers no rights.


That is the resolution above, the remote dp, required for the site server account be added as a member of the local admin group

 

[gshin8359]

Above resolution was obtained from:

http://www.mbawizards.com/updating_dp_0000081468.htm