December 2005 - Posts
To maintain product compliance in your organization, you must first determine if there are compliance issues by analyzing data in your organization. By using the analysis results, you can determine if there are any issues that need to be resolved.
To use the product compliance feature, you must generate product compliance data. Product compliance data is a collection of the software guidelines and standards that are set in your organization and organized and stored in a specific way. Every compliance guideline must include two key data items: compliance type and compliance level.
Compliance type A type of product guideline or standard. You can create as many compliance types as required in your organization.
Compliance level A descriptive measure of the level of product compliance with respect to a specific compliance type.
For example, your organization might set a requirement to use only the latest version of Microsoft Office. To detect compliance issues with this standard, you can define an Office Standard compliance type. For that compliance type, you might define the following compliance levels: compliant, noncompliant, and compliant with issues - requires an update. Using these definitions, you can create the following product guidelines:
Microsoft Office 2003 is compliant with the Office Standard compliance type.
Microsoft Office XP is compliant with issues - requires an update with the Office Standard compliance type.
Microsoft Office 2000 is noncompliant with the Office Standard compliance type.
In a similar way, you can define other product guidelines to generate additional product compliance data. You can then run queries and reports that compare product compliance data against software inventory data or software metering data to determine which clients are noncompliant.
To resolve compliance issues, you can use the software distribution feature to upgrade software or to add specific updates to bring software into compliance. You might need to remove noncompliant software that cannot be updated.
More Information: SMS 2003 Operations Guide
When you use Microsoft Operations Manager (MOM) 2000 or MOM 2005 to monitor a Microsoft Windows 2000-based or Microsoft Windows Server 2003-based domain controller that has the MOM Active Directory Management Pack installed, the MOM Replication health monitoring may fail. When this problem occurs, the Windows Server 2003-based domain controller reports an error event back to the MOM Management Server, and the following events appear in the Alerts pane of the MOM Operations Console:
The script ‘AD Replication monitoring’ encountered a runtime error. Failed to determine whether the WMI replication provider is installed. The error returned was: ‘Invalid Parameter’ (0x80041008)
AD Remote Topology Discovery cannot determine whether the WMI Replication Provider is installed. The error returned was: ‘Invalid Parameter’ (0x80041008).
This problem occurs when the Replprov.dll file tries to access a pointer that is not valid. The Replprov.dll file is used by the MOM Active Directory Management Pack to retrieve Active Directory replication-related information, including replication status. When this problem occurs, the Replprov.dll file cannot determine the replication status of the domain controller, and the error messages are generated.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article.
Stored shadow copies of backup replicas are overwritten even if there is sufficient storage space allocated for shadow copies in Microsoft System Center Data Protection Manager (DPM) 2006. This symptom typically only affects protected volumes with less than 25 gigabytes (GB) of data.
This problem occurs because DPM 2006 incorrectly determines the minimum required disk space threshold that is used to allocate space for shadow copy storage on the DPM 2006 server. The Volume Shadow Copy Service (VSS) uses a minimum disk space threshold for shadow copy area disk allocations. When the threshold for the minimum disk space that is required is incorrect, stored shadow copies can be overwritten.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix.
More Information: Microsoft KB Article 910330
Error Message:
Failed to create data source for data warehouse. An exception occurred.
Check that you can access the SQL Services Reporting Server from this
machine. Error Code : -2147467259 (Unspecified error)
Workaround:
1. Open Registry Editor.
2. In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. Right-click "Lsa", point to "New", and then click "DWORD Value".
4. Type "DisableLoopbackCheck" for the name, and then
press ENTER.
5. Right-click "DisableLoopbackCheck", and then click "Modify".
6. In the "Value data" box, type "1" to enable it, and
then click "OK".
7. Quit Registry Editor, and then restart your computer.
Source: My 9th Microsoft KB Article
There are no built in tools for uninstall the SMS Advanced Client remotely.
You must need to run the uninstallation on each SMS client or by logon script.
However, You can download a useful tool-PsExec from Sysinternals.
PsExec is a light-weight telnet-replacement that lets you execute processes on other systems, complete with full interactivity for console applications, without having to manually install client software. PsExec's most powerful uses include launching interactive command-prompts on remote systems and remote-enabling tools like IpConfig that otherwise do not have the ability to show information about remote systems.
To uninstall the SMS Advanced Client remotely by PsExec.
- Share the MOM resources kit tool-ccmclean.exe to the network share first. And configure the permission of the network share.
- Place the PsExec under C:\ (or other root)
- Open command prompt.
- Run the following command to uninstall the remote SMS Advanced Client: C:\PsExec.exe \\remote_computer_name -u Domain\Domain_Admins -p Domain_Admins_Password \\network location\shared_folder_name\ccmclean.exe
- Click Enter and wait about 5mins for the uninstallation.
Official!
How to use Microsoft System Center Data Protection Manager 2006 to help protect an Exchange server
This article describes how to use DPM 2006 to help protect an Exchange server. The methods that this article describes are for the following Exchange Server versions:
| • |
Microsoft Exchange Server 2003 |
| • |
Microsoft Exchange 2000 Server |
| • |
Microsoft Exchange Server version 5.5 |
| • |
Microsoft Exchange Server 5.0 |
| • |
Microsoft Exchange Server 4.0 |
Note The methods in this article are tested with the Windows NT Backup program. If you select to use a third-party backup solution, follow the recommended third-party procedures for backing up the Exchange server before you use DPM 2006 to help protect the Exchange server.
More Information: Microsoft KB Article 909644
Use the following SQL Statement to query the OS language.
select SMS_R_System.ResourceId, SMS_R_System.ResourceType,
SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier,
SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from
SMS_R_System inner join SMS_G_System_SoftwareProduct on
SMS_G_System_SoftwareProduct.ResourceID = SMS_R_System.ResourceId where
SMS_R_System.OperatingSystemNameandVersion like "%Server 5.2%" and
SMS_G_System_SoftwareProduct.ProductLanguage = 1028
* %Server 5.2%=Windows Server 2003
* 1028=Traditional Chinese, 1033=English..etc
Source: My 8th Microsoft KB Article