Exchange 2003 2007 

Exchange Articles, News and Discussions
Welcome to Exchange 2003 2007  Sign in | Join | Help
in Search

  • Exchange 2007 SP1– Exchange 2007 SP1 what’s in it for you?

    Exchange 2007 SP1 which was released in November 2007 brings together improvements for Exchange 2007 in the following areas:  Client Access Improvements, Protection & Availability improvements, Transport Improvements, Mailbox Role Improvements, and Unified Messaging Improvements.

     

     Exchange 2007 SP1 Features and Improvements

     

    An interesting fact is that unlike a traditional Service Pack Exchange 2007 SP1 is only available as a full slipstreamed package (Full install and Exchange 2007 SP1 are integrated) giving you the administrator the option to either perform a new Exchange 2007 SP1 install or an in-place upgrade from either Exchange 2007 RTM or Exchange 2007 SP1 Beta 2 (Beta 2 upgrade only if member of Exchange 2007 SP1 TAP or RDP program).

     

    I hear you ask so how about the new features and improvements in Exchange 2007 SP1?

     

    Protection & High Availability Improvements, in Exchange 2007 SP1 include

     

    Standby Continuous Replication (SCR)

     

    Exchange 2007 SP1 Standby Continuous Replication is basically an availability feature that allows an organization to recover quickly from a data center disaster. The technology works by having this Exchange 2007 SP1 Standby server which is constantly receiving log shipped mailbox data from its peer, this ensures the SCR standby partner has exactly the same mailboxes and messages that exist or existed on the original mailbox server. If there were ever a data center disaster the Exchange 2007 SP1 standby node can be activated and immediately start serving users their mailboxes.

     

    Exchange 2007 SP1 improvements with Windows Server 2008

     

    Exchange 2007 SP1 now allows Exchange 2007 to be installed on Windows Server 2008, giving you the following high availability features, including the new disk and file share quorum models, DHCP IPv4, Multi-subnet failover clusters and support for IPv6

     

    Other improvements include transport dumpster, reporting and monitoring and Continuous replication (redundant cluster networks in a CCR environment) Improvements.

     

    Another interesting fact is that Exchange 2007 SP1 can only be installed on a fresh Windows Server 2008 install, you cannot upgrade Exchange 2007 to Exchange 2007 SP1 then upgrade your operating system from say Windows 2003 server to Windows Server 2008, also you cannot upgrade your operating system to Windows Server 2008 then upgrade from Exchange 2007 to Exchange 2007 SP1.  

     

    Mailbox Role Improvements in Exchange 2007 SP1 include

     

    Mailbox Management

     

    Import and export of mailboxes into and out of PST files

     

    Previously when wanting to either import or export mailboxes into and out of PST files you either needed to make use of Microsoft Outlook or Exchange Exmerge tool, with Exchange 2007 SP1 Mailboxes can be imported into and out of PSTs via the use of the new Export-Mailbox and Import-Mailbox Management Shell Cmdlets.

     

    Mailbox management

     

    Some of new features found in Exchange 2007 SP1 include both the Manage Send-As and Manage full access permissions wizard allowing and administrator to grant or remove Send As or Full Access permissions on a mailbox.

     

    Another Mailbox management feature that administrators will appreciate is the ability for mailboxes to be created in bulk for existing user accounts.

     

    Public Folder Features

     

    Public folder Referrals can now be maintained from within the Exchange Management console, the new public folder administrator role which is used for administering public folders and can be granted to a user or group.

     

    Improvements in Monitoring of Online Defragmentation include two ESE performance counters to monitor online defragmentation effectiveness and efficiency, and additional information for Event 307.

     

    Client Access Improvements

     

    Client access feature improvements in Exchange 2007 SP1 include Exchange ActiveSync, Outlook web access light, Outlook Web access premium and POP and IMAP 4 Improvements.

     

    In the area of Outlook Web Access Light, user’s sessions are monitored so that during a long message composition the user’s session does not time out.

     

    With the Outlook Web Access Premium client users can now create and edit personal distribution lists and server side rules, access to the dumpster, viewing of some Office 2007 file formats via WebReady, A new Monthly Calendar View, Move and copy commands, Public folders supported thru the /owa virtual directory, S/MIME support added, and some customization features.

     

    For IMAP/POP various settings such as port, authentication, connection and messages settings can be changed.

     

    Transport Improvements

     

    Exchange 2007 SP1 delivers transport improvements in the Edge Transport server and Hub transport Server roles and some additional core transport enhancements.

     

    Core Transport enhancements include back pressure monitoring that allows the system to better handle systems that are under high resource use. Also now more transport settings can be configured from the Exchange Management console.

     

    Edge Transport improvements in Exchange 2007 SP1 include, the Star-EdgeSynchronization and Test-EdgeSynchronization cmdlets to kick off ADAM edge synchronization from a remote PC, and check the synchronization results for individual users

     

    Hub Transport improvements in Exchange 2007 SP1 include priority queuing where the priority assigned to a message by a user is used by the Hub Transport server when categorizing a message.  Transport rules can now be applied to unified messaging messages.

     

    The new MaxMessageSize parameter can be found on the Set-AdSiteLink, New-RoutingGroupConnector and Set-RoutingGroupConnector cmdlet allows an administrator to limit the size of a message that is relayed between Active Directory sites (Set-AdSiteLink) and restored the size of messages relayed between Exchange 2007 HTS server and Exchange 2003 and Exchange 2007 bridgehead servers (New-RoutingGroupConnector and Set-RoutingGroupConnector cmdlets).

     

    Unified Messaging

     

    The most notable Unified Messaging improvements found with the introduction of Exchange 2007 SP1 include, access to Outlook Voice Access via Office Communicator without the need for a pin number, Subjects and priorities can now be assigned to voice messages, Integration of missed calls notification email messages in Office communicator 2007, along with Quality of Service (QOS) support, and Secure Real-time Transport Protocol support.

     

    As you can see Exchange 2007 SP1 is an extreamly feature rich update, there should be something in it for everyone, and it is an update that should not be taken lightly, testing an planning are the keywords here, because of the complex nature of Exchange 2007 and this service pack planning is essential before even thinking of letting Exchange 2007 SP1 loose on your production environment.

     

    Articles from ExchangeIS.com and other Flying High media websites:

     

      Exchange 2007 Roles – An introduction to Exchange 2007 Server Roles

      Eseutil /R (Soft Recovery) – A Quick and Simple Tutorial

      Eseutil /P – A Quick and Easy Tutorial

      Eseutil - A Quick and Easy Tutorial

      Top 5 Tools an Exchange Administrator should not be without!

     

    WindowsIS.com

       Windows Server 2008 Features: Windows Server 2008 New Features and improvements

       Windows Server 2008 Active Directory Domain Services ADDS DCPromo walkthrough

       Windows Server 2008 Install walkthrough

       Requirements for 64 bit Guest Virtualization

     

    The Business Travel Guru

       Emirates unveils ultra modern lounge in Brisbane Australia

       Jetstar Starclass flight review Ho Chi Minh City SGN to Sydney SYD

       US Airline Carriers Wake up and Smell the?

       Singapore Airlines to operate out of Beijing International Airport Terminal 3 From 26 March 2008

  • Exchange 2007 Roles – An introduction to Exchange 2007 Server Roles

    Exchange 2007 Server Roles – Exchange 2007 has expanded the concept in Exchange 2007 Server of server roles, which further extends the old 2 role front end back end topology, with a new 5 role model.

    Breaking down the Exchange 2007 server roles has a lot of advantages, allowing your exchange topology to be more flexible, highly scalable, allowing better hardware utilization, this together with the advantages of 64bit allow more mailboxes to be hosted on a single server.

    The five Exchange 2007 Server Roles are as follows and shown in figure 1 below:

    ·         Mailbox Server Role

    ·         Client Access Server (CAS) role

    ·         Hub Transport Server (HTS) role

    ·         Edge Transport role

    ·         Unified Messaging

     

     Exchange 2007 Server Roles

    Figure 1 "Exchange 2007 Server Roles"

    Each of these Exchange 2007 Server Roles are detailed below

    Exchange 2007 Mailbox Server Role

    The Exchange 2007 Mailbox server role is responsible for hosting exchange mailboxes and public folders. Given that this is the only function a server with this role will do (Unless installed with multiple roles) along with the 64bit factor the number of mailboxes supported per server is greatly increased.

    Exchange 2007 Client Access Server Role CAS

    The Exchange 2007 Client Access Server role allows client applications and devices to connect and could be considered the same as the old Exchange front end server, also providing the Outlook Web Access OWA feature. Types of clients that connect to exchange via the Client Access Server Role include:

    ·         Outlook 2000/2003/2007

    ·         Via Web browser (OWA)

    ·         ActiveSync via Mobile Clients Windows Mobile 5 & 6 + other licensed Devices

    ·         Outlook Express, POP3, IMAP4

     

    Exchange 2007 Hub Transport Server Role HTS

    The Exchange 2007 Hub Transport Server role should be considered the co-ordinator of internal mail thru your exchange Organization, and is also responsible for receiving messages from the Edge Transport server for delivery to the internal mailbox servers, and the receiving of messages from Exchange mailbox servers to be sent to the Hub Transport server for delivery to the internet.

    Other functions the Hub Transport servers does or can have is:

    ·         Messaging Policy, Compliance, and retention

    Allows rules and setting to be applied to messages as they enter pass thru the Hub transport server role to/from the Mailbox Edge.

    Depending on your organization industry and the countries/s you operate in they may be subject to regulations such as Sarbanes Oxley, also your company may have internal policies, the Hub Transport Server is the server where compliance and retention rules are set and acted.

    ·         Anti-Virus & Anti-Spam features

    Your Exchange 2007 Hub Transport server can be configured to perform additional Anti-Virus and Anti-Spam protection, before messages reach your mailbox server. This feature is not enabled on a Hub Transport Server by default and is normally done at the Edge Server level therefore this needs to be enabled if required by your organization at this level.

    Exchange 2007 Edge Transport Server Role

    A hosting the Exchange 2007 Edge Transport role sits in your organization’s perimeter network (DMZ) and is located on a standalone non-member server (not  a domain member server).  Instead Active Directory Application Mode (ADAM) is used to perform the edgeSync to keep your organizations AD recipient information up to date for recipient filtering.

    The primary reason the Edge transport role sits in your perimeter network is for security ensuring messages that enter and leave your organization are legitimate and clean, ensuring security, reducing Spam, and decreasing the number of messages your internal exchange servers need to deal with.

     Sitting in your perimeter network and not on the domain, there is an added security if the server is compromised there is less of a chance of compromising your internal network.

    Primary functions performed by the Exchange 2007 Edge Transport Server include:

    ·         Internet Mail Flow – accepts and sends messages destined for the internet

    ·         Anti-Spam Anti-Virus – Filter messages before they enter or leave your Exchange org

    ·         Edge Transport Rules – Taking action on messages that meet specific conditions

    ·         Address Rewriting – Rewrite SMTP address of internet and external bound messages

    Exchange 2007 Unified Messaging Server Role

    The Exchange 2007 Unified Messaging Server role is the biggest changes to Exchange 2007, introducing the totally new concept of Voice messaging, other voice features, and faxing to Exchange.

    Unified messages features provided by the Exchange 2008 Unified Messaging Server role include:

    ·         Auto Attendant – A Set of voice prompts that gives external users access to the Exchange 2007 Unified Messaging system

    ·          telephone, including creating greetings, changing their Unified messaging settings

    ·         Receiving of Faxes – For delivery to a user/s mailbox

    ·         Call Answering – Answering of incoming calls for a user

    ·         Subscriber Access – Gives users access to their mailbox, and unified messaging system via a touchtone telephone.

    Exchange 2007 Server roles is one of the biggest changes to Exchange 2007 from previous versions, further segmenting roles improves performance, extends security and scalability, making it the number 1 enterprise messaging platform.  

     

  • Using PortQry to troubleshoot Exchange rpc connection issues

    In today’s secure corporate WAN networks one common issue I see on a regular basis is Exchange connected Outlook clients not working because of corporate firewall changes or misconfiguration.

     

    Properly the quickest way to check if a firewall is blocking or filtering rcp traffic between you outlook client and an exchange server is to use the PortQry.exe tool. This Windows Server Support tool sends packets to specified ports and looks to see if that port has been blocked (filtered).

     

    To begin install the Server Support tools from your Windows Server CD for your version of Windows Server once installed, or download the new version PortQry version 2 from the following location.

    PortQry Version 2 Download


     

    If you are a GUI type person you can also download the PortQueryUI tool from the below location

    PortQueryUI PortQry GUI Download location


     

    Using the PortQry or PortQueryUI tool returns the below values depending on the state or filtered state of the destination servers port

     

    Listening                             Some Process is running on the port you have queried

    Not Listening                     No process is running on the port you have queried      

    Filtered                                                The port queried has been blocked (filtered)

     

    To use PortQry to check for filtered rpc ports we first need to understand how rpc works, firstly an initial connection is made over port 135 after which a random port between 1024 and 65535 is negotiated for the main communication.

     

    If you were issuing checking a standard ports status you would run the following command from the command prompt:

     

    portqry -n ServerName -e 135

     

     Using PortQry to troubleshoot Exchange connection issues

    Figure 1 "Output from PortQry Tool"

     

    It is most likely that port 135 will be listening and not filtered, but one of the endpoints  between 1024 and 65535 are blocked, so now you need to check the output above taking note of each of the endpoint ports, after this you can use portqry again using the -o switch to specify each of the individual endpoint ports.

     

    portqry -n ServerName -o 1117,1118,6001 

     

    Once you have ran the above command the status of each of ports will be listed, either Listening, Not listening or Filtered. If any of the ports are listed as Filtered then it fairly much rules out a Windows and/or Exchange service issue, and is something you can take to your Network/WAN specialists to fix for you.

    Related Articles

    WindowsIS.com

       What is the Vista Network Location Feature?

    ExchangeIS.com

       Using ADModify - A real world example

       Using ADSIEdit - A Real World Example

    Why not Become a member of Exchange Information Store and participate in our forums

     

  • Requirements for 64 bit Guest Virtualization - Repost from WindowsIS.com

    64Bit guest virtualization is becoming a requirement especially with the release of Exchange 2007 and the announcement that it will be 64 bit only for all server operating systems after Windows Server 2008. So to get a taste of 64bit virtualization just what are the requirements to run a virtualized 64 bit host under VMware?

    When thinking about running a 64 bit Guest in VMware you need to be concerned with the following three components:

    - Motherboard and Chipset

    - CPU

    - Virtualization Product Support

    Funny enough it does not matter if your host operating system is 32 or 64 bit VMware can run a 64 bit host just as long as you meet the above criteria that is outlined in detail below.  But one advantage you do have running a 64 Bit operating system is you increase the maximum amount of RAM (from approximately 3.6Gb) your can run in your host operating system which means there is more available for your guests. With that in mind I decided to go with Windows Vista 64 bit along with around 8 GB of RAM for my virtualized  test lab PC.

     

     

    CPU

    Intel

    Requirements are an Intel CPU that supports the EM64T standard along with support for Intel VT (Virtualization Technology or Vanderpool Technology), which is basically any of the following CPUs:

    Pentium 4 –Only  662 and 672

    Pentium D  Only 960, 950, 940, 930, 920

    Core Duo All Except  T2300E

    Core 2 Duo Processors all except E4400, E4300, T5500

    Pentium Extreme All except for 840

    Itanium 2 All except 9010

    Intel Xeon MT CPUs all

    When choosing an Intel CPU I highly recommend using the following Intel CPU Guide to determine if your CPU supports EM64T along with Intel VT: http://www.intel.com/products/processor_number/index.htm

    AMD

    The AMD 64bit virtualization feature is known as AMD-V and provides guest virtualization via the method called segmentation (a method that Intel does not use), the following revisions of AMD CPUs (and later) have the AMD-V feature:

    AMD64 rev D or later.

    AMD Opteron rev E and later

    AMD Turion rev E and later

     

    Motherboards

    This is a bit of a hit and miss, it very much depends on the Chipset of your motherboard and the  if your motherboards manufacturer has enabled the Intel VT or AMD-V feature (for current older mother boards this may be as simple as a BIOS/Firmware Upgrade) Current Intel Chipsets that

    The following Intel Chipsets support CPUs with the Intel VT feature.   

    Intel 915/E8500

    Intel 945G

    Intel 955X

    Intel 975X

    Intel E7532

    If you are looking at purchasing soon I highly recommend you check on your motherboard manufacture’s website to determine if the motherboard that you are about to purchase supports Intel VT. Of if you are purchasing a full system ask you system manufacturer.

    If you want to check your current system, just download the VMware Processor Check for 64 Bit Compatibility tool from the link located on the following page:

    http://www.vmware.com/download/ws/drivers_tools.html

    Virtualization Product Support

    Presently VMware 5.5 and above support 64 bit guest virtualization, Microsoft’s Virtual Server does not support a 64bit guest yet but it is soon to release a version of Virtual Server that supports this feature.

     

    Other articles of interest:

     

    WindowsIS.com

       What is the Vista Network Location Feature?

      

    ExchangeIS.com

       Using ADModify - A real world example

       Using ADSIEdit - A Real World Example

     

     

     

     

  • Using Eseutil /MH - How to check which Transaction log files are not committed

    You have been busy and have not had the time to check your backups recently, all of a sudden your all of the Exchange Databases go offline, after some investigation you realise your full backup has not ran for several weeks and the drive that houses these transaction logs is now full. This is an extremely common issue, and I see it in the real world on a regular basis, a lot often than I should.

    We are lucky as the quickest and easiest way to get your Storage Group and its Information Stores back online is to move the committed Exchange Transaction Logs files to another location.

    How do I know which Transaction log files aren’t committed?

    One of the features of Eseutil is its ability to read the header information of an Exchange Database or a Checkpoint file to give you various information including the transaction log files that have not yet been committed.

    How to read the Log Required value of an MDB or STM file

     In order to read the header information for each edb and stm file in the storage group that has stopped, but as your Database file/s have become dismounted because of a full volume, this is not an issue. The command to show the Log Required value is:

    Eseutil /MH <database_name>

    Performing this command will display the header information similar to shown in figure 1 below:

     

    Figure 1: The Exchange Database header information

    From the Example in Figure 1 the Log Required Value is 0-0 which basically means my database is in a clean shutdown state and all log files are committed. This value specifies the log files required for the Exchange Database to mount and means if the value of Log Required was anything other than 0-0, you can move log files that are lower than the lowest value of this field.

    In any version of Exchange Pre Exchange 2003 SP1 you will need to convert this decimal value to a Hexadecimal value but with Eseutil from Exchange 2003 SP1 and above this value will already be in Hexadecimal.

    You should never move the latest log file as this will prevent log files from being played back in a recovery scenario. This rule should always be followed even if the databases are in a clean shutdown state.

     

    TIP:

    You can find the location of your Exchange mdb and stm files by Opening the Exchange Administrator in Exchange 2003 server and navigating to:

     

     Servers | <Name of Exchange Server> | <Name of Storage Group i.e. First Storage Group> | Right click on the dismounted Information Store selecting Properties and click on the Database Tab  

     

    You can now simply copy and paste the Exchange Database location into the command line saving you typing

     

     

    It is highly recommended that you perform a full backup after this procedure; if this backup is successful you can safely delete the transaction log files that were moved.

    Related Articles:

    Eseutil /R (Soft Recovery) – A Quick and Simple Tutorial

    Eseutil /P – A Quick and Easy Tutorial

    Eseutil - A Quick and Easy Tutorial

    Top 5 Tools an Exchange Administrator should not be without!

     

  • Eseutil /R (Soft Recovery) – A Quick and Simple Tutorial

    Eseutil /R what does this mode do and when would you use Eseutil /R ? The Eseutil /R mode is used when you need to perform a soft recovery of your Exchange Database/s ( Information Store ).  This mode of the tool should not be confused with the hard recovery mode Eseutil /C

    What is the Difference between Hard and Soft recovery with Eseutil?

    As mentioned above there are two recovery modes hard and soft recovery, the Hard recovery mode Eseutil /c is only used after performing an online restore (restore database because of corruption, or system failure; basically an online restore from media) and is used to playback to transaction log files so that you have a current database.

    Normally Soft Recovery happens automatically after the Exchange Information store service starts and manual soft recovery using Eseutil /r is rarely required as it is run automatically, in fact manual soft recovery is not recommended at all with Exchange 5.5, yet there are some instances when you will need to perform a soft recovery manually, below are the scenarios where you would perform a soft recovery manually with Eseutil /r

    ·         Database drive that contains one of a storage groups Information Store fails

     

    This causes the storage group and other Exchange Information stores (on other drives) to go offline (Dirty shutdown)

    o   In this scenario if you intend on later restoring your missing database your can, still recover (soft recovery) the remaining Information stores with the use of  the /r mode along with the /I (Ignore) switch.

     

    ·         To perform an Out of Place Restore of an Information Store

     

    Using the recovery mode together with the /D switch will allow you to recover an information store out of place, either to a Recovery Storage Group and would be particularly useful when you are ready to restore the missing database from the previous scenario above. The D switch basically allows you to specify an alternate locate (Other than the original) for the Exchange Database files

     

    ·         After a restore you see Event ID 494, 454, 101, 904, 903 the following description: Information Store (1352) ….. as outlined in the following Microsoft Kb Article: http://support.microsoft.com/kb/843092

    The valid options and syntax for use with Eseutil /R is as follows:

    Eseutil /R <E00>

    This is normally E00 but in different scenarios may be different

     

     

    /L<Path>

    Path to the log file location

     

    /s<Path>

    Location of the System files (Checkpoint file, etc)

     

    /I

    Ignore errors missing/mismatched database files (Exchange 2003 and above only)

     

     

    /D [Path]

    Path to the location of the database files, if switch is not specified path will use the original local of database files, if switch is specified without a path the current working directory is used, if switch and path is specified the path specified is used.

     

    /8

    Set 8k database page size (the default is 4k)

     

    /o

    Suppress logo

                   

    Now that you have seen the options that can be used with Eseutil /R let’s look at it in action:

    Suppose we had a scenario as one above where a drive failed that contained one of your storage groups databases, and this failure caused the storage group and remaining databases (located on another drive)to go offline. Now you want to get these remaining information stores back online ASAP and worry about restoring the missing database later. Figure 1 below show the Eseutil /R command and its output.

    Figure 1: Eseutil Soft Recovery

    The inclusion of the /D switch makes it possible to run this command against your database/s file in just about any location, it no longer needs to be in the original location. You can see how this switch can make Out of Place Restores and restores/recoveries of Recovery Storage groups possible. This feature however is only available in Exchange 2003 and above.

    Before running Eseutil /R with the /I option is highly recommended that you make a backup copy of your transaction log files, especially in a scenario when you are recovering databases but you plan to use these log files in the future after you have restored the missing database file, as the use of Eseutil /r makes changes to your Transaction log files and may change them so that future recovery of your missing database files is impossible.

    I highly recommend looking at the Microsoft document on running Eseutil /R:

    http://technet.microsoft.com/en-us/library/aa998075.aspx

    Please feel free to leave comments or questions I am always happy to answer!

  • Eseutil /P – A Quick and Easy Tutorial

    Eseutil /p - This article is the second part of my original article titled Eseutil – A quick and easy tutorial, in which I gave readers an overview of the Eseutil tool, some basic guidelines along with a look at Eseutil /d (defrag). In this article I will talk about Eseutil /p, the mode that can get you in the most trouble if correct procedures are not followed. So if you have not already please read my previous article where I outline some basic safety steps.

    The Eseutil /p command is known as the repair mode and is used to repairs a database at the page and ese table level of the database. It should be noted that this repair process may leave your database incomplete, as to repair it may be required for Eseutil  to delete rows and tables to repair the database.

    Eseutil /p should be used as a last resort,  so if you cannot restore and replay or fully replay your transaction log files, and if possible the database should be restored from backup to the most recent date then the corrupt database repaired and merged into the restored database using a recovery storage group. If possible never put only a repaired database back into production.

    When using Eseutil /p you should always follow up the use of this tool with the use of the following two commands Eseutil /d to rebuild the indices and defrag the database ISInteg to repair the database at the application level.

    If the database that you want to run Eseutil /p against is in a dirty shutdown state the Eseutil /p cannot be performed, and the database must be shutdown cleanly if this is not possible then the Eseutil /r  switch (recovery) must be ran to perform a soft recovery and put the database back into a clean shutdown state.

    Now for the syntax of Eseutil /p

    ESEUTIL /p <database name> [options]

    /s<file>     Streaming file location (Optional default is not to use)

    /t<db>      Temporary Database Location and name default is: TEMPREPAIR*.EDB

    /f<name>    Prefix for database report files, the default is: <database>.integ.raw)

    /i           bypasses the mismatch error check on database and streaming file

    /g           To run the integrity check before repairing database

    /createstm   Creates and empty stm streaming file if this is missing

    /8           To set the 8k database page size (default: auto-detect)

    /o            suppress logo

    Running the eseutil /p command with only the basic default options looks like this:

    eseutil /p  "C:\Program Files\Exchsrvr\MDBDATA\priv1.edb"

    Figure 1 below shows the command running, and the warning says that this command should only be ran against a corrupt database and may cause data (pages and tables) to be deleted.

     

    Figure 1: The Eseutil /p command (Repair) warning

    A screenshot of the completed output of the tool is shown in figure 2 below:

    Figure 2:The output of the completed Eseutil /p command

    As stated above Eseutil /D should be ran followed by Isinteg, the database should now be backed up.

    I hope this article enlightened you to the use of Eseutil /p, if you have any questions, comments or suggestions about this tool please post a comment. You could even start a new post in the forums above.

    My next post will be on the /r mode of this tool the recovery mode.

    To purchase or transfer a domain name look here:

    $14.95 domain registration $8.95 Domain Names Transfers from Dotster
  • Eseutil - A Quick and Easy Tutorial

    Eseutil some feel comfortable with this tool others don't; Eseutil should not be taken lightly, some modes of Eseutil that can reak havock if not used in the correct situation or with the correct procedure, which is why I am outlining some simple rules and steps, so that you can use Eseutil without fear and know exactly how it use it in a certain situation.

    Eseutil is used in the majority of situations when you experience issues with your Exchange Information Store not starting or misbehaving but there are some senarios were this migh not be the case as you will see in the first example of the switch Eseutil /d below:

    Firstly let's look at the what this tool does, Eseutil.exe can be used to  analyze/verify and then modify/repair  your exchange Information Store database files, these files in a default setup are named priv1.edb priv1.stm pub1.edb pub1.stm. It should be noted now with the release of Exchange 2007 (only with the Exchange 2007 version of the tool) eseutil can be used to perform these tasks against the ESE database files on the Exchange 2007 Edge Transport and  Hub Transport servers along with the mailbox and public folder stores.

    So now that you know what eseutil does I am now going to outline the switches that Eseutil uses and then give an overview of the defragment mode (eseutil /d), I will save the rest of the switches for another article.

    Eseutil                 

    Defragment                      /d <database name>  [options]
    Recovery                             /r <logfile base name> [options]
    Integrity                               /g <Database name> [options]
    Checksum                           /k <file name> [options]
    Repair    &