Re: Advanced Client and MP Policies
From: Travis Sweat \(MSFT\) (travsw_at_microsoft.com)
Date: 02/25/04
- Next message: JAT: "Uninstalling an SMS 2.0 site"
- Previous message: Craig Farrell: "Client install issues"
- In reply to: Matty: "Advanced Client and MP Policies"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 25 Feb 2004 07:37:07 -0800
Matty,
Please send me the following logs:
Mpcontrol.log
MPsetup.log
MPmsi.log
Also try the following things(Good list of MP troubleshooting steps)
This was intended to be in least intrusive to most intrusive order.
1.. Run http://
1.. This returns a blank screen.
2.. Run http://
1.. This returns a long list of numbers and letters.
3.. Verify that the DTS Service is enabled.
4.. Verify that the Task Scheduler is enabled.
5.. Verify that the Windows Management Instrumentation service is running.
6.. Verify that the SMS Agent Host service is running.
7.. Verify that the World Wide Web Publishing Service is running.
8.. Verify that the MP machine account has been added to the
SMS_SiteSystemToSQLConnection_<site_code> group.
9.. Verify that the SQL Server has named pipes enabled.
10.. Update MDAC on the server.
1.. Review Q820910 for details.
2.. http://support.microsoft.com/default.aspx?scid=kb;en-us;820910
11.. SQL boxes that are running under a user account, instead of system,
need the SPN updated in AD.
1.. Review Q829868 for additional details.
2.. http://support.microsoft.com/default.aspx?scid=kb;en-us;829868
12.. Crossing domain boundaries between MP and SQL may also need the SPN
updated in AD.
1.. Review Q829868 for additional details.
2.. http://support.microsoft.com/default.aspx?scid=kb;en-us;829868
13.. IIS Lockdown Tool
1.. If you are using the IIS lockdown tool on your IIS 5 servers be sure
to apply the SMS server template from the SMS 2003 toolkit.
2.. http://www.microsoft.com/smserver/downloads/2003/tools/toolkit.asp
14.. Deinstall the MP and IIS, then reinstall IIS and the MP.
1.. Remove the MP role on the server.
2.. Disable IIS. Remove completely. Reboot the server.
3.. Verify that the DTS Service is enabled.
4.. Verify that the Task Scheduler is enabled.
5.. Verify that the Windows Management Instrumentation service is
running.
6.. Enable BITS, enable WEBDEV and install IIS.
7.. Verify that the World Wide Web Publishing Service is running.
8.. Verify that the MP machine account has been added to the
SMS_SiteSystemToSQLConnection_<site_code> group.
9.. Enable MP role on the server.
--
Travis Sweat [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
"Matty" <anonymous@discussions.microsoft.com> wrote in message
news:697AA861-4145-4C40-80F0-135F9C3C381D@microsoft.com...
> Hi
>
> I have just upgraded an SMS 2.0 site to SMS 2003, it is a single server
running Windows 2000, IIS 5 and SQL 2000. I am having real problems getting
the Management Point policies to be generated and deployed to the advanced
clients on our network (to configure remote control etc).
>
> When I installed the MP it created several new virtual directories (inc.
SMS_MP) on the IIS server and the logs suggested it installed correctly
without any issues.
>
> All our clients are getting the correct site assignments and showing up as
installed in the collections. (Fyi.. I have extended the AD schema and the
MP and SLP are published in AD).
>
> Although the Adv. client is being installed on each client it does not
appear to be configured with the settings I have enabled in the site
settings, ie. remote control, software metering etc. I have tried enabling
and renabling them between reboots etc yet still nothing..
>
> I have also used the Management Point Spy tool from the SMS tookit and
although it connects to the SMS database it retrieves no policies.. Does
anybody have any ides why the polices are not being generated by the MP?? If
I look in the SMS_MP folder on the IIS server there are no files in there.
>
> Please help!
> Matt
>
>
Relevant Pages
... Verify that the Task Scheduler is enabled. ... Verify that the Windows Management Instrumentation service is running. ... Verify that the SQL Server has named pipes enabled. ... If you are using the IIS lockdown tool on your IIS 5 servers be sure ...
(microsoft.public.sms.admin)
... Could be you have too many connections to the server and are out of Server ... You might also want to try reinstalling IIS. ... SMS 2003 Technical FAQ: ... The Default Web Site is disabled in IIS. ...
(microsoft.public.sms.setup)
... Verify that the Task Scheduler is enabled. ... Verify that the SQL Server has named pipes enabled. ... If you are using the IIS lockdown tool on your IIS 5 servers be sure ... I've successfully turned up> a Management Point on the Central Site server. ...
(microsoft.public.sms.admin)
... and the secondary site server is W2K3/ running IIS 6.0, ... Start IIS Admin ... If there was a problem with the IWAM account, ... Verify that the Task Scheduler is enabled. ...
(microsoft.public.sms.admin)
... IIS lockdown isn't needed for Windows server 2003. ... Did you get an error status message in the SMS admin console for MP control ... The SQL server site system is turned off, ...
(microsoft.public.sms.setup)
