How To Add Holidays to Outlook 2010

By Joe Piggee Sr.

1. Open Outlook and Click on the File Tab.
2. Scroll Down and Select “Options”
3. Click Calendar 4. Click Add Holidays

Restore Exchange to a New Server or Move Exchange to a New Server

 

By Joe Piggee 

In Active Directory Users and Computers, reset the computer account of the failed Exchange Server. Just right-click the computer and choose "Reset Account". We do this so as to later join a new machine to the domain, with the same name as the failed server. The failed server will never be in use anymore, but the new computer will have its name and will take over from Active Directory all Exchange settings and configuration of the failed server.

1. Next, install an operating system with appropriate service pack and hot fixes on the new server.
2. The new server should have the same computer name as the previous one.
3. Configure with same drive configurations
4. The new server should then be added to the domain.
5. We should install the Exchange Server software on the new machine in recovery mode using the command: Setup.com /m:recoverserver.
6. Restore Databases. Be sure to place them in same place
7. Mount Databasesetup

Email will not send after P2V

By Joe Piggee

Monday, February 04, 2013
5:15 AM

1. Use one of the following methods to go to a command prompt:
    ○ In Windows 8 or in Windows Server 2012, use the Search charm to search for cmd, and then tap or clickCommand Prompt.
    ○ In earlier versions of Windows, click Start, click Run, type cmd.exe, and then press Enter.
2. Type set devmgr_show_nonpresent_devices=1, and then press Enter.
3. Type Start DEVMGMT.MSC, and then press Enter.
4. Click View, and then click Show Hidden Devices.
5. Expand the Network Adapters tree.
6. Right-click the dimmed network adapter, and then click Uninstall.

Pasted from <http://support.microsoft.com/kb/269155>

Setup AutoDiscover DNS Record

 
By Joseph Piggee Sr.
Create the AutoDiscover DNS Record

1. Open the DNS Manager.
2. Expand Forward Lookup Zones then expand domain.com
3. Now right-click domain.com then select New Host(A).
4. Type autodiscover and the IP Address of theExchange 2010 server, then click Add.
5. Click OK to close the dialog box then click Done.
6. Close the DNS Manager. 

ActiveSync users cannot synchronize an EAS device for the first time in an Exchange Server 2010 or Exchange Server 2013 environment

By Joseph Piggee Sr.
You can work around this , just assign the Exchange Servers group the right to change permissions against msExchActiveSyncDevices objects.
To do this, follow these steps:
1. Start Active Directory Users and Computers.
2. Click View, and then click to enable Advanced Features.
3. Right-click the object where you want to change the Exchange Server permissions, and then click Properties.
4. On the Security tab, click Advanced.
5. Click Add, type Exchange Servers, and then click OK.
6. In the Apply to box, click Descendant msExchActiveSyncDevices objects.
7. Under Permissions, click to enable Modify Permissions.
8. Click OK three times.
http://support.microsoft.com/kb/2579075

The operation couldn’t be completed because a change occurred in the remote forest

 

By Joseph Piggee Sr.

Many tech ask me about this problem, and whenever I go into a new environment I get the error myself, so I decided to put this little reminder out. If you run into an error when opening the Exchange Management Console (EMC initialization failed and “the operation couldn’t be completed because a change occurred in the remote forest”.

You may also find that while EMC does not work, you are able to launch the Exchange Management Shell (EMS) without any issues.

This may occur when the server you are connecting to has been updated with a Service Pack or Roll Up Update (RU).

Now, there is a possibility that this error may not always indicate a version mismatch between the tools on the client and the RU level of the server, so how can you confirm this is actually the issue? As shown in this Exchange Team blog post, you can confirm the versions do not match by running the following command on both the client and the server from the shell:

Get-Command EXSetup | %{$_.FileVersionInfo}

Here’s the result from the above command on a Windows 7 box running the Exchange 2010 SP1 Management Tools:

This command is checking the file version information for the local instance of ExSetup.exe on both the client and the server installed by default in C:\Program Files\Microsoft\Exchange Server\V14\bin\

.

Once you get the version numbers you can compare it, using the the following link:

Exchange Server and Update Rollups Builds Numbers

http://social.technet.microsoft.com/wiki/contents/articles/exchange-server-and-update-rollups-builds-numbers.aspx

After confirming the version numbers, you know that you’ll need to update the tools on my client machine and install RU2 or other related Roll-up to resolve the issue. At the time of this posting the current Rollup is 8.

Incoming Mail Flow Stops

By Joe Piggee Sr.

Event Source: MSExchangeTransport

Event Category: Resource Manager

Event ID: 15007

Description: The Microsoft Exchange Transport service is rejecting message submissions because the service continues to consume more memory than the configured threshold. This may require that this service be restarted to continue normal operation.

Event Source: MSExchangeTransport

Event Category: Resource Manager

Event ID: 15004

Description:

Resource pressure increased from Previous Utilization Level to Current Utilization Level.

• Quick fix is to just restart your Transport service.
• Long term fix is to either disable Transport from monitoring or what I'd recommend is to give the Exchange server the necessary resources, and adjust the settings accordingly.

To Disable the Transport from Monitoring :
Modify the edgetransport.exe.config file using notepad. This can be found in c:\program files\microsoft\exchange server\v14\bin. Change the “EnableResourceMonitoring” from “True” to “False”, save and close the file, then restart the Microsoft Exchange Transport Service.

Exchange 2010: Update the Global Address List(GAL)

You can use the Shell to update a global address list (GAL). A GAL is a directory that contains entries for every group, user, and contact within an organization's implementation of Microsoft Exchange.
1. Open the EMC Shell.
2. Run the following command:

Update-GlobalAddressList -Identity <GlobalAddressListIdParameter> –DomainController

* Note that this starts the process, but the completion could take 15 min. to a couplehours.

More Information:

Syntax:

update-GlobalAddressList -Identity <GlobalAddressListIdParameter> [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-WhatIf [<SwitchParameter>]]

Identity = The Identity parameter specifies a unique identifier of the GAL being updated. These unique identifiers include the common name (CN), GUID, or distinguished name (DN).