Can not see Reporting Service in SCOM 2007 Administration on left pane

After installing/reinstalling SQL 2005 and SCOM 2007 I still didn't see SCOM 2007 reporting module on left pane under Administration.

After lots of research and tweek I found out best way to have Remote SQL 2005 and SCOM 2007 configure is below

SQL 2005:
SQL 2005 Database services
OperationsManagerDW database
ReportServer database
ReportServerTempDB database

SCOM 2007:
IIS
SQL 2005 reporting services instance
Operations Manager Reporting install

mount the remote system using smbfs OR How to mount remote windows partition (windows share) under Linux

Procedure to mount remote windows partition

1) One need to have below required info before proceeding further:
a. Windows privilages to access share name
b. Sharename (i.e //server/share) or IP address of sharename server
c. Root level access on Linux (i.e root)

2) Login to Linux as a root user

3) Create the required mount point under mnt/:
# mkdir -p /mnt/Windows_mount_share_name)
Use the mount command as follows:
# mount -t cifs //ntserver/download -o
username=Windows_username_use_1.a,
password=Windows_userpwd
/mnt/ntsharename

4) Access Windows 2003/2000/NT share using cd and ls command:# cd /mnt/ntsharename;
ls -l

Dell Power Edge servers MIBs

You can download Dell Power Edge servers MIBs from there Open Manager CD or latest from there website.

I download to work with SCOM 2007 to monitor all my Dell server and below is its config.

This section provides information on open issues with the Dell Management Pack 3.0 for Operations Manager 2007.

- Operations Manager Health Service may stop due to certain Monitor thresholds. The Workaround for this issue is to modify the following threshold settings for the Monitors:

1. Go to the Authoring pane

2. Select Authoring-> Management Pack Objects-> Monitors

3. Select Target as "Agent"

4. Select Entity Health-> Performance-> Health Service Performance
a) Right-click "Health Service Handle Count Threshold"
b) Select Overrides-> Override the Monitor-> For a Group
c) Choose "Management Server Computer Group"
d) Override the following parameters * "Agent Performance Monitor Type - Threshold" - "Override Setting" value from 2000 to 10000 * Enabled - "Override Setting" value to "true"
e) Apply the settings.

5. Select Entity Health-> Performance-> Health Service Performance
a) Right click "Health Service Private Bytes Threshold"
b) Select Overrides-> Override the Monitor-> For a Group
c) Choose "Management Server Computer Group"
d) Override the following parameters * "Agent Performance Monitor Type - Threshold" - "Override Setting" value from 104857600 to 1610612736 * Enabled - "Override Setting" value to "true"
e) Apply the settings.

- The IPMI Power control and LED Identification tasks shipped with the Dell Management Pack v 3.0 require BMU 2.0 or later to be installed on the Operations Manager Management Server and have default BMC credentials, which cannot be modified.

If your systems have different BMC credentials, you need install BMU 2.0 or later on the Operator Console system and create new console tasks in Authoring pane targeted on "BMC for Dell Server".

Select "Create new task" -> "Console Tasks - CommandLine" and set the following command line parameters:"Application:" Input the path of application "ipmish.exe"
(For example, c:\Program Files\Dell\SysMgt\bmc\ipmish.exe)"

Parameters:
" for example: -ip $Target/Property[Type="Dell.Connections00130025!Dell.Connections.ServerBMC"]/BMCIPAddress$ -u %BMCUserName% -p %BMCPassword% -k %BMCKGKey% %IPMITaskString%

The above BMCIPAddress string can be populated by selecting the drop-down button indicating "BMC IP Address."

Update the BMC credentials - %BMCUserName%, %BMCPassword%, %BMCKGKey%%IPMITaskString%
- "power status" for CheckPowerStatus Task
- "power on" for PowerOn Task
- "power off" for PowerOffGrace Task
- "power off -force" for PowerOffForce Task
- "power cycle" for PowerCycle Task- "power reset" for PowerReset Task
- "identify on" for LEDOn Task- "identify off" for LEDOff Task
- Operations Manager cannot discover DRAC on Dell PowerEdge(TM) xx55 systems with modular chassis.

http://support.dell.com/support/edocs/software/smconect/msscom/30/readme/readme.txt

how to use MIB into SCOM 2007 and net-snmp tools

After searching a lot on MIB to work with SCOM 2007, I'm not able to find much about it insted got lots of link about downloading MIBs.

Below are the links that you can use to download tools and MIBs

http://www.it-jedi.net/2007/04/network-device-monitoring-in-essentials.html

http://www.elifulkerson.com/articles/net-snmp-windows-binary-unofficial.php

