Backtrack:  
Blog
 
showing posts tagged with 'exchange'
 
Set up application impersonation for on-premise Exchange/Office365
edited by on August 28th 2014, at 13:11
For migrations from other e-mail platforms to Exchange, you probably want to have full access enabled for a certain Exchange-account to facilitate the migration without having to set up complex access rights. Exchange has something called application impersonation, which allows a user to impersonate other users to access individual mailboxes, which comes in very handy during a migration.

In order to set up application impersonation, you need access to the Exchange Management Shell (EMS), with an account which has permissions to set up access rights.

Exchange 2007 does not support application impersonation as in Exchange 2010 and up. Impersonation does exist but has to be set on each indivi  ...
 
Enable Basic Authentication for Exchange Web Services
edited by on August 28th 2014, at 13:09

If for some reason you need to enable Basic Authentication, you can do so quickly through the Exchange Management Shell. This is sometimes needed if you're migrating to Exchange from another (third-party) e-mail provider.

If you do not know what Basic Authentication is, you do not need this!

Start up EMS as an account which has the required permissions to make changes to the virtual directories used by Exchange. Then, run this:

Set-WebServicesVirtualDirectory -Identity "EWS (Default Web Site)" -BasicAuthentication $true

Note that Office365 has Basic Authentication enabled by default.

 
Manually truncate Exchange database logs
edited by on August 22nd 2014, at 12:44
In case you need to manually truncate the database logs of your Exchange server, you can follow the steps below. You'll need sufficient permissions and access to the Exchange Management Shell.

Caution!
Be cautious when you perform this action, as making mistakes here could cause database corruption and loss of data. Don't do this during production hours because this will temporarily make some (or all) mailboxes unavailable! As always, it's a good idea to have a working backup before attempting this.

Open the Exchange Management Shell.

If you don't know the physical path of your database, locate it first:

Get-MailboxDatabase | Select Name,EdbFilePath,LogFolderPath

You'll notice the datab  ...
 
Manually remove Exchange-attributes from an AD object
edited by on August 20th 2014, at 10:12

Exchange stores plenty of things in Active Directory, including mailbox information for each account. In case of a deinstallation of Exchange, this information usually remains behind, making it impossible to perform a new clean installation of Exchange and assigning a new mailbox to this user.

I found a solution here: http://www.telnetport25.com/2009/09/forcing-the-removal-of-exchange-attributes-on-a-directory-user-the-removeexchangeattributes-tool%E2%80%A6/

This command-line tool allows you to query and/or remove Exchange-attributes on AD objects (such as users and groups).

 
Allow to send e-mail from external e-mail address in Exchange
edited by on January 8th 2014, at 14:34

To allow an Exchange user to send from an external e-mail address, perform the following steps:

  1. Create a Mail Contact with the correct external e-mail address in AD and in Exchange.
  2. Open Exchange Management Shell and set up the permissions: 
    Get-MailContact MyUser@MyExternalDomain.com | Add-ADPermission -User MyUser@MyLocalDomain -AccessRights ExtendedRight -ExtendedRights "Send As"
    Replace the first e-mail address with the external one, the second part contains the user you wish to assign the permission to.
 
Windows SBS Exchange-services stop scripts
edited by on February 23rd 2013, at 11:13
Windows SBS has a nasty habbit of taking forever to shutdown/restart. This is because there's a built-in waiting mechanism to allow enough time for the Exchange-services to shutdown. Unfortunately this delay is usually a whole lot longer than it normally would take if you were to stop the Exchange-services yourself. Because the delay does no longer occur when the Exchange-services are already stopped manually, I usually tend to stop Exchange first, then do the shutdown/restart.

Because Exchange consists of many services, at work, we wrote some helper scripts to stop all Exchange-services with only a mouse click, allowing for a quicker shutdown/restart of a server. I've decided to share thes  ...
 
Exchange: move mail to a folder depending on which alias it's sent to
edited by on August 24th 2012, at 10:34

