28 March, 2010

Project Management

What is a Project?
Project is a temporary assignment which has a definitive start and end date. Project can be considered successful when it meets the objectives of the Stakeholders. Project can be ended on successful closure, or when its objective can't be met, or when the need no longer exists.

What is Project Management?
Project Management is the application of knowledge, tools, skills and techniques to Project activities to meet Project requirements. Project management consists of 5 process groups, these are

  • Initiating – it is the process of determining if a Project is valid and can be delivered successfully
  • Planning – it produces how a plan for Project delivery by defining WBS with Schedule.
  • Executing – it is the actual delivery of project which is conducted using Project processes.
  • Monitoring and Control – It is where Project Manager and Project Management team ensures that the project is delivered on time, on budget, with required resources and the Project is delivered as initiated.
  • Closing – it is gaining final acceptance of the Project and ensuring that the Project is successfully delivered.

What is Project Process?
Project process is defined for the Project delivery team. It consists of

  • Analysis
  • Design
  • Development
  • Implementation

What is Project Lifecycle?
Project management processes and Project processes together form the Project Life Cycle. The relationship of Project management and project processes are illustrated in the chart below

Monitoring
and
Control

Initiating

 
 

Executing

Analysis

Design

Development

Implementation

Closing

 
 


 

What is Project Management Office?
Project Management Office (PMO) is an Organization body or entity which is assigned with various responsibilities of centralized and coordinated management of project sunder its domain. The responsibilities can vary from Project management support function to directly managing the projects.


 


 


 


 

24 March, 2010

Directory Service Requirements for Exchange 2010

Component

Requirement

Schema master

The schema master must be running any of the following:

  • Windows Server 2003 Standard Edition with Service Pack 1 (SP1) or later (32-bit or 64-bit)
  • Windows Server 2003 Enterprise Edition with SP1 or later (32-bit or 64-bit)
  • Windows Server 2008 Standard or Enterprise (32-bit or 64-bit)
  • Windows Server 2008 R2 Standard or Enterprise

Global catalog server

In each Active Directory site where you plan to install Exchange 2010, you must have at least one global catalog server running any of the following:

  • Windows Server 2003 Standard Edition with SP1 or later (32-bit or 64-bit)
  • Windows Server 2003 Enterprise Edition with SP1 or later (32-bit or 64-bit)
  • Windows Server 2008 Standard or Enterprise (32-bit or 64-bit)
  • Windows Server 2008 R2 Standard or Enterprise

Domain controller

In each Active Directory site where you plan to install Exchange 2010, you must have at least one writeable domain controller running any of the following:

  • Windows Server 2003 Standard Edition with SP1 or later (32-bit or 64-bit)
  • Windows Server 2003 Enterprise Edition with SP1 or later (32-bit or 64-bit)
  • Windows Server 2008 Standard or Enterprise (32-bit or 64-bit)
  • Windows Server 2008 R2 Standard or Enterprise

Active Directory forest

Active Directory must be at Windows Server 2003 forest functionality mode or higher.

Extending Database Size limit for Exchange 2010 Standard edition

You can use Registry Editor to modify a database size limit in Microsoft Exchange Server 2010. The default database size limit for Exchange 2010 Standard Edition is 50 gigabytes (GB). There is no default database size limit for the Exchange 2010 Enterprise Edition. The Exchange store checks any database size limits periodically and dismounts a database when the size limit is reached. You can modify the database size limit by adding or changing a value in the registry.

  1. Start Registry Editor (regedit).
  2. Locate the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<SERVER NAME>\Private-<database GUID>
  3. If the Database Size Limit in GB DWORD exists for the subkey, change its value to the desired size in gigabytes.
  4. If the Database Size Limit in GB DWORD doesn't exist for the subkey, create a new DWORD with that name, and then set its value to the desired size in gigabytes.


 

You can get the database guide by the below powershell cmdlet

Get-MailboxDatabase -Identity "<server name>\<database name>" | Format-Table Name, GUID

Supported Exchange 2010 Coexistence Scenarios

 

The following table lists the scenarios in which coexistence between Exchange 2010 and earlier versions of Exchange are supported.

Coexistence of Exchange 2010 and earlier versions of Exchange Server

Exchange version

Exchange organization coexistence

Exchange 2000 Server

Not supported

Exchange Server 2003

Supported

Exchange 2007

Supported

Mixed Exchange 2007 and Exchange Server 2003 organization

Supported


 

You can't upgrade an existing Exchange 2000 organization directly to Exchange 2010. You must first upgrade the Exchange 2000 organization to either an Exchange 2003 or Exchange 2007 organization, and then you can upgrade the Exchange 2003 or Exchange 2007 organization to Exchange 2010. It is recommend that you upgrade your organization from Exchange 2000 to Exchange 2003, and then upgrade from Exchange 2003 to Exchange 2010.