we are looking at implement the product for one of our customer but according to the documentation, it only supports up to server 2012. will the work on 2012 R2 and 2016 or is that on the road map to support those 2 OS.

What was the solution fore this problem. I have the same error.

regards,

Hans

I also did the manual configuration because the automatic failed.  When I run the command below in the Exchange management shell I get the warning "Can't remove the access control entry on the object because the  ACE doesn't exist." for all mailbox accounts.

Get-Mailbox -Resultsize Unlimited | Remove-MailboxPermission -User 'zAdd2Exchange' -Deny -InheritanceType 'All' -AccessRights 'FullAccess' -confirm:$false

I have an A record for the external mail hostname that point to the mail server.

Log Name:      Add2Exchange

Source:        Add2Exchange
Date:          5/7/2014 6:25:38 AM
Event ID:      5001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SRV02.dsc.com
Description:
RDO Logon Session Failed To Get Default Folder for Mailbox 'ZADD2EXCHANGE@MYDOMAIN.COM' for Server 'EXCHSRV' Error: -2147221231 Error in IMAPISession::OpenMsgStore: MAPI_E_LOGON_FAILED
Make sure your code runs under the Windows user identity that has MAPI profiles.
When running in a service (including ASP under IIS), set your code to run under
the Windows user account that has MAPI profiles.
When connecting to an Exchange Server, you can also use RDOSession.LogonExchangeMailbox
which does not require an existing profile.
ulVersion: 0
Error: The information store could not be opened.
Component: MAPI 1.0
ulLowLevelError: 0
ulContext: 646 At Line 210

Add2Exchange Console v16.5.1953

If when opening the Add2Exchange Console you get a fail to log in, there are several causes:

• Incorrect password
• Incorrect format of service account:  Must be SMTP email address such as zAdd2Exchange@domain.com
• Server name should be netbios name or name of exchange server dag or cluster

In some environments a new DNS entry must be made for internal autodiscover to resolve this.  Autodiscover may be set up external and Errors such as these in the Add2Exchange Event log will manifest:

Domain/autodiscover/autodiscover.xml: ERROR_WINHTTP_NAME_NOT_RESOLVED (MAPI_E_CALL_FAILED)

To resolve this failure to log in for 2013, you must add a new Host A record entry in DNS  in the forward lookup zone which points your external www-mail hostname to the internal IP address of the server or load balancer.

The Add2Exchange and SQL service are both running and using the service account and password that I used above.

I verified that the service account is showing up in my Outlook address book (on my desktop).  

This is a fresh install on Server 2012 R2 and Exchange 2013.

You get into this kind of issue if you didn't let the program create a new instance of the database within your existing sql server. If you created our database within your instance, then you would specify the main instance and have to give owner/creator permissions to the main SQL database instance. Let's take a closer look at this though support: http://support.diditbetter.com/support-request.aspx

thanks for the quick response!

what is the name of the service? i dont see a sql service there - the only listed services are the services running on the exchange server (where the program would be installed) and there is no sql server installed locally.

quick question to the remote sql installation:

I've found this solution:

"Set a new Group policy to grant the user with proper permission to access and view the service.

Please perform the following steps on the domain controller.

1. Click Start, point to Administrative Tools, and then click Active Directory Users and Computers.

2. Find and locate the organizational unit which contains the user, Right-click on it and click Properties

3. Click the Group Policy tab, and then click New, or find existing policy. Type a name for the new Group Policy object (for example, use the name of the organizational unit for which it is implemented), and then press ENTER.

4. Click the new Group Policy object in the Group Policy Objects Links list (if it is not already selected), and then click Edit.

5. Expand Computer Configuration -> Windows Settings -> Security Settings -> System Services

6. In the right pane, double-click the target service to that you want to apply permissions. The security policy setting for that specific service is displayed.

7. Click to select the "Define this policy setting" checkbox.

8. Click "Edit Security"

9. Add the user account and grant it with "Start, stop and pause" and "Read" permissions to the user account that you want to access the service remotely, and then click OK.

10. Under "Select service startup mode", click "Automatic" startup mode option, and then click OK.

11. Close the Group Policy Object Editor, click OK, and then close the Active Directory Users and Computers tool.

12. Please run "gpupdate /force" on both the DC and the client to make the GPO settings come into effect.

13. Reset the problematic client and then check if the issue can be resolved."

What i need to know is, which service do i need to enable / give the user the permissions here?

"6. In the right pane, double-click the target service to that you want to apply permissions. The security policy setting for that specific service is displayed."

what is the name of the specific service? i dont see a sql service here as this probably targets the domain controller and not the sql server

thank you in advance

Receiving message: "SQL failed to install because the machine is missing the appropriate requirements."

Resolution: Download the Windows Installer 4.5 Redistributable found at this link http://www.microsoft.com/en-us/download/details.aspx?id=8483

For a better explanation, visit this link and refer to the "Tip" between steps 8 and 9: http://guides.diditbetter.com/a2e-guide/install_add2exchange.htm

In the picture, the setting states domain\system instead of domain\zadd2exchangeservice account.

Again, it should be installed and started as the domain/zadd2exchange service account.

This means that UAC is still on and not rebooted, or if newer versions of windows, must edit and change this key: http://www.petri.co.il/disable_uac_in_windows_vista.htm

Resolution: Stop the install or uninstall if it was successful.  Change the key then reboot and reinstall.

How does Add2Exchange treat a move of a contact from the main contact private folder to a subfolder of the main contact private folder?  Does it treat it as a delete of the contact or how will it be treated?  If the contact is moved to a subfolder and then deleted from the subfolder how is that treated as well?

Answer:

A move will treat it as a delete and the deletion trigger will take effect if it is a source or destination folder for the relationship where that item is going to or coming from.

have a great weekend.

So for someone new to our products

Consider the Enterprise for larger installs or more effortless relationship creation, management and removal.

With Standard you make one to one relationships for Calendar Contacts and Tasks.  Enterprise you can do the same folder types and make individual

relationships, but you can also do Posts, Notes, Gal Sync and you have the Relationship Group Manager.

It will make a template relationship (to the service account) and then you attach an email enabled dist list with the people you want to sync to

or from  - something like z_GalSync,  and it will make and remove the relationships for you by the inclusion or exclusion in the distribution list.

It is our best technology and is very useful in the one to many, many to one, and full mesh relationships. 

For example, if you wanted to make relationships where everyone got everything no matter where they made it, then it would be a full mesh relationship.

A full mesh relationship is actually three rels, Pub to private, private to pub, and private to private (each with its own relationship settings) and then in RGM, you attach the same dist list to all.

If you had 5 people, you would need to make (5+1) x 5 relationships - or 30 and it would take 30 minutes with singles.  The Enterprise RGM templates you can do in about 4.

It is not much more expensive, an easy upgrade from Standard,

just a thought for someone new to our product line

maybe other Aussies want to be in the know, on the go.

...hey, that was good.

Also, I took it you were an independent IT guy, and we have programs to collaborate

I uninstalled.  Rebooted the server. Then re-run the pre-installer, followed by the setup program and it has worked.  I can now confirm that new relationships are establishing fine and are syncronising.  Many thanks for your help.

please call in to 800-837-8636 and we will assist with Premier Support, or continue with Free Support by filling out a support ticket here: http://support.diditbetter.com/support-request.aspx.

In answer to your questions:

I tried running the console with and without the A2E service running without sucess.

The SQL service is runnign with the A2E service account not a special A2E SQL service account which I think is what you are suggesting.  I didn't knwo that I needed a second service account.  Please confirm.

This is the first installation and I ran the preinstaller on the exchange box.

The service account was not a local admin.  I made it a local admin but that did not fix the problem.

I believe UAC is turned off.

I checked the service account in the registry.  It was set to system.  I changed it to the A2E service account.  This did not work either.

The database folder was empty.

I finally was able to proceed further by naviagting to the console executable and selecting "run as administrator".  The databases were then created and the console launched.  Does this suggest that there is a problem with UAC?

It is now replicating properly.  However I need to manually shutdown the A2E service before launching the console and manually restart it when I close the console.  Is this normal?

http://support.diditbetter.com/kb/a2e_220.aspx

Try picking the services account for sqlserver a2esqlserver and putting in the password, and restating the sql service

then open the Add2Exchange Console again.

Questions, is this a first time installation?  Did you run the preinstaller first on the exchange box?

Is the Service account part of local administrators of the box you are installing this on (permanently - and added to any AD policy you may have)

It could be UAC was not turned off and a reboot prior to the Add2Exchange installation? 

To check this, if you navigate in the registry to local machine, software, or wow6432node and OpenDoor Software, what is the value of the service account?  If it is not the a2eservice account, and it says system, then that is the issue, change it to the service account name and try to open the A2E Console again.

If it is the service account, check in the file system to see if you already have DB files in the c:\program files (x86)\openDoor software\add2exchange\database from a previous install.  If not,  fill this out please to continue: http://support.diditbetter.com/support-request.aspx

I am installing Add2Exchange Standard on an Exchange 2010 server.  The installation has completed correctly.  However when I run the A2E Console I get an error saying "Problems encountered during creation of database/tables.  Please switch to Service Control Panel and start the SQL A2ESQLServer instance with the service account credentials..."

I have checked that the SQL instance and the A2E Service is using the service account and both services are running.  Where do I go to from here?

Description:

20130102152639: GAL Command Get GAL Error: -2147467259 Error in IMAPITable::Restrict: MAPI_E_CALL_FAILED At Line 280 | Calling program: Add2Exchange Console

After an upgrade to A2E Enterprise version 14.12.1384.600  (or later), when accessing an Exchange 2010 server, the A2E GAL exclusions tab may be empty.  This is normal, so you do not have to do anything on the screen except cancel. 

This empty list is due to a newer technology we are using to make GAL Sync faster and more efficient, and less  taxing on resources.  Unfortunately, this is a known issue by Microsoft and the new improvement requires an update to Exchange. Please verify you have Exchange SP2 Rollup 3 (or later) to work correctly.

http://support.microsoft.com/kb/2685289

Stop the A2E Service, do the MS Exchange update and reboot the Exchange Server. 

After the reboot, open the A2E Console and verify the list is correct.

If it is not correct, please submit a ticket here: http://support.diditbetter.com/support-request.aspx

Error: 9669 - CRC check found invalid on Add2Exchange Console executable causing licensing and therefore syncronization issues.

Technical Bulletin: http://support.diditbetter.com/kb/a2e_221.aspx

http://guides.diditbetter.com/a2e-guide/index.html?exchange_2003_configuration.htm document.  I am not a happy camper.

In the meantime, here's where that link should point:

http://guides.diditbetter.com/a2e-guide/manual_exchange_2007_and_2010_configuration.htm

Sorry for the confusion.

http://www.diditbetter.com/manuals/Add2Exchange/Add2Exchange%20Enterprise%20Guide/index.html?preparing_to_install.htm

For example, the help button simply calls your default browser to go to our help web page.  There aren't too many things that can go wrong with that operation unless the application is being blocked in some manner.

