Tag Archives: Exchange

Log File is Damaged – KB10392001

KB10392001

Description:  Received an alert that a log file is damaged for exchange

Windows Event Log: Application
Windows Event Source: ESE
Windows Event ID: 440
Windows Event Severity: Error
Windows Event Message: eseutil (10056) JetDBUtilities – 11056: The log file C:Program FilesMicrosoftExchange ServerV14MailboxMailbox Database 1013801047E00.log is damaged, invalid, or inaccessible (error -501) and cannot be used. If this log file is required for recovery, a good copy of the log file will be needed for recovery to complete successfully.

Steps to resolve: There isn’t much to do about this alert. If it’s important and they need it, you will have to restore the file from a good backup copy.

If this happens a lot, use the troubleshooting and diagnostic tools on the exchange database to check the health of it.

 

Exchange Average Delivery Time – KB10391837

KB10391837

Description:  Received an alert that the customer’s email is taking a long time to get to them

Common customer description: My mail is taking a long time to send or receive

Probing questions: Is this a common issue?

Is this a recent thing that has been happening?

Is there a lot of people using mail?

Steps to isolate: Send test email to yourself

Check inbound/outbound queues

Steps to resolve:

1. Check the alert, see how long it says the time that it’s taking to deliver

2. Log onto the Customer’s OWA with IE, Chrome, or Firefox on your computer or connect to the server and log onto the OWA from there

3. Send a test email to yourself (your email address)

4. See how long it takes before you receive that email

5. You can also run some diagnostics to see if everything is okay

Additional considerations: This could be an issue with the Exchange database or some setting with Exchange.

Barracuda Appliance Incremental Backups Issue: Circular Logging Enabled – KB10391557

KB10391557

Description:  Warnings or Failures about Incremental backups being performed for exchange

Common customer description: My backups are failing, can you fix them?

I received an email that my backups have been failing

I got a call that my backups are failing

Probing questions: Was this recent?

How long have you been receiving these emails and/or phone calls?

Steps to isolate: Check the backup report for the errors and/or warnings

Steps to resolve:

1. Log into Barracuda web console

2.  Check the backup report. What is the error or warning that it generates?

Exchange error

3. Barracuda cannot backup the mailbox when circular logging is enabled

  • Why? When circular logging is enabled, transaction log files that have already been committed to the database are overwritten, preventing the accumulation of logs. The log files are overwritten whether or not a full or incremental backup has been run, and a history of previous logs since the last full or incremental backup is not maintained. This is why, when circular logging is enabled, differential and incremental backups of the Exchange databases cannot be performed (since these types of backups rely on complete history of logs). So basically, with circular logging enabled, only information included in the last full backup can be recovered.

4. To work around this, you will have to create a backup job specifically for the exchange server (if the server is a stand-alone server)

To do that go to the Backup Tab, then to Schedules

Schedules

5. On the right hand side, go to Add a Schedule

add

6. Name the backup job (make it obvious – if it’s the exchange call it by the exchange server name)

name

7. Select the server that you want to back up (in this case, it will be mail2)

select server

8. Select the days you want it to back up

days

9. Set the time you want it to back up (Barracuda runs in a 24 hour format – military time)

  • Repeat means if you want the backup to run 2 or more times in one day

Time

10. Choose the backup type – in this case we can’t do the incremental or “smart” backups, we will chose Full instead

Full

11. Double-check the configuration. When you think it’s correct, on the top right, look for a green button called Save

Save

Now you have to watch the backups for a bit, since we changed the backups to Full it might start taking up space. Monitor the job to make sure their disk space doesn’t get full.

Since we made a new backup just for exchange, we have to deselect the exchange server from the previous job(s)

1. Go back to step 5 but instead of adding a schedule, edit the existing schedule.

2. There might be a check box that says “backup all computers and data sources” – uncheck that box and unselect the exchange server. (Don’t forget to say save!)

Additional considerations: If there is only one server being backed up (example: server02 is the PDC, BK, MX, DNS, DHCP), switching the backup to Full might not be an option.

Removing Phone from Exchange / Trust Relationship – KB10391463

KB10391463

