Category: Exchange 2010

Permission issues Ex2013 shared calendar with Ex2010 mailbox

​​Scenario: A user with a mailbox in Exchange 2010 is getting permission errors in Outlook when trying to access and edit a shared calendar of a mailbox in Exchange 2013 even though the correct permissions are set for that Exchange 2010 mailbox. The error is:
“You do not have permission to veiw this calendar. Do you want to ask user to share his or her Calendar with you?”
Resolution: Enable Outlook to connect to Exchange using HTTP for the Exchange 2010 mailbox in the Outlook Profile
1. Start Outlook if not started already.

2. Navigate to your Outlook Account Settings:

a. Outlook 2013/2010: Click on File –> Account Settings–> Account Settings.
b. Outlook 2007: Click on Tools –> Account Settings.
3. Select your Exchange account, and then click Change.

4. Click More Settings, and then click the Connection tab.

5. Under Outlook Anywhere (Exchange over the Internet for 2007), select the Connect to Microsoft Exchange using HTTP check box.

6. Click Exchange Proxy Settings.

7. Make sure the following settings are set:
a. Enter the URL to connect to  proxy server for Exchange: https://mail.domain.com
b. On fast networks, connect using HTTP first,… is checked.
c. On slow networks, connect using HTTP First,… is checked
d. Proxy Authentication Settings is set to Basic Authentication.

8. Click OK to close each Outlook window.

9. Restart Outlook

10. If your are prompted for authentication, use the following:
a. username: domainusername
b. password: your password.

Exchange Management Console initialization failed when opening

Scenario: You have installed Exchange 2010 management tools on a computer, but EMC can no longer connect to the server (we knew this server was turned off). You receive this error message:

 
Initialization Failed
The following error occurred while attempting to connect to the specified Exchange server ‘servername’.
The attempt to connect to http://servername/Powershell using “Kerberos” authentication failed: Connecting to remote server failed with the following error message : The WinRM client cannot process the request because the server name cannot be resolved.
 
Resolution:
1. Navigate to C:users(username)AppDataRoamingMicrosoftMMC and deleteExchange Management Console.
2. Navigate to: HKCUSoftwareMicrosoftExchangeserverv14AdminTools and deleteNodeStructureSettings.

EMC was able to connect to a different server and open successfully.

Mailbox Auditing in Exchange 2010

Scenario: You want to audit the activity in a mailbox. Auditing includes information on who does what in a mailbox.

Enable Auditing for a mailbox: Set-Mailbox -identity “Mailbox Name” -AuditEnabled $true
Search Audit Logs for a mailbox: Search-MailboxAuditLog -Identity “Mailbox Name” -showdetails
Disable Auditing for a mailbox: Set-Mailbox -identity “Mailbox Name” -AuditEnabled $false
By default, the audit logs are retained for 90 days and then purged. This can be controlled by the -AuditLogAgeLimit parameter. The logs are stored in the mailbox under the Audits Subfolder under the Recoverable Items Folder. The Recoverable Items Folder is a hidden folder.

Conditions for Log Truncation in Exchange

These are the conditions in which Exchange’s Replication service will truncate the committed log files in Exchange:

Exchange 2010 & 2013
  • The log file must have been successfully backed up, or circular logging must be enabled.
  • The log file must be below the checkpoint (the minimum log file required for recovery) for the database.
  • All other lagged copies must have inspected the log file.
  • All other copies (not lagged copies) must have replayed the log file.
Exchange 2013
Exchange 2013 uses quite a big checkpoint depth (100MB), it’s usual to find a hundred or more transaction logs even when circular logging is enabled and the database is essentially quiescent. It’s far removed from the five or six transaction logs that a standalone database enabled for circular logging might use.

Entering Exchange Product Key in Exchange Powershell

Task: Enter in the Exchange Product Key in Exchange Powershell by using the command below.

Set-ExchangeServer servername –ProductKey aaaaa-aaaaa-aaaaa-aaaaa-aaaaa
Even though you can see the new edition on Exchange, the new edition/product key will not be fully activated until the Information Store service is restarted. The new editions functionality will not be there until the service restart. Restart it from Exchange Powershell Below.

Creating Exchange Databases and creating Database Copies in Exchange Powershell

Task: To create Exchange DB’s and DB Copies, follow the following powershell commands below. Note everything with this highlight will need your adjusting.

Create the DB:
New-MailboxDatabase dbname -Server servername -LogFolderPath C:dbfolderLogs -EDBFilePath C:dbfolderDBdbname.edb 
Mount the DB:
Mount-Database dbname 
Add the DB Copies to other DAG members:
Add-MailboxDatabaseCopy dbname -MailboxServer PassiveServerName -ActivationPreference 2 
Add-MailboxDatabaseCopy dbname -MailboxServer PassiveServerName -ActivationPreference 3 
Add-MailboxDatabaseCopy dbname -MailboxServer PassiveServerName -ActivationPreference 4 

Mailbox is Disabled after Reconnecting mailbox from disconnected state.

Scenario: After you reconnect a disconnected mailbox, you may receive the following error in Outlook Web App, ​ ‘Your mailbox has been disabled.’ You may also have trouble connecting to her mailbox in powershell or EMC saying the mailbox is not avaiable.
Solution: Run the following command in Exchange Powershell.
clean-mailboxdatabase <Database Name>

modify domain names for hybrid org relationship

​Task: Modify domain names configured for an organization relatinship in a hybrid deployment
you can use powershell command below to complete task
$domains = (get-organizationrelationship ‘On Premises to Exchange Online Organization Relations
hip’).domainnames
 
Set-organizationrelationshp -id  ‘On Premises to Exchange Online Organization Relations

hip’ -domainnames $domains