Monday, August 20, 2012

Outlook 2010 "Could not Complete the Operation" when Forwarding Email

This issue is a result of the contact information being "misread" or "corrupted".

In Outlook 2010 there are a couple of way to work with this.

1. When you go to forward the message and the person's name automatically appears, simply hover the mouse over it and press DELETE.  This will remove it from the cache.   Now type in the address and the message will complete properly.

2. If you want to clear out all of your cache without trying to address them one at a time, then here are the steps:
  • Open Outlook 2010
  • Open File
  • Click Options
  • Click Mail
  • Select "Empty Autocomplete List"
 That will clear all of the cache items including tasks or appointments that could also be causing the issue.

Microsoft's first recommendation is to clear your Outlook profile and create another one which is sure work but is a bit overkill for such a small issue.

I'm sure the process is similar with other versions of Outlook but YMMV.

Good luck...

Sunday, August 12, 2012

Uninstalling Exchange 2003 during Exchange 2010 Migration

If you are getting the following error:

'The component "Microsoft Exchange Messaging and Collaboration Services" cannot be assigned the action "Remove" because: - One or more users currently use a mailbox store on this server.'

then the odds are good you have an item in AD that is still pointing to the old Exchange 2003 server.  Here's how you get rid of it.

Just open up ADUC, do a find, create a custom query and paste in the command you see below:

 












Then select VIEW, then choose Columns.

From there you can add in the extra values needed to find out which account is still showing old Exchange 2003 data.  Just add in both attributes with Exchange on them.  Redo the Find Now and you'll be able to sort them by server name to find out the offending accounts.

During my last SBS 2003 to SBS 2011 migration it turned out to be the SBSAdmin account that I had created during the migration steps.

Once these accounts are removed or corrected you can continue your uninstall of Exchange 2003.

Good luck!

Sunday, August 05, 2012

How to Load the Answer File on a SBS 2003 to SBS 2001 Physical to Virtual Migration

I just ran into this issue today during a migration.  Simply put how do I get an answer file into a new VM?  The process is simple.

1. Using another VM, add a floppy drive and select the option to create a new floppy image.
2. Boot the VM and once loaded open the floppy and format it.
3. Copy your SBS answer file to the newly created floppy.
4. Using the VMWare console remove the floppy from your running VM.
5. Once your new SBS 2011 VM gets to the point where you can choose either a new install or migration, select Migration.
6. At this point on the console click to add a floppy and then select your new floppy image from the datastore that contains the answer file.
7. From there continue your migration.

This is a quick easy step to allow your to get the migration answer file loaded without the need for any 3rd party applications or other issues.  It keeps the disc stored on the datastore with your other ISO files and is there for future use if needed.

Good luck with your migration.

**Update: Make sure you removed the virtual floppy image before your next VM restart**

Friday, July 27, 2012

Configure Two Ironport C-Series Devices Where the Backup Hosts the Quarantine

These steps come straight from Cisco and it works like a charm.  This allows the primary device to focus on email filtering and the second device to take care of the quarantine work.  I have another post on how to sync the SLBL on these two devices since users will be getting their information from the backup IronPort.


How to configure two C-Series devices where the backup hosts the Quarantine 
Question: How to configure two C-Series devices where the backup hosts the Quarantine Answer All-in-one-plus-one IronPort Spam Quarantine Configuration
Note: This approach will not work if using Centralized Management.

Many sites will run two IronPort appliances, one that is designated as the "Primary MX" server and processes the majority of mail, and a second appliance as a hot spare that is designated as the "Secondary MX."  If the Primary MX should become unavailable for any reason, then the normal SMTP protocol will redirect traffic to the Secondary MX until the primary is available again.  For sites that wish to deploy the IronPort Spam Quarantine feature for their end-users but do not have enough traffic to justify a dedicated M-Series appliance, we offer the below configuration hints to allow you to configure the Secondary MX system to act as a centralized quarantine for both appliances, and to tell the Primary MX that messages detected as spam should be sent to that central quarantine on the Secondary MX system.

Please note that this configuration should only be used by sites that are not at or near the peak performance throughput on their Primary MX server, or doing equal-weighted load balancing between two appliances, as the additional load of processing end-user quarantined messages could result in reduced throughput in the event of a Primary-to-Secondary fail-over.  For high-volume sites whose multiple appliances are running at or near peak throughput, we recommend deployment of the M-Series appliance to offload quarantine duties from your C-Series appliances.

The second IronPort MGA that will contain the IronPort Spam Quarantine, must be able to identify messages coming from the Primary MTA and force the messages to the Quarantine.  This can be accomplished by using an X-Header once a messages is identified as spam.
To avoid having two IronPort C-Series MGA's scanning the same message be sure to perform the following steps.

Procedure overview:


1. On the Primary