Description of Work
How to disable a Phone in Office 365 or Exchange 2007 / 2010 when you are disabling a user from accessing their company email

– Option to preform a remote wipe of the Exchange data on the phone

Steps to remove the trust Relationship that Exchange created with the phone

Estimated Time to Complete
Half Hour

Requirements before beginning Service Work
Which user account to disable phone on, Approval from Main contact, Access to Domain Controller

 

Exchange 2013 or Office 365

Logged into the admin account for the company

locate the user in Exchange management that the changes need to be made on

then Double click to open the properties windows noted below

photo3
Next select the “Edit Exchange Properties option

Photo2

On this screen select the

– Disable Exchange ActiveSync

– Disable OWA for Devices

Select the “View Details” Option

phone1

This screen will allow you to

– Remove trust relationships from phones

– preform a remote wipe of the device ” Clear all Exchange Information on the phone ”

when on this screen

– first wipe and devices that need to be clear of exchange data “only if customer requests remote wipe of device

– then remove all devices from the mobile devices list

Exchange 2007 / 2010

open the Exchange Management console on the server hosting exchange

Phone4
select the user and right click on the name

in the drop down menu select “Manage Mobile User”

– if this option is not in the list the user has never paired a mobile device to the account and you can disregard the information

If the option is listed select the item

phone5

From this screen you can wipe a device

– select the device a from the list at the top

– select ‘Preform a remote wipe to clear the mobile phone data” – Only if the Company requests this to be done on the phone

select remove

– to remove partnership from the Exchange to phone select the phone from the list and ” remove mobile phone partnership” then select the remove button

remove all device from the exchange list. this will prevent any phone from accessing the Exchange server

with Exchange 2007 and 2010 a restart of IIS is needed

open a admin command prompt

and run command ” iisreset /noforce ”

this will restart the IIS services on the server and finish the removal of the partnerships on the phone

After Mobile devices are Disabled see article on how to Disable user in AD

http://www.cpumd.com/KB103983

 

 

 

Force Update the Global Address List Exchange 2007 / 2010 KB10391439

WHEN WILL YOU USE THIS ARTICLE
1. Outlook Address List not showing newly created users or contacts
2. Users not receiving latest contacts in cached mode

 OPEN EXCHANGE MANAGEMENT CONSOLE (EMC) BY DOING THE FOLLOWING:

1. Connect to your Exchange Server using RDP or any remote application
2. Now click on start and type Exchange Ma
3. And select Exchange Management Console from the list
Open EMC
NOW WE WILL START THE UPDATE PROCESS, PLEASE DO THE FOLLOWING:
1. Now Expand Microsoft Exchange > Microsoft Exchange On-Premises > Organization Configuration > Mailbox
Expand EMC2. Now Select the Offline Address Book tab
3. Locate your Default Offline Address book and Right Click on it then select Update. You can also click on the Update link located in the Action pane on the far right after highlighting the Default Global Address List.
Update GAL4. You will receive the following message, just select Yes
Update Warning

5. Now to force the update
6. Open a Admin Command Prompt
7. Type  net stop MSExchangeFDS
8. Type  net start MSExchangeFDS

Done after verification

 

Move Exchange 2007 – 2010 Database Log Files – KB10391343

KB10391343

To use the Exchange Management Console to set the log file location when you create a storage group

 Special notes: You might need to log in as “Administrator” to perform these tasks because they require all of the permissions.
  1. Start the Exchange Management Console on the server on which the storage group is located.
  2. In the console tree, expand Server Configuration, and then click Mailbox.
  3. In the result pane, click the Mailbox server on which you want to create the storage group.
  4. In the action pane, click New Storage Group. The New Storage Group wizard appears.
  5. On the New Storage Group page, the Log files path box displays the default location where your transaction log files will be stored. Click Browse to change the default location.
    noteNote:
    You cannot use the Exchange Management Console to change the log file location for remote Mailbox servers. To create storage groups on other Mailbox servers, use the New-StorageGroup cmdlet in the Exchange Management Shell.
  6. Enter any other information in the remaining boxes as needed, and then click New to create the new storage group. For more information about creating storage groups, see How to Create a New Storage Group.

