Buchatech.com

Posts Tagged ‘Exchange 2007’

This blog is for those that have your Exchange stores and logs on the C drive and the c drive on your server is running out of space. You know you need to move them but you don’t know how. Well I will cover this in this blog step by step below.

NOTE: Here are a couple of things to note before going further:

1. If your server is running out of space on the C drive check all possible areas and be sure Exchange is the culprit before moving its components around.
2. Do not jump on the server and start manually deleting log files.
3. This post is to be used before your disk is full or after you have recovered from a full disk disaster. If your disk is completely full now visit this link How to Recover from “Disk Full” on an Exchange Log Drive once you have cleared some space come back to this blog to move the log files and database store.
4. Make sure you have a good backup of Exchange before following these steps.
5. Use the below steps at your own risk.

MOVING THE DATABASE:

First off we are going to use the Move wizards in this post for both the logs and databases move. Using the wizards will simplify these tasks  and we like to keep things simple. If you would prefer to do this in PowerShell see the link at the end of this blog post.

• Open “Exchange Management Console”.
• Expand “Server Configuration”>Select “Mailbox” .
• 
• You should now see the “Database Management” tab in the lower center console.
• Right click on each of the Storage groups and click “Move Database Path”.
• 
• Record the “Database file paths”.
• Go to your new drive that you are going to move the store to and create a folder to move it to. I recommend that you create a similar path (folder structure) to the folder you are moving your store to. EXAMPLE: %newdrive%\Microsoft\Exchange Server\Mailbox\First Storage Group\.
• No go back into “Exchange Management Console”>”Server Configuration”>“Mailbox”.
• In the lower center console right click on the Storage group you want to move and click “Move Database Path”
• Click the browse button and select the path to the folder you created in the previous step.
• Once you have selected the path click the “Move” button.

Read the rest of this entry »

I recently had the task of backing up Exchange 2007 using DPM 2007. I added the DPM agent to the Exchange server just fine. When I modified the protection group to add my storage groups I got an error saying I needed the eseutil.exe and ese.dll on the DPM server. I got these off my Exchange server and copied them to the DPM bin folder (C:\program files\Microsoft DPM\DPM\bin\). This took care of that error. You can also create a hard link to eseutil.exe and ese.dll. For more on this see: Exchange Server Database Utilities  & DPM07. 

After I got past that error I then ran into other errors on my Exchange protection members in DPM.

• “DPM has detected a discontinuity in the log chain“

and

• “Error 30216: DPM has detected a discontinuity in the log chain for Storage group First Storage Group on SERVERNAME.fqdn since the last synchronization.
  Error details: Unspecified error (0×80004005)

To resolve this I turned circular logging off on my Exchange storage groups and restarted the Exchange Information Store service. I then performed a consistency check on each of my storage group protection members and all errors went away.

• For further help backing up Exchange with DPM 2007 visit: Troubleshooting Exchange Server Protection Issues
• Here a blog on restoring Exchange using DPM: DPM 2007: Recovering Exchange data

At a client’s site they had Small Business Server 2008. For some reason Exchange 2007 was no longer working after they ran some windows updates on SBS 2008 and did a reboot. The information store service would no longer start. I checked event logs and saw this “Source: MSExchange ADAccess Event ID: 2114“. After doing some research I found out that if you disable IPv6 it will cause this error. Sure enough they had disabled IPv6.

I re-enabled IPv6 and the information store service would start again and all was good. Exchange 2007 requires IPv6 be enabled even if you are not using it. You can read more on this here: Don’t forget IPv6

I ran across a tool Microsoft has for testing remote Exchange connectivity such as: Outlook Anywhere, ActiveSync, Autodiscover and more. Here is the URL: https://www.testexchangeconnectivity.com

Do you want to setup Exchange Server in your house and run your own email server? Let me guess you do not have a static IP address and do not want to get one. Well below are my steps on how to set this up.

What you will need:

• A Windows domain and an Exchange Server setup.
• Dynamic DNS service such as no-ip.com or dyndns.com.
• A purchased domain name from somewhere like voxdomains or any other service. Just make sure you have full management of the DNS.

Go ahead and setup your Domain controller with AD and your Exchange server. I assume you have some working knowledge of domains and networking so I am not going to cover how to do this in this article.

Once you have your Exchange up and ready to go. Go download the no-ip client or update client from the dynamic DNS service you signed up for. This client runs in your system tray and will update your no-ip address with the public IP whenever it changes. Now install the update client on your Exchange box.

Configure your router/firewall to forward incoming traffic on port 25 (my port is different as my ISP blocks incoming port 25. I will explain further below.) to your Exchange server. Configure your router/firewall to allow outgoing traffic on port 25. (my port is different as my ISP blocks outgoing port 25. I will explain further below.)

Go to your domain host and add the address your dynamic DNS service gave you. For example your domain MX record points to test.no-ip.com. Now you should be able to receive and send mail.
Ok. above I mentioned my setup is a little bit different. This is because my ISP (Comcast) blocks outgoing and incoming SMTP traffic on port 25. This is a tactic by them to combat SPAM. They do however allow SMTP traffic in and out on port 587. Below I explain how to get around this.

Read the rest of this entry »

I had a user that was an external contractor. He was on a few distribution lists and wanted to receive those emails at his yahoo.com email account. Here is what I did to accomplish this:

I created a contact in Exchange for user1 with an external email of user1@yahoo.com.

Read the rest of this entry »

Have you ever had email from one specific domain bounce back from Exchange with status code of: #550 4.4.7 QUEUE.Expired; message expired ##? I ran into this problem. It turned out the mail server on that domain was blocking email coming from our Exchange 2007 mail server. Here is what I did to narrow down the issue.

Read the rest of this entry »