cpsolutions.be

Error when opening Exchange 2010 Management console:

Exception calling “GetSteppablePipeline” with “1″ arguement: File c:\program files\Microsoft\Exchange Server\V14\RemoteScripts\ConsoleInitialize.ps1

Run the command : Get-ExecutionPolicy and check the output.

If it comes as Restricted then run the command Set-ExecutionPolicy RemoteSigned

Run the Exchange Management Console again and it will work!

http://www.exchange-genie.com/2008/02/configuring-outlook-anywhere-for-exchange-2007-sp1/

Free, Fast and easy tool for removing duplicate items from Outlook folders

With ODIR it’s a snap to clean your Outlook folders by removing all duplicates. ODIR removes duplicates from Contacts; Calendar; Tasks; Notes and Email folders.

http://www.vaita.com/ODIR.asp

The information in this article applies to:

• GFI MailArchiver 2011 for Exchange
• GFI MailArchiver for Exchange 4
• GFI MailArchiver for Exchange 5
• GFI MailArchiver for Exchange 6

Article ID: KBID003025

Query keywords: installation, migrate, move

If it is necessary to move GFI MailArchiver to a new server and you wish to retain your configuration settings, you need to follow the procedure described below.
Pre-installation notes:

• In this procedure the server where GFI MailArchiver was installed will be referred to as ‘Server_Old’ and the server on which GFI MailArchiver will be newly installed will be referred to as ‘Server_New’.
• The same build of GFI MailArchiver should be installed on new server as was installed on the old server. If an upgrade is required, you can upgrade the installation on the old server before moving the installation to the new server, or upgrade after the installation on the new server is complete.

Moving to the new server:

1. Stop the GFI MailArchiver services on ‘Server_Old’. At this stage, any new emails that need to be archived will remain in the Journaling mailbox.
2. Locate the GFI MailArchiver folder (by default it will be situated in ‘C:\Program Files\GFI\MailArchiver’).
3. Make a copy of the GFI MailArchiver folder from ‘Server_Old’ to exactly the same path on ‘Server_New’. For example, if on ‘Server_Old’ the GFI MailArchiver folder was located at ‘C:\Program Files\GFI’, the GFI MailArchiver folder on ‘Server_New’ should also be located at: ‘C:\Program Files\GFI’.
4. If using a Firebird database which resides in a different path than the GFI MailArchiver installation, copy the Firebird database to ‘Server_New’. If possible, the path of the Firebird database on ‘Server_New’ should be the same as the path of the same database on ‘Server_Old’.
5. If Binary files and Indexes have been created in a separate than the GFI MailArchiver installation folder, these need to be moved to ‘Server_New’, using exactly the same path used on ‘Server_Old’.
6. Install GFI MailArchiver on to ‘Server_New’, selecting to install to the directory where the files were copied in step 3.
7. When the installation is finished, check the following on ‘Server_New’:
   • If GFI MailArchiver is configured to archive to a Microsoft SQL server, ensure the configured Microsoft SQL server is accessible from ‘Server_New’.
   • Ensure that the paths to any Firebird database, binary files and Indexing files are configured correctly.
8. Still on ‘Server_New’, enable archiving. This can be done from the GFI MailArchiver ‘Configuration’ -> ‘Mail Servers to Archive’ -> click on the ‘Edit Settings’ icon for the mail server you want to archive from. In the ‘Mail Server Wizard’ enable ‘Archive emails from this server’. If on ‘Server_Old’ you were using EXOLEDB as the connection provider and you are moving to a non-Exchange machine, use IMAP to connect to the Journal Mailbox.

Post installation notes:

• If after installing on the new server you get the error “Failed to load ASPNET (Error code: 404)” when loading the MailArchiver console, kindly check the knowledgebase article KBID003115
• Confirm the path of the Index file from the GFI MailArchiver ‘Configuration’ -> ‘Search Index Management’ -> ‘Full path to Search Index’.
• Confirm the settings of the archive store GFI MailArchiver is configured to archive to, from the GFI MailArchiver ‘Configuration’ -> ‘Archive Stores’ -> ‘Location’. You can edit the location of the database, binary files and  index files of an archive store by clicking on the ‘Edit Settings’ icon next to the ‘Store Name’.
• Should you need to move the SQL databases to a different server also, kindly check the knowledgebase article KBID002314
• Kindly check knowledgebase article KBID003024 should you encounter the error ‘Query Failed’ when you browse the emails on the new server after performing the above procedure. This error is encountered when GFI MailArchiver cannot access the Archive Stores.

When a user is deleted from Microsoft Active Directory, GFI MailArchiver can be configured so that archived emails for the deleted user can be viewed by another user. This can be achieved as follows:

GFI MailArchiver 2011

1. Open the GFI MailArchiver User Interface
2. Click on ‘Configuration’
3. Click on ‘Access Control’ -> ‘Configure User Access Control’.
4. In the ‘User’ field, type the name of the user which should have access to the archived mails of the deleted accounts.
5. In the ‘Has Access to User’ field type the name of the deleted account. This will be listed in square brackets and will have ‘(Deleted)’ next to it.
6. Click on the ‘Add’ button.
7. Click on the ‘Save’ button at the bottom of the page.

GFI MailArchiver 6 and previous version

