May 30 2012

Inbox missing in Outlook when using Exchange Server

We had a user today that advised his Inbox is missing from Outlook.

The first few things you need to check and try are as follows:

1. Open Outlook and click on yourname@company.ccc, on the right-click “Customize Outlook Today…”
2. Then click on “Choose Folders”
3. Tick “Inbox” if it has not been ticked. If Inbox shows that it has been ticked go to the step 4.
4. Close Outlook.
5. Click on start, and in “run” or  “Search Programs and Files” type outlook.exe /resetfolders
6. Open Outlook. If the Inbox is still not shown the read the next few steps but make sure you only change what the article says or you may run into other problems.

Using MFCMAPI to “unhide” the Inbox:

1. Browse to this website.
2. Click on download and save the zip file to a location you choose.
3. Extract the zip file to the PC having the issue.
4. Open MFCMAPI, and click ok on the pop up window.
5. Click on Session and then Logon as per below screen shot












6. Choose the Outlook Profile you need to edit and click on OK
7. You will now see the Mailbox Database and Public Folder Database as per below.












8. Right click the  Mailbox Database and choose open.
9. A new Window will pop-up like the one below.









10. (1) Click on the Arrow next to “Root Container”. (2) Click on the Arrow next to “Top of Information Store”. (3) Click on “Inbox”. (4) Click on “PR_ATTR_HIDDEN”












11. Right Click “PR_ATTR_HIDDEN” and choose edit property.












12. Untick Boolean, click OK, close MFCMAPI and open Outlook.











13. Your Inbox should now be visible in Outlook.






Apr 18 2012

How to export the relay list from an Exchange 2003 server

It’s always a good idea to export your relay list regularly in case of server crash or failures. Yes there’s other ways to restore this but if you have a txt document then it’s a lot quicker to import the list to a rebuilt or new server.

In order to do this download IPsec.vbs from here.

After you have downloaded the package unzip it and then register the exipsec.dll by opening the command prompt and using the syntax “regsvr32 pathtoexipsecurityexipsec.dll” and pressing enter.

After registering the dll open the command prompt again and change to the ExIpSecurity folder. Then type “cscript ipsec.vbs -s (servername) -i (instance id like 1 or 2 or 3) -o e -d (domaincontroller name) -r relay >c:relaytable.txt

After running the script you should see a text document in c: named relaytable.txt which will contain all the allowed IP’s in the relay list.

For more information on ipsec.vbs just run cscript ipsec.vbs to get all the switches that are available for you to use. You are also able to import the list to a new server etc.

Dec 29 2011

Export Sending Message Size Limits for users in Exchange 2003

Some companies love to set Sending Message Size Limits per user to avoid certain users from sending mail larger than the set limit on their Active Directory Account. (Please note that this is not the best practice and when used extensively will become a huge headache for you in the future)

If you need to report on the set sizes for users in your environment then I would recommend you use CSVDE to export the data from Active Directory to a CSV file.

The attribute in Active Directory that you are looking for is “submissionContLength”. You can see the set value in ADUC or using ADSIEDIT.

To change the allowed send limit per user go to: Active Directory Users and computers, find the user you want to set the limits for, right-click and choose properties, click on the Exchange General Tab, click on Delivery Restrictions and then click on Maximum KB under Sending Message Size and set the size limit. (as previously noted this is not recommended but helps when a user’s machine is infected with a virus so you can bring the message size down to zero KB to prevent the account from sending mail)

Now to the good stuff!

You need to report on who the users are that have custom set sending limits and what these limits are set to.

1. Login to your Exchange server and run the command prompt. (Start, Run, type cmd and press enter)
2. Type the following command to export users attributes in a certain OU:  csvde -d “OU=Users and Computers,OU=theOUname,DC=test,DC=domain,DC=example,DC=local” -f c:export.csv
3. This will export all user attributes to a csv file to c:
4. Open the export.csv with Excel and delete all the columns except the submissionContlength column and others that you’d like to keep.
5. Now you are able to see which user has limits set and what size they are in KB

Note that it’s easier to add the values for the csvde command when you have Active Directory open and browsed to where the users ar homed. Then just fill in the query from the bottom to the top like: OU=user,OU=branch1,=DC=yourdomain,DC=local

