January 2006 - Posts
Usage
SMS 2003 Server Locator Point used to:
- When you are deploying Legacy Client or Advanced Client by Logon Script with capinst.exe, You have to add /SLP= in the logon script to connect to the Server Locator Point for locate the Client Access Point or Management Point to complete the installation. Legacy Client requires to connect to the Client Access Point.
- Advanced Client supports automatic site assignment by extending the Active Directory schema. If you want to use the automatic site assignment without extending the Active Directory schema, Advanced Client uses WINS server to lookup the Server Locator Point, and then use it to obtain the site code of the SMS site.
Required Configuration
You should configure the SMS 2003 Server Locator Point in the Central Site. To reduce the network traffic, you can enable the additional Server Locator Point in the Primary Child Site.
In Microsoft Windows Server 2003, you may receive the following error message when you use the synchronization with consistency check feature in Microsoft Data Protection Manager:
Access Denied
This problem occurs when the following conditions are true:
| • |
A user is granted permissions to folders or to files that have long file names. |
| • |
The short name of one or more files on the destination server does not match the short name of the corresponding files on the source server. |
The problem occurs because during a consistency check, both the long name and the short name of each file must match. Short names are assigned according to the order in which they are created. Therefore, the short names of the files on the destination server may not match the short names of the files on the source server. For example, this problem occurs in the following scenario:
| • |
The LongFileName02.txt file is created on the source server. The short name of the LongFileName02.txt file is LongFi~1.txt. |
| • |
The LongFileName01.txt file is created on the source server. The short name of the LongFileName01.txt file is LongFi~2.txt. |
| • |
A consistency check is run. The files are validated by using the long name in alphabetical order. The LongFileName01.txt file is validated first. |
| • |
A LongFileName01.txt file is created on the replica. This file is given the LongFi~1.txt short name. |
| • |
During the next synchronization, the LongFileName02.txt file is created. The short name of this file is LongFi~2.txt. |
In this scenario, the short names of LongFileName02.txt and LongFileName01.txt are exchanged.
The next time that you run a consistency check, the synchronization fails because the long name and the short name of each file do not match. Therefore, the replica remains inconsistent with the source server.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix.
More Information: Microsoft KB Article 906881
The System Center Reporting Manager 2006 Release Candidate build has been
released to BetaPlace <https://beta.microsoft.com>.
The following changes have been made in the Release Candidate from the Beta:
Improved setup to assist the SCRM Administrator with database and disk space planning
Added wildcard filters to reports to avoid large drop down lists
Added ability to report on SMS_DEF.MOF extensions.
Organized reports into folders
Improved report performance
Improved data warehouse performance
When you try to access the MOM 2005 Web Console on any machine, You may get the HTTP Error 403 - Forbidden Error.
It is cause the IIS configuration problem, to solve the problem:
1. Open Internet Information Services.
2. Expand Web Sites
3. Right click MOM 2005 Web console and Choose Properties
4. Select documents tab
5. Add default.aspx to the list.
Microsoft System Center Capacity Planner 2006 helps size and plan deployments of Microsoft Exchange Server 2003 and Microsoft Operations Manager (MOM) 2005 by providing you with the tools and guidance to deploy efficiently while planning for the future by allowing for "what-if" analyses in the following ways:
| • |
Proactive performance planning: Helping an organization meet their service level goals consistently, now and in the future. |
| • |
Infrastructure planning and optimization: Plan for IT purchases to optimize cost. |
| • |
Help to ensure success of Microsoft Exchange 2003 and MOM 2005 deployments: Use to plan correct amount of infrastructure needed for a new application to meet service level goals. |
| • |
Performance analysis and predictive reporting: Automatically report performance trends and bottlenecks to manage current and future performance issues. |
System Center Capacity Planner 2006 is designed to help you create a system architecture model for deploying a Microsoft server application, such as Microsoft Exchange Server 2003 or MOM 2005. A typical system architecture model consists of the following information:
| • |
Topology: Site locations, types of networks, network components, and network characteristics (bandwidth, latency) |
| • |
Hardware: Server distribution and characteristics, server and network mapping |
| • |
Software: Server role and service mapping, file and storage device mapping |
| • |
Usage profiles: Site usage and client usage |
After you create a model, you can run a simulation that provides a summary and details about the performance of the application and its supporting components.
You can get it from Technet Subscription or MSDN Subscription.
Learn More
When you try to create new availability report in MOM Reporting Console, You may see an error message.
"Invalid Object Name
'SC_Class_Group_View' and in the details it sais following: "An error has
occured trying to complete the operation. The result code returned was
0x80040e37. Please provide this number to technical support."
To solve this problem, Just run the "SystemCenterDTSPackageTask" scheduled tasks manually.