Trust relationship failed

Run this command:

Reset-ComputerMachinePassword -Server DC01 -Credential Domain01\Admin01

Recipient isn't the expected type

Set-Mailbox fails, update "Send on behalf" exchange 2010, recipient isn't the expected type.

Issue:

When update "sent on behalf", you may face error "recipient isn't the expected type"

Cause:

"Send On Behalf" access has not been removed while disabling the mailbox, they accounts are still pointing to shared mailbox, it usually happens with migrated exchange.

Solution:

Go to AD Users & Groups

Select email account having problem

Click properties and select Attribute Editor

select PUBLIC DELEGATES and remove the mailbox account you seen in the error.

Error message when you try to set an IP address on a network adapter

This error often occurs when cloning/copying virtual machines. You may have come across this error:

The IP address XXX.XXX.XXX.XXX you have entered for this network adapter is already assigned to another adapter Name of adapter. Name of adapter is hidden from the network and Dial-up Connections folder because it is not physically in the computer or is a legacy adapter that is not working. If the same address is assigned to both adapters and they become active, only one of them will use this address. This may result in incorrect system configuration. Do you want to enter a different IP address for this adapter in the list of IP addresses in the advanced dialog box?

There's a simple fix to this and requires following these steps from the command prompt.

1. Type set devmgr_show_nonpresent_devices=1, and then press Enter.
2. Type Start DEVMGMT.MSC, and then press Enter.
3. Click View, and then click Show Hidden Devices.
4. Expand the Network Adapters tree.
5. Right-click the dimmed network adapter, and then click Uninstall.

Here's the link to Microsoft's site for this error, Microsoft KB 269155

Access Denied when executing remote powershell

It's been a while since I've posted anything here, and I need to get back into the habit of adding to this blog as issues arise.

When trying to remotely run a PowerShell script you may find that you need local administrator access to the remote computer to successfully run the script. If not properly configured, you will receive an access denied message. A simple fix would be to add the user running the script to the local Administrators group, but we don't necessarily want to grant them this level of access.

If you haven't already done so, you must enable PowerShell remoting. This is done by running this command in PowerShell: Enable-PSRemoting on the remote computer. For more info on this command go to this technet link: Enable PSRemoting

Next you need to run this PowerShell command:
Set-PSSessionConfiguration -Name Microsoft.PowerShell -showSecurityDescriptorUI

Confirm that you want to perform this, it will then open a window allowing you to add users/groups with the appropriate permissions. You should now be able to remotely run your PowerShell scripts.

Note: This can impose security risks to your system, so please use this at your own discretion.

For additional information you may reference this page: PowerShell Blog

ExMon Unknown Start Trace Error (183)

When trying to run Exchange Monitor (ExMon) you may run into this error:

Here are the steps to fix this common problem.

• From the CMD prompt, Query the running traces:
  • Logman query -ets
  • You should see one called "Exchange Event Trace"
• To stop the Exmon trace, run this:
  • Logman stop “Exchange Event Trace” -ets
• You should now be able to run ExMon

MS Exchange abnormal log generation

We came across an issue where one of our Exchange 2010 databases was quickly filling with logs.  The server was generating 10-20 times more logs than average, which caused the database drive to fill and took the database offline.

The root cause, a user had updated their iPhone iOS which resulted in a sync error with ActiveSync.  I discovered this by using the below tips to locate the mailbox generating the logs and disabling the ActiveSync feature for the mailbox.  With ActiveSync disabled the logs stopped.  So a quick wipe of the Exchange account from the iPhone, rebooting the iPhone, and recreating the Exchange account on the iPhone resolved the issue.

If you have a single mailbox database you are lucky, and the Exchange User Monitor should be all you need. Download Exchange User Monitor (ExMon) from Microsoft:
http://www.microsoft.com/en-us/download/details.aspx?id=11461

Run the ExMon.exe application from "C:\Program Files (x86)\Exchange User Monitor".  With ExMon you can see the users mailboxes, their CPU usage, Bytes In, Bytes out, Log Bytes, etc.  You may quickly find a user with a large consistent CPU usage and large Log Bytes compared to other users, this may be your culprit.  Try disabling their Exchange ActiveSync within the Mailbox Features.  This will only stop the ActiveSync communication, the mobile device will reconnect when you re-enable the ActiveSync, so no need to reconfigure the mobile device if this doesn't resolve the log issue.  With ActiveSync disabled for the suspected log generating mailbox, monitor the logs for the database and verify they have returned to a normal generation rate.  If so, you found the user.  Delete the email account from the mobile device, restart the device, and then re-add the email account.

If you ever run into the 'Unknown Start Trace Error (183)' when starting ExMon, see this post for a fix.

If you have multiple databases, ExMon is not as easy as it will list all mailboxes for the server.  To filter per database, us the Exchange Management Shell and this powershell script.

Get-StoreUsageStatistics -Database <DatabaseIdParameter> | export-csv c:\temp\LogonStats.csv

Modify the <DatabaseIdParameter> to the name of your database, and also change the path for the export of the csv file.  You can find additional information on this command here:
http://technet.microsoft.com/en-us/library/dd876852.aspx