1. Open the GFI MailArchiver Configuration.
2. Expand the ‘Access Control’ node and locate the ‘User Access Control’ section.
3. In the ‘User’ field, select which user should have access to the archived mails of the deleted accounts.
4. In the ‘Has Access to user’ field select the deleted account. This will be listed in square brackets and will have ‘(Deleted)’ next to it.
5. Click on the ‘Add user’ button.
6. Click on the ‘Save settings’ button at the top of the page.

Note:

• You can view all users that have emails archived by GFI MailArchiver, including deleted users, in the GFI MailArchiver Configuration -> Conversations -> Account List. Deleted accounts will show within square brackets.
• If you wish to view e-mails of users who have left the company (and who’s Active Directory user accounts have been disabled as opposed to deleted), please read the following article: How can I view emails of employees who left the company?

Exchange Client Access Checks for 2010

These use the inbuilt test functionality in Exchange through the Exchange Management Shell. These tests log in using the test cas users to the various servers and actually test functionality AND response. So it will fail if something underlying is failing in the system too.

Before running these – you must have created the test cas user using the “new-testcasconnectivityuser.ps1″ script found in your Exchange Management tool installation (under scripts folder).

Check scripts for:
- ActiveSync Connectivity
- IMAP Connectivity
- MAPI Connectivity
- Outlook TCP (RPC) Connectivity
- OWA Connectivity
- WebServices Connectivity

I have not been able to test all of the failure cases yet.

http://exchange.nagios.org/directory/Plugins/Email-and-Groupware/Microsoft-Exchange/Exchange-2010-CAS/details

This Nagios XI wizard allows you to easily monitor Microsoft Exchange servers – including service states, protocol availability, and performance metrics.

http://exchange.nagios.org/directory/Addons/Configuration/Configuration-Wizards/Exchange-Server-Monitoring-Wizard/details

1. Create 2 folders:

• Database              –> D:\Recovery\Database
• Transaction Logs   –> D:\Recovery\Logs

2. Now restore the database which is to be recovered and the subsequent logs exactly to the above location

3. Now follow steps 1-7 mentioned in the article and make the database in a clean shutdown :

4. Once the database is in clean shutdown state, rename the original database file to “RecoverDB.edb”.

NOTE: Don’t copy the logs since ESEUTIL /R replayed them into the EDB and the database does not require any more logs to make it clean shutdown.

5. Use the Exchange management Shell to create a recovery database.

This example creates the Recovery Store “RecoverDB” on the server MSXGuru-Exch using the defined path for the database file and transaction logs folder.

New-MailboxDatabase -Recovery -Name RecoverDB -Server MSXGuru-Exch -EDBFilePath D:\Recovery\Database\RecoverDB.edb -LogFolderPath D:\Recovery\Logs

Important: If you have EMC Console open, you will need to restart it to see the newly created Recovery mailbox Store “RecoverDB“ under the Organization Configuration–> Mailbox –>Database Management and its state will be dismounted.

6. Now Right click on the newly created recovery Store and mount it.

7. Now open Shell and type the command as shown:

Get-MailboxStatistics -Database RecoverDB

This will show the list of mailboxes in that database.

8. This is the cmdlet to recover entire mailbox content for the mailbox UserA

Restore-Mailbox -Identity UserA -RecoveryDatabase RecoverDB

This will take time depending on the size of the mailbox.

9. This is the cmdlet to restore UserB mailbox content into UserA mailbox under the RecoverTest folder.

Restore-Mailbox –Identity UserA –RecoveryDatabase RecoverDB –RecoveryMailbox UserB –TargetFolder RecoverTest

10. This is the cmdlet to restore all mailboxes in the database mbx1 which are also present in the RecoverDB database. For every mailbox it will ask you to confirm the action, we do have an option “Yes to All”

Get-Mailbox –Database mbx1 | Restore-Mailbox –RecoveryDatabase RecoverDB

SYMPTOMS

CAUSE

RESOLUTION

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

To resolve this problem, use another screen saver program (such as Logon.scr) that is installed locally on the system or that is not corrupted.

1. Start Registry Editor (Regedt32.exe).
2. Locate the Scrnsave.exe value under the following registry key:
   HKEY_USERS\.Default\Control Panel\Desktop
3. On the Edit menu, click String, type logon.scr, and then click OK.
4. Locate the ScreenSaverIsSecure value.
5. On the Edit menu, click String, type 0, and then click OK.
6. Quit Registry Editor.

WORKAROUND

To work around this problem, use the appropriate method.

Method 1: When the Error Message States the Computer Is Locked by domain\username

1. Press CTRL+ALT+DELETE to unlock the computer.
2. Type the logon information for the last logged on user, and then click OK.
3. When the Unlock Computer dialog box disappears, press CTRL+ALT+DELETE and log on normally.

Back to the top

Method 2: When the Error Message Does Not State Who Locked the Computer

1. Use the Shutdown tool in the Microsoft Windows Resource Kit and attempt to shut down the locked computer. The System Shutdown dialog box is displayed on the locked computer, but the computer does not restart.
2. When the shutdown timer expires, the Welcome to Windows dialog box is displayed.
3. Before the screen saver becomes active, press CTRL+ALT+DELETE, and log on normally.

NOTE: If you do not use one of these methods to log on, you must restart the computer and log on before the screen saver program starts.