You regularly monitor your Windows NT Server running as a site
server. You notice SMS application events appearing in the Windows
NT Event Viewer Application log. Why is this happening and how can
you stop SMS application event logging to the Windows NT Event
Viewer?
You use the SMS Service Manager to stop SMS Executive. You then
query all of the components appearing in the SMS Service Manager
and notice that many components have stopped. Why did stopping the
SMS Executive also stop many of the components appearing in the SMS
Service Manager?
You stop the SMS Component Manager, the SMS Executive, the SMS
SQL Monitor, and the SQL Server running the site database. You then
run WBEMTest and notice that you can connect to the WBEM site
namespace. You then attempt to access site object instances and the
procedure fails. Why were you able to access the site namespace but
not site object instances?
After installing HealthMon on your site server, you register
all of your Windows NT/2000 computers in the site as monitored
systems. No data appears in HealthMon except down arrows next to
all registered computers. Why is this happening?
From the primary site server, you install a secondary site
server. The status of the secondary site server in the SMS
Administrator console is 'Pending.' You wait 48 hours, verify that
your addresses to and from the secondary site server are correct,
and ensure that the computer being configured as a secondary site
server is accessible from the primary site server. You check the
computer that will be a secondary site server to see if the
secondary site server package has been delivered. You see that the
package has been delivered, but it has not been installed. What are
two possible causes for the 'Pending' status? Also, what log file
should you analyze to determine the cause of the failure?