Logout

Alt-N Discussion Groups > MDaemon Discussion Groups > MDaemon Support > Archive > Migrate MDaemon to new server with new 64bit OS

 [F] Alt-N Discussion Groups  / MDaemon Discussion Groups  / MDaemon Support  / Archive  /

Migrate MDaemon to new server with new 64bit OS

[kwfoo@hovid.com]
kwfoo@hovid.com
Novice
Novice
Posts: 151
kwfoo@hovid.com - 02:26am, Oct 15 2018

Hi,
I am working to migrate the existing MDaemon v18.0.2 in Windows 2003 (32bit) to a new server with Windows 2016 (64bit).

Reading the KB of https://www.altn.com/Support/KnowledgeBase/KnowledgeBaseResults/?Number=1200 and have some questions:

1. When install the MDaemon in new server, we just have to install the same version using 64bits installer, right?

2. For third party SSL certificates, is there a guide to export and move the certificates to the new server?

3. In case of activation issue, will the system still able to run in a period of time while we are obtaining help?

4. Is there a way for me to do a trial upgrade test to ensure no surprise that incur more downtime?

In case we encounter any critical problem during the migration, anyway to obtain help (we are in different time zone)?

  All MessagesOldest ItemsOlder ItemsNewer ItemsNewest Items

Tyler Davis - Oct 17, 2018 3:54 pm (#1 Total: 11)  

Alt-N Technical Support  

Photo of Author
Tyler Davis
Novice
Novice
Posts: 215

MDaemon
RelayFax
SecurityGateway
Outlook Connector
SecurityPlus
ProtectionPlus
WebAdmin
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/
---------------------------------------------------------------------

kwfoo@hovid.com - Dec 8, 2018 6:41 pm (#2 Total: 11)  

 

Photo of Author
kwfoo@hovid.com
Novice
Novice
Posts: 151
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.

Tyler Davis - Dec 14, 2018 9:52 am (#3 Total: 11)  

Alt-N Technical Support  

Photo of Author
Tyler Davis
Novice
Novice
Posts: 215

MDaemon
RelayFax
SecurityGateway
Outlook Connector
SecurityPlus
ProtectionPlus
WebAdmin
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/
---------------------------------------------------------------------

kwfoo@hovid.com - Dec 14, 2018 9:51 pm (#4 Total: 11)  

 

Photo of Author
kwfoo@hovid.com
Novice
Novice
Posts: 151
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.

kwfoo@hovid.com - Dec 15, 2018 4:00 am (#5 Total: 11)  

 

Photo of Author
kwfoo@hovid.com
Novice
Novice
Posts: 151
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.

kwfoo@hovid.com - Dec 15, 2018 4:40 am (#6 Total: 11)  

 

Photo of Author
kwfoo@hovid.com
Novice
Novice
Posts: 151
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?



  (newer msg:5)All MessagesOldest ItemsOlder ItemsNewer ItemsNewest Items



 Content:

Read New | Search

 Guest:

Email to Admin



You are visiting as a Guest user.