Currently, Exchange/Outlook only supports client-side rules if you want to move messages to a specific folder, depending on which alias it's sent to. This means that the rule only works when Outlook is running, which is not always possible.

You can workaround the issue by creating a rule that checks for the content of the message headers. This type of rule can be created server-side and will always run when messages arrive on the Exchange server. By checking whether the alias is present in the message headers, you can easily create a rule that moves those messages to another folder.

 
Expired Avast subscription kills Exchange Information Store
edited by on June 22nd 2012, at 16:04

A note of warning I read on the Avast Forums: if your Avast subscription runs out, the Exchange Information Store no longer starts and bails out with an error "failed to start virus scan". Very annoying indeed...

Source: http://forum.avast.com/index.php?topic=92162.0

 
Exchange 2010 with Avast disrupts Transport Service
edited by on June 22nd 2012, at 16:00
We updated Avast to the latest version on a client's server running SBS 2011. The update apparently included antispam. All of a sudden, the Transport service kept failing, and all messages (in both directions) landed in the Poison Queue. Restarting the Transport service did not fix the issue, and there was nothing we could do.

Googling around, we found that the trouble was indeed related with Avast. Disabling the Antispam Shield did not resolve the issue, but disabling the transport agent in Exchange, via Powershell was the fix:

disable-transportagent "avast antispam for exchange"

After disabling the agent, everything came to life again.

@ Avast: you should really start  ...
 
Install Exchange 2007 SP3 on SBS 2008
edited by on June 20th 2012, at 12:49
Unlike SP2, there's no installation tool for installing SP3 on an SBS 2008. Fortunately, the installation is pretty straight-forward. The steps to perform depend largely on whether or not your SBS 2008 server is running Forefront Security or not. If it's not, simply install SP3 like you normally would. The installation will succeed without additional tasks. If you are running Forefront Security, you will have to disable it before installing SP3, then re-enable it when installation has completed.

Download SP3: http://www.microsoft.com/download/details.aspx?id=24111.

Run the software, it will extract its contents to a directory of your choosing. I recommend creating an empty directory as the  ...
 
Manually configure Exchange Online in Outlook
edited by on September 2nd 2011, at 12:49
If you are not able to configure Outlook using the Microsoft Online Sign-in Tool for some reason, there's a way to do it manually.

For this to work, you need the following:

a working internet connection (duh);

your username and password;

your storage location (usually closest to your HQ).

First off, we need the mailbox store server. To find this, you have to log in to Outlook Web Access. Your ICT department should already have given you information on how to do this. If not, use one of the following urls, depending on your location:

Asia Pacific (APAC): https://red003.mail.apac.microsoftonline.com/owa

Europe, the Middle East, and Africa (EMEA): https://red002.mail.emea.microsoftonline  ...
 
Empty message body in Outlook with Exchange 2010 on 2008R2 terminal server
edited by on May 6th 2011, at 15:17
Had a problem with a client who is running Outlook 2007 with Exchange 2010 on a 2008R2 terminal server: each message sent from Outlook (composed by Outlook) had a blank message body. The recipient side would see it like this, and the empty message would be stored in the Sent Items folder of Outlook. This behaviour was system-wide, meaning that each user was experiencing this problem.

After some digging around, I found this link on the internet stating it could be related to the virus scanner. My eye was particularly caught by a post of someone who was running Avast 4.8 on TS (which was identical to what the client was running). After disabling scan outbound mail the problem was fixed.



I   ...
 
Installing Exchange 2007 SP2 on SBS 2008
edited by on September 15th 2010, at 11:31
Installing Exchange 2007 Service pack 2 on a Windows 2008 SBS generates an error, as detailed here:
http://support.microsoft.com/kb/973862.

To resolve, you can either follow the instructions outlined in the KB, or you can download the installation tool, especially designed for SBS 2008.

First, download these: Exchange 2007 SP2 (64-bit edition):
- http://www.microsoft.com/downloads/en/details.aspx?FamilyID=4C4BD2A3-5E50-42B0-8BBB-2CC9AFE3216A

