welcome System Center 2007!

System Center Operations manager 2007 in Egypt

قُل لّوْ كَانَ الْبَحْرُ مِدَاداً لّكَلِمَاتِ رَبّي لَنَفِدَ الْبَحْرُ قَبْلَ أَن تَنفَدَ كَلِمَاتُ رَبّي وَلَوْ جِئْنَا بِمِثْلِهِ مَدَداً

Tuesday, May 29, 2007

Upgrading from evaluation version of System Center Operations Manager 2007 to the full product version

You can upgrade the 180-day evaluation version of Microsoft System Center Operations Manager 2007 to the full product version. To do this, you do not have to upgrade individual files.

This upgrade operation requires that you use a Microsoft Select CD image that is available as part of the Microsoft volume licensing agreement.

The Select CD image includes a Licensing Wizard to update the license.

To upgrade the 180-day evaluation version of Operations Manager 2007 to the full product version, follow these steps:

  • Download the Select CD image for Operations Manager 2007. To do this, visit the following Microsoft Web site: https://licensing.microsoft.com
  • Extract the Select CD image.
  • Locate the following folder in the location where you extracted the Select CD image:\SupportTools\system_architectureNote The system_architecture placeholder represents the architecture of the computer that you are using.

For example, this placeholder should be i386 on an x86-based computer.

  • Run the LicenseWizard.msi file, and then follow the instructions in the Licensing Wizard.
    Microsoft KB 937826

Operations Manager 2007 Performance and Scalability

The official tool for performance and scalability planning will be System Center Capacity Planner (SCCP).
SCCP combines the best practices presented in this document along with performance modeling and simulation to build detailed sizing guidance specific to your environment

you can use this document which describes performance and scalability guidelines to consider when planning a Microsoft System Center Operations Manager 2007 deployment.

Operations Manager 2007 Performance and Scalability White Paper


Monday, May 28, 2007

Understanding Audit collection server Database table “Dtconfig Table”

Dtconfig Table contain an important setting to configure ACS collector and database, I will list all this setting and the default values and how to work with this table.

Convert timestamps to local time
Use this value to use the local time to stamp the collected event
1 = use local time
0= use UTC time

Database schema version
This is the schema version value, it is now equal 6

Perform index maintenance
Use this value to configure the Database to perform index maintenance
1= the option is enabled.
0= the option is disabled.

Table switch offset in seconds since midnight UTC
Use this value to configure when the ACS will use another table to store the collected events since midnight UTC
The value 82800 = 82800/ 60*60 = 23 UTC
This value 82800 = 2:00 AM Egypt daylight time.
The table will be changed at 2:00 AM but we did not configure the interval until now.

Table switch interval in seconds
Use this value to configure the interval between every table
The value 86400 = 24 hours, so the table will be switched every day “24 hours” at 2:00 AM Egypt daylight time.

Number of partitions
Use this value to configure how many tables will be available in the Database to store the security events.
The value 15 = the ACS will store the security in 14 table and other will be running.
This value must be configure with the registry key below
EventRetentionPeriod “This vale was configured in hours”

For Number of partitions = 15 and Table switch interval in seconds = 86400 the EventRetentionPeriod will equal to 14 *24 = 336 in decimal.

For Number of partitions = 31 and Table switch interval in seconds = 86400 the EventRetentionPeriod will equal to 30 *24 = 720 in decimal.

How the OpsMgr 2007 Agent Deployment affect the managed system

source: Operations Manager blogger by Kerrie Meyler and Cameron Fuller

During installationof the SCOM agent the following ranges of impacts on the system:

Processor: 29-37% increase during installation
Disk: 18-19 additional pages per second
Disk: 154 MB data (%programfiles%\System Center Operations Manager 2007)Network: 11 MB data sent to the system during installation
Memory: 22 MB less available memory

After the installation was complete
Processor: 3-4%
Disk: 0.5 additonal pages per second
Disk: 156 MB data (%programfiles%\System Center Operations Manager 2007)
Network: .5-.6 MB/min additional traffic
Memory: 11 MB less available memory

for more details about the Test check the link below:

Friday, May 25, 2007

Configuring Audit Collection Services !

After Installing and Configuring Audit Collection Services, I found some special setting will help the OpsMgr administrator to control ACS service Behavior , my installation document of ACS was updated with this items:


You can download the full docuemnt from the following link


or contact me @ tarek_877@hotmail.com to get a copy

Have a Nice Day with System Center Operation manager 2007

Tuesday, May 22, 2007

Egypt With System Center Operations Manager 2007

Today, i have finished the installtion and Configuration of System Center Operations manager in Suez Cement Group

