Monday, 18 January 2010

ExchangeDefender – Adding New Domains In ED5

As with any new setup, there will be hiccups.

For ExchangeDefender Service Providers, we would normally add a new client’s domain or domains via the SP console on OWN’s site.

With ED 5, we actually need to log on to the ED Admin panel, click the _Find_ button, then click the Add User/Domain wizard.

While the Add Wizard is still available in the SP Admin panel, it is the old wizard and not to be used.

Also, the script to run on the server must be downloaded via the new wizard as the content produced by the script has changed to an XML output as opposed to the old TXT file. The produced XML file can be uploaded directly into the Add wizard and parsed from there.

The link on the set up guide for the VBS is actually the old script and is not compatible with the wizard found in ED’s Admin page.

Once we had all of that straightened out, the new process is actually quite well done.

ExchangeDefender is our product of choice for e-mail hygiene and continuity.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

2 comments:

Vlad Mazek said...

Actually, nearly everything in the "provisioning" process has changed with ExchangeDefender 5. Here is the new document while the ExchangeDefender site is being upgraded:

http://www.ownwebnow.com/go/ExchangeDefender-DeploymentGuide.php

-Vlad

Philip Elder SBS MVP said...

Vlad,

Thanks for pointing to that. When I clicked through the Deployment Guide earlier, it was still showing the old page as that is where I go to download the VBS for each deployment.

That way I can watch out for any changes in the process.

The whole process came to light as the previous guide had the previous VBS which choked when I ran through the old wizard that was still linked to in our ED SP control panel.

It did get cleared up when we opened a ticket to figure out what was up. Your support folks did an excellent job as usual! :)

Thanks,

Philip