Thursday, May 28, 2009

Database Size Limit on Exchange 2007

In Exchange 5.5, Exchange 2000, and Exchange 2003 up until sp1 the standard edition had a database size limit of 16 GB. With the release of Exchange 2003 Sp2, Microsoft increased the database size limit to 75GB! The database size limit for the enterprise edition has always been unlimited (or limited by hardware...)

Here's the table taken from the Microsoft Site detailing the differences between Standard and Enterprise Edition for Exchange 2007:

According to this table, the database size limit is unlimited for the standard edition. It was a great surprise for me to notice the following event log entry after installing a 64bit standard version of Exchange 2007:

What's going on?
The Exchange Server 2007 Standard Edition has apparantly a hard coded licensing database size limit of 50 GB, and for Service Pack 1 this is set to 250 GB...


Can this be changed?
Yes :-) the database size limit of 50 GB can be increased by creating the Database Size Limit in Gb registry value.

How do you do this?
The following two pictures show you the entry you have to do in the registry to change this, and the third one shows you the result after dismounting and mounting the store again.


What's the source for this registry key?
http://technet.microsoft.com/en-us/library/aa997432.aspx



Whats new in SP1?
In Exchange 2007 Sp1 (beta at least) the default limit has been increased to 150GB.

Tuesday, May 19, 2009

Microsoft Exchange Server 2007 Management Tools (32-Bit)

Brief Description
Exchange Server 2007 is a native 64-bit application that includes 64-bit management tools. You can use the management tools to administer your Exchange Server environment remotely. If the remote computer is running a 32-bit operating system, you will need to download the 32-bit management tools.

Quick Details
Version:685.25
Date Published:5/7/2008
Language:English
Download Size:686.7 MB - 1527.3 MB*
*Download size depends on selected download components.


Overview

The Exchange management tools include the Exchange Management Console, the Exchange Management Shell, the Exchange Help file, the Microsoft Exchange Best Practices Analyzer Tool, and the Exchange Troubleshooting Assistant Tool.



The new Exchange Management Console (formerly named Exchange System Manager) provides Exchange administrators with a graphical user interface (GUI) to manage the configuration of Microsoft Exchange Server 2007 organizations. For more information about the improvements to the Exchange Management Console, see New Administration Functionality in the Exchange Management Console.



The Exchange Management Shell is a new Exchange-specific command-line interface based on Microsoft Windows PowerShell, formerly codenamed “Monad”. You can use the Exchange Management Shell to run a single command or a series of multiple commands for managing your Exchange Server 2007 servers and objects. For more information about the Exchange Management Shell, see Using the Exchange Management Shell.

System Requirements

  • Supported Operating Systems: Windows Server 2003 R2 (32-Bit x86); Windows Server 2003 Service Pack 1; Windows XP
To see additional requirements for this download, view the Exchange Server 2007 System Requirements.


Instructions


  1. Click the Download button on this page to start the download.

  2. Click Save, to save the download to your computer to install at a later time.

  3. View the Exchanger Server 2007 Help file for detailed instructions about how to install the Management Tools.


Files in This Download

The links in this section correspond to separate files available in this download. Download the files most appropriate for you.

Files in This Download

The links in this section correspond to separate files available in this download. Download the files most appropriate for you.
File Name:File Size

E2K7EN32.exe

686.7 MB

E2K7SP1EN32.exe

840.6 MB



Configure Exchange 2007 GAL (Global Address List)

Don't dabble with GAL settings. Either leave the configuration alone, and just let Outlook users see the Default Global Address List; or else, take the time to study, plan, and test before you implement custom Address Lists.

What is the Exchange 2007 Global Address List?

Configure Global Address List (GAL) Exchange 2007

  1. A directory service for Outlook users to find email addresses and distribution lists.
  2. THE phone book for email.
  3. An inventory of all Exchange 2007 objects.
  4. The mother of custom Address Lists.
  5. Some people refer to the GAL as the Global Address Book (Rather than List).

How to Find the Exchange 2007 GAL

  1. Launch the Exchange Management Console.
  2. Expand the Organization Configuration (Key point).
  3. Select the Mailbox node.
  4. Click on the Address Lists tab.
  5. Observe the Default Global Address List