the Operations manager server monitor more than 30 Servers.

I think this the First Installtion of SCOM 2007 In Egypt

Who do it Before Me in EGYPT?

Monday, May 21, 2007

Installing and Configuring Audit Collection Services

Audit Collection Services (ACS) collect local Security event log records generated by audit policy and store them in a centralized database.
Audit Collection Services (ACS) consolidates individual Security logs into a centrally managed database.
Only a user who has the right to access the ACS database can run queries and create reports on the collected data.
Audit Collection Services (ACS) consists of three components:

ACS forwarders
ACS collector
ACS database
Audit Collection Services (ACS) requires mutual authentication between the ACS collector and each ACS forwarder.
All Data between ACS forwarders and the ACS collector are encrypted.
Data is not encrypted between the ACS collector and the ACS database.
You can encrypt all communication between ACS collector and the ACS database using Secure Sockets Layer (SSL) or Transport Layer Security (TLS).
ACS Forwarders send all security event log to ACS Collector using inbound TCP port 51909 “open this port in case of you have firewall”.
A local Security log of any server can be accessed by the local administrator, but cannot access ACS database by default.
You can assign a group with permissions to access the audit database to views and queries the ACS database.
Local administrator cannot change Configuration of ACS forwarder, all changes must be come from ACS collector.
ACS forwarder closes the inbound TCP port used by ACS collector after authentication so only outgoing communication is allowed.
ACS collector must terminate and reestablish a communication channel to make any configuration changes to an ACS forwarder.

To Installing and Configuring Audit Collection Services you can download the full docuemnt from the following link
or contact me @ Tarek_877@hotmail.com to get a copy

Saturday, May 19, 2007

Install and configure System Center Operation Manager 2007

  • Microsoft System Center Operations Manager 2007 can monitor end-to-end information technology services.
  • Operations Manager 2007 can monitor large environments and organizations, and use Microsoft application and operating system knowledge to resolve operational problems.
  • Operations Manager 2007 provides one consolidated Operations Console.
  • Operations Manager 2007 Reporting feature has been enhanced and focuses on customer scenarios, performance, and usability.
  • Operations Manager 2007 Client Monitoring feature used to monitor operating systems and applications for errors and participate in the Customer Experience Improvement Program (CEIP).
  • Operations Manager 2007 Client Monitoring feature consist of the following components “Agentless Exception Monitoring (AEM) - Customer Experience Improvement Program (CEIP) - Management Packs for Windows-based workstation operating systems and applications”.
  • Operations Manager 2007 is integrated with Active Directory Domain Services (AD DS) which will allow assigning agent-managed computers to Management Groups.
  • Active Directory integration will allow Manual agent deployment using MOMAgent.msi to computers to get its Management Group information from Active Directory automatically.
  • Operations Manager 2007 Role-based security limit users privileges to have access to various aspects of Operations Manager 2007.
  • Delegation of Operations Manager 2007 roles, such as Operator, utilizing AD DS user accounts and security groups.
  • Operations Manager 2007 integration with Active Directory provide Authentication and authorization for Operations Manager 2007 Management Groups using AD DS.
  • Microsoft System Center Operations Manager 2007 contain many server role which can be installed on one server or distributed on multiple servers, some of this roles support Microsoft cluster and other did not support.
  • Microsoft System Center Operations Manager 2007 contain the following server roles:
  1. Operational database
  2. Audit Collection Services (ACS) database
  3. Reporting Data Warehouse database
  4. Reporting database
  5. Root Management Server
  6. Management Server
  7. Administrator console
  8. Audit Collection Services (ACS) collector
  9. Gateway Server
  10. Web Console server
  11. Agent

To Install Microsoft System Center Operations manager you can download the full docuemnt from the following link
or contact me @ tarek_877@hotmail.com to get a copy

Thursday, May 17, 2007

Migrate from MOM 2005 to System Center Operations Manager 2007

  • Operations Manager 2007 supports a side-by-side migration model.
  • Operations Manager 2007 can be deployed along side your MOM 2005 implementation to provide dual monitoring.
  • All Operations Manager 2007 components can run on side-by-side on the same systems as MOM 2005.
  • You can migrate any MOM 2005 Management Packs and any custom Management Packs you have created to Operations Manager 2007 using the Migration Wizard.
  • The Migration Wizard converts MOM 2005 AKM-format to the new Operations Manager 2007 XML-format.

Monday, May 14, 2007

Microsoft Egypt - System Center Operations Manager 2007

Welcome Welcome System Center !

Today 14/05/2007 is the first day in Microsoft Egypt For the new product System Center Operations Manager 2007
System Center Operations Manager 2007 is end-to-end service management solution