I am funny, it really bothers me when buttons on a simple app don't work.  I hear you on the OU but why should the DB query fail?  re the cdo you lost me, I already have a cdo installed from besx, do you need this specific verision or what exactly?  thanks

Are you running the Preinstaller on a machine with Exchange Command Shell in an Exchange 2007 or 2010 environment?

if yes so far, not sure why, but there are two solutions:  Go get some more coffee

Then you can manually make your A2E Service account "zadd2exchange" in whatever unmanaged "service account" type OU you wish from within Exchange Management Console

Then rerun the Preinstaller again and make sure the name of the account is correct, then select the checkbox that account exists

Next, make sure the service account is part of the local administrators of the machine you are installing it on and any Exchange Server you are talking to or are replicating to including DR (usually all of them).

Then Log off and back on as the A2E Service account and run the CDO mapi install (if not on the same machine you ran the preinstaller) from the Preinstaller Dir, then go through the installation again.  If CDO asks to upgrade, do not do it.  Stop, uninstall the old and then install the new.

This should do it.

Even the best of technologies can at times be troublesome.
Known Issues: 

Console Load Error and/or Run-time error ‘429’: ActiveX component can’t create object
http://support.diditbetter.com/kb/a2e_168.aspx - Resolved issue, upgrade to latest

Note:  The above error is not directly related to a sync stopping issue, but only to opening up the Console. 
TIP: If Add2Exchange is stopping, and you have Outlook installed on the replication server to sync to Exchange 2013, 2016 or Office 365, it is most likely you are logging off as the service account,  so don’t. It still runs as a service, but recent MS updates made the system unable to log off.  Keep the service account logged in and lock the machine with that user on and you should be fine. If rebooting though, have to log in and stop and start the Service and then lock as that user. 

During Sync:

Add2Agent Process Exception.: Conversion from string "FTPSite" to type 'Double' is not valid.
Update to latest using normal procedure

Must read to avoid long sync times:  Best practices on syncing calendar appointments and contacts / Disable Social Connector and iCloud Sync

The following is a historical listing of other issues and other relevant information.

There are a few known incompatibilities we have found. We are working hard to fix these, but in the interim these links should prove helpful:

Microsoft Warning about third party devices:

Known issues in underlying infrastructure - Microsoft reported issues syncing Active Sync from earlier Apple and Android devices: https://support.microsoft.com/en-us/kb/2563324
Important Read: http://www.networkworld.com/article/2226464/microsoft-subnet/microsoft-exchange-calendaring-problems---a-current-perspective--mar-2014-.html
LINK: Update to the latest Critical Service Packs on all mobile devices, OWA and Outlook for client machines.

Use this link for workstations: http://update.microsoft.com/microsoftupdate/v6/vistadefault.aspx?ln=en-US

Calendaring Issues solved by Microsoft Critical updates: Microsoft Office Updates and Release Notes

Incorrect Time Zone Settings can cause issues: Time Shift in Calendar Full mesh (bidirectional) if one of the users Timezone is incorrect

Migration Wiz and Skykick Issues when migrating to O365

- 3/17/2017 update - Applicable for any folder type and for many to one or full mesh Contacts Relationship sync.  Some New features will match existing Contact items stripped of named properties.  However, this is only possible for one to one relationships.  Submit a support request for us to do a "preflight" for your ideal Migration plan!

https://www.migrationwiz.com/ 
3/15/16 Named properties and custom fields are not migrated with Migration Wiz or Skykick migration tools- It is critical to upgrade to Add2Exchange Enterprise and sync once prior to using this tool to migrate to Office 365 or hosted Exchange.  Our recommended option is to  dereplicate prior to the use of the tool for migration.  If dereplication is not done prior, the A2O Toolkit is required to remove Add2Exchange Copies in the destination folders.  It has been updated to accommodate the fact that Migration Wiz or Skykick does not sync named properties, the keys we use to determine our copies from originals. Use this link for further information. 

We were told this mailbox migration utility service WILL have functionality for an inplace migration of named properties, at the end of April 2013, yet does not have it as of March 2018. Be very careful when using these tools.

Presently, they are not compatible because they do not copy over the "named properties" of the copied items, so we completely lose control of them.  A local to hosted migration with this tool is not possible without dereplicating Calendars, Notes, Tasks,  Notes and depending on your configuration, Contact relationships. 
Export the setup in the Add2Exchange Console (Help Export Setup) and save it offline to make note of the current relationships, dereplicate prior and then install and license Add2Exchange Enterprise O365,  and set them up again using this new sync technology after the migration.   If Add2Exchange is installed on a Hub or Exchange Server, you will need to move it off to a virgin machine.   If you have migrated using this technology or premigrated and did not dereplicate prior, please contact technical support for the migration assistance immediately before you finalize the migration. 

With a proper onboarding process to O365, it is possible to dereplicate the appropriate relationships and keep some if not all Contact data in place, thereby not losing the Outlook type ahead of those users.   Please schedule a preflight BEFORE migration or presync of related folders.

Google sync

If you are using Google sync, and have bidirectional relationships, this second sync could cause items to revert back to original date or edit.  It is best practices not to have this service turned off.

iOS6 

http://blogs.technet.com/b/exchange/archive/2012/10/23/ios6-devices-erroneously-take-ownership-of-meetings.aspx

*update* iOS update 6.0.1 is now out and most of the bugs have been fixed.  You can read about it here: http://updates.gizmodo.com/post/34769325331/ios-update-6-0-1-is-out-and-its-mostly-bug

ProLaw works with proper configuration

http://support.diditbetter.com/Forums/Thread.aspx?pageid=1&mid=2&ItemID=3&thread=52&postid=114

Windows 2008R2 - Update 3/20/2017 this is applicable anymore

http://support.diditbetter.com/Forums/Thread.aspx?pageid=1&mid=2&ItemID=1&thread=113&postid=225

Microsoft Live Search Maps

http://support.diditbetter.com/kb/a2e_182.aspx

Exchange 2007 and CDO

http://support.diditbetter.com/kb/a2e_193.aspx

Samsung Galaxy III

http://community.office365.com/en-us/forums/158/t/22409.aspx

http://android.stackexchange.com/questions/25232/how-can-i-get-exchange-email-subfolders-on-my-samsung-galaxy-s3

iPhone

http://hosting.intermedia.net/support/kb/default.asp?id=1794

BlackBerry

http://supportforums.blackberry.com/t5/BlackBerry-Pearl/Sync-inbox-and-subfolders/td-p/1408361
http://supportforums.blackberry.com/t5/BlackBerry-Enterprise-Service-10/Outlook-contact-subfolders-are-not-synchronised-anymore-since/td-p/557114
http://blog.link2exchange.com/syncing-outlook-email-folders-and-inbox-subfolders-to-your-blackberry/

Android

http://community.office365.com/en-us/forums/158/t/22769.aspx
http://code.google.com/p/android/issues/detail?id=8072

Changed Items are Reverting Back

It could be that the relationships are not set to copy changes back, so make the relationships to sync back to the source and always overwrite the source with those changes,

It may also be cause by a third party product updating the items.  Please refer to the links provided below as they may help to solve this problem.

Android: http://www.companionlink.com/support/kb/How_to_turn_off_Google_Sync_on_an_Android_device

NitroDesk TouchDown: https://groups.google.com/forum/?fromgroups=#!topic/nitrodesk/GyAvBQ9pzRk

iCloud: http://forums.macrumors.com/showthread.php?t=1245236
https://discussions.apple.com/thread/3380162?start=30&tstart=0

You can use any tool to backup Add2Exchange or you could manually backup the installation of Add2Exchange.

The manual process is stopping the Add2Exchange Service, and the SQLA2ESqlserver Service from Service Control Manager.

By default, the files are located in this location: C:\Program Files (x86)\OpenDoor Software®\Add2Exchange\Database

Copy the files under the \Database directory to a new location off the machine.  Daily is usually sufficient.

This directory includes the A2E.mdf and A2E.ldf files and are usually all that is sufficient for the restore for any Enterprise installation to the last time it synced.

To be complete, you can copy and save the registry key HKEY_LOCAL_MACHINE\WOW6432Node\SOFTWARE\OpenDoor Software®

After the backup copy of files and registry, be sure to start first the SQL Service and then the Add2Exchange Service:

Recovery

It is fairly easy to recover if you have the files to restore.  See the caution re reverting VMs below.  That is usually not a fix unless considerations are made prior. Save this instance.

Migrations and Restorations 

Make a new machine as per specifications.  Once done, open the Add2Exchange Console. It will install SQL.

Then close the Console, detach the database files and move to the installed directory and attach the old database files.

Open the Console and submit a license request.

For a smooth transition, we need the most recent copy of the database before the disaster, after any relationship changes and most recent sync for a smooth reconstruction after a disaster.

Note: If the Add2Exchange machine is a VM, consider avoiding any reverting of the replication server to a prior instance. If you are restoring Add2Exchange, it only contains meta data of the synced informaiton, and the real information could have already been copied into Exchange.  To avoid duplication - it would be best not to revert, or to revert, but get the copy of the Database as it is on the affected machine, then revert, and then attach the newer database to the older installation.

In the event of an Add2Exchange database restore, or system failure and reinstall of Add2Exchange, this "worst case" would involve a desync - which you can do by configuring Add2Exchange as a "start over".  Contact Tech support to proceed. 

This "desync" can also be done "surgically", or one folder at a time, or by group

Caution:

As a side note, using the Add2Exchange Toolkit to surgically delete items from folders without removing the metadata stored in the user properties table can result in relationship item deletion triggers activating. If you remove copies and leave the metadata in place, it would appear to the working system that the user deleted the copies, and if the relationship was set to delete sources if destination items are deleted, then it could potentially delete the source items.

In the Enterprise edition, at least backup the database after every relationship change or export the setup from the Console\Help option and save somewhere so we can reference the current relationships. If you backup our entire directory, the \Registry directory has backup copies of Add2Exchange Standard relationships. We would also caution about importing prior registry files into the registry. Email tech support prior, save what was there first, and track changes if tempted to fix it in this way (which would almost be never).

In Add2Exchange Standard, we store the relationships in the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\OpenDoor Software®

In Enterprise, we store the relationships in the database.