Exchange 2007 SP2 installation tool for SBS 2008:
- http://www.microsoft.com/downloads/en/details.aspx?FamilyID=FFD2FE61-9278-489E-9B96-3816394C9CB6



Run the first file to extract its contents to a folder of your c  ...
 
Change SmartHost outgoing port in Exchange 2007
edited by on January 28th 2010, at 17:28
I've written an article before on how to change the outgoing SMTP port for SmartHost in Exchange 2003. Now, I have to do this again for Exchange 2007 as they've changed this procedure.

When you're unable to send e-mail directly to the internet (using MX), you probably have to set up a SmartHost to relay the e-mail for you. This is basically your ISP's SMTP server, but can be another server as well.
In certain cases, the default SMTP port (port 25) cannot be used to connect to the SmartHost, so you have to change this to something else. Gmail for instance, uses port 587 for SMTP. Other 3rd party mail services use this (or another port) as well to circumvent spam protection initiated by a lot  ...
 
Configure Exchange Server Auto-Discovery
edited by on January 18th 2010, at 13:30
When you are running an Exchange server, and have your users access the server from outside the company network, you usually have to open up access to OWA. This enables users to access their mail, contacts and appointments by using an internet browser. Occassionally, someone also has a ActiveSync enabled phone that they would like to use. This protocol also uses OWA for syncing data. And very rarely, there's also a guy (usually the CEO) who simply wants to use its Outlook to connect - this is possible through web as well using RPC-over-HTTP(S), but that's information for another blog post (on another day in the far far future...) .

One of the hassles when configuring this, is the fact that   ...
 
[Exchange] mailbox sharing and delegation
edited by on June 26th 2007, at 09:23
 
Exchange 2000/2003: change in-/outgoing SMTP port
edited by on May 17th 2007, at 15:24
Because of (Belgian) providers limiting SMTP (port 25) traffic to their own servers, makes it necessary for us (as an 3rd party ISP) to allow our customers to use our own mailserver for all outgoing mail. To circumvent this limitation, we've configured the mailserver to listen on port 26 as well.

For our customers with only a few mail clients (so no local mailserver), this is usually not a problem. A quick change of the SMTP port, solves their issues. For people that have a catch-all mailbox (and a local mailserver), the mailserver itself usually allows the change.

Of course, some of our clients have Exchange servers, and there, the change was not that obvious.
After a bit of a search, we'  ...
 
Enabling in-place archive after Hybrid migration to Office 365
by on January 1st 1970, at 01:00
After migrating your on-premise Exchange mailboxes to Office 365 using Hybrid method, and subsequently decommissioning your on-premise Exchange, you may run into the issue where it is not possible to enable the in-place archive for a mailbox through the online Exchange Admin Portal or ECP. Attempting to do so will trigger an error.Microsoft has released some Powershell scripts to work around the issue. You can run the scripts to enable or disable the in-place archive for a certain mailbox. The script does not need any prerequisites other than the Powershell AD module and the user running the script must have the proper permissions as outlined on the downloads page.

https://docs.microsoft.co  ...
 
Editing (default) room calendar permissions in Exchange
by on January 1st 1970, at 01:00
It is possible that room mailboxes have their default permissions set to show only availability, but sometimes you may want to allow users to see what has been booked (title of the meeting). You can either set this through Outlook but this is tedious as you'll need full mailbox access for this to work. However, admins can also set this via Powershell (for M365, load the Exchange Online module).

To view the current permissions:

Get-MailboxFolderPermission my-meeting-room:\calendar

To set the permissions to show limited details by default:

Set-MailboxFolderPermission -AccessRights LimitedDetails -Identity my-meeting-room:\calendar -User default

Optionally, if you wish to know who booked t  ...
 
 
showing posts tagged with 'exchange'
 
 
« ‹December 2024› »
SunMonTueWedThuFriSat
1234567
891011121314
15161718192021
22232425262728
293031    
 
Links
 
Quote
« I needed a password with eight characters so I picked Snow White and the Seven Dwarves. »