Migrate MDaemon to new server with new 64bit OS

1. I would install the 32-bit version on your 64-bit OS to verify the server is running correctly. Once it's running as intended, the 64-bit installer can be installed over top of the existing installation.

2. MDaemon doesn't handle SSL certificates, only uses what's available on the server. Depending on which version of Windows you're running, there should be a way to export/import certificates.

3. A single license activated in multiple locations will one of the machines to fail a license verification and/or lock the the registration key, requiring a MDaemon operator to review/unfreeze the key.

4. New installations will allow a trial activation with the latest version of MDaemon only. If you're migrating MDaemon 18.0, a trial key will not work. Please contact sales@help.mdaemon.com for more information.

If you're looking for a MDaemon partner local to your location, please see the link below. Support options may vary.

https://www.altn.com/Partners/FindAPartner/

--
Tyler Davis
MDaemon Technologies
http://www.mdaemon.com

---------------------------------------------------------------------
These forums are provided by MDaemon Technologies for user-to-user
support and discussion. MDaemon staff members may participate in the
forums periodically but please recognize that this is not the official
method of receiving technical support. To receive personal technical
support please use the form here:
http://www.altn.com/Support/RequestSupport/
---------------------------------------------------------------------

Hi,
I am performing test migration on the new server today follow the KB guide with the latest version.

After install the 32bit MDaemon in the new server with a Trial Key, system running fine except with some certification/security issue when connecting client to IMAP. Believe it is cause by I am using different IP for the test server and client connection purely on IP and not the SSL domain name. I can only connect client without using SSL.I cannot perform more test on this area cause the production server is still running.

After that I am trying to upgrade the MD to 64bit by running the 64bits latest MDaemon downloaded and it detected need to uninstall 32bit BES.

Trying to follow the KB (https://www.altn.com/Support/KnowledgeBase/KnowledgeBaseResults/?Number=KBA-02339) and encounter problem where I do not see the BES for MDaemon, SQL Servers in the Windows Uninstall. Only MDaemon is available.

How should I proceed from here.

When MDaemon was migrated, was the certificate migrated as well. If you're using a self-signed certificate, was a new one created? MDaemon's SSL/TLS support for SMTP/POP3/IMAP options are in the menu below.

http://help.altn.com/mdaemon/en/index.html?ssl_mdaemon.htm

Do you see a BES folder in the /MDaemon directory? If so, remove it and try running the installer once again.

--
Tyler Davis
MDaemon Technologies
http://www.mdaemon.com

---------------------------------------------------------------------
These forums are provided by MDaemon Technologies for user-to-user
support and discussion. MDaemon staff members may participate in the
forums periodically but please recognize that this is not the official
method of receiving technical support. To receive personal technical
support please use the form here:
http://www.altn.com/Support/RequestSupport/
---------------------------------------------------------------------

After remove folder BES, no problem to install the 64bit Mdamon.

After installation, found that AD authentication failed where previously has no problem on the 32bit. It show message no able to contact AD server. Same when perform test in the AD setup.

When we do Test on the Active Directory Authentication Settings, it show:

AD Error 1355: The specified domains either does not exist or could not be contacted.

I have test to login an AD user on the server without problem.

Hi,
Further test result follow:

Before I make any changes, the settings is:
Bind DN: (blank)
Password: (blank)

Base entry DN: LDAP:rootDSE

It does not work with the above settings till I change to the following:
Bind DN: (AD username)
Password: (AD user password)

Base entry DN: LDAP://x.x.x.x (AD server IP address)

Test success with the above changes.

How the system authenticate without specifying the AD server info previously ?

What should be the proper setup?

If the Active Directory server requires queries to authenticate, then you will need to supply the user/pass. Based on your testing, submitting a query to your Active Directory server fails when you do not submit a user/pass.

--
Tyler Davis
MDaemon Technologies
http://www.mdaemon.com

---------------------------------------------------------------------
These forums are provided by MDaemon Technologies for user-to-user
support and discussion. MDaemon staff members may participate in the
forums periodically but please recognize that this is not the official
method of receiving technical support. To receive personal technical
support please use the form here:
http://www.altn.com/Support/RequestSupport/
---------------------------------------------------------------------

1. I do not have such problem in the production server. Which is using the same environment with the setting before making any changes. In the test server, before I upgrade to x64 also working fine without specifying the server and login info.

2. We have multiple AD servers that sync the AD to each other, possible to setup multiple servers for authentication to avoid problem if one of the server down?

Actually base on my testing, the MD is not able to reach the AD server if we use LDAP://rootDSE

After I put in the AD IP then it prompt for invalid user/pass.

1. Is the test server a member of the same domain as the production server?

Microsoft has a AD Explorer which can be used to make inquiries from the tool to the AD server and verify if your configuration/login details are correct.

https://docs.microsoft.com/en-us/sysinternals/downloads/adexplorer

2. MDaemon can only query one AD server. Which problems are you attempting to avoid? If MDaemon is only being used to monitor user accounts, the only issue you would see during any Active Directory downtime is new accounts could not be automatically created (if this option is enabled).

--
Tyler Davis
MDaemon Technologies
http://www.mdaemon.com

---------------------------------------------------------------------
These forums are provided by MDaemon Technologies for user-to-user
support and discussion. MDaemon staff members may participate in the
forums periodically but please recognize that this is not the official
method of receiving technical support. To receive personal technical
support please use the form here:
http://www.altn.com/Support/RequestSupport/
---------------------------------------------------------------------

Hi

If you want to migrate MDaemon to New Server, then there is a solution available. I wanted to migrate MDaemon mailbox to Exchange and it helped me a lot in this. And, I am sure, it will help you too. It is easy and very simple and carries direct functioning. Besides this, it offers 20+ saving options. You can use according to need and perform desired migration. If you want, you can try the tool by downloading its free demo. It allows to migrate first 25 files free of cost. With the help of this, you can check the software working on your own before purchase.

Know more: https://www.cubexsoft.com/mdaemon/