To use the Exchange Management Console to change log file locations for an existing database

  1. Start the Exchange Management Console on the server on which the storage group is located.
  2. In the console tree, expand Server Configuration, and then click Mailbox.
  3. In the result pane, click the Mailbox server that contains the storage group for which you want to change the log file location.
  4. In the work pane, click the storage group for which you want to change the log file location.
  5. In the action pane, click Move Storage Group Path. The Move Storage Group Path wizard appears.
  6. On the Introduction page, the Log files path box displays the location where your log files are currently stored. Click Browse to specify a location to which to move these files.
    noteNote:
    You cannot use the Exchange Management Console to change the log file location for remote Mailbox servers.
  7. Click Move. A warning appears that all databases in the storage group must be temporarily dismounted, which will make them inaccessible to any user. To continue, click Yes.
  8. On the Completion page, confirm whether the log file path was changed successfully. A status of Completed indicates that the wizard completed the task successfully. A status of Failed indicates that the task was not completed. If the task fails, review the summary for an explanation, and then clickBack to make any configuration changes. Click Finish to complete the Move Storage Group Path wizard.

Emails with attachments are delayed – KB10391041

KB10391041

Description:  Emails are being delayed by hours or even days.

Common customer description: We are receiving emails a lot later than we should.  Sometimes days later.

Probing questions:

When did this start?
Did you recently get a spam filtering service like Securence?
Is everyone affected?
Do the emails that are delayed have attachments?

Steps to isolate: If the client recently signed up and started using a spam filtering solution make sure emails without attachments arrive on time.  If regular emails arrive quickly but emails with attachments are delayed proceed to the next step.

Steps to resolve: Check Exchange and the clients firewall for spam filtering and virus scanning attachments.  Since Securence and other name brand spam filtering solutions scan the emails for infections along with spam, these tasks do not need to be performed in Exchange or on the firewall.

Additional considerations: It has been found that once the spam filter solution is finished scanning the email it opens a socket with the Exchange server.  Exchange is expecting the email to be transmitted within a certain amount of time.  If something like a firewall is also set to scan attachments prior to allowing the transmission Exchange will close the socket due to timeout.  Eventually the email will get sent through if enough attempts move fast enough to beat the timeout.  Better to just leave the filtering to the spam filtering service.

Exchange Does Not Have Audit Security Privileges – KB1039482

KB1039482

Description:  The Exchange server doesn’t have the audit security privilege on the Domain Controller

Common customer description: Normally the customer will not call in about this issue

Probing questions: None

Steps to isolate: Check Local Policies>>User Rights Assignment and make sure that under managing auditing and security log, you can find Exchange Servers, Exchange Domain and Exchange Enterprises. If not, you will have to add them.

Steps to resolve:

  1. On the start menu, search for secpol.msc

secpol

2. Go to Security Setting>>Local Policies>>User Rights Assignment

user rights

3. Right click on Manage auditing and security log and go to Properties

properties

4. Click on Add User or Group

exchange

5. Enter Exchange and click on Check Names

name

6. Add Exchange Domain, Exchange Enterprise, and Exchange Servers (some will not have all three listed or sometimes none of them are listed, if that’s the case, add Exchange Administrator or All Exchange…)

adding serv

7. Click Apply then OK

apply

8. Check on this for a few days, look for Event ID: 2112 to make sure that it hasn’t re-appeared

Additional considerations: Double check these articles: http://technet.microsoft.com/en-us/library/bb218747(v=exchg.80).aspx and https://technet.microsoft.com/en-us/library/dd772623(v=ws.10).aspx (look under the Important section) If you tried these and it still doesn’t work, consult with a Tier 2 tech.

Set Message Size Limits in Exchange KB1039433

Set Message Size Limits in Exchange 2010 and Exchange 2007

1Organizational limits

The organizational send and receive size limits apply to all Exchange servers in the Organization. The default is 10MB.

You can modify the organizational message size limits using the Set-TransportConfig cmdlet from the Exchange shell:

Set-TransportConfig -MaxReceiveSize 40MB -MaxSendSize 40MB