In a disaster, start here (http://support.diditbetter.com/support-request.aspx) but please don’t do anything in regards to Add2Exchange until you get a response. Our email support is free and initial conversation, and together we will find the simplest fix for your unique situation.

　Being a member of Premier Support, you will have a certified technician resolve your unique issue.

command shell scripts will not run across the network in this instance

Thanks

just specify that the account already exists, has a mailbox (first) and is not hidden

and then select that it already exists

or you have specified it does already exist and did not call it the correct name.

One thing we have seen that this utility does not allow for extended characters in the password, so a complex password at this stage will not work

We apologize for this shortcoming.  You can always change the password after the fact in AD.

Hope this helps

Thank you

Get-User : The operation couldn't be performed because object 'zAdd2Exchange' c
ouldn't be found on 'SERVER.domainname.local
At C:\Users\Administrator.DOMAIN\Desktop\a2e-standard.9.9.177.185\preinstal
ler\lib\groups.ps1:32 char:25
+ $user       =   Get-User <<<<  $account
    + CategoryInfo          : NotSpecified: (:) [Get-User], ManagementObjectNo
   tFoundException
    + FullyQualifiedErrorId : 12CB719B,Microsoft.Exchange.Management.Recipient
   Tasks.GetUser

Exception calling "add" with "1" argument(s): "Exception from HRESULT: 0x800050
00"
At C:\Users\Administrator.DOMAIN\Desktop\a2e-standard.9.9.177.185\preinstal
ler\lib\groups.ps1:7 char:17
+     $adGroup.add <<<< ("LDAP://" + $userDn)
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : CatchFromBaseAdapterMethodInvokeTI

Exception calling "add" with "1" argument(s): "Exception from HRESULT: 0x800050
00"
At C:\Users\Administrator.DOMAIN\Desktop\a2e-standard.9.9.177.185\preinstal
ler\lib\groups.ps1:7 char:17
+     $adGroup.add <<<< ("LDAP://" + $userDn)
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : CatchFromBaseAdapterMethodInvokeTI

Exception calling "add" with "1" argument(s): "Exception from HRESULT: 0x800050
00"
At C:\Users\Administrator.DOMAINDesktop\a2e-standard.9.9.177.185\preinstal
ler\lib\groups.ps1:7 char:17
+     $adGroup.add <<<< ("LDAP://" + $userDn)
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : CatchFromBaseAdapterMethodInvokeTI

Exception calling "add" with "1" argument(s): "A member could not be added to o
r removed from the local group because the member does not exist.
"
At C:\Users\Administrator.DOMAINTD\Desktop\a2e-standard.9.9.177.185\preinstal
ler\lib\groups.ps1:39 char:11
+ $admin.add <<<< ("WinNT://$domain/$account,user")
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : CatchFromBaseAdapterMethodInvokeTI

Add-ADPermission : User or group "zAdd2Exchange" wasn't found. Please make sure
you've typed it correctly.
At C:\Users\Administrator.DOMAIN\Desktop\a2e-standard.9.9.177.185\preinstal
ler\lib\rights.ps1:3 char:39
+ Get-MailboxDatabase | Add-ADPermission <<<<  -User $account -AccessRights Ext
endedRight -ExtendedRights Send-As, Receive-As, ms-Exch-Store-Admin
    + CategoryInfo          : InvalidData: (:) [Add-ADPermission], ManagementO
   bjectNotFoundException
    + FullyQualifiedErrorId : 56B1126D,Microsoft.Exchange.Management.Recipient
   Tasks.AddADPermission

Get-PublicFolderClientPermission : Public folder user "zAdd2Exchange" doesn't e
xist. A valid public folder user should be a mail-enabled user, mailbox, or dis
tribution group.
At C:\Program Files\Microsoft\Exchange Server\V14\Scripts\AddUsersToPFRecursive
.ps1:81 char:48
+     $permission = get-PublicFolderClientPermission <<<<  -identity $_ -user $
User -erroraction Stop -server $OriginatingServer
    + CategoryInfo          : NotSpecified: (0:Int32) [Get-PublicFolderClientP
   ermission], ManagementObjectNotFoundException
    + FullyQualifiedErrorId : 6E5A2F69,Microsoft.Exchange.Management.MapiTasks
   .GetPublicFolderClientPermission

New-ThrottlingPolicy : Active Directory operation failed on SERVER.DOMAIN.l
ocal. The object 'CN=A2EPolicy,CN=Global Settings,CN=DOMAIN,CN=Microsoft Ex
change,CN=Services,CN=Configuration,DC=domain,DC=local' already exists.
At C:\Users\Administrator.DOMAIN\Desktop\a2e-standard.9.9.177.185\preinstal
ler\lib\throttlingSp1.ps1:2 char:21
+ New-ThrottlingPolicy <<<<  A2EPolicy
    + CategoryInfo          : NotSpecified: (0:Int32) [New-ThrottlingPolicy], 
   ADObjectAlreadyExistsException
    + FullyQualifiedErrorId : 912768BB,Microsoft.Exchange.Management.SystemCon
   figurationTasks.NewThrottlingPolicy

Set-Mailbox : The operation couldn't be performed because object 'zAdd2Exchange
' couldn't be found on 'SERVER.Domain.local'.
At C:\Users\Administrator.DOMAIN\Desktop\a2e-standard.9.9.177.185\preinstal
ler\lib\throttlingSp1.ps1:4 char:12
+ Set-Mailbox <<<<  $account -ThrottlingPolicy A2EPolicy
    + CategoryInfo          : NotSpecified: (0:Int32) [Set-Mailbox], Managemen
   tObjectNotFoundException
    + FullyQualifiedErrorId : B2F697BD,Microsoft.Exchange.Management.Recipient
   Tasks.SetMailbox

 

BTW, you also have to copy the files to the box, it will not run across from a UNC.

The first passwords I tried had @ , $, !, or = in the password which was causing the user creation to fail.

I have tried different OUs. We only have one mailbox database.

Unrecognized token in source text.
At line:1 char:70
+ .\lib\mailbox.ps1 zAdd2Exchange 'Users' 'Mailbox Database' GCA.LOCAL @ <<<< 5
1@n$$$!
Get-User : The operation could not be performed because object 'zAdd2Exchange'
could not be found on domain controller 'MYSERVERNAME'.
At C:\Users\Administrator\Desktop\a2e-standard.9.9.177.185\preinstaller\lib\gro
ups.ps1:32 char:25
+ $user       =   Get-User  <<<< $account
Exception calling "add" with "1" argument(s): "Exception from HRESULT: 0x800050
00"
At C:\Users\Administrator\Desktop\a2e-standard.9.9.177.185\preinstaller\lib\gro
ups.ps1:7 char:17
+     $adGroup.add( <<<< "LDAP://" + $userDn)
Exception calling "add" with "1" argument(s): "Exception from HRESULT: 0x800050
00"
At C:\Users\Administrator\Desktop\a2e-standard.9.9.177.185\preinstaller\lib\gro
ups.ps1:7 char:17
+     $adGroup.add( <<<< "LDAP://" + $userDn)
Exception calling "add" with "1" argument(s): "Exception from HRESULT: 0x800050
00"
At C:\Users\Administrator\Desktop\a2e-standard.9.9.177.185\preinstaller\lib\gro
ups.ps1:7 char:17
+     $adGroup.add( <<<< "LDAP://" + $userDn)
Exception calling "add" with "1" argument(s): "A member could not be added to o
r removed from the local group because the member does not exist. (Exception fr
om HRESULT: 0x8007056B)"
At C:\Users\Administrator\Desktop\a2e-standard.9.9.177.185\preinstaller\lib\gro
ups.ps1:39 char:11
+ $admin.add( <<<< "WinNT://$domain/$account,user")
Add-ADPermission : User or group "zAdd2Exchange" was not found. Please make sur
e you have typed it correctly.
At C:\Users\Administrator\Desktop\a2e-standard.9.9.177.185\preinstaller\lib\rig
hts.ps1:3 char:39
+ Get-MailboxDatabase | Add-ADPermission  <<<< -User $account -AccessRights Ext
endedRight -ExtendedRights Send-As, Receive-As, ms-Exch-Store-Admin
The pipeline has been stopped.
At line:1 char:1
+ g <<<< et-publicfolder -identity \ -Recurse -resultsize unlimited
Get-PublicFolderClientPermission : Command execution stopped because the shell
variable "ErrorActionPreference" is set to Stop: The specified public folder us
er "zAdd2Exchange" does not exist. A valid public folder user should be a mail-
enabled user, mailbox or distribution group.
At C:\Program Files\Microsoft\Exchange Server\Scripts\AddUsersToPFRecursive.ps1
:130 char:48
+     $permission = get-PublicFolderClientPermission  <<<< -identity $_.Identit
y -user $User -erroraction Stop -server $_.OriginatingServer

If on Opening Console for existing install which did work

Account hidden from the GAL

If on Opening Console for new install

If you are installing Add2Exchange on the Exchange server right after running the pre-installer in some instances It shuts down the address book and doesn’t start it back up and it will leave errors in the event log for address book

You will receive location 5 errors when opening up Console for the first time after SQL Installs

Also, when trying to do a logon test, it will fail with the network issues dialogue

Resolution:

Start address bookservice back up

Sometimes this does not work and a reboot is required.

Or

If not on the Exchange Server and doing the Login Test, the Exchange Server does not evaluate – reboot the box

If still, check for Hosts file edit

On a new Add2Outlook machine, do a simple Add2Outlook install.

At this point, if there is replicated data in the destination folders from Add2Exchange, it has to be removed before syncing with Add2Outlook to avoid duplicates. 

There are two ways to do this.

• Use the Add2Outlook toolkit for manual dereplication of Add2Exchange items in ALL destinations  copied through Add2Exchange - even if they are not making relationships there now, they might later. Reset products, pick folder and do for each.
• Another simpler way is to make all the relationships again, close the console and do not let Add2Outlook replicate. Stop the timer (from Addins - since it automatically starts when you close the Console so don’t let it happen.  Close Outlook.
  • Download, install, and license the Add2Outlook toolkit and select the option in reset products for Add2Exchange  and select the option for Prior relationships settings for dereplication of Add2Exchange items in ALL destinations 
  • TIP: With this option if they are not making relationships to a destination now, then they might later so you have to manually pick that folder and  reset the product.  Pick a folder and do for each.
  • Tip:  Be sure to select the Settings Display tab to select the checkbox to include other OpenDoor software products so you don’t have to strip the sources as well

On Add2Exchange Server

• Update Add2Exchange
• If any relationships are in alert, download RMM and license
• If Standard, consider to Alert all relationships from Toolkit directly in registry if recent sync
• If Enterprise, and not all relationships are in alert, let sync or if they are,  go next
• Run RMM to fix relationships if possible
• Export the Setup and Save to remake relationships manually in Add2Outlook
• For all relationships If not in alert, Delete all relationships, select to remove destination items
• Let Run a full sync, no errors, if so stop and disable Add2Exchange service and sql

Go to Add2Outlook full install

• Be sure to Make relationships  - be sure to select in Add2Outlook settings display to include other OpenDoor Software products so you don’t have to strip the sources as well

Have old Add2Exchange Server available

• Use  Add2Exchange Move Migration

NEXT

Have the Stop/Start Add2Exchange Service for MS updates or reboot

Turn off auto MS updates so you can reboot after any MS update

Also Stop Add2Exchange Service before MS updates on this box or Exchange Server if not the same, Reboot after Antivirus Active File Scanning Exclusions

Pivot folder optimization if have private to private rels - remove per user read and unread in ESM or Exchange System Manager
Set Limits on retention to those folders and aging to 1,1  no replication by exchange for pivot public folder

http://support.diditbetter.com/Forums/Thread.aspx?pageid=1&mid=2&ItemID=2&thread=91

Not actually a Move.  If do not Have Old Add2Exchange Server – Add2Exchange Crash, no Exchange Crash

• Need to create or get the relationships list to manual use surgeon to remove old destination copies
• Backup- Old folders Install Fresh Manually remove old destination copies in IG
• Re Set up Relationships

Have Old Add2Exchange Server –No Add2Exchange Crash, Exchange Crash

• Update Add2Exchange
• Export Setup - TIP: This can be tough since some of the data may not have been restored, best to reset up relationships so they are destination copy deleted to recopy for at least 2 syncs
• USE RMM to fix old relationships
• Make sure Add2Exchange is licensed

Log in as Add2Exchange to the replication server

Tell the users not to panic when the stuff starts to delete

Open the Add2Exchange Console

Help export setups
Put that somewhere else

If Add2Exchange Standard: 
Assuming no relationships in alert
Delete each and every relationship and select to remove destination items  so it will desync

Then close the console
Start the service
And WAIT until success audits for all folder types you have

If Add2Exchange Enterprise:

DELETE all relationships as above AND delete the Templated Relationships in RGM in the Console
In Global Options and uncheck the location for the GAL Manager Folder

Then you can do as you wish to the machine
 

When reformatting, call the machine the same name to avoid a license transfer
Also turn off UAC as it says to in the manual, do all MS Updates  and reboot prior to the install
Then Download and install the full version
And log in as the Add2Exchange Service Account and install full
Tip: During the installation, you may have to manually start the SQLA2ESQLSERVER Service and then hit retry
Remake your relationships 

Standard

Upgrade
Export Registry to landing zone – obviously off this box if it is to be reformatted
Export settings to landing Zone
Run Diags and detach Database
Save DB files to new landing zone
Format and update to latest service packs
Name the machine the same thing – be sure to remove computer from AD and let it re add it.
Do Simple Full install
When console opens
Close Console, do not start service
Standard
                Import Registry
                In diags, Detach db files and move to subdir
                Move old db files from landing zone to \Database Directory

In diags, Attach Database 

Fresh with No Relationships

• Log into old – export setup – review for homogeneity by using the find by “ExistingItems”
• Upgrade to latest Standard
• Delete all relationships
• Select to Remove Deleted copies
• DeSync
• Note Success Audit
• Check in Inspector General
• Make sure sources have no copies
• Fresh Install on New Server

• Log into old – export setup – review for homogeneity
• Delete all relationships
• Select to Remove Deleted copies
• DeSync
• Note Success Audit
• Check for dereplication  in Inspector General
• Make sure sources have no copies

http://support.diditbetter.com/kb/a2e_178.aspx

• Stop Add2Exchange Standard Edition
• Uninstall Add2Exchange Standard
• Download  Enterprise Edition, All Other Upgrades
• Install Enterprise Upgrade
• Do Diags before opening up Console
  • Do Santize Database test in tools and if > 0 then delete bad rows
• Open Add2Exchange Enterprise Console
• Re-License by submitting a new license request :
  • Product Activation: License Key Instructions after Purchase
  • Potentially set up Templates or GAL Sync or Possibly Convert to RGM  - talk to technical support by opening a ticket

YTD

Discuss updates:  policy to download and notify, and do MS critical updates

Again, it is not necessary to convert them but you can after the upgrade if you wish to do so.

Additionally, if you have been exporting the GAL manually (or by some other process) and want to use the automatic GAL relationship function, you would remove the relationship(s) to your manually exported GAL folder, and either use a new folder or empty that folder to use the GAL function, and then make a GAL Template function to replace the manual export.  

Again, this does not have to be done immediately upon upgrading, but can be planned as Enterprise Edition will use the same kind of single relationships Standard made without issue.

In Standard edition, you can fill the GALCache with any contacts you want, including those from AD, but it is a manual process.  Enterprise edition will automatically extract the contents of the GAL, minus the ones you have excluded, and create the folder and contacts contents automatically, and you can make Template GAL relationships to go to the individual users.  You can also put small pictures attached to the GALCache contacts, and when the user calls from their numbers listed or send emails, those pictures will show up both in Outlook and on the phone.

Questions to ask:

• Licensed for product? Add2Exchange Standard, Add2Exchange Enterprise Edition?
• What happened before?
• What’s happening Next – Exchange Migration?  Determines if in place upgrade or move is in order
• What version of Exchange, UAC off?, Outlook off machine?
• What kind of relationships to convert

Begin

• Do Add2Exchange Upgrade  - may need license
• Export Setup
• Review to make sure all homogenous by using the find by “Existing Items”
• Warn USERS of the change-
• Any in Alert?  Do RMM OR FORCE DELETE (CAREFUL)
• Delete all RGM Relationships which would be converted
• Select to remove destination items
• Licensed?
• Close Console and turn on Add2Exchange Service
• Let DeSync
• Make new distribution lists – naming convention – if unique to DIB, Limit email in ESM
• Add members
• Look for Success Audits
• After desync, check with IG for copies in source and dereplication
• Make templates
• Attach dist list
• Console: Turn on Relman Services in Services Utility
• Start Resync
• Look for Success Audits
• Set favorite to how Add2ExchangeWorks

Clean Start without RMM Tools: How Do I Migrate Exchange Without Migrating Add2Exchange Relationships and Replicated Data

With replicated Data and RMM Tools

• Do prerequisites on the new Exchange server
  • Run Preinstaller and Local Admin
• Open Registry Set Server to new CAS Exchange (only after all accounts and pfs are migrated)
• Save and Remove Old License Address
• Open Console – if login, and get Console, close Console and Do not start service
  • If not, try login Test to get actual CAS Server Name – look to his outlook profile if not known
• Open RMM
• License RMM
• Fix relationships until done, wait for apply notice – close RMM, make sure closed in TM
• Run Add2Exchange Service, view TM for proper operation and view event log for success 

Moving the Add2Exchange Installation

Download Full – product
Download RMM

Update to latest  version  of product -if cross grade to Enterprise and then move, do the upgrade on the original box.

(If Standard, note if this box is 32 or 64 to require Registry Conversion from Diags later before importing)

Export Setup and put in zlibrary, under new “Migration” directory save as “before migration and your initials”

Do Standard Diags- search for SMF - remove
If yes there were greater than 0 rows, open Add2Exchange Console, look for any relationships with destination item to delete source or mark deleted or do nothing, if there are any relationships there with this setting, Export relationships to zlibrary, do SMF cleanup before and then change all relationships to recopy, and then run full sync, then change back after full sync to avoid deleting good items.

Note all Relationships OK? If not, delete alerted or Run RMM

If moving with Tool and Automatic -  License Toolbox and follow Migration instructions in the Manual

If without tool and Manual

Be sure you have the recent Export Setup

Make new “landing zone” migration Folder in zlibrary Migration [Date] [Initials] Directory in zlibrary Old export settings
Detach DB – save copy to landing zone in zlibrary
If Add2Exchange Standard: Export registry If Add2Exchange Standard
                Clean up zlibrary of old installs
                Move zlibrary directory to Landing  Zone
On New Box,  Do Full Simple install for  the product – eventually Console will open
Close Console

If Standard and 64 bit from 32 bit, open Add2Exchange Diags

Convert from 32 to 64 via file
Import New File into Registry

Edit Registry: Server, DB, License, Path (C:\Program Files x86)
Run Diagnostics

Detach virgin DB

Make “Virgin” Directory under \Database
Move virgin DB to virgin DIR
Copy OLD DB from LZ to \Database Dir
Attach DB
Open Add2Exchange Console
Do Licensing
If Standard or Enterprise Edition and you did not do SMF before, do it now

If done before, skip if not Do Standard Diags- search for SMF

If yes, open Console, export Setup and search for Existing , inspect for each relationship for destination item, delete to yes or do nothing, or mark Deleted and if so Export relationships to zlibrary, call it  “SMF before Surgery [Initials]  and then change all relationships to recopy, and then run full sync, then change back after.

If Enterprise Edition – Check and Change template
Note all Relationships OK?  If not, delete deleted alerted and Empty Trash or we will Run RMM to fix

Standard: Open Diags and alert all relationships directly in Registry

If Enterprise Edition we will have to let it sync to put relationships in alert

Open Console
Attach License keys
 

IF Standard Run RMM
Then Turn on Add2Exchange Services
Open Diditbetter MMC and go to event Viewer
Make link to How it works as favorite and explain
Complete Sync – on success if SMF, be sure to change all relationships back to original format
On success  - Open Console
License if not done already

NEXT

Have the Stop/Start conversation –

Turn off auto MS updates,
stop before MS updates on this box or Exchange, Reboot after
Antivirus Active File Scanning Exclusions

• If private to private relationships, in ESM, select Pivot folder for optimization
  • take off per user read and unread
• Set Limits on Retention and Aging to 1,1 no Replication by Exchange for Pivot

If clean, Update to latest Version
Open Add2Exchange Console and Export Setup, save
Delete all relationships and select to remove destination items
Let run a full sync and then verify dereplication in Surgeon General for source and sample destinations
If all ok, disable Add2Exchange Service, Stop SQL Service
Take Export Setup to the new machine to have a record of relationships to rebuild

Go to Simple Install Add2Exchange Full  Version 

Questions to ask

What Happened recently?

• What product?  Add2Exchange Standard, Add2Exchange Enterprise Edition, Add2Outlook, any other sync product (blank destination folders)?
• Pending Reboot?  MSUpdates to do?
• What happened before?  First time, Add2Exchange Standard, Add2Exchange Enterprise Edition, Add2Outlook, any other sync product (blank destination folders)?
• Did it ever replicate?
• Where is it installed?  On Exchange Server?  What version of Exchange? UAC off? Outlook off machine?
• What kind of relationships?
• What’s happening in the future – Exchange Migration, moving Add2Exchange hosting?

Service Not started
Stuck A2ESP
Pending Reboot or MS Update

Tools to see

• TManager – see if replicating, multiple in memory and if stop service stops sync
• Event viewer
• Open Console, does it open?
• Check Console Version – check for Software Assurance date to see if upgrade if free
• Do Diags  - All diags – to see if account properties have changed
• Diags – Do SMF  - delete bad destination rows
• Is there a Pending reboot MS Updates – See where they are win MS updates – don’t do them
  • We guarantee that this version will work with the current MS criticals in effect at the time
• Preinstaller?
• License?
• Exchange Mgmt Guide
• Upgrade
• Move MMPS
• Antivirus Exclude

Console

• Do Relationship Therapy
  • Export Setup
    • Find “Existing”
    • Explain
    • Source Net?
    • Event
    • Conversation: Add2Exchange Won’t Copy a Copy - Use Inspector General to show and verify 

*License Transfer: Please note a license transfer is only available to licensed end users who have valid software assurance in place. If your software assurance has expired, then a current version upgrade license is required before transferring the software to a new replication machine.

NOTE: Pricing for services above is based on service being rendered during normal business hours Monday through Friday 9 am to 5 pm ET, excluding holidays; last appointment at 3 pm ET. After hours service is available up to 10 pm ET with last appointment at 8 pm ET billed at time and a half.

Both tools can be bundled with our Premier Support to ensure a smooth transition and to assist you in solving your issue quickly and efficiently.  The best value is the Server Move Tool Bundle.  Other Options

Server Move/ToolKit

For moving where Add2Exchange is installed but not for moving or migrating Exchange®

OPTION 1: ‘Doing It Myself’

You will need to license the Add2Exchange ToolKit for $250 and a $150 license transfer fee. NOTE: A license transfer is only available to licensed end users who have valid software assurance in place. If your software assurance expired, then a current version upgrade license is required before transferring the software to a new replacement replication machine.  ToolKit:  Buy +  License Transfer:  Buy Now

OPTION 2: I need Support Help and ToolKit

The Add2Exchange ToolKit license bundled with our 4 hour block of Premier Support (remote/phone support up to 4 hours) for $525 and this includes one license transfer FREE (value $150) Buy Now

OPTION 3: Support Only, I have already licensed the ToolKit
4 hours of Premier Support with one of our engineers for $399 (reg. $600). Sessions are held by appointment during our normal business hours, excluding holidays.  Any time remaining after your session can be used for future remote support requests. Includes one license transfer FREE for this project (value $50)  Buy Now

Recovery and Migration Manager (RMM) Tool

For preserving relationships while you migrate your users and/or public folders to another Exchange® server

OPTION 1: ‘Doing It Myself’

You will need to license the Add2Exchange Recovery & Migration Manager for $250 and a $150 license transfer fee. NOTE: A license transfer is only available to licensed end users who have valid software assurance in place. If your software assurance has expired, then a current version upgrade license is required before transferring the software to a new replacement server.  Recovery & Migration Manager Tool  Buy Now +  License Transfer for $150.  Buy Now

OPTION 2: I need Support Help and Recovery & Migration Manager

The Add2Exchange Recovery & Migration Manager license bundled with our 4 hour block of Premier Support for $525 (reg. 799) and this includes one license transfer FREE (value $150)  Buy Now

OPTION 3: Support Only, I have already licensed the Recovery & Migration Manager
4 hour block of Premier Support with one of our engineers for $399 (reg. $600). Sessions are held by appointment during our normal business hours, excluding holidays.  Any time remaining after this remote session can be used for future support requests. Includes one license transfer FREE for this project (value $150) Buy Now

Both -- Moving where Add2Exchange is installed & migrating Exchange or moving Mailboxes

For when you are moving Add2Exchange with phased-stepped mailbox/public folder moves or when you anticipate future mailbox/public folder moves, or for disaster recovery planning

OPTION 1: ‘Doing It Myself’

You will need to license the Add2Exchange Recovery & Migration Manager and ToolKit for $400 (reg. $500) and a $150 license transfer fee. NOTE: A license transfer is only available to licensed end users who have valid software assurance in place. If your software assurance has expired, then a current version upgrade license is required before transferring the software to a new replacement server.

Both Recovery Migration Manager and ToolKit  Buy Now+  License Transfer for $150.  Buy Now

OPTION 2: I need Support Help and Both Tools

The Add2Exchange Recovery & Migration Manager and ToolKit licenses bundled with our discounted 4 hour premier remote/phone support package for $595 (reg. $1049) and this includes one license transfer FREE (value $150) Buy Now

OPTION 3: Support Only, I have already licensed both tools
4 hour block of  Premier Support with one of our engineers for $399. Sessions are held by appointment during our normal business hours, excluding holidays.  Any time remaining after this remote session can be used for future support requests. Includes one license transfer FREE for this project (value $150) Buy Now

License Transfer

Server moves require a new license key for $150.  Buy Now

Please note a license transfer is only available to licensed end users who have valid software assurance in place. If your software assurance has expired, then a current version upgrade license is required before transferring the software to a new replacement replication machine.

Note: License transfer is already included in the Server Move products bundled with a block of Premier Support above.

Add2Exchange is licensed as the unique combination for a specific Exchange server name, a specific Exchange Organizational Unit, a specific replication service account and on a specific replication server at the time of purchase. Because the license key issued is based on the combination of the installed server name, Exchange server name, service account and Exchange Organizational Unit (License Address) and replication server derived from your license registration request, any changes to the license address requires a license transfer of $150. If you already have an Premier Support in place, you are eligible for one license transfer free.

A license transfer is needed for:

• An Exchange or Replication Server crash requiring a rebuild of the server unless you name it the same thing again
• Any changes to the Add2Exchange replication service account display name
• Moving the Add2Exchange replication service account to a new Exchange /ou can cause a license transfer, especially an Exchange Migration
• A new or renamed Exchange Server netbios name or a new cluster or CAS name
• A new or renamed “replication server” name where Add2Exchange is installed
• An Exchange Migration from an older version to a newer version or a new exchange “/o/ou” combination after a migration. Recommended add-on tool: Use Recovery and Migration Tool to facilitate
• An Add2Exchange migration where you move where Add2exchange software is installed to one of your other servers or virtual machines. Recommended add-on tool: Use the Add2Exchange ToolBox to facilitate

Rebuild Relationships

For when you have only a few relationships and have not yet moved the mailboxes

If you have already moved the mailboxes and the relationships are in alert, then you need the Recovery & Migration Manager add-on tool in order to avoid creating duplication.

• Delete all the relationships, select to remove the destination copies and let sync and then open the Add2Exchange Console to make sure they have all deleted.  Then ideally, you would use the Add2Exchange ToolBox. Then migrate and rebuild the relationships.

Clean Install

For when you are Migrating your users to another Exchange® server or moving public folders to another Exchange® server and do NOT have relationships replicated from a prior install
You will need to install the latest build from the web for your licensed edition – if your software assurance subscription is active, you are eligible for this free update . You will also need to purchase and request a license transfer for $50 per key reissued. If your software assurance period has lapsed, you will need to purchase an upgrade/crossgrade license prior to installing the update.  Please note a license transfer is only available to licensed end users who have valid software assurance in place. If your software assurance has expired, then a current version upgrade license is required before transferring the software to a new replacement server.

Preferred Method and Tips for Migrating/Moves and Tools: 

• It is almost always best to keep replicated relationships in place, and use the tools since all replicated history and information from relationships you deleted prior will be gone from the new installation.
• If you are migrating, and doing the entire migration at one time, you can have our Service department take care of the service without having to license the tools.
• If you are doing a stepped migration with some mailbox and public folders at one time, then you should license the tools.
• If you are migrating a few mailboxes at a time, you should have us to handle the initial migration and you should license the Migration Tool which you can run after you move mailboxes, the relationships become “alerted”, and you need to migrate the relationships to the new server when you want to without our assistance.

I have Premier Support in place. Help me, please.

To have us assist when purchasing the support service:

• Please schedule a remote session at least two to three business days in advance before the time you would like this migation/move service.  Call in and speak with the assigned engineer to make them aware of your current status and configuration.  We will migrate Add2Exchange to the new server and run the Migration Tool to migrate the relationships.  If you are doing a partial migration, you will need to purchase a license for the Recovery and Migration Manager Tool.

Self Help Support Resources:

• I already Migrated Exchange without regard to migrating Add2Exchange
• I’d like to migrate Exchange without migrating Add2Exchange relationships and replicated data. I’d like a clean start on the new server.

• License and use the Add2Exchange Recovery & Migration Manager after the movement of the mailboxes and/or public folders. If you are doing a stepped migration, you will need to use this tool repeatedly.  TIP:  Move the Add2Exchange service account as part of the last migrations to ensure a smooth transition.
• You will then need to change the new server name as per this article.

• If you are migrating from Exchange Server 2000 or 2003 to 2007 or 2010, please be sure to give the new permissions to the service account next.  Follow these instructions.
• You will then have to run the Recovery & Migration Manager to repoint the relationships to the new server. Buy Now

*License Transfer: Please note a license transfer is only available to licensed end users who have valid software assurance in place. If your software assurance has expired, then a current version upgrade license is required before transferring the software to a new replacement server.

Do you have the Add2Outlook REG file or list of relationships from the old Add2Outlook?
Download and Install the Full Add2Exchange Standard or Enterprise

May not need to License Toolbox
Backup Source Folders
Use Inspector/Surgeon General - Toolkit can be unlicensed for the next procedure
Add2Outlook = T  delete  Items for each destination folder
Remove Add2Outlook Named properties off of Source folders

• What product? Add2Exchange Standard, Add2Exchange Enterprise Edition, Add2Outlook, any other sync product (blank destination folders?)
• What happened before? Is this a First time install of Add2Exchange Standard, or Add2Exchange Enterprise Edition, or Add2Outlook, or any other sync product?
• Have we replicated before with any of the products listed above?
• What’s happening Next – Exchange Migration
• What kind of relationships are we setting up
• Where is it being installed?  On Exchange Server? What version of Exchange, UAC off?, Outlook off machine
• Discuss ideal place to install Add2Exchange  - either VM or BES or Exchange, in that order

Where to Install?

You could install Add2Exchange on the Exchange Server, and often people do.  If you have another server, or virtual servers, the time to consider them is now.  Yes it can be moved, but it is kind of a pain to move it and to be smoothest, you will need some tools to do it better.  It is advisable to do a virtual machine or utility server install if possible with a fully patched 2008 Release 2: with no Outlook installed, not on a Terminal Server, or Citrix Server, and the utility server could be an aging Blackberry Server.

It is ideal to be installed on it's own server, with at least 4 gb memory single processor and 40 gigs of hard drive space with UAC (User Access or Account Control) off and rebooted.  This way we can manipulate the machine and optimize performance without regard to other constraints.  Again, normal installation is easy, you should have the Add2Exchange Service account as part of the local administrators of the machine you are installing it on and all the Exchange server(s) replicating to and from - even if it is Exchange replication.  The Preinstaller part of the install makes the user account if necessary and adds the account you specify as part of the local administrators group of the machine you are on automatically and the proper groups and memberships. 

Refer to the installation guide for the list of prerequisites.

Procedure:

Download Full Edition into a zLibrary dir/A2ESEtups and make shortcut on desktop to A2ESEtups, and potentially change auto download location for Service account.

Shortcuts to Best Tips for updating and understanding: http://support.diditbetter.com/kb/a2e_219.aspx

Log in to Exchange Server as Domain Admin with Exchange Org admin or Org Admin credentials

If 2007 or 2010 - Run 2007-2010 Preinstaller

If 2003 – Make account manually, memberships, Permissions to Public, Admin to servers

If prompted and UAC on, turn off and Reboot before continuing install

If Add2Exchange Enterprise Edition – make Dist lists – discuss naming – z_GALSYNC or Z_PUBCALSYNC, etc, add members, limit mail

If not on Exchange 2003 Exchange server and is installed on this box, Install Exchange MapiCDO

Then depending, reboot, Log off and back on as New Service Account to replication server
Or Log Off or MSTSC LocalHost  - Log on as Service Account
Install Add2Exchange FULL – Install SQL – if 2008 r2 manually Start SQL Service A2ESQLService and then retry
Open Console
Do License Request
Relationship Therapy  - are the destination folders empty, to avoid duplication?
Don’t have to invite anymore if calendars, has public folder contacts been manually copied?
Make Relationships
  If Enterprise Edition and using RGM, make Dist lists in Exchange, limit the email to
  Make Templates

• For those with Private to Private relationships: Do Pivot folder optimization if have private to private
  • Take off per user read and unread

Set Limits on retention and aging to 1,1  no replication by exchange for pivot

Set and Explain Service Utility 
Set and Explain Global Options – Recurring Calendars

NEXT
Make License.TXT in Zlibrary
If not already, Shortcuts to Best Tips for updating and understanding: http://support.diditbetter.com/kb/a2e_219.aspx

Have the Stop/Start conversation –
Turn off auto MS updates,
Stop before MS updates on this box or Exchange, Reboot after
Antivirus Active File Scanning Exclusions - If Antivirus Active File Scanning – Make c:\windows\mmp directory and Move MMP location  add all to Exclude List

Questions?  Visit http://support.diditbetter.com/support-request.aspx to fill out a ticket for support.

• On Add2Outlook machine, Export setup – Save to new landing zone
• If they did not already migrate, and relationships are not in Alert and just a few relationships: you could delete relationships and select to dereplicate
•  
•  
• Do this NEXT STEP AFTER you have set up the Add2Exchange System and made the relationships to minimize downtime.  See the section
  • GET Add2Exchange Ready: 
    Or if already migrated, use or use Add2Outlook Toolkit for manual dereplication after the fact and avoid duplication
  •  
• If relationships are in Alert – use Add2Outlook Recovery to edit and fix them first
• Delete all Add2Outlook relationships individually, specifying to remove destination copies.
  TIP:  If you set Add2Outlook in Debug mode, a new option will appear at the top in the Addins of Outlook.
  To "start over" or remove all copies, select Add2Outlook Reset and start the Sync.  The time should and will remain off.
  • Or if the older system is not available or the mailboxes have migrated already, on the new system you will use the A2O Toolkit to remove all the A2O copies
    • Add2Outlook Copy = T  delete  Items for each destination folder
    • Add2Outlook Original = T remove Named Property

Before you go off of old Add2Outlook system, In Outlook, uninstall Add2Outlook or uncheck the Add2Outlook Add in in File/Options/Add ins.  uncheck Add2Outlook.

GET Add2Exchange Ready: 
On new Replication Server, Do Simple Full Add2Exchange Install: Add2Exchange Enterprise/365 PDF

• Depending on what you did prior may need to Clean up, you may need to use the Add2Exchange Toolkit to clean up folders if migrated or not able to use A2O to clean up the A2O copies
  • Before setting up relationships, use the Add2Outlook Toolkit to Reset Products and remove the copies made by A2O by manual dereplication if necessary
    • Add2Outlook Copy = T  delete  Items for each destination folder
    • Add2Outlook Original = T remove Named Property

Then make your Add2Exchange template or single relationships.

To make sure the relationships are consistent, in the A2E Console/Utility, set Relman to once a day (so it makes the relationships) and everything else to OFF.  Close the Console and start the service.  After a few success audits, and one Relman Success, you can open the Console and inspect the relationships.  If they are to your satisfaction, you can then dereplicate the Add2Outlook.  Wait until it is completely finished with no errors before you start up Add2Exchange.  To verify dereplication, on the A2O machine, look to the Event Log for Open Door Software and notice errors.  To see if the relationships were deleted successfully, open Outlook and select the Add ins, Add2Outlook and inspect the relationships. There should be none in alert and all noted in the Relationships Deleted Folder in the Add in.  If so, you can disable the Add2Outlook add in and close Outlook. 

On the Add2Exchange Box, in the Registry, in the key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\OpenDoor Software®\Add2Exchange\Profile 1 
   set the key to Include ODS Copy = 1 Include ODS = 1

NEXT :
License Add2Exchange
Have the Stop/Start conversation –
Do but then Turn off the auto MS updates, set to download and notify, then stop before MS updates on this box or Exchange
Reboot after

If any Private to Private relationships, set Pivot folder optimization
– take off per user read and unread
Set Limits on retention and aging to 30,30 

Thanks

when you start the sql 2005 A2ESQLSERVER instance, are you starting it with the Add2Exchange Service Account?

Did you turn off User Account Control and reboot prior to the install?

If not, then turn it off (run Regedit. Search for EnableLUA in registry and set to 0) and then reboot

If SQL Fails to install, open Regedit and search for PendingFileRename in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRename) and leave the key, but blank out the contents.  Then close and try again to open the Console.

Use these procedures to uninstall both A2E and SQL200x

http://support.diditbetter.com/kb/A2E_198.aspx

then reboot

Then Install again please.

Problems encountered during creation of Database/Tables.

It then asks me to manually start the SQL A2ESQL service  which I do but still get the same error

Make sure CDO has been installed on that replication server machine from the preinstaller directory

Make sure the server you are referencing is you exchange or cas or dag group name.

Make sure for the service account you are using just the name of the service account, or email address, not in the format domain\serviceaccountname

If none of these work, please submit a request and copy exact error. http://support.diditbetter.com/support-request.aspx

Hope this helps

Please advise.

There are two ways to solve the problem:

Make the account manually in the mailbox you want manually and then

Log in to one of the Exchange Servers (with Exchange Command Shell installed) as the domain admin

run the Preinstaller

and check that the account already exists. 

OR

Log in as the domain admin

run the Preinstaller

Click on OU button and open the text file

copy the appropriate ou in the dialog from the text file to the preinstaller

Then click on the MDBs button for the Mailbox DB and open the text file

copy the appropriate MDB in the dialog from the text file to the preinstaller Mailbox DB field

Then do not check that the account already exists, but type in the password twice (if you make a mistake on the password, you have to close the Preinstaller and start over. The next time, just copy the appropriate info into the fields.  You don't have to push the button again, just copy to info to the two places)

Then run the preinstaller again by pressing OK.

That should do it.  Be sure to make the A2E service account part of local administrators of all exchange servers we are replicating to or from in order to test to make sure the exchange servers are up during sync.

That should do it.  If you need further support, please fill this out:  http://support.diditbetter.com/support-request.aspx

Hope this helps

Multiple organizational units match identity "Users". Specify a unique value.
At C:\Users\zach\Desktop\Add2Exchg\a2e-standard.9.4.170.171\preinstaller\lib\ma
ilbox.ps1:3 char:1
+  <<<< new-Mailbox -alias $account -name $account -database $mdb -organization
alunit $ou -UserPrincipalName "$account@$domain" -Password $pw
    + CategoryInfo          : NotSpecified: (:) [], ManagementObjectAmbiguousE
   xception
    + FullyQualifiedErrorId : D726360

Get-User : The operation couldn't be performed because object 'zAdd2Exchange' c
ouldn't be found on 'SERVER2012.rsmcpas.local'.
At C:\Users\zach\Desktop\Add2Exchg\a2e-standard.9.4.170.171\preinstaller\lib\gr
oups.ps1:32 char:25
+ $user       =   Get-User <<<<  $account
    + CategoryInfo          : NotSpecified: (:) [Get-User], ManagementObjectNo
   tFoundException
    + FullyQualifiedErrorId : C31F296F,Microsoft.Exchange.Management.Recipient
   Tasks.GetUser

Exception calling "add" with "1" argument(s): "Exception from HRESULT: 0x800050
00"
At C:\Users\zach\Desktop\Add2Exchg\a2e-standard.9.4.170.171\preinstaller\lib\gr
oups.ps1:7 char:17
+     $adGroup.add <<<< ("LDAP://" + $userDn)
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : CatchFromBaseAdapterMethodInvokeTI

Exception calling "add" with "1" argument(s): "Exception from HRESULT: 0x800050
00"
At C:\Users\zach\Desktop\Add2Exchg\a2e-standard.9.4.170.171\preinstaller\lib\gr
oups.ps1:7 char:17
+     $adGroup.add <<<< ("LDAP://" + $userDn)
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : CatchFromBaseAdapterMethodInvokeTI

Exception calling "add" with "1" argument(s): "Exception from HRESULT: 0x800050
00"
At C:\Users\zach\Desktop\Add2Exchg\a2e-standard.9.4.170.171\preinstaller\lib\gr
oups.ps1:7 char:17
+     $adGroup.add <<<< ("LDAP://" + $userDn)
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : CatchFromBaseAdapterMethodInvokeTI

Exception calling "add" with "1" argument(s): "A member could not be added to o
r removed from the local group because the member does not exist.
"
At C:\Users\zach\Desktop\Add2Exchg\a2e-standard.9.4.170.171\preinstaller\lib\gr
oups.ps1:39 char:11
+ $admin.add <<<< ("WinNT://$domain/$account,user")
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : CatchFromBaseAdapterMethodInvokeTI

Add-ADPermission : User or group "zAdd2Exchange" wasn't found. Please make sure
you've typed it correctly.
At C:\Users\zach\Desktop\Add2Exchg\a2e-standard.9.4.170.171\preinstaller\lib\ri
ghts.ps1:3 char:39
+ Get-MailboxDatabase | Add-ADPermission <<<<  -User $account -AccessRights Ext
endedRight -ExtendedRights Send-As, Receive-As, ms-Exch-Store-Admin
    + CategoryInfo          : InvalidData: (:) [Add-ADPermission], ManagementO
   bjectNotFoundException
    + FullyQualifiedErrorId : 5571496B,Microsoft.Exchange.Management.Recipient
   Tasks.AddADPermission

Get-PublicFolderClientPermission : Public folder user "zAdd2Exchange" doesn't e
xist. A valid public folder user should be a mail-enabled user, mailbox, or dis
tribution group.
At C:\Program Files\Microsoft\Exchange Server\V14\Scripts\AddUsersToPFRecursive
.ps1:81 char:48
+     $permission = get-PublicFolderClientPermission <<<<  -identity $_ -user $
User -erroraction Stop -server $OriginatingServer
    + CategoryInfo          : NotSpecified: (0:Int32) [Get-PublicFolderClientP
   ermission], ManagementObjectNotFoundException
    + FullyQualifiedErrorId : 6D7143F9,Microsoft.Exchange.Management.MapiTasks
   .GetPublicFolderClientPermission

New-ThrottlingPolicy : Active Directory operation failed on SERVER2012.rsmcpas.
local. The object 'CN=A2EPolicy,CN=Global Settings,CN=First Organization,CN=Mic
rosoft Exchange,CN=Services,CN=Configuration,DC=rsmcpas,DC=local' already exist
s.
At C:\Users\zach\Desktop\Add2Exchg\a2e-standard.9.4.170.171\preinstaller\lib\th
rottlingSp1.ps1:2 char:21
+ New-ThrottlingPolicy <<<<  A2EPolicy
    + CategoryInfo          : NotSpecified: (0:Int32) [New-ThrottlingPolicy], 
   ADObjectAlreadyExistsException
    + FullyQualifiedErrorId : 2C03B4A9,Microsoft.Exchange.Management.SystemCon
   figurationTasks.NewThrottlingPolicy

Set-Mailbox : The operation couldn't be performed because object 'zAdd2Exchange
' couldn't be found on 'SERVER2012.rsmcpas.local'.
At C:\Users\zach\Desktop\Add2Exchg\a2e-standard.9.4.170.171\preinstaller\lib\th
rottlingSp1.ps1:4 char:12
+ Set-Mailbox <<<<  $account -ThrottlingPolicy A2EPolicy
    + CategoryInfo          : NotSpecified: (0:Int32) [Set-Mailbox], Managemen
   tObjectNotFoundException
    + FullyQualifiedErrorId : 6323CF49,Microsoft.Exchange.Management.Recipient
   Tasks.SetMailbox

Generally good advice:

http://support.diditbetter.com/kb/a2e_219.aspx

Migrations:

http://support.diditbetter.com/Forums/Thread.aspx?pageid=1&mid=2&ItemID=2&thread=91

Mixed Mode:

http://support.diditbetter.com/Forums/Thread.aspx?pageid=1&mid=2&ItemID=1&thread=64

Similar for 2007 and 2010 as for 2003 and 2007 or 2010

Basically, the overview is that your relationships will go into alert status after you migrate mailboxes and you fix them with the Recovery and Migration Management Tool  Buy Now

Stop the Add2Exchange Service, migrate the users all at once or in a stepped fashion, Start Add2Exchange Service, those rels will go into alert and then you them with the Recovery and Migration tool.  The tool is half off on support.

Thanks!

Sorry if its been answered in a previous post!

MattJ

Summary

If you are preparing to migrate Add2Exchange to a new location on the same server, here are the steps to manually make this process easier.

*Note*

These instructions refer to the Add2Exchange service account as “zAdd2Exchange” since that is the recommended account name. This makes it possible to cut and paste many examples. If your service account name differs, substitute it instead.

Instructions

*These procedures require the A2EDiags tools, included in the latest versions of the Add2Exchange installation package. It may also be downloaded from:

FTP Site Link for A2Diags tools:  ftp://ftp.diditbetter.com/a2ediag

1. Log on to the computer using the zAdd2exchange service account
2. Stop the Add2Exchange Service
3. The A2EDiags are included in the zipped file of the new downloads.  You can download and extract the A2EDiags Tools from the FTP site link provided
4. Run A2EDiags.bat from the extracted or installed directory
5. Detach the Add2Exchange database with the Detach Database option
6. Uninstall Add2Exchange
7. Reinstall and select the new drive
8. Manually move the a2e.mdb file from the existing local drive <C :\> to the new drive location

Example: < D:\Program Files\Open Door Software\Add2Exchange\Database>

9. Attach the database using the A2EDiags Tool option Attach Database files
10. Open the Add2Exchange Console
12. Check to see for proper operation. Close the Add2Exchange Console and Start the Add2Exchange Service
13. Monitor the Add2Exchange Event log for Success Audits

Next problem: after the installation I start the Add2Exchange console which runs the SQL-Server setup. It finishes without errors, but when starting the service, an error appears telling me the Add2Exchange service can't be started.

In the even log I find the error 4040 from Add2Exchange with these detailed information:

Add2Exchange ConsoleError encountered attempting to modify the Username and Account settings for the A2ESQLSERVER DBMS.  Please open the Services applet and start the A2ESQLServer as the Add2Exchange Service Account and password before continuing and restart the Add2Exchnage service.

For further information/support, please visit:
http://support.diditbetter.com/SearchResults.aspx?q=Add2Exchange ConsoleError encountered attempting modify Username Account settings for A2ESQLSERVER DBMS.

But both, the SQL service and the Add2Exchange service are started with the zAdd2Exchange service account, so what's the problem?

Thanks in advance for your help.

Regards,

Thomas

http://support.microsoft.com/kb/329291/en-us

Regards,

Tom

Make sure User Access Control is off and rebooted

Make sure the A2EService account is part of local administrators

Make sure you are logged in as the service account when you install

If you are running on Exchange 2007 or 2010, make sure you run the Preinstaller included using these instructions:

http://support.diditbetter.com/kb/A2E_214.aspx

Does any of this work for you?  Where are you exactly during the install when it fails?

the following error appears upon installation on W2k8 R2 (error is manually translated into English):

.NET error: The application tried a procedure that isn't allowed by the security policy.

...

The requested registry access is forbidden.

Additional details to this error are:

Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.

************** Ausnahmetext **************
System.Security.SecurityException: Der angeforderte Registrierungszugriff ist unzulässig.
   bei System.ThrowHelper.ThrowSecurityException(ExceptionResource resource)
   bei Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable)
   bei Microsoft.Win32.RegistryKey.OpenSubKey(String name)
   bei Add2Exchange_Setup_Initialize.Add2Exchange_Setup_Initialize.Setup_Initialize()
   bei Add2Exchange_Setup_Initialize.Add2Exchange_Machine_List.btnAccept_Click(Object sender, EventArgs e)
   bei System.Windows.Forms.Control.OnClick(EventArgs e)
   bei System.Windows.Forms.Button.OnClick(EventArgs e)
   bei System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   bei System.Windows.Forms.Control.WndProc(Message& m)
   bei System.Windows.Forms.ButtonBase.WndProc(Message& m)
   bei System.Windows.Forms.Button.WndProc(Message& m)
   bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Die Zone der Assembly, bei der ein Fehler aufgetreten ist:
MyComputer

************** Geladene Assemblys **************
mscorlib
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5420 (Win7SP1.050727-5400).
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll.
----------------------------------------
Add2Exchange Setup Initialize
    Assembly-Version: 13.9.923.333.
    Win32-Version: 13.9.923.333.
    CodeBase: file:///C:/Program%20Files%20(x86)/OpenDoor%20Software%AE/Add2Exchange/Setup%20Initialize/Add2Exchange%20Setup%20Initialize.exe.
----------------------------------------
System.Windows.Forms
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5420 (Win7SP1.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll.
----------------------------------------
System
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5420 (Win7SP1.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll.
----------------------------------------
System.Drawing
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5420 (Win7SP1.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll.
----------------------------------------
Microsoft.VisualBasic
    Assembly-Version: 8.0.0.0.
    Win32-Version: 8.0.50727.5420 (Win7SP1.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll.
----------------------------------------
mscorlib.resources
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5420 (Win7SP1.050727-5400).
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll.
----------------------------------------
System.Windows.Forms.resources
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.4927 (NetFXspW7.050727-4900).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.
----------------------------------------

************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.

Zum Beispiel:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.

Please advise.

Thanks in advance.

Tom

If you have not migrated mailboxes or public folders yet, and you are planning this migration beforehand, then Congratulations!

Your company may be on Premier Support and have all the tools necessary already. Start this process by requesting support.

Sometimes it happens that IT administrators have not taken into account Add2Exchange replication when migrating Exchange. If this is your case, there are several options, each designed to fix the system as quickly as possible.

If the migration has already occurred, it is likely you will need some tools and support to assist and relicense the application. Since you may not have dereplicated data before you migrated the mailboxes, the mailboxes may have replicated data in them and remaking the relationships will cause duplication, so it may be necessary to remove the data (from default folders) or sync to a new folder and remove the data. See all option scenarios below.

• If you don't have or want the tools licensed, or you can't do remote support and/or do not have Premier Support in place, the "almost free way" is to remove all Add2Exchange relationships and select to remove the destination copies, and then run a complete sync before the migration. This will dereplicate everything and you can remake the relationships on the (old or) new server.  However, many businesses do not like this option because the users do not have access to even the "stale" data that was replicated before the migration.  If you do not want to remove and rebuild the relationships or have already migrated, then the following options below are available to proceed. 
• If you have migrated mailboxes and or public folders already, when you sync the relationships will naturally go into alert because they are in a different data store and environment. Do the Preinstaller Permissions on the new server and do not delete those alerted relationships. It is best practices to fix them with the Recovery tool and re-license. If you are doing a stepped migration, leave the Add2Exchange Service account on the older server until all the other users with relationships are moved. 

The best value and shortest resolution in any situation you are in now or will be in the future, is to consider the Premier Support and the essential Tools Bundle  - Option 1 below.  As a benefit of the Premier Support program, the savings start immediately with a free license transfer and over 60% discount on advanced Essential tools to manage your installation now and in the future. (More info on Tool Uses: ToolKit, Add2Exchange Recovery & Migration Manager)

We offer a bundle which includes both discounted tools – ToolKit and the Recovery & Migration Manager AND a discounted 4 hour block of Premier Support for up to 4 hours of remote/phone support services.  Buy Online

If you can handle the migration yourself, the Recovery & Migration Manager tool is $250 and available for purchase on our online store.

Since we are experts at what we do, most administrators let us handle the migrations and support by enrolling in a Premier Support Plan to allow our engineers to remote in to assist for smooth transitions. Migrations take about an hour and a half or so, depending on the kind of migration because the ideal process depends on your unique situation. 

One of our engineers will assess your unique situation. If requested, we will completely re-certify your synchronization system or changing systems, provide help with your Exchange/Add2Exchange migration and/or move the replication server so as to minimally disrupt your end users.

OPTION 1 - BEST VALUE
'Help Me Please' Migration/Move with 4 hour Premier Support Bundle and Both Recovery and ToolKit Tools

We do it all for you, license both tools and train you. This option gets the "Full Monty" of Support and the recommended add-on tools at a discount and a free license transfer to ensure no duplication and smooth conversion.  Use this option for all migration options, either scheduled before and during or after the fact.

Our team will survey what you have and recommend and implement the best solution for you. With the system fixed and updated, re-certified, and licensed, there is enough time for personnel training and some "relationship therapy", where we discuss your relationships and your desired business goal to the data relationships. With this option there is often enough support time available on account for future support to avoid these kinds of emergencies and make things run smoother for you in the future. Premier Support is time-based, rather than incident based; once the time is used up and if additional support is needed, you would buy another block of hours.

This bundle includes:

• 4 hour block of Premier Support, up to 4 hours of remote/phone support 
  We would use at least an hour and schedule the appointments, hold the remote session next business day or the first available during our normal business hours. Any remaining time could be used for future remote support services as needed.
• Discounted Recovery & Migration Manager add-on tool 
• Discounted ToolKit add-on tool license

$595 (reg. $1049-- bundle savings $454) Buy Now 

OPTION 2 

The relatively FREE option after migration: Only use this option if syncing to non default folders and only if the folder is not a source of another relationship(s). You will only need a license transfer.  Be careful, this is a dangerous option which is hard to undo if it does not truly apply in your situation and if not done correctly.  This option is only ideal for public to private, public to public or private to public  - one way to non default mailbox folders or public folders with no source items.  In this option you would be deleting folders and recreating the destination folders and requires some manual cleanup of existing destination folders.

If you have ONLY a one way relationship and not two way and are replicating to a non-default folder, and you can just delete (backup and move) the folder without adverse effects, depending on the relationship web you have created, you may be able to just delete the destination folders and simply reinstall fresh on a new A2E Server and reset up the relationships.  

If you are not moving where Add2Exchange is installed, in this unique situation, follow this procedure to uninstall and then reinstall the full version. Then you would remake the folders and relationships.  

IMPORTANT: If you have public to private AND private to public relationship(s) or a full mesh (folder participation), this option will not work because you will likely be deleting source data. Option 2 should not be used in this situation or if you have the relationships going to the default folders where originals reside.
 

OPTION 3
'Doing It Myself  with a ToolKit Startover or by using the Surgeon General' 

If you have already migrated mailboxes with data from the older install of Add2Exchange
and you do not have access to the old Add2Exchange Server, and there are just a few relationships, you can clean up the data from the old replication server and use the Surgeon General to remove Copies from the destination folders.  Requires license transfer.  We suggest backing up the source folders prior to the Startover option.

The startover process is simple.  Do the prerequisites as outlined in the manual.  Install the full version on the new server, make the same relationships, license Add2Exchange and the Add2Exchange Toolbox and run the "Startover" from the ToolKit. This will automatically de-replicate all the Add2Exchange copied data and then start re-replicating again with no duplication. Unfortunately, the startover may remove source data users accidentally put in copied folders.  Backup prior to running a startover.

Alternatively, if you have just a few relationships, you can also use the ToolKit and use the Surgeon General to manually select to remove the destination copied items. This is a more surgical approach and eliminates the possibility of removing source items. This process manually de-replicates just the Add2Exchange copied data and then you can start re-replicating again with no duplication.  License Transfer: $150: NOTE: A license transfer is only available to licensed end users who have valid software assurance in place. If your software assurance has expired, then a current version upgrade license is required before transferring the software to a new replacement server.

• ToolKit license to run a "startover" after relationships are re-made on the new sync server or when using Surgeon General to manually clean up
• Both options will remove any possibility of duplicates caused by non-migration of your old replication server. $250 and license transfer. 
  CALL to order this option 

OPTION 4
'Doing It Myself with the Recovery & Migration Manager Tool' 

Use this option if the old replication server is still avail.able, and you may or may not be moving where Add2Exchange resides. 

Use this option if you have many relationships or do not know the relationships, or cannot de-replicate the old data and cannot have the users without it for any length of time, and have no duplication.  If you have duplication already, you may also need the ToolKit to assist.  See option 6 below.

• License Transfer: $150 Buy Online
  NOTE: A license transfer is only available to licensed end users who have valid software assurance in place. If your software assurance has expired, then a current version upgrade license is required before transferring the software to a new replacement server. There is "startover" needed.  If you are not moving Add2Exchange and you did an Exchange stepped or swing migration, there are links in this Migration section of the site to assist in pointing to the new Exchange Server. Then you just run the Recovery & Migration Manager (RMM) tool to reconnect the older relationships. 
   
• The Recovery & Migration Manager add-on tool license is $250 + license transfer $150
  CALL to order this option. 

The 'Do It Myself' instructions are posted HERE  and HERE.
 

OPTION 5
'Help Me Please with Premier Support and the ToolKit'

Use this option if the older replication server is not available and you have just a few relationships.  Option 6 is the best deal below and will be able to solve any situation.

This option is used to let us help you manually get rid of any copies in any of the destination folders.  You would get a Premier Support plan, and the ToolKit and use the Inspector/Surgeon General tool and a free license transfer to ensure no duplication. The only difference between this option and the Full Monty, below, is you are not getting the Recovery and Migration Manager tool license to enable you to fix alerted relationships in the future, should that occur.

Our team will survey what you have and recommend and implement the best solution for you.  With this option, we would load the new installation of Add2Exchange and run the necessary Prerequisites, re-certify your system, re-license it at no additional charge, and spend the time to show you how to work the Surgeon General correctly in your situation to remove destination copies for all users, or to make them originals again.  (We suggest backing up the source folders prior to the service please).  We would then set up the desired relationships and provide some "relationship therapy", where we discuss your relationships and your desired business goal and make sure the information relationships are correct. Also, even though there is training and optimization, there will be enough support time left after the service for future support to avoid these kinds of emergencies and make things run smoother for you in the future.

• 4 hour block of Premier Support $399. We would use at least an hour and hold the remote session next business day or first available appointment during our normal business hours; any remaining time could be used for future remote support services as needed.
• Discounted ToolKit add on tool license for $125 (reg. $250)

The ToolKit add-on tool license with 4 hour block of Premier Support for only $525.  Buy Now

Tip: Get both tools in Best Option 1 for only $51 more.  Save time now and be quick later.

OPTION 6
'Help Me Please with Premier Support and the Recovery & Migration Manager'

This option gets the Premier Support, the Recovery and Migration Tool to fix any alerted relationships (such as after a migration) and thus avoid duplication from deleting alerted rels and recreating and have time provide some training to enable your technical team to do the stepped migration. A free license transfer is included to ensure a smooth conversion.

Use this option if the old replication server is available and either you did an Exchange migration and may or may not be moving where Add2Exchange resides.

Our team will survey what you have and recommend and implement the best solution for you. We license the Recovery and Migration Tool to fix any alerted relationships. We will update, re-certify, and re-license, and there will be enough time for personnel training and some "relationship therapy", where we discuss your relationships and your desired business goal. Also, even though there is training and optimization, there will be enough support time available for future support to avoid these kinds of emergencies and make things run smoother for you in the future. You can get the Premier Support with the add-on tool license or just have us fix it without them.

• 4 hour block of Premier Support for $399. We would use at least an hour and hold the remote session next business day or first available appointment during our normal business hours; any remaining time could be used for future remote support services as needed.
• Discounted Recovery & Migration Manager add on tool for $125 (reg. $250) for a 50% savings on this add on tool when purchased with our premium support package.

The Recovery & Migration Manager add-on tool license with 4 hour Premier Support for only $525. Buy Now

 Tip:  Get both tools in Best Option 1 for only $71 more.  Save time now and be nimble later.

If you have additional questions on any of the above options, especially the FREE option above, begin the process and submit your request.

To move forward with one of the options, call to place your order and to plan your preferred level of support for your unique situation.

We have combined both Standard and Enterprise manuals and updated it to make it easier for 2007 and 2010 installations.  Again, sorry for the delay.  The product are moving so fast the doc team waits too long to let the dust settle.

Thanks for your reply.

This is a fresh installation but we managed to find the culprit.

The SQL instance was stopped and was causing the whole delay(over 2 hours).We noticed this was stopped early on but since the other process was saying optimizing the database structure we though that  was the reason.
Anyhow once the  instance  is up it took only a couple of minutes for the whole installation to get completed.

If any  Add2Exchange staff are viewing this thread we would like to request a installation guide update because the current one needs a serious make-over .Most of the post installation  sequences are missing from it so it made our day difficult and i m sure many others will agree with us.

Regards
Inbay

this is normally a fast process on a new install

if it does not come back in an hour, please cancel the process - from TM if you have to

then, close the A2e Console and reopen it

keep me posted on success of this please

The database structure optimization process is now running its 5th pass. Do you know how many passes that it normally runs because it has now taken over an hour to run these 5 passes.

Regards

Inbay

Everything should still work fine.  Let us know if you encounter any errors.

We did a fresh A2E installation on a client server but during the SQL setup got the following error message
http://imageshack.us/photo/my-images/8/a2e.png/

But even with this the setup got completed. Please do let us know if we are to any changes to the installation or if we can safely ignore this error.

In addition we are getting the following. This  is going on for about 45 minutes now but nothing is mentioned on the installation guide of such a process

http://imageshack.us/photo/my-images/135/a2e2.png/

Is this normal behavior for a fresh installation?

Thanks

2. Also when I want to create a new relationship with a mailbox on EXBE07-Y I have this error:

 An error occurred while attempting to logon to: ....

3. We now have the public folders on the EXTRE07  exchange server and mailboxes on both EXTRE07 and EXBRE07.

  Is there something to change in the configuration or should I change the license product ? 

  It is possible to keep the public folder on EXBE07-X, move all the mailboxes on EXBE07-Y and use the A2EToolBox.exe to change the Exchange server ?

Answer:

First, let's answer your last questions first to get them out of the way. You can have folders anywhere you want on any server(s) if the proper permissions are applied to the A2E service account.

Make sure the following Permissions are set on the 2003,  2007 or 2010 servers:

The A2E service account is part of local administrators of any Exchange Servers so it can test to see if the store is up using WMI over RPC.  This is the issue here.

Next, be sure the following Permissions are set on just the 2007 or 2010 servers.  When you run this, make sure you run this on the Exchange Server (one with Exchange PowerShell) as an Exchange Org/admin/domain admin with rights to give the Add2Exchange Service Account the appropriate rights. http://support.diditbetter.com/kb/A2E_214.aspx

Then log off of the A2E server and back on to the server as the A2E service account 

Wait a bit for the exchange permissions to catch up to you and then try again to make the relationship again.

Important Tip, if you had an Add2Exchange or Add2Outlook relationship before you migrated the mailbox and then moved it, and did not remove the relationship before you migrated, that existing relationship would still have destination items copied there and the relationship would have gone into alert.  If you still have that relationship, it would be best to fix that relationship with the Recovery and Migration Tool to avoid any duplication.  Buy Now

If you did remove the relationship before you migrated and selected to remove the destination items, then after the permissions above are applied, you can reset the same relationship up and it will work after you give the new permissions.

If you already deleted the relationship in alert status for those mailboxes or public folders which you migrated,  resetting up the relationship will cause duplication if you recreate it, once for the old relationship and once for this relationship.

In order to fix the problem where you deleted the alerted relationship, if you know that that folder is not the source of any other relationship or is a special non default folder, you could just delete the folder or the folder contents.   This is a big IF so pay attention to the prior IF,  I would back up and then move folders rather than delete to be safe, and moving a folder within a mailbox or changing the name does not disassociate it from the relationship. Since it keys on the store and folder ID, you would have to move the folder to another store, export to PST or move it to a public folder for backup.  My personal favorite is to use the Add2Exchange Service account as the place to put all backups.  This can be done with this procedure: http://guides.diditbetter.com/a2e-guide/managing_relationships.htm

If this condition is not the case here, that you can't simply remove the folder because this folder is not the source or destination of any other relationship, you can use the A2E Toolbox, Inspector General, Surgeon General to strip the items or remove the copies from that destination automatically.  Buy Now

using this procedure: http://guides.diditbetter.com/a2e-guide/inspectorgeneral2.htm

Another big TIP These are the normal migration instructions:

 http://support.diditbetter.com/Forums/Thread.aspx?pageid=1&mid=2&ItemID=2&thread=76

To be complete, if you are migrating away from a 2003 Server and you are decommissioning it, make sure you do this:

http://support.diditbetter.com/kb/A2E_217.aspx

Incidentally, we offer remote recertification services to unravel anything you can’t wait for to solve:

http://support.diditbetter.com/premium-support.aspx

Hope this helps