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