1. Ensure messages received from Primary MX MGA are scanned for Anti-Spam filtering
2. When Spam Positive and/or Suspect Positive, send to the IronPort Spam Quarantine and add X-Header: X-Ironport-Quarantine

2. On the Secondary

1. add a Mail Flow Policy which by-passes Anti-Spam scanning
2. Add a new Sender Group called "Quarantine_From_Primary", set the order # to 1.
3. Configure this Sender Group to accept messages from the Primary appliance
4. Configure this Sender Group to use the Mail Flow Policy created previously

5. Configure the local quarantine on the "secondary" MGA
6. Edit Log Global Settings to monitor the X-header: X-Ironport-Quarantine

3. Test




If this is not setup correctly one message will actually be scanned by both MGA’s before ending up in the quarantine.  
(The following example is using a Sender Group on the secondary MX MGA called "QUARANTINE_FromMail2")

Primary Server
Thu Apr 27 15:05:45 2006 Info: New SMTP ICID 1348 interface Mail (192.168.1.2) address 1.1.1.1 reverse dns host pproxy.gmail.com verified yes
Thu Apr 27 15:05:45 2006 Info: ICID 1348 ACCEPT SG SUSPECTLIST match sbrs[-2.0:-0.5] SBRS -1.4
Thu Apr 27 15:05:45 2006 Info: Start MID 1661 ICID 1348
Thu Apr 27 15:05:45 2006 Info: MID 1661 ICID 1348 From:
Thu Apr 27 15:05:45 2006 Info: MID 1661 ICID 1348 RID 0 To:
Thu Apr 27 15:05:45 2006 Info: Start MID 1661 ICID 1348
Thu Apr 27 15:05:45 2006 Info: MID 1661 ICID 1348 From:
Thu Apr 27 15:05:45 2006 Info: MID 1661 ICID 1348 RID 0 To:
Thu Apr 27 15:05:45 2006 Info: MID 1661 Message-ID '<16ac64320604271305o755483cdx28677153c5e4032@mail.spammer.com>'
Thu Apr 27 15:05:45 2006 Info: MID 1661 Subject 'Fwd: Impotenc-e hellp no doc visilt'
Thu Apr 27 15:05:45 2006 Info: MID 1661 ready 13559 bytes from
Thu Apr 27 15:05:45 2006 Info: MID 1661 matched all recipients for per-recipient policy DEFAULT in the inbound table
Thu Apr 27 15:05:51 2006 Info: MID 1661 using engine: CASE spam positive
Thu Apr 27 15:05:51 2006 Info: EUQ: Tagging MID 1661 for quarantine
Thu Apr 27 15:05:51 2006 Info: MID 1661 antivirus negative
Thu Apr 27 15:05:51 2006 Info: EUQ: Tagging MID 1661 for quarantine (X-Ironport-Quarantine)
Thu Apr 27 15:05:51 2006 Info: MID 1661 queued for delivery
Thu Apr 27 15:05:51 2006 Info: Delivery start DCID 4789 MID 1661 to RID [0] to offbox IronPort Spam Quarantine
Thu Apr 27 15:05:51 2006 Info: Message done DCID 4789 MID 1661 to RID [0]
Thu Apr 27 15:05:51 2006 Info: MID 1661 RID [0] Response 'ok:  Message 22017 accepted'
Thu Apr 27 15:05:51 2006 Info: Message finished MID 1661 done

Secondary Server
Thu Apr 27 15:05:50 2006 Info: New SMTP ICID 121070 interface Mail (192.168.1.2) address 192.168.1.2 reverse dns host unknown verified no
Thu Apr 27 15:05:50 2006 Info: ICID 121070 ACCEPT SG QUARANTINE_FromMail2 match 192.168.1.2 SBRS rfc1918
Thu Apr 27 15:05:50 2006 Info: Start MID 22017 ICID 121070
Thu Apr 27 15:05:50 2006 Info: MID 22017 ICID 121070 From:
Thu Apr 27 15:05:50 2006 Info: MID 22017 ICID 121070 RID 0 To:
Thu Apr 27 15:05:55 2006 Info: ICID 121070 close
Thu Apr 27 15:05:50 2006 Info: Start MID 22017 ICID 121070
Thu Apr 27 15:05:50 2006 Info: MID 22017 ICID 121070 From:
Thu Apr 27 15:05:50 2006 Info: MID 22017 ICID 121070 RID 0 To:
Thu Apr 27 15:05:50 2006 Info: MID 22017 Message-ID '<16ac64320604271305o755483cdx28677153c5e4032@mail.spammer.com>'
Thu Apr 27 15:05:50 2006 Info: MID 22017 Subject '[SPAM] Fwd: Impotenc-e hellp no doc visilt'
Thu Apr 27 15:05:50 2006 Info: MID 22017 ready 13907 bytes from
Thu Apr 27 15:05:50 2006 Info: MID 22017 matched all recipients for per-recipient policy DEFAULT in the inbound table
Thu Apr 27 15:05:50 2006 Info: EUQ: Tagging MID 22017 for quarantine (X-Ironport-Quarantine)
Thu Apr 27 15:05:50 2006 Info: MID 22017 queued for delivery
Thu Apr 27 15:05:54 2006 Info: RPC Delivery start RCID 10882 MID 22017 to local IronPort Spam Quarantine
Thu Apr 27 15:05:54 2006 Info: EUQ: Quarantined MID 22017
Thu Apr 27 15:05:54 2006 Info: RPC Message done RCID 10882 MID 22017
Thu Apr 27 15:05:54 2006 Info: Message finished MID 22017 done
Detailed Steps for Primary Server