Default Address Lists (See Screenshot above)

Once you realize that there are a handful of built-in Address Lists, you soon realize that you could create your own Custom Address Lists. However, be careful, don't create too many lists, and furthermore, give thought to meaningful names for your lists.

  • All Users
  • All Groups
  • All Contacts
  • All Rooms
  • Default Global Address Lists
  • Public Folders
  • (Custom Address Lists)

Updating a Global Address List in Exchange 2007

The situation, you want to modify the GAL, however, you discover that you cannot edit (or delete) the Default Global Address List. This is the master list of all the Exchange 2007 objects, and the operating system won't let you mess with it. Fortunately, there is a well respected work-around, create a new Global Address List, and then 'update' the mailbox. This procedure has its own PowerShell command.

PowerShell Commands to Manage GlobalAddressList

As an alternative to clicking in the Exchange Management CONSOLE, you could type commands in the Exchange Management SHELL. Using cmdlets like those below will save you time, more so when you realize that every Exchange 2007 configuration task has a faster command-line equivalent. Furthermore, certain commands are ONLY available in the Shell, for example, new-GlobalAddressList.

As a learning progression, by all means start with GUI Exchange Management Console, but note as each Wizard completes so it shows you the corresponding PowerShell commands. Why not save these so that in future you can use the cmdlets in the Shell?

Research in the Exchange Management Shell with:
get-Command *GlobalAddressList

Five verbs for GlobalAddressList
get, new, remove, set, and update. For example:
get-help new-GlobalAddressList

Note 1: As usual, PowerShell uses a singular noun: GlobalAddressList

Note 2: There is another family of cmdlets without the word 'Global', their noun is plain 'AddressList'.

Preliminary Step: Create a new Global Address List
Launch the Exchange Management SHELL and use this PowerShell cmdlet

new-GlobalAddressList -Name "Worcester" -IncludedRecipients MailboxUsers

Important: Firstly, you have to use PowerShell to create your new Global Address List (There is no equivelent command in the GUI). Secondly, once created, you can only edit it with the set-GlobalAddressList cmdlet.

Suggestion: Research the cmdlet new-GlobalAddressList, in particular the -conditional family of parameters. Try: get-help new-GlobalAddressList -full

Help with error message: 'Access to address list service on all Exchange 2007 servers has been denied' try the following.

a) Simply repeat the command! It worked for me, also maybe try a different name, I tried "Worcester2" the second time I ran the command.

b) Check the Services snap-in. Are all the Exchange services running, e.g. System Attendant?

c) Revert to the old trick of rebooting the server, maybe it has just received a 'Patch' or update.

Method: PowerShell - Exchange Management SHELL

The situation, you have created and defined a new Global Address List using the above cmdlet.

update-GlobalAddressList -Identity "Worcester"

Note 1: If you don't get the required result either create a new Global Address List, else use set-GlobalAddressList to modify the one you created earlier.

Guy recommends: SolarWinds LANsurveyorSolarwinds LANsurveyor

LANsurveyor will produce a neat diagram of your network topology. But that's just the start; LANsurveyor can create an inventory of the hardware and software on your machines and network devices. Other neat features include dynamic update for when you add new devices to your network. I also love the ability to export the diagrams to Microsoft Visio.

Finally, Guy bets that if you take a free trial of LANsurveyor then you will find a device on your network that you had forgotten about, or someone else installed without you realizing.

Managing Address Lists

Begin with a clear idea of what you want to achieve with a custom address list. Presumably, making it easier for Outlook users to find addresses ranks high on your agenda. If you are doing this task for real, as opposed to just learning about Exchange 2007 Address Lists, then involve at a cross-section of users before you design a complex, multi-levelled, address list scheme only to find that the end-users hate it.

Good news, behind the scenes Active Directory changes the members of the list dynamically based on LDAP queries.

Research in the Exchange Management Shell with:
get-Command *AddressList

Let me emphasise that these are simple Address Lists (There is no 'Global' word here).