Sunday, May 6, 2007

System Center Essentials 2007 installation document

Welcome welcome System Center !

This is my first document in SCE 2007

This document for how to install SCE 2007
You can Download it from the following link
Installing System Center Essentials 2007

or contact me @ tarek_877@hotmail.com get a copy

System Center Essentials 2007 Installation tips and tricks

the following points are required to be checked before start installtion SCE 2007:
  • Upgrading from any Beta and RC versions to System Center Essentials 2007 RTM isn’t supported.
  • Windows 2000 SP4 clients need to connect to windows update to update the Windows Update client with the last version.
  • Explicitly configure a proxy server in your Internet Explorer connection settings to be able to import a third party update catalog when proxy server setting required integrated Windows authentication.
  • A remote SQL Server 2005 instance must not installed on Domain controller.
  • Remove the SQL Native Client using Add or Remove Programs, if you get the error message: "An installation package for the product Microsoft SQL Native Client cannot be found. Try the installation again using a valid copy of the installation package 'sqlncli.msi'.", and re-run the installation.
  • In SQL Server Workgroup Edition, turn off Address Windowing Extensions (AWE) before the installation.
  • Install IIS with ASP.NET before install NET Framework 2.0 and NET Framework 3.0, else you need to re-register ASP.NET 2.0 and 3.0
  • Stop the WSUS 2 synchronization before SCE installation, if you are upgrading from WSUS 2 to SCE 2007.
  • Ensure there is no computer group in WSUS called All Clients and All Servers before installation, else delete it.
  • If you upgrade from WSUS 3 RC to SCE 2007, you need to reassign the certificate to the WSUS Administration Web site after upgrade.
  • Don’t use compressed drive for your installation locations.
  • You need to use Configure local policy on the DC to point to the Essentials 2007 management server, if the domain controller of a trusted domain fails to pick up the Essentials 2007 managed computers policy.
  • To use domain policy, install the GPMC on the Essentials 2007 management server.
  • Don’t use SQL Server Reporting Services (SRS) instance that is configured to use SSL during Essentials 2007 setup.
  • Ensure the printer spooler service is enabled on a managed computer to enable inventory collection.
  • You will not be able to generate charts if you are using Microsoft SQL Server 2005 Express Edition, else reinstall SCE with other SQL version.
  • Remove the self-signed certificate from the default Web site before installing the Essentials 2007 management server.
  • After setup has completed successfully, re-assign the self-signed certificate to the default Web site.
  • At this time you can not install SCE 2007 if your domain netbois name not the same as FQDN, this issue will be fixed soon

Friday, May 4, 2007

Installing System Center Essentials 2007

System Center Essentials 2007 is a new management solution in the System Center family of IT systems management products specifically designed for midsized businesses.
System Center Essentials 2007 is designed to be easily installed and configured.

System Center Essentials 2007 can mange up 500 Microsoft Windows-based client computers, 30 Microsoft Windows-based servers, and 50 Network devices when the Essentials 2007 database is installed remotely.

Only 10 remote Essentials 2007 consoles can be used at a time.

an installtion document will be avilable soon, it will contain the following items:
  • System Center Essentials 2007 REQUIREMENTS

Thursday, May 3, 2007

How to Import hotfixes from the catalog site to WSUS 3 Server

With Microsoft WSUS V3 you can import any update from Microsoft Catalog to update the clients with this Update.
You must be logged on to the computer as an administrator to import the hotfixes.
Use any computer that has the WSUS administrative console installed to import hotfixes from the catalog site.
In the WSUS administrative console, select the Updates node, and in the Actions pane click Import Updates.
A browser window will open at the Microsoft Update Catalog Web site.
You can browse this site for Windows hotfixes and hardware drivers.When you have found the ones you want, add them to your basket.
When you have finished browsing, go to the basket, specify a download location, and click Import to import your updates.

Wednesday, May 2, 2007

WSUS svchost/msi issue

With WSUS V2 some client face a great problem due to svchost.exe pegging the cpu of workstations, rendering the computer nearly unresponsive for minutes at a time.

If this problem occurs on your system you have to Combine the installation of the new client of WSUS V3 , with the latest MSI fix available in KB927891 available on Microsoft Download Center, Microsoft completely address the what we have fondly called the svchost/msi issue.

It’s important to keep in mind that the new client is only a partial solution and clients must have both KB927891 and the new 3.0 client installed for a full solution.

Tuesday, May 1, 2007

Windows Server Update Services 3.0

Microsoft announced that WSUS 3.0 has released April 30th and is available now on the Microsoft Download Center.

Installing and configuring WSUS Version 3


Upgrade to Windows Server Update Services Version 3