What is SNMP (http://technet2.microsoft.com/WindowsServer/en/Library/2a4711d6-2e0a-48a0-b4c4-d03c1b43c6901033.mspx)

no report servers were found on the specified machine. Details: Invalid namespace

First step to do is to make sure IIS and ASP.NET is running/installed. If those are installed and working well, now the easy way is to run sql setup.exe file to reinstall reporting service by checking that option then prompt to install all the components.

How to install SQL Server 2005 Reporting Services a Windows Vista-based computer

After you install the original release version of SQL Server 2005, you must apply SQL Server 2005 Service Pack 2 (SP2) or a later service pack to obtain support from Microsoft. Additionally, SQL Server 2005 Express Edition with Advanced Services SP2 is already at the SQL Server 2005 SP2 level. For more information, visit the following Microsoft Web site:http://go.microsoft.com/fwlink/?LinkID=63922 (http://go.microsoft.com/fwlink/?LinkID=63922)
Before you install SQL Server 2005 Reporting Services, you must enable Microsoft ASP.NET and Microsoft Internet Information Services (IIS).

To enable ASP.NET and IIS, follow these steps:

1. In Control Panel, click Programs, and then double-click Programs and Features.

2. In the User Account Control dialog box, click Continue.

3. Click Turn Windows features on or off.

4. In the Windows Features dialog box, expand Internet Information Services, expand Web Management Tools, expand IIS6 Management Compatibility, and then click to select the following check boxes:
• IIS 6 WMI Compatibility
• IIS Metabase and IIS 6 configuration compatibility

5. Expand World Wide Web Services, expand Application Development Features, and then click to select the following check boxes:
• ASP.NET
• ISAPI Extensions
• ISAPI Filters

6. Expand Common HTTP Features, and then click to select the following check boxes:
• Default Document
• Directory Browsing
• HTTP Errors
• HTTP Redirection
• Static Content

7. Expand Security, and then click to select the Windows Authentication check box.

Install SQL Server 2005 Reporting Services

To install SQL Server 2005 Reporting Services, follow these steps:

1. Log on to Windows Vista, and enable ASP.NET and IIS. For more information, see the "Prerequisites" section.

2. Verify that the World Wide Web Publishing service is started. If the World Wide Web Publishing service is not started, configure the service to start automatically. To do this, follow these steps:
a. In Control Panel, click System and Maintenance.
b. Click Administrative Tools.
c. Double-click Services.
d. In the User Account Control dialog box, click Continue.
e. Right-click World Wide Web Publishing Service, and then click Properties.
f. In the World Wide Web Publishing Service Properties dialog box, click Automatic in the Startup Type list. g. Click Apply, click Start, and then click OK.

3. Start to install SQL Server 2005 or SQL Server 2005 Express Edition with Advanced Services SP2.
Notes
• When you install the original release version of SQL Server 2005, you receive a warning message that explains that this program has known compatibility issues. Click Run program to continue the installation.
• In the Feature Selection dialog box, make sure that Reporting Services is selected.
• In the Report Server Installation Options dialog box, select either of the following options:
• Install the default configuration
• Install but do not configure the server

4. Install SQL Server 2005 SP2.
Notes
• For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: 913089 (http://support.microsoft.com/kb/913089/) How to obtain the latest service pack for SQL Server 2005
• If you install SQL Server 2005 Express Edition with Advanced Services SP2, skip step 4 because SQL Server 2005 SP2 is already installed.
• You must make sure that the SQL Server service is started before you install SQL Server 2005 SP2. The SQL Server service must be running to perform an authentication check in the Authentication Mode dialog box of the Setup program.
• After you leave the Authentication Mode dialog box, you can stop the SQL Server service to avoid a system restart. To stop the SQL Server service, click Administrative Tools in Control Panel, double-click Services, right-click the SQL Server service, and then click Stop.
• If the SQL Server 2005 User Provisioning Tool for Vista starts, start the SQL Server service before you grant administrative rights to a user. You can use the SQL Server 2005 User Provisioning Tool for Vista to add Windows user accounts to the SYSADMIN fixed server role easily.

5. Start the SQL Server service if the service is not started. If you install SQL Server Express Edition with Advanced Services SP2, reset IIS.
To reset IIS, follow these steps:
1. Open a command prompt by using the Run as administrator option.
2. Type IISRESET, and then press Enter.

6. If you selected the Install but do not configure the server option in the Report Server Installation Options dialog box, configure the report server. To do this, follow these steps:
a. Start the Reporting Services Configuration tool. To start the tool, click Start, point to All Programs, point to SQL Server 2005, point to Configuration Tools, and then click Reporting Services Configuration.
b. In the User Account Control dialog box, click Continue.
c. In the Report Server Installation Instance Selection dialog box, type the name of the computer in the Machine Name box.
d. Click the instance of SQL Server 2005 Reporting Services in the Instance Name list, and then click Connect. e. Configure the server for operation. Note Reporting Services runs as a legacy application on IIS 7.0. If you configure the application pool for the Report Server virtual directory on a new Reporting Services installation, one of the following methods:
• Select Classic .NET AppPool for the report server.
• Create a new application pool. Then, set the Managed Pipeline Mode option to Classic.

If you installed Reporting Services by using the default configuration, the report server runs in its own application pool under the NetworkService account. If you use the default configuration, the report server is fully operational on Windows Vista. However, you should avoid running the report server in the default application pool on IIS 7.0. The default application pool has the Managed Pipeline Mode option set to Integrated. You will receive an "HTTP 500" error message if you run the report server in the default application pool.

7. Configure the report server for local administration. To access the report server and Report Manager locally, follow these steps:
a. Start Windows Internet Explorer.
b. On the Tools menu, click Internet Options.
c. Click Security.
d. Click Trusted Sites.
e. Click Sites.
f. Under Add this Web site to the zone, type http://ServerName. If you are not using HTTPS for the default site, click to clear the Require server certification (https:) for all sites in this zone check box.
g. Click Add. h. Repeat step 7f and step 7g to add the http://localhost URL, and then click Close. Note This step enables you to start Internet Explorer and open either the localhost or the network computer name of the server for both the Report Server application and the Report Manager application.

8. Create role assignments that explicitly grant you access together with full permissions. To do this, follow these steps:
a. Start Internet Explorer together with the Run as administrator option. To do this, click Start, click All Programs, right-click Internet Explorer, and then click Run as administrator.
b. Open Report Manager. By default, the Report Manager URL is http://ServerName/reports.
If you use SQL Server Express with Advanced Services SP2, the Report Manager URL is http://ServerName/reports$sqlexpress. If you use a named instance of Reporting Services, the Report Manager URL is http://ServerName/reports$InstanceName
c. In the Home dialog box, click Properties.
d. Click New Role Assignment.
e. Type a Windows user account name by using the following format:Domain\User
f. Click to select the Content Manager check box.
g. Click OK.
h. In the Home dialog box, click Site Settings.
i. Click Configure site-wide security.
j. Click New Role Assignment.
k. Type a Windows user account by using the following format:Domain\User
l. Click System Administrator.
m. Click OK.
n. Close Report Manager.

9. Use Internet Explorer without the Run as administrator option to reopen Report Manager.

http://support.microsoft.com/kb/934164


http://www.microsoft.com/downloads/details.aspx?familyid=4C6BA9FD-319A-4887-BC75-3B02B5E48A40&displaylang=en


http://msdn.microsoft.com/en-us/library/ms143718.aspx

SCOM_ClientMonitoring

How to Configure Clients for Client Monitoring in Operations Manager 2007

follow the following link to do initial setup of client monitoring from OpsMgr http://technet.microsoft.com/en-us/library/bb381453.aspx

Run the Group Policy Object Editor (gpedit.msc) for the domain or local computer. NoteFor information about Group Policy, see http://go.microsoft.com/fwlink/?LinkId=70168.

You can find the GP under Computer Configuration/Administrative Templates/System/Internet Communication Management/Internet Communication settings. Also you can configure as per your requirement to turn on/off Windows Error Reporting policy.

On Group Policy administrative template or local computer policy, you can add Agentless Exception Monitoring to the domain . Run Client Monitoring Configuration Wizard to create Group Policy administrative template file .

NOTE: Use the same procedure to Disable the Group Policy settings, thereby disabling Client Monitoring on the clients.

Config SCOM 2007 Notification setup

SMTP Notification

In this example we will use Microsoft Exchange 2007, which will use Windows integrated SMTP
authentication when sending e-mails. However, Exchange is not required. You can use just about any SMTP server for sending e-mail notification in Operations Manager 2007, including a local instance of IIS SMTP installed on your Management Server.

NOTE: How to test SMTP services manually in Windows server 2003
http://support.microsoft.com/kb/323350

Setup Notification Channel

In this part we will setup channels SCOM 2007 can use to send IM and SMTP.

1. From the Start Menu, select the SCOM Operations Console

2. In the Navigation pane (left), Click Administration

3. In the Administration pane, click Settings

4. In the Action pane, right click Notification and select Properties from the context menu.

5. On the E-mail tab, select the "Enable e-mail notification" checkbox.

6. Next, we’ll add the SMTP Server. Click the Add button. Enter the FQDN of the target SMTP
Server, port number (In most cases you can leave default port 25), and the authentication
method for the SMTP Server. In this example, the SMTP Server requires Windows Integrated
authentication. Consult your e-mail administrator for the appropriate authentication setting for
your SMTP Server.

NOTE: You can add additional SMTP servers for failover to provide redundancy in the event of
failure of the primary SMTP Server.

7. Next, input the Return address; this address will be shown as sender when notifications are sent to notification recipients. Note that this e-mail needs to be the e-mail address of the Notification Action Account. Accept the default values in the remaining fields.


8. Next, select the Instant Messaging tab. Select the “Enable instant messaging notifications"
checkbox. In the IM Server field, enter the FQDN of your LCS server. In the Return address field, enter the sip address of the Notification Action Account.

NOTE: You must add sip: in front of the return address, for example
sip:scom-notification@scomresources.local.

9. If you have installed a Microsoft Office Live Communication 2005 Server with default settings, you will have to change IM port to 5060. It is important that you use your Notification Action Account instant messaging address; otherwise instant message notifications may fail due to lack of permissions. Accept the remaining default values by clicking OK.


Setup Notification Action Account

In this part we will create an account that will be used to send SMTP and IM notification, the notification action account. Note that this account should have the e-mail and SIP URI that you have filled in as return addresses under notification channels. I have created a domain user account named SCOMNOTIFICATION that will be used to both send SMTP and IM.

1. From the Start Menu, launch the SCOM Operations Console

2. In the Navigation pane (left), Click Administration

3. In the Administration pane, right-click Run As Accounts and choose Create Run As Account from the context menu to launch the Create Run As Account Wizard.

4. On the Introduction screen, click Next

5. On the General screen, choose Windows from the Run as account type drop-down box, input
display name and a short description. Click Next

6. On the Account screen, input user name, password and domain, then click Create. The wizard
will close when done.

Configure Run As Profile for Notification Action Account

We will now configure SCOM to use that account when sending notifications from your Management Server.

1. In the Administration pane click Run As Profiles. In the Action pane, right-click the Notification Account node and choose Properties

2. Select the Run As Accounts tab, then click New

3. On the Alternative Run As Account screen, choose the Run As Account created in previous
section, and then select your Management Server in the matching computer list. Then click OK.
Click OK again to finish.


Create a Notification Recipient to Receive SMTP and IM Notifications

First we will create a recipient and fill in all information about that account. Then we will create a
subscription and setup what notifications will be sent to that recipient. Finally, we will add notification devices to allow the notification recipient to receive notifications via both e-mail and instant message. In this example, we have created a domain account named John Conner that will receive all alerts at all times, both IM and SMTP.

1. From the Start Menu, launch the SCOM Operations Console

2. In the Navigation pane (left), Click Administration

3. In the Administration pane, right-click Recipients and choose New Notification Recipient

4. On the General tab click the button to the right of the textbox to select your notification
recipients’ domain account and click OK.

5. On the Notification Devices tab, click Add to launch the Create Notification Device Wizard.

6. Choose E-mail from the Notification channel dropdown. Verify that the recipient e-mail address is correct in the “Delivery address for the selected channel" textbox. Click Next.

7. On the Schedule screen, leave the default settings and this recipient will receive e-mails 24/7.
Click Next

8. On the General screen, enter a device name, for example John Conner E-Mail. Click Finish

9. On the Notification Devices screen, click Add.
10. Then choose Instant Messaging from the notification channel dropdown. Verify that the
recipient address is correct in the "Delivery address for the selected channel" textbox, for
example SIP:tom.cruze@scomresources.local. The value should be the notification recipients
SIP URI. Click next

11. On the Schedule screen, leave the default settings, this recipient will receive IM 24/7. Click Next

12. On the General screen, enter a device name, for example John Conner IM, and then click Finish. Click OK again to finish.

13. In the Administration pane, right-click Subscriptions and choose New Notification Subscription to launch the Create Notification Subscription Wizard.

14. Create Notification Subscription Wizard - Introduction: Click Next

15. On the General screen, input a name, for example "all alerts at all time". Input a short
description and then click Add

16. Choose your domain recipient created in the previous section and click OK. Click Next.

17. On the User Role Filter screen, leave the default settings and click Next

18. On the Groups screen, leave default settings, all groups selected, and click Next

19. On the Classes screen, leave default settings, all classes, and click Next

20. On the Alert Criteria screen, leave default settings, all alert criteria, and click Next

21. On the Alert Aging screen, leave default settings, do not notify on alert aging. and click Next

22. On the Formats screen, leave the default e-mail and IM format, click Finish


Additional Resources:
http://www.momresources.org/scom/how-to/scom_notification.pdf

Live Communications Server 2005 Deployment Resources
http://office.microsoft.com/en-us/products/FX011526591033.aspx

SMS_COMPONENT_STATUS_SUMMARIZER

Event ID: 4610 <SiteServerName> reported: SMS Component Status Summarizer set the status of component "SMS_SITE_COMPONENT_MANAGER" running on computer "<"siteservername">"
Possible cause: The component is experiencing a problem.

Solution: Diagnose and fix the problem by:

1. Examine the status messages that the component reports.

2. Correcting the problem.

3. Instructing SMS Component Status Summarizer to reset the counts of Error, Warning, and/or Informational status messages reported by the component. To reset the counts, right-click Reset Counts on the component in the Component Status summary in the SMS Administrator console. When the counts are reset, SMS Component Status Summarizer will change the status of the component to OK. This might take some time if site "NYC" is a child site.

4. Deleting any unwanted status messages from the site database, if necessary.

5. Monitor the component occasionally to verify the problem does not reoccur.

Possible cause: The component is OK and you were unnecessarily alerted because the Component Status Thresholds are set too low for the component.

Solution: Increase the Component Status Thresholds for the component using the Thresholds tab of the Component Status Summarizer Properties dialog box in the SMS Administrator console.

Possible cause: The component is "flooding" the status system by rapidly reporting the same message repeatedly.

Solution: Diagnose and control the flood of status messages by:

1. Verifying that the component is actually flooding the status system. View the status messages reported by the component, and verify that the same message is continually reported every several minutes or seconds.

2. Noting the Message ID of the flooded status message.

3. Creating a Status Filter Rule for site "" that instructs Status Manager to discard the flooded status message when component "SMS_SITE_COMPONENT_MANAGER" on computer "" reports it.

4. Verifying that your sites' databases were not filled up by the flooded status message. Delete any duplicate status messages from the site database, if necessary.
5. Refer to the Microsoft Knowledge Base for further troubleshooting information.
http://support.microsoft.com/?id=886092

SMS_COLLECTION_EVALUATOR

*** [28000][18456][Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON

http://support.microsoft.com/?id=832109

WORKAROUND
To work around this problem, switch from a TCP connection to a Named Pipes connection between the Management Point and the SQL server. This can also be used to test whether the issue is with Kerberos authentication, which TCP uses. Named Pipes uses NTLM authentication. If switching from TCP to Named Pipes does not resolve the issue, run a Network Monitor trace to investigate possible network connectivity issues. If enabling Named Pipes on the Management Point resolves the issue, it indicates that Kerberos authentication is failing and the troubleshooting steps in this article will be helpful in diagnosing the cause. To enable Named Pipes, do the following on the Management Point server. Click Start, click Run, type cliconfg, and then click OK. This starts the Client Network Utility. Add the SQL server NetBIOS name on the Alias tab with Named Pipes selected. This is the default setting. On the SQL server, run the Server Network Utility and make sure Named Pipes is at the top of the protocol stack. The Management Point queries SQL every 10 minutes. A log entry will appear that indicates the number of Management Points in the site. This indicates a successful connection.

Verify permissions
To start troubleshooting these symptoms, verify that the Management Point has the correct permissions to connect to the SQL database. To do this, follow these steps:

1.At the Management Point server, log on with the SMS Service account credentials, click Start, click Run, type cmd, and then click OK. If your SMS site is running under the Standard security mode, go to step 4. If your SMS site is running in the Advanced security mode, go to step 3.

2.If your SMS site is running Advanced security, start a new Command Prompt window that is running under the local system account. To do this, type the following at a command prompt, and then press ENTER:
ATFutureTime /interactive cmd
At the time that you specify, a new Command Prompt window opens that is running under Svchost.exe.Note FutureTime can be any time that is later than the current time, in 24-hour form.

3.At a command prompt, type the following, and then press ENTER:
osql -S SQLServer -d SMSdbname –E (*Run this on SQL server)
Note SQLServer is the name of the server that is running SQL Server, and SMSdbname is the name of the SQL database for your SMS site.If this command succeeds, your Management Point has the correct permissions to the SQL database. The command is successful if a 1> prompt is returned. Type exit, and then press ENTER to return to the command prompt. If you receive the following error message, go to step 4:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.

4.If you receive the "Login failed" error message that is described in step 3, repeat the command, but use the Fully Qualified Domain Name (FQDN). For example, type:
osql -S SQLServer.europe.corp.microsoft.com -d SMSdbname -E
If the command does not succeed, view the DNS settings for the domain where the Management Point computer is located.

5.If the command still fails check to see whether the MSSQLServer Service is using a user account to log on with, change the service to use the Local System account on the Log On tab in the service properties and run the commands again. If you must run the service by using a user account, make sure that the user account is added to the Domain Administrator group. You will also have to follow the steps in the following article in the Microsoft Knowledge Base:
829868 (http://support.microsoft.com/kb/829868/) Systems Management Server 2003 Advanced Security site with Remote SQL does not connect to SQL Server


Back to the top
Additional troubleshooting

1.The appropriate Service Principal Name (SPN) attributes may not be generated for the account that started the SQL services. To resolve this issue, you must manually create the fully qualified domain name (FQDN) and NetBIOS SPN entries. To do this, you can use the SetSPN utility from the Windows 2000 Server Resource Kit. To download the SetSPN utility, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyID=5fd831fd-ab77-46a3-9cfe-ff01d29e5c46&DisplayLang=en (http://www.microsoft.com/downloads/details.aspx?FamilyID=5fd831fd-ab77-46a3-9cfe-ff01d29e5c46&DisplayLang=en)
You must run the SetSPN utility on a computer that resides in the SQL server's domain. You must use Domain Administrator credentials. Determine if the SQL services run as a domain account or as the local computer account. To use the SetSPN utility to manually create the appropriate SPNs, follow these steps:

When the SQL service is started with a user account

• To create the FQDN SPN at a Command Prompt window, type the following command:
setspn -A MSSQLSvc/SqlHostname.mydomain.com:1433 SqlServiceAccount

• To create the NetBIOS SPN at the command window, type the following command:
setspn -A MSSQLSvc/SqlHostname:1433 SqlServiceAccount
When the SQL service is started with the SQL server's System account

• To create the FQDN SPN, type the following command at a command prompt:
setspn -A MSSQLSvc/SqlHostname.mydomain.com:1433 SqlHostname

• To create the NetBIOS SPN at the command window, type the following command:
setspn -A MSSQLSvc/SqlHostname:1433 SqlHostname

2. On each primary site, make sure that the SMS_SiteSystemToSQLConnection security group contains the computer accounts or SMS service accounts for all the child servers that report to the primary site. Typically, these accounts are added to the SMS_SiteSystemToSQLConnection security group when a site is installed. If the Setup program cannot add the account, the following site status message is logged in the SMS Administrator Console:
4908 - Site Component Manager could not add machine account "%1" to the SQL Access Group "%2"on the SQL Server machine "%3".

3. The Kerberos ticket cache may have to be reset. Use the Kerbtray tool from the Windows 2000 Server Resource Kit to clear the existing Kerberos ticket cache. To download the Kerbtray tool, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyID=4e3a58be-29f6-49f6-85be-e866af8e7a88&displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyID=4e3a58be-29f6-49f6-85be-e866af8e7a88&displaylang=en)
For more information about how to use the Kerbtray tool, click the following article number to view the article in the Microsoft Knowledge Base:
232179 (http://support.microsoft.com/kb/232179/) Kerberos administration in Windows 2000

4. Make sure that the DNS server for the domain is listed first in the TCP/IP properties of the Management Point server.

5.The FQDN for the target domain must be listed at the top of the suffix search list on the Management Point server. To change the suffix search list, follow these steps:

a. Click Start, click Run, type ncpa.cpl, and then click OK
.
b. Right-click the connection that you want to change, and then click Properties.

c. In the Connection Name Properties dialog box, select Internet Protocol (TCP/IP) under This connection uses the following items, and then click Properties.

d. On the General tab, click Advanced, and then click the DNS tab.

e. Click Append these DNS suffixes (in order), click the target domain, and then move the target domain to the top of the list by clicking the scroll arrow.

f. Click OK two times, and then click Close.

http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B886143

WORKAROUND
To work around this problem, manually configure an SPN for the site database. To manually configure an SPN for Microsoft SQL Server, follow these steps:

1. Log on to the SQL Server-based server that is hosting the SMS 2003 site database

2. Obtain and install the Setspn.exe utility. For information about how to obtain and install the Setspn.exe utility, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyID=5fd831fd-ab77-46a3-9cfe-ff01d29e5c46&displaylang=en

3. Click Start, click Run, and then type a Setspn.exe command in the Open box using the following syntax:

setspn -A MSSQLSvc/Host:port domainname\serviceaccount
For example:
C:\>setspn -A MSSQLSvc/lphbar2.hemlock.com:1433 hemlock\delegation
In this example, "lphbar2" is the host name of the server that is running SQL Server, "hemlock" is the Microsoft Windows 2000 domain name, and "delegation" is the domain account under which SQL Server is running.
4. Click OK to run the Setspn.exe utility

OR

http://support.microsoft.com/kb/829868/

1. Click Start, point to Programs, point to Windows 2000 Support Tools, click Tools, and then click ADSI Edit.

2. Expand Domain NC, and then expand CN=Users.

3. Right-click the account that starts the SQL services, and then click Properties.

4. In the Properties dialog box, click ServicePrincipalName in the Select a property to view box, and verify that entries that are similar to the following entries exist:
FQDN SPN entry:
MSSQLSvc/sqlhost.mydomain.com:1433

NetBIOS SPN entry:
MSSQLSvc/sqlhost:1433

Windows XP SP3 upgrade issue on HP Pavilion

If you see below error after installing Service Pack 3 for Windows XP the most possible casue would be that the Service Pack 3 update copies an Intel power management driver to the computer that was not on the computer before the update. Computers with AMD processors may experience a blue screen error that displays similar to the following

A problem has been detected and Windows has been shut down to prevent damage to your computer...
Technical information:
*** STOP: 0x0000007E (0xC0000005, 0xFC5CCAF3, 0xFC90F8C0, 0xFC90F5C0
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED


Only perform this procedure on computers that are using AMD processors.

Step 1: Disable Intel Power Management

Prevent the Intel Power Management driver from loading during system startup:
1. Restart the computer in Safe Mode:

a. Turn off the computer by pressing and holding the power button until the computer shuts down.

b. Wait about 5 seconds.

c. Press the power button to turn on the computer.

d. Turn on the computer and immediately begin pressing the F8 key repeatedly (at the HP or Compaq logo screen) until the Windows Advanced Options Menu appears.

e. Press the Up Arrow key until Safe Mode (top of list) is highlighted, and press the Enter key.

f. Press Enter again if an OS selection screen displays.
The Computer restarts into Safe Mode.

If the computer does not restart to Safe Mode and continues to display the Stop error, skip to the next section: STEP II .

2. Click Yes in the “Windows is running in safe mode” window.

3. Right-click the Start button, and select Explore .

4. Browse to C:\Windows\System32\Drivers.

5. Find and right-click the file intelppm.sys .
Select Rename and type the text: XXXintelppm.syx .
Press Enter and look to make sure the file was renamed successfully.

6. Close the Explorer window, and restart Windows.
The error no longer opens and the computer starts normally.

NOTE: If desired, you can delete the renamed file "XXXintelppm.syx".


Step II: Use Microsoft Recovery Console to rename intelppm.sys

If the computer is unable to open Windows XP Safe Mode, use Microsoft Windows Recovery Console:

1. Restart your computer in the Microsoft Windows Recovery Console.

a. Turn off the computer by pressing and holding the power button until the computer shuts down.

b. Wait about 5 seconds.

c. Press the power button to turn on the computer.

d. Turn on the computer and immediately begin pressing the F8 key repeatedly (at the HP or Compaq logo screen) until the Windows Advanced Options Menu appears.

e. Press the Down Arrow key until Return to OS Choices Menu (bottom of list) is highlighted, and press the Enter key.

f. Press the Down Arrow key until Microsoft Windows Recovery Console is highlighted, and press the Enter key.

g. At the screen “Which Windows installation would you like to log onto” type the number that matches C:\Windows, and press the Enter key.

h. When prompted, type the Administrator password and press the Enter key. If no password has been created, leave the password filed empty, and press the Enter key.
The Microsoft Windows Recovery Console opens and a command prompt is shown.

2. At the C:\WINDOWS> prompt, type the following: cd c:\windows\system32\drivers
Make sure the text has been entered correctly and press the Enter key.
At the C:\WINDOWS\SYSTEM32\DRIVERS> prompt, type the following: rename intelppm.sys XXXintelppm.syx

3. Make sure the text has been entered correctly and press the Enter key.
The computer restarts. If prompted, select Start Windows Normally and press the Enter key.
The error no longer opens and the computer starts normally.

NOTE: If desired, you can delete the renamed file "XXXintelppm.syx".

http://h10025.www1.hp.com/ewfrf/wc/genericDocument?docname=c01457284&cc=us&dlc=en&lc=en&jumpid=reg_R1002_USEN

Windows XP SP3 upgrade issue

When you install Windows XP SP3 from download WindowsXP-KB936929-SP3-x86-ENU.exe and find out Windows keeps on rebooting after that upgrade. Below are the steps you should take to resolve this issue.

1. Boot from a Windows XP CD and go for the repair option by keen on pressing F8 when you see BIOS screen.

2. Go to c:\windows\system32\ and make a copy of gdi32.dll

3. Copy gdi32.dll from c:\windows\servicepackfiles\i386\gdi32.dll to c:\windows\system32\gdi32.dll.

3. Reboot normally

Windows XP SP3 upgrade issue using SCCM

I pushed Windows XP SP3 from SCCM and find out Windows keeps on rebooting after that upgrade. Below are the few thing one have to check before creating SCCM package (see details in Packaging Windows XP SP3)

1. Boot from a Windows XP CD and go for the repair option by keen on pressing F8 when you see BIOS screen.

2. Go to c:\windows\system32\ and make a copy of gdi32.dll

3. Copy gdi32.dll from c:\windows\system32\Cache\gdi32.dll to c:\windows\system32\gdi32.dll.

4. Reboot normally

SMS_REPORTING_POINT

Problem viewing report using IE

An error occurred when the report was run. The details are as follows:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
Error Number: -2147217843
Source: Microsoft OLE DB Provider for SQL Server
Native Error: 18456

Also in mpcontrol.log file
“Http verification .sms_aut (port 80) failed with status code 500, Internal Server Error”
End of the file…
Solution

http://support.microsoft.com/?id=832109

Run the command cliconfg on the site server make sure that namedpipe and tcpip are added.
Check all the settings and Restart the IIS server, SMS site component server

You need to run dcomcnfg.exe from the Site server.
Expand:
Computers
My Computer
DCOM Config

Locate the component:
SMS_REPORTING_POINT

Right-Click, select Properties, select Security

Customize and edit:

Launch and Activation Permissions
Configuration Permissions

Add the necessary user's.

SMS_SITE_COMPONENT_MANAGER

SMS Site Component Manager failed to reconfigure site system "\\" to receive SMS server components.

Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager cannot reinstall any SMS server components on this site system until the site system is reconfigured successfully. SMS Site Component Manager will automatically retry this operation in 60 minutes. To force SMS Site Component Manager to immediately retry this operation, stop and restart SMS Site Component Manager using the SMS Service Manager.

SOLUTION

Run the command cliconfg on the site server make sure that namedpipe and tcpip are added

SMS_MP_CONTROL_MANAGER

MP Control Manager detected MP is not responding to HTTP requests. The http error is Unauthorized.

Possible cause: MP service is not started or not responding.
Solution: Manually restart the SMS Agent Host service on the MP.

Possible cause: IIS service is not responding.
Solution: Manually restart the W3SVC service on the MP.

Possible cause: MP encountered an error when connecting to SQL Server.
Solution: Verify that the SQL server is properly configured to allow Management Point access. If using a standard SQL security account, verify that the SQL Server is configured to allow standard SQL Security; or configure the Management Point to use an NT integrated security account, with appropriate access. If using integrated security, verify the account used by the MP to connect to the SQL server is a member of the SMS_SiteSystemToSQLConnection_ group on the SQL server, that the account is not locked out, and that the account password is not expired. (In standard security, the default account is SMS_SQL_RX_.)

Possible cause: The SQL server Service Principal Names (SPNs) are not registered correctly in Active Directory
Solution: Ensure SQL server SPNs are correctly registered. Review Q829868.

Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which SMS is configured to communicate.
Solution: Verify that the Default Web Site is configured to use the same ports which SMS is configured to use.

Possible cause: The Default Web Site is disabled in IIS.
Solution: Verify that the Default Web Site is enabled, and functioning properly.

Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges.
Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy.

SOLUTION

http://support.microsoft.com/?id=832109

Use cmd line “cliconfg” and make sure that you selected “Named Pipes” TCP/IP on “Enabled protocols by order:” box on right side of “General” tab.

Check “colleval.log and slpsetup.log” file.

Go to
1)
• Site Hierarchy  NYC-  site Settings  Site Systems

• Right click \\ go to properties

• Click Reporting Point” and make sure “use this site system as a reporting point” is checked.
2)
• make sure if your using advanced security that the MP machine account is in the SiteSystemToSQLServer connection group.

If you are in standard security, make sure that the account specified on the admin UI has rights to the SQL server (is a member of the SiteSystemToSQLserver connection group)
1. Click Start, point to Programs, point to Windows 2000 Support Tools, click Tools, and then click ADSI Edit.
2. Expand Domain NC, and then expand CN=Users.
3. Right-click the account that starts the SQL services, and then click Properties.
4. In the Properties dialog box, click ServicePrincipalName in the Select a property to view box, and verify that entries that are similar to the following entries exist:

FQDN SPN entry:
MSSQLSvc/sqlhost.mydomain.com:1433
NetBIOS SPN entry:
MSSQLSvc/sqlhost:1433