Six verbs for AddressList
get, move, new, remove, set, and update. For example:
get-help update-AddressList

Note 1: There is another family of cmdlets without the word 'Global', their noun is plain AddressList.

Method 1: PowerShell and the Exchange Management SHELL

The situation, you have created, and defined a new Address List using the Exchange Management SHELL.

update-AddressList -Identity "Boston"

or

update-AddressList -Identity "All Users\Campus\Students"

Note 1: 'Students' is the name of the Address List. All Users\Campus is a sub-folder.

That's it! This is why people use PowerShell instead of the GUI! To be fair, you need to run the cmdlet below to see the names of possible Address Lists. Again, to be fair, everyone takes a peek in the GUI the first time they configure an item; it's for the repetitive tasks that PowerShell saves times.

get-AddressList

Method 2: Exchange Management CONSOLEUpdate Exchange 2007 Global Address List (GAL)

Here below is an alternative to PowerShell. Before you 'Apply' your Global Address List you may like to click on Edit, the benefit is that you can check, and if necessary, edit the settings.

  1. Launch the Exchange Management Console
  2. Expand the Organization Configuration node
  3. Select Mailbox.
  4. Click the Address List tab
  5. Select the particular Address List that you want.
  6. Click 'Apply' in the Actions pane. (Key point)
  7. The Apply Address List wizard should launch.
  8. On the Introduction page, complete the following fields:
  9. Apply the address list
    Immediately (Best)
    At the following time (If the server is busy).

What Happened to RUS in Exchange 2007?

Quite frankly, RUS was slow and cumbersome, so he won't be missed now that his role has been incorporated into Exchange 2007.

Exchange 2003's RUS (Recipient Update Service) has been replaced in Exchange 2007 by two PowerShell cmdlets, update-AddressList and update-EmailAddressPolicy.

Thus, don't go looking for RUS in Exchange 2007, instead launch the Exchange Management Shell and experiment with 'Address' family of cmdlets.

Exchange 2007 Email Address Policy

Exchange 2007's E-mail address policy generates email addresses for your users, contacts, and groups. This is important, for without an address nobody could send or receive emails. The killer reason to configure this setting is to adjust the way that email addresses display in the Exchange 2007 GAL. For example, small companies display email addresses as FirstName LastName, whereas large companies display prefer, Lastname, Firstname. It is small companies who are exapanding that need to change their Email Address Policy, this is how you can adjust the Exchange 2007 GAL settings.

Using the Exchange Management Console to Configure your E-Mail Address Policy

Stage OneE-mail address policy Exchange 2007

  1. Launch the Exchange Management Console.
  2. Expand the Organization Configuration
  3. Select the Hub Transport node (Key point).
  4. Click on the Address Lists tab.
  5. Click E-Mail Address Policies tab.
  6. Select the e-mail address policy that you want to edit.
  7. In the Actions pane, click Edit.

Stage Two - Follow the Address Policy Wizard

  1. On the Introduction page, review the name.
  2. From the Conditions page, view or edit the following fields:
  3. Select the condition(s) Use this section to set one or more conditions for your e-mail address policy. If you do not want to set any conditions for the policy, do not select any of the check boxes.
  4. On the E-Mail Addresses page, select the e-mail address, and then click Edit.
  5. You can now change the way email addresses display in the GAL,
    First name.last name.
    or Last name.first name.
    (and many other formats).

PowerShell Commands to Manage EmailAddressPolicy

Research in the Exchange Management Shell with:
get-Command *EmailAddressPolicy

Five verbs for EmailAddressPolicy
get, new, remove, set, and update

Note 1: Singular EmailAddressPolicy

How to Find the Exchange 2007 Offline Address Book

Principles and techniques that you learned with other Exchange 2007 'Address' names, will be useful for the Offline Address Book. Please take note, this is not the Global Address Book.

  1. Launch the Exchange Management Console.
  2. Expand the Organization Configuration.
  3. Select the Mailbox node.
  4. Click on the Offline Address Book tab. (Key point)
  5. Right-click on the Default Offline Address Book.
  6. Tick the box: Include the following address lists.
  7. Make your selection of Address List(s).