1. Ensure messages received from Primary MX MGA are scanned for Anti-Spam filtering

1. Ensure that Anti-Spam scanning is enabled
2. Configure the appropriate Anti-Spam policies on the Incoming Mail Policies page to send Positive and/or Suspect spam to the IronPort Spam Quarantine (now hosted on the Secondary MX appliance)

1. (Mail Policies -> Email Security Manager -> Incoming Mail Policies)


2. Configure the default Mail Policies: Anti-Spam settings ; Positively-Identified Spam Settings actions also to include additional X-header:

1. Header Name: X-Ironport-Quarantine
2. header Text: offbox (any text value will work)

3. If desired, repeat the above for Suspected Spam Settings
4. Setup an External Quarantine

1. Designate the Secondary MX appliance as an External Quarantine host by navigating to Monitor -> Quarantines -> External Quarantines 
2. Click the "Add Quarantine..." button
3. Enter a descriptive name so you know you are routing to your Secondary MX appliance
4. Enter the IP address of the Secondary MX appliance
5. Change the default port from 6025 to 25
6. Submit
7. Commit changes





Detailed Steps for Secondary Server

1. On IronPort that will host the Quarantine (Secondary) add a Mail Flow Policy

1. Select the Mail Flow Policies, beneath the HAT Overview
2. Click the Add Policy, button
3. Name the policy, example: SpamQuarantine 
4. Connection Behavior set to Accept    
5. In the Security Features, turn off Virus Protection and Spam Protection
6. Turn Off Sender Verification
7. Select  Submit

2. Add a new Sender Group called "Quarantine_From_Primary", set the order # to 1.

1. Open the HAT Overview, add a new Sender Group
2. Click Add Sender Group
3. Name: Quarantine_From_Primary
4. Set Order to 1
5. Add comments
6. Select the new Policy created, example SpamQuarantine
7. Leave other fields, unchecked
8. Click the Submit and Add Senders, at the bottom right.
9. Enter the IP of the Primary IronPort.
10. Add comments
11. Check Submit
12. Configure Local Quarantine
13. Enable Local quarantines 
14. Monitor-> Quarantines-> Local Quarantines

3. Edit Log Settings

1. System Administration > Log Subscriptions -> "Global Settings" box,
2. click "Edit Settings..."
3. In the "Headers (Optional)" text box add: X-Ironport-Quarantine

4. Test 

1. Send messages that have spam (use X-header: X-Advertisement: spam)
2. Send messages that do not contain spam
3. Review the logs

Use BGInfo with Server 2008 R2


This is a great program to use if you work with a lot of different servers and you need to keep track of what you are connected to.  It also gives the ability to see the specifics of the box without the need to run all of that information down.

Here's the process:

1.  Create a text file named AutoRunBGInfo.reg and place it on your desktop.
2.  Enter the text in the file as follows - 

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
"BGInfo"="\"C:\\BGInfo\\Bginfo.exe\" \"C:\\BGInfo\\config.bgi\" /timer:0 /silent"

3.  Now place a folder on C:\ named BGInfo.  Inside there place the BGinfo.exe file and your config.bgi file.  The config.bgi file is created when you customize the information you want on your server's desktop.  Below I have a list of the ones I use and in the same order.

4.  Start BGInfo once manually, accept the programs question, and then load the config.bgi file to set the wallpaper.  

5.  That's all.

Now that you've done this process everytime you login to the server you will get a fresh update of the statistics.  Having things such as free drive space at a glance is great when doing network maintenance tasks.

My BGInfo config: (All text in white except for the colors below.  Change yours to match the wallpaper's contrast so you can see it easily)

**COMPANY  NAME**
                                                                                      
User and Computer Info

UserID:   
Host Name:   
OS Version:   
Edition:   
OS Bits:    bit
Hardware Bits:    bit
Service Pack:   
IE Version:   
Boot Time:   

CPU:   
Memory:   
Volumes:   
Free Space:   
                                                                                     
Network Settings

IP Address:   
Subnet Mask:   
Default Gateway:   
DNS Server:   
MAC Address:   
Network Speed:   
Machine Domain:   

                                                                                      
Virtual (or Physical)

Model:    * or * will show here.