In Exchange 2007 SP1 and later, you can also set the organizational message size limits using the EMCby going to Organization Configuration | Hub Transport | Global Settings tab | Transport Settings | properties | General tab.

Exchange Server 2007 | Transport Settings
Figure 1: Setting the organizational message size limits from the Global Settings tab in the EMC in Exchange 2007 SP1 and later

2Receive Connector limit

To modify the maximum message size on a Receive Connector using the Exchange console, select Server Configuration | Hub Transport | select a Hub Transport server | Receive Connectors -> select a connector | Properties | General tab.

Screenshot: Maximum message size on a Receive Connector
Figure 2: Setting the maximum message size on a Receive Connector

To set ReceiveConnector limit using the shell:

Set-ReceiveConnector “CONNECTOR NAME” -MaxMessageSize 40Mb

3Send Connector limit

Send Connectors are used for sending outbound messages to the internet or particular address spaces (domains). Edge Transport servers also have a Send Connector to send inbound messages to Hub Transport servers in an AD Site. To modify the maximum message size on Send Connectors, select Organization Configuration | Hub Transport | Send Connectors -> select connector | Properties |General tab.

Screenshot: Maximum message size on a Send Connector
Figure 3: Setting the maximum message size on a Send Connector

To set SendConnector limit using the shell:

Set-SendConnector “CONNECTOR NAME” -MaxMessageSize 40Mb

Offline address book is not updating new users in office. KB1039403

 KB1039403

Description:    Offline address book is not updating new users in office. This is billable if happening to all users.

Common customer description: User may call in saying the new user they added are not showing up in the offline address book in outlook.

Probing questions: How long has it been since the new users was created. Users typically take around 24 hours to show up in the offline address book. If it has been longer there may be a problem with the address book updating users from the exchange database.

Steps to isolate:

  • Have the user download a new address book from: Outlook 2010; Send / Receive tab; Send/Receive Groups; Download Address Book. From Outlook 2007: Tools menu; Send/Receive; Download Address Book.
  • If the address book downloads check to see if the new user names shows up if so problem resolved.
  • If the address book does not download there is a problem with distribution of the address book. Not related to this article.
  • If the address book downloads and the user does not show up.
  • Check on the exchange server if the user is hidden from the address book.
  • If they are not hidden go to steps to resolve.
  • You can also check the outlook client installed on the onsite manager to see if the users in question are showing up. This way you can determine if it’s not just the one users that is having the problem.

Steps to resolve:

Exchange issues can be complicated and business-impacting, so please consult Tier 2 for assistance.

For Exchange 2007/2010:

  1. Open the Exchange management console
  2. Drill down the organization configuration, mailbox
  3. In the action pane select the new offline address book
  4. Give the OAB a name, select a generation server (in case of a CCR this needs to be the active node)
  5. Include the default global address list
  6. When presented with the distribution point’s page enable the web base distribution and, in case of outlook 2003 clients, enable the public folder distribution.
  7. Once the wizard has completed, right click the new OAB and select to generate the OAB.
  8. Now drill down to the mailbox database, right click it and set the new OAB to be the default for that database.
  9. Open outlook with a mailbox that is residing in that mailbox database
  10. In outlook, click on the down arrow next to Send/receive. Selects download address book and click OK. Note that if asked, you should select to download the entire address book and not just the changes.

For Exchange 2003:

  1. Open Exchange system manager
  2. Drill down to recipients, offline address lists
  3. In the right pane you should see the default offline address list.
  4. Right click in the right pane and create a new offline address list.
  5. Now drill down to the mailbox database, right click it and set the new OAB to be the default for that database.
  6. Open outlook with a mailbox that is residing in that mailbox database
  7. In outlook, click on the down arrow next to Send/receive. Selects download address book and click OK. Note that if asked, you should select to download the entire address book and not just the changes.

Additional considerations: After the new address book is created it may take up to a few days for it to re download to all outlook clients. Users may need to download the new address book manually if needed, using the steps above in this article.

Source:  http://geekswithblogs.net/marcde/archive/2012/01/31/new-users-do-not-show-up-in-outlook-when-in.aspx