DPM 2010 Add firewall rule

Will — Mon, 30 Aug 2010 23:52:27 +0000

Here is a simply way of adding a Windows firewall rule to allow DPM remote agent push:

netsh advfirewall firewall add rule name="Allow DPM Remote Agent Push" dir=in action=allow service=any enable=yes profile=any remoteip=[IP]

Exchange 2010 – Import-mailbox and Export-Mailbox cmdlets fail with error code –2147221219

Will — Wed, 28 Jul 2010 04:30:03 +0000

I have been attempting to figure out an issue with the mailbox-import cmdlet for the last 10 hours. Never mind the fact that nearly every single thread and blog post online points to answer (s), which aren't necessarily the end all solutions to a problem that's unique to everyone. The error, -2147221219 is generic, and doesn't necessarily mean the same for everyone. In my case, my deployment consists of two Mailbox Role hosts, and three hosts for the CAS/HUB roles. The CAS array is balanced using an HLB.

After a lot of research and trial and error, I was able to pinpoint the issue. To import PST files using import-mailbox, you have to make sure that you meet the following requirements:

Created a Windows 2008R2 VM
Install Exchange with the mailbox role only.
- Create a new database, name is IMPORT.
Install Microsoft Outlook 2010 x64.
Before you begin, make sure that you point your IMPORT database to one of the internal CAS hosts:
- Set-MailboxDatabase [DATABASE] -RpcClientAccessServer [INTERNAL RPCACCESS HOST]
- Trust but, verify: Get-MailboxDatabase [DATABASE] | fl RpcClientAccessServer
Once you've done this, create the new mailbox, and then move it to the the IMPORT database.
From there, you can run in your mailbox-import command, which should be successful.

You should also make sure that your databases have the correct permissions. You can do this through ADSI under CN=Databases,CN=Exchange Administrative Group (ID),CN=Administrative Groups,CN=US,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=[FQDN],DC=[TLD]:

Read
Administer information store
Allow impersonations to personal Exchange Information
Create named properties in the information store
Open mail send queue
Send as
Receive as
View information store status

Simple conclusion: Make sure that your CAS array is not causing the issue...

Exchange 2010 remove public folder/database

Will — Thu, 22 Jul 2010 14:48:25 +0000

If you have dealt with Exchange for as long as I have, then you'll know that public folder was/is a poor replacement for better solutions. Microsoft will eventually remove this feature as it moves forward with the future versions of Exchange.

That said, I decided to axe public folders from my Exchange deployment because I don't want to trouble myself with a legacy features that might hinder on my operation. With that in mind, here is how you would remove a public folder/database from Exchange 2010:

Start EMS
[PS] get-OfflineAddressBook -Server Exchange02 | remove-OfflineAddressBook
[PS] Get-PublicFolder “\” -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Recurse -ErrorAction:SilentlyContinue
[PS] Get-PublicFolder “\Non_Ipm_Subtree” -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Recurse -ErrorAction:SilentlyContinue

You are done. Now you just have to re-create your OAB, and you are set!

Exchange 2010 ECP virtual directory missing

Will — Wed, 21 Jul 2010 17:41:42 +0000

I was troubleshooting several issues at the same time. During the process, I had to recreate the Exchange IIS website along with the virtual directories. However, after doing so, I found out the ECP virtual directory was not created in IIS. Based on my finding, I decided to run Set-ECPVirtualDirectory command via Powershell. The only problem is that I don't run a Standalone Exchange server, I have a CAS array running in the background, and because of that, I saw the following error immediately following the command above:

Cannot process argument transformation on parameter 'DC'. Cannot convert value "SERVER\ecp (default Web site)" to type "Microsoft.Exchange.Data.Fqdn".

The solution is rather simple:

New-EcpVirtualDirectory -externalurl "https://fqdn.tld/ecp" -internalurl "https://SERVER/ecp" -Server "exch01.xxx.local"

Once you've done this, be sure to close down EMC and re-open it. You should also verify by running GET-ECPVirtualDirectory.

Exchange 2010 changing HUB transport default policy SMTP address

Will — Thu, 08 Jul 2010 18:13:14 +0000

If you want to change the default policy SMTP address (e.g. *@domain.local) via EMC you may run into an error such as this:

Summary: 2 item(s). 0 succeeded, 1 failed.

Elapsed time: 00:00:00

Edit Default Policy

Failed

Error:

The operation can't be performed on the default e-mail address policy.

Exchange Management Shell command attempted:

set-EmailAddressPolicy -ConditionalDepartment @() -ConditionalCompany @() -ConditionalStateOrProvince @() -ConditionalCustomAttribute1 @() -ConditionalCustomAttribute2 @() -ConditionalCustomAttribute3 @() -ConditionalCustomAttribute4 @() -ConditionalCustomAttribute5 @() -ConditionalCustomAttribute6 @() -ConditionalCustomAttribute7 @() -ConditionalCustomAttribute8 @() -ConditionalCustomAttribute9 @() -ConditionalCustomAttribute10 @() -ConditionalCustomAttribute11 @() -ConditionalCustomAttribute12 @() -ConditionalCustomAttribute13 @() -ConditionalCustomAttribute14 @() -ConditionalCustomAttribute15 @() -RecipientContainer $null -EnabledEmailAddressTemplates 'SMTP:@domain.local' -Name 'Default Policy' -Identity 'Default Policy'

Elapsed Time: 00:00:00

You can easily bypass this by running the following command from Exchange PowerShell:

Get-EmailAddressPolicy def* | Set-EmailAddressPolicy -EnabledEmailAddressTemplates 'SMTP:@NEWDOMAIN'

Exchange 2010 Management Console log-in failure.

Will — Wed, 30 Jun 2010 15:54:41 +0000

I've been focusing on setting up Exchange 2010 with DAG that's probably why I haven't had the time to post on my blog lately. That said, I ran into an issues with EMC, which I thought I would write about it since, I'm sure some other folks are running into it as well.

When I started EMC (logged-in as Domain Admin), I would see an Access denied error. To correct the issue, I simply ran the following from Exchange Management Shell:

$credential = get-credential (enter admin credentials in the prompt).


$session = new-pssession -configurationName Microsoft.Exchange -connectionuri http://[SERVER]/powershell -credential $credential
import-pssession $session

Behind the logo

Will — Fri, 28 May 2010 01:38:27 +0000

Given the recent events, I thought this link would be appropriate to follow.

VMWare vSphere client on Mac

Will — Wed, 19 May 2010 20:56:03 +0000

Kudos to Michael for providing us with a valuable document detailing an X11 hackery to get vSphere client running on Mac: http://www.punchingclouds.com/?p=856

Then again, I could use Parallels/VMWare Fusion in coherence mode and get the same results...

Brocade AP-7131 default password

Will — Thu, 29 Apr 2010 02:41:20 +0000

For those of you that are in search of the default password, its "admin123", not "admin" as documented.

Microsoft Outlook missing Webex toolbar

Will — Tue, 06 Apr 2010 17:26:18 +0000

Are you using Webex? Do you not see the Webex Outlook toolbar? Here is the solution to your problem:

Start Outlook.
Go to Help > Disabled Items.
Look for the Webex plug-in, select it, and then click on enable.

Restart Outlook and you'll have your toolbar back!