To export attributes from the root use: csvde -f c:export.csv (this will export the whole environment but beware your text file could be huge!

CSVDE is a very powerful tool and you can customise the query to produce filtered results. Google is your friend 😉

Dec 8 2011

Reporting on OWA for Exchange 2003

I recently received a request to report on OWA for a 2003 Exchange environment.

Needless to say without any 3rd party tools you are kind of left in the dark. However, I found the below website that assisted me with pulling some stats from the IIS logs using Log Parser 2.2 and 2 SQL scripts.

First browse to this website and follow the instructions. The site will give you 99% of the information you need to pull the reports. There was one issue that they failed to mention though. How do I export the data to CSV???

Here is a screenshot of how the command looks like: (you need to add -o:CSV to export the data to CSV format)

Other things to keep in mind:

1. I had to copy the log files to c:publicLogs for Log Parser to run against the logs
2. Add -o:CSV before the SQL Script path to export the output to CSV
3. The CSV file is found in C:PublicLogParserOutput
4. Open the CSV in Excel and panel beat the report to your heart’s desire

This article was very helpful and there’s some other commands that you might want to use.
Lastly I could not get the 2nd script to work for exporting the data to a pie graph.

Hope you found this useful.

Nov 10 2011

Export mailbox permissions on Exchange 2003

I had a request to export mailbox permissions on an Exchange 2003 Exchange server to see who has rights on certain individuals’ mailboxes and what rights these groups and people have on the said mailboxes.

I found a tool called ADModify that did the job perfectly. The tool exports the data to xml. Open it with Microsoft Excel and choose “Open as XML Table”. Then use the filters at the top to view what the permissions are and what permissions each object holds on the particular mailbox.

The download link to ADModify is here.

A very nice tutorial on using the tool to only export mailbox rights can be found here.

Note that the tool may be used to do bulk permission changes to mailboxes etc. Please read the tutorial before using the tool as the last thing you would want to do is add or delete permissions on 1000’s of mailboxes.

Oct 15 2011

Windows 2003: The Cluster Service on node ‘Clustername’ cannot be started. The network path was not found.

There are two ways of resolving an issue when you receive the error “Windows 2003: The Cluster Service on node ‘Clustername’ cannot be started. The network path was not found.” when trying to open Cluster Administrator on an Exchange 2003 server running Windows 2003

First try this:

From one of the cluster nodes:

  1. Click Start, go to Programs, go to Administrative Tools, click on Cluster Administrator.
  2. When prompted to connect to a cluster, type a (.) in the Open Connection to Cluster box, and then click Open. (Just bring the offline resources online if nothing has changed on the Network Adapter side of things and skip the next steps)
  3. Click the cluster group, and then click the cluster IP address.
  4. On the File menu, click on Properties.
  5. On the Parameters tab, click New Cluster Network in the Network to Use box (the Public Network no longer exists), and then click on OK.
  6. Click the cluster IP address.
  7. On the File menu, click Bring Online.

You can now bring the remaining resources online.

If you are unable to gain access to one of the cluster nodes:

  1. Start Cluster Administrator.
  2. When you are prompted to connect to a cluster type the NetBIOS name of one of the Cluster nodes in the Open Connection to Cluster dialog box and click Open.
  3. Then follow the steps above.



Sep 8 2011

Unable to Exmerge or getting error (0x8004011d)

If you are unable to exmerge a mailbox on Exchange 2003 or get the error (0x8004011d) try the following:

1.Verify that the user account under which you run the Exchange Mailbox Merge program has the Receive As and Send As security permissions set to Allow for the Mailbox Store.
To do this, follow these steps:
•Start Exchange System Manager.
•Expand Servers and expand the server that you want to run exmerge on and expand the storage group that you want.
•Right-click Mailbox Store, and click on Properties.
•Click on the Security tab and then click the user account whose permissions you want to verify (this is the account you are running exmerge with).
•In the Permissions list click to select the Receive As and Send As check box in the Allow column, and then click OK.
•If the user account is a member of a group like Domain Administrators or Enterprise Administrators then the group must have send as and receive as rights on the mailbox store.

2.Verify that the user account you use to run exmerge has delegation authority on the Organization level in Exchange System Manager. To check follow these steps:
•In Exchange System Manager  right-click the organization and click Delegate control.
•Click Next.
•If the user account under which you run the Exchange Mailbox Merge program is not listed and it does not have the role of Exchange Full Administrator, click Next, add this user account with the role of Exchange Full Administrator and click OK.
•Click Next then Finish.

3.Quit Exchange System Manager.

4.Restart the Microsoft Internet Information Service (IIS) Admin Service.

Aug 12 2011

Export Mailbox sizes per server to csv (Exchange 2003)

If you need a rather quick way to export all the mailbox sizes on a particular server then the below link is for you.

Download the script, run it by opening the command prompt and type cscript MSX_GetMailboxSize.vbs thenameoftheserverhostingthemailboxes>filenameyouwanttochoose.csv

Remember to add the export location to the above command if you want to save the export to a particular path ie: cscript MSX_GetMailboxSize.vbs servername>e:reportsserver1.csv

Open the csv export with Excel after you ran the script. You can then manipulate the contents to the format you need as all mailbox data will be there.

Fields exported to csv using this script are:

Display Name
Storage Group
Total Items

I used this to work out an average mailbox usage per server.

I found the script here. There’s also more information on this script from the source site.

Hope this has been helpful.

May 11 2011

Outlook Web Access is not showing the same content as in Outlook

I had a very interesting problem today that I’ve never experienced before with Exchange 2003 and OWA.

Some users advised that when in OWA the mail shown is a month old and no new mail is shown in OWA newer than the previous month. All e-mail is visible and accessible in Outlook though.
I logged onto OWA using the user’s credentials and noted the same. I then saw that the view in OWA is set to messages (which should show all messages) as per below:

I then chose unread messages (which shows unread mail but not necessarily all or recent mail) as per below:

This showed all unread mail but not the results we wanted. I then chose messages again and all mail was shown as we expected it in the first place. All read, unread, most recent and old mail as per the Outlook client was visible.

This however is a quick fix and the first time that I’ve personally seen it. I’m sure with some more investigation there will be a patch or config that will resolve this.

Apr 8 2011

Unable to open items in mailbox

We had an issue where we were unable to open any new or old mail in any user’s mailbox.

We then found that the antivirus software was reloaded on the Exchange servers and no exclusions where set. After stopping the antivirus software’s services we were able to open any mail as per usual.

The exclusions where setup and services started.

Exclusion list for Exchange 2003:

EDB,MDB,LOG,NDX,ND4,ND3,ND2,MSL,ML,LDB,DGN,DBF,DBB                  Security Risk Extensions                Ignore

C:Program FilesExchsrvr                                                                                            Security Risk Folder                         Ignore

D:Program FilesExchsrvr                                                                                           Security Risk Folder                         Ignore

E:Program FilesExchsrvr                                                                                            Security Risk Folder                         Ignore

C:Program FilesSymantecSMSMSE4.0ServerTemp                                Security Risk Folder                         Ignore

C:Program FilesSymantecSMSMSE4.0Quarantine                                    Security Risk Folder                         Ignore

D:Program FilesSymantecSMSMSE4.0Temp                                               Security Risk Folder                         Ignore

D:Program FilesSymantecSMSMSE4.0Quarantine                                   Security Risk Folder                         Ignore

C:Program FilesSymantecSMSMSE4.6ServerTemp                                Security Risk Folder                         Ignore

C:Program FilesSymantecSMSMSE4.6ServerQuarantine                    Security Risk Folder                         Ignore

D:Program FilesSymantecSMSMSE4.6ServerTemp                               Security Risk Folder                         Ignore

D:Program FilesSymantecSMSMSE4.6ServerQuarantine                    Security Risk Folder                         Ignore

E:Program FilesSymantecSMSMSE4.6ServerTemp                                Security Risk Folder                         Ignore

E:Program FilesSymantecSMSMSE4.6ServerQuarantine                     Security Risk Folder                         Ignore

C:WINNTsystem32inetsrv                                                                                      Security Risk Folder                         Ignore

D:Exchsrvr                                                                                                                         Security Risk Folder                         Ignore

E:Exchsrvr                                                                                                                         Security Risk Folder                         Ignore

H:Exchsrvr                                                                                                                         Security Risk Folder                         Ignore

C:Program FilesHyperion                                                                                          Security Risk Folder                         Ignore

I:Exchsrvr                                                                                                                          Security Risk Folder                         Ignore

M:                                                                                                                                          Security Risk Folder                         Ignore

Q:Exchsrvr                                                                                                                        Security Risk Folder                         Ignore

D:SMTPLogs                                                                                                                     Security Risk Folder                         Ignore

H:ExcLogs                                                                                                                          Security Risk Folder                         Ignore

C:SESA                                                                                                                                Security Risk Folder                         Ignore

O:EXCHSRVR                                                                                                                    Security Risk Folder                         Ignore

P:Exchsrvr                                                                                                                         Security Risk Folder                         Ignore

R:Exchsrvr                                                                                                                         Security Risk Folder                         Ignore

S:Exchsrvr                                                                                                                         Security Risk Folder                         Ignore

T:Exchsrvr                                                                                                                         Security Risk Folder                         Ignore

U:                                                                                                                                           Security Risk Folder                         Ignore

Q:                                                                                                                                           Security Risk Folder                         Ignore

V:Exchsrvr                                                                                                                         Security Risk Folder                         Ignore

W:Exchsrvr                                                                                                                       Security Risk Folder                         Ignore

L:                                                                                                                                             Security Risk Folder                         Ignore

N:                                                                                                                                           Security Risk Folder                         Ignore

I:                                                                                                                                             Security Risk Folder                         Ignore