PowerShell Commands to Manage OfflineAddressBook

Research with:
get-Command *OfflineAddressBook

Six verbs for OfflineAddressBook
get, new, new, remove, set and update

Note 1: Singular OfflineAddressBook

Note 2: There is another family of cmdlets, their noun is OABVirtualDirectory.

Coexistence Exchange 2007 and Exchange 2003

Where Exchange 2007 and Exchange 2003 coexist, you can edit the GAL or the Address List objects from either Exchange 2003 or Exchange 2007. However, there are two 'gotchas'; firstly, you must upgrade Exchange 2003 objects before they can be edited by Exchange 2007. Secondly, if you do upgrade the object, then you cannot edit it from Exchange 2003.



Objects found in the Exchange 2007 GAL

I often say that being good at computing means being aware of subtle difference in Microsoft names. Exchange 2007's mail objects is a case in point. Pay careful attention to the difference between a mailbox enabled user and a mail-enabled user; a security group and a distribution group. Here is a list of the objects which you find the Global Address List.

  • Mailbox enabled accounts. Regular users with MAPI mailboxes Active Directory accounts.
  • Mail-enabled users. Contractors who have an Active Directory logon but no mailbox. (No mailbox in your Exchange Organization.)
  • Contacts. Suppliers, customers, people with email address outside your organization. No Active Directory account. Thankfully, contacts have a different symbol in the GAL.
  • Distribution groups. These can be Global or Universal Groups, but they are designed for email rather than security. These are sometimes referred to as DLs - Distribution lists instead of distribution groups. Pay attention to detail and examine the Members and MemberOf tabs.
  • Query-based distribution groups. Well worth setting up. Again, note the different symbol from other groups. Incidentally, I wish Microsoft would use different colors for different scopes of group. Say, Red for Universal and Green for Local Groups.
  • Mail-enabled groups. Security groups that have mailboxes. Guy says that unless you have a good reason, favour the classic Distribution group and avoid Mail Enabled Security Groups.
  • Public Folders. Mail-enabled public folders if your users need an easy way to post.

How the Exchange 2007 GAL works

All the address information is held by Active Directory. To the left of the @ is the username, to the right of the @, the email domain name. In fact, I think of the GAL as merely a fancy LDAP query which produces a list of addresses, for example guyt @ cp.com. The final piece of the address jigsaw is RUS (Recipient Update Service. RUS is the engine which generates and updates the email addresses that you see in the GAL.

If the GAL is slow to update, then look to the Global Catalog servers. Make sure that there is Windows 2007 Global Catalog server near the Exchange 2007 server. As you may know, the Global Catalog replicates a sub-set of all the user's properties, including Exchange features such as email address. So if Exchange has access to a local Global Catalog server, then its GAL will be up-to-date.

Clients

Potentially, any client who can query Active Directory can access the GAL. However, you can control who sees which list through read permission on the security tab found on the lists.

Summary - Exchange 2007 Global Address List (GAL)

It's only natural that Outlook users try and find each others email addresses in the GAL. But why would an administrator need to configure Exchange 2007's GAL? The most likely answers are: control how the names are displayed in the Global Address List, and possible the need for custom lists.dit.

Friday, May 15, 2009

REMOVE EXCHANGE FROM ONE SERVER

Before you remove a Microsoft Exchange Server 2003 server from a production environment that has multiple servers in the administrative group, make sure that you know all the roles that are held by the server. Take steps to move those roles to another server before you follow the steps in this article to remove the Exchange Server. For example, the server may hold special roles such SRS server or routing group master, or the server could be listed as a bridgehead server on a connector such as an SMTP connector or a routing group connector.

Be sure to remove the Exchange Server after you transfer the server specific Exchange roles. If you forget this, you may experience adverse effects including the following:

  • Mail flow may stop if the server is a Exchange bridgehead server.
  • Mail flow may be adversely affected if the server is the routing group master, because the link state data for the remaining servers in the site is not updated for each other and the link state data for the remaining servers in the site is not updated to other sites.
  • Outlook and OWA Free/busy problems may occur if the server is the site folder server.
  • And many other effects that you will notice after the removal

Before you remove Exchange 2003, you must disconnect all mailbox-enabled users from the mailboxes on the Exchange server. It is not possible to remove an Exchange Server when it has mounted mailboxes. If you think it is enough to dismount and delete every Exchange store – you are wrong. This is not a solution.

After all mailbox-enabled users have been disconnected; you can use the Exchange 2003 Setup program to remove Exchange 2003.

If you are not able to use the Exchange 2003 Setup program to remove Exchange 2003, you can manually remove Exchange 2003. You must first stop and disable all Exchange services.

Then you must use Registry Editor to remove registry keys that are part of the Exchange installation. After you have removed the registry keys, you must remove and then reinstall Microsoft Internet Information Services (IIS). You must then reinstall any service packs or security updates that had been installed on your server.

High level Steps

I will not explain every step, because I think that some processes are self explanatory. If you have any questions, look through the Knowledge Base articles that you can find at the end of this article.

  • Use the Active Directory User and Computers snap-in to disconnect all mailbox-enabled users
  • Run the Exchange Server 2003 Setup program to remove the installed components
  • Manually remove Exchange 2003
  • Stop and disable the Exchange 2003 services
  • Use Registry Editor to remove the Exchange registry keys
  • Remove and reinstall the Internet Information Server (IIS) component
  • Remove the Exchange 2003 server object from the Exchange 5.5 Admin program
  • Remove the Exchange 2003 server from Active Directory
  • Use the /removeorg switch to remove the whole Exchange 2003 organization from Active Directory

Stop and disable the Exchange 2003 services

Set the start up type of the following services to disabled and stop the services:

  • Distributed Transaction Coordinator.
  • Internet Information Services (IIS) Admin Service
  • Microsoft Exchange Event
  • Microsoft Exchange Internet Message Access Protocol (IMAP4)
  • Microsoft Exchange Information Store
  • Microsoft Exchange Message Transfer Agent (MTA) Stacks
  • Microsoft Exchange Post Office Protocol version 3 (POP3)
  • Microsoft Exchange Routing Engine
  • Microsoft Exchange Site Replication Service
  • Microsoft Exchange System Attendant
  • Network News Transfer Protocol (NNTP)
  • Simple Mail Transfer Protocol (SMTP)

Use Registry Editor to remove the following Exchange registry keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DAVEX
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EXIFS
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ExIPC
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EXOLEDB
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IMAP4Svc
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeActiveSynchNotify
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeADDXA
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeAL
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeDSAccess
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeES
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeFBPublish
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMGMT
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMTA
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMU
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeOMA
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeSA
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeSRS
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeTransport
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeWEB
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\POP3Svc
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RESvc

Remove and reinstall the Internet Information Services (IIS) component

Remove IIS over the Add/Remove feature of the computer. After you have removed Exchange, you can reinstall IIS if necessary.

Remove the Exchange 2003 server object from the Exchange 5.5 Admin program

If the Exchange 2003 server is installed in an existing Exchange Server 5.5 site, and you use the Exchange 5.5 Admin program, you must delete the Exchange 2003 server object from the Exchange 5.5 Admin program.

Remove the Exchange 2003 server from Active Directory

Start the Exchange System Manager to remove the server object expand Administrative Groups / “your administrative Group Name” /Servers.


Figure 1: Remove server in ESM

If you cannot run Exchange System Manager, you may use the ADSI Edit snap-in to manually remove the server attributes so that you can try a successful reinstallation. This method does not perform cleanups of references to the server object outside the server's own container.

ADSIEDIT is part of the Windows 2003 support tools. You can find the support tools on the Windows 2003 CD under the folder \Support\TOOLS. Install the support tools by double clicking SUPTOOLS.MSI.


Figure 2: Remove server with ADSIEDIT

Use the /removeorg switch to remove the whole Microsoft Exchange 2003 organization from Active Directory.

You can use the /removeorg switch with the Exchange 2003 Setup program to remove the whole Exchange 2003 organization from Active Directory.

The /removeorg switch removes the Organization container and all sub-containers from Active Directory. You can run this command from any server in the forest, not just from an Exchange 2003 server. This command does not remove services, files, or registry keys.

Important:
Do not use this method unless you want to remove Exchange completely from your enterprise. The /removeorg switch will remove all the Exchange servers from your organization. If you do this inadvertently, you may be forced to reinstall all the Exchange servers in your enterprise.

How to Remove the First Exchange 2003 Server Computer from the Site

Removing of Exchange 2003 if this machine is the first installed Exchange Server in the site (administrative group) is a little bit different from a normal Exchange deinstallation.

The high level steps are:

  • Replicate All Public Folders to Another Server
  • Rehome Connectors to Another Server
  • Rehome the Schedule+ Free Busy Folder
  • Remove the First Exchange 2003 Server Computer
  • Rehome the Offline Address Book Folder
  • Rehome the Recipient Update Service (RUS)
  • Designate Another Server to Be the Routing Group Master
  • Move Mailboxes to Another Server

The first Exchange Server 2003 computer that is installed in an administrative group holds the following important roles.

  • Offline Address Book folder
  • Schedule+ Free Busy folder
  • Events Root folder, and other system folders

Replicate All Public Folders to another Server

All public folders and system folders that are housed on the first Exchange 2003 computer must be replicated to another Exchange 2003 computer that is in the site

Rehome the Recipient Update Service (RUS)

In Exchange System Manager, expand Recipients, and then click Recipient Update Services.

Under “General” click “Browse” right of “Exchange Server” and select the Server that should host the Recipient Update Service.


Figure 3: Rehome RUS

Designate another Server to Be the Routing Group Master

If this server is the routing group master, you must designate another server to be the routing group master.


Figure 4: Change the Routing Group Master

If this Exchange 2003 computer has the Site Replication Service (SRS) installed and running on it, you must create a new SRS in Exchange System Manager. To do this, follow these steps:

Start Exchange System Manager on the Exchange Server 2003 computer where you want to create the SRS, and then expand Tools.

Right-click Site Replication Service, click New, and then click Site Replication Service.

When you receive the “Are you sure you want to install a new Site Replication Service on this server (ServerName)” prompt, click Yes.

When you receive the order to create a Site Replication Service on the local machine, enter the password for the Exchange service account (Domain\service account) prompt, type the password for the Exchange service account.

This creates the SRS, and it also creates an associated configuration Connection Agreement.

Rehome Connectors to another Server

If this Exchange Server 2003 computer has any connectors that are hosted on it, these connectors must be rehomed to another server before you remove this Exchange 2003 computer from the routing group. For example, if the source server hosts an X.400 connector, you must set up this connector on the destination server. For information how to setup a SMTP connector see the following article:

http://www.msexchange.org/tutorials/Configuring-SMTP-Connector.html

Move Mailboxes to another Server

Use Active Directory Users and Computers or the Exchange System Manager to move mailboxes.

Remove the First Exchange 2003 Server Computer

Insert the Exchange Server 2003 CD in the CR-ROM drive in the Exchange 2003 computer, and then click Remove for each component that has been installed.

How to completely remove Exchange 2003 from Active Directory

You have to completely remove all instances of Microsoft Exchange 2003 from the Active Directory service.

Note:
This procedure will completely remove all instances of Microsoft Exchange Server 2003 from Active Directory.

SETUP/UPDATE/REMOVEORG

Exchange 2000 SP2 and later contains a setup command-line switch, /removeorg, that removes the Organization container and all sub-containers from Active Directory. You can run this switch from Exchange 2000 Server Service Pack 2 or later by using the following command: update.exe /removeorg. Additionally, you can run this command from any server in the forest, not just from an Exchange 2003 server. This command does not remove services, files, or registry keys.

In Exchange 2003 the switch /removeorg is part of setup.exe.


Figure 5: SETUP /REMOVEORG switch

The next steps are the following:

  • Shut down the member server or domain controller where Exchange 2003 was installed.
  • Restart the domain controller that you were using to remove the Exchange organization.
  • Allow sufficient time for replication to occur between the domain controllers.
  • Save the setup logs.
  • Rerun setup /forestprep.
  • Rerun setup /domainprep. If this is the same server that was used previously, move the old setup logs out.
  • Verify permissions in the Exchange 5.5 organization. The user who is logged on must be in the group that was designated during forestprep and must have permissions on the Exchange 5.5 Organization, Site, and Configuration containers.
  • Make sure that you can connect to all the Exchange 5.5 computers by using the Administrator program from the intended Exchange 2003 installation server, and then view the properties of the Exchange 5.5 servers.
  • Remove the Administrator program from this server.
  • Install Exchange 2003.

Thursday, May 14, 2009

Windows Physical Memory Limits

Physical Memory Limits: Windows Server 2008

The following table specifies the limits on physical memory for Windows Server 2008. Limits greater than 4 GB for 32-bit Windows assume that PAE is enabled.

Version

Limit in 32-bit Windows

Limit in 64-bit Windows

Windows Server 2008 Datacenter (full installation)

64 GB

2 TB

Windows Server 2008 Datacenter (Server Core installation)

64 GB

2 TB

Windows Server 2008 Enterprise

64 GB

2 TB

Windows Server 2008 HPC Edition

Not applicable

128 GB

Windows Server 2008 Standard

4 GB

32 GB

Windows Server 2008 for Itanium-Based Systems

Not applicable

2 TB

Windows Web Server 2008

4 GB

32 GB

Physical Memory Limits: Windows Vista

The following table specifies the limits on physical memory for Windows Vista.

Version

Limit in 32-bit Windows

Limit in 64-bit Windows

Windows Vista Ultimate

4 GB

128 GB

Windows Vista Enterprise

4 GB

128 GB

Windows Vista Business

4 GB

128 GB

Windows Vista Home Premium

4 GB

16 GB

Windows Vista Home Basic

4 GB

8 GB

Windows Vista Starter

1 GB

Not applicable

Physical Memory Limits: Windows Home Server

Windows Home Server is available only in a 32-bit edition. The physical memory limit is 4 GB.

Physical Memory Limits: Windows Server 2003

The following table specifies the limits on physical memory for Windows Server 2003. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

Version

Limit in 32-bit Windows

Limit in 64-bit Windows

Windows Server 2003 with Service Pack 2 (SP2), Datacenter Edition

128 GB

64 GB with 4GT

2 TB

Windows Server 2003 with Service Pack 2 (SP2), Enterprise Edition

64 GB

2 TB

Windows Storage Server 2003, Enterprise Edition

8 GB

Not applicable

Windows Storage Server 2003

4 GB

Not applicable

Windows Server 2003 R2 Datacenter Edition

Windows Server 2003 with Service Pack 1 (SP1), Datacenter Edition

128 GB

16 GB with 4GT

1 TB

Windows Server 2003 R2 Enterprise Edition

Windows Server 2003 with Service Pack 1 (SP1), Enterprise Edition

64 GB

16 GB with 4GT

1 TB

Windows Server 2003 R2 Standard Edition

Windows Server 2003, Standard Edition SP1

Windows Server 2003, Standard Edition SP2

4 GB

32 GB

Windows Server 2003, Datacenter Edition

128 GB

16 GB with 4GT

512 GB

Windows Server 2003, Enterprise Edition

32 GB

16 GB with 4GT

64 GB

Windows Server 2003, Standard Edition

4 GB

16 GB

Windows Server 2003, Web Edition

2 GB

Not applicable

Windows Small Business Server 2003

4 GB

Not applicable

Windows Compute Cluster Server 2003

Not applicable

32 GB

Physical Memory Limits: Windows XP

The following table specifies the limits on physical memory for Windows XP.

Version

Limit in 32-bit Windows

Limit in 64-bit Windows

Windows XP

4 GB

128 GB

Windows XP Starter Edition

512 MB

Not applicable

Physical Memory Limits: Windows 2000

The following table specifies the limits on physical memory for Windows 2000.

Version

Limit in 32-bit Windows

Windows 2000 Professional

4 GB

Windows 2000 Server

4 GB

Windows 2000 Advanced Server

8 GB

Windows 2000 Datacenter Server

32 GB