Everything you've ever wanted to know about MDaemon
Over the years I’ve heard the odd complaint that MDaemon will crash when a RDP (remote desktop / TSE) session connects.
I’ve never reproduced this in the lab, so I can’t confirm the fix, but I’ve heard a rumour that Microsoft KB article 914048 solves the problem.
Please post in the comments if you have this problem and whether or not the fix works?
Notice that your primary domain field is disabled and you can’t change it? Well, you just bumped into one of the few limitations of a “configuration session” (formerly known as a “ghost” session)
To change the primary domain, close the MDaemon console, open the Windows “Services” management interface (start –> run –> “services.msc”) and stop MDaemon, then launch “MDaemon.exe” from the \MDaemon\App\ directory manually. Note that you must not use the “Start MDaemon” option in the start menu here, that option will restart the service.
Once MDaemon starts, you can change the primary domain, then shut down MDaemon, return to the Windows “Services” management interface and restart MDaemon from there.
The account pruner logs it’s activities in the accountprune.log file in the \MDaemon\Logs\ directory, including potentially important details like accounts which were deleted due to inactivity.
In addition to MDaemon’s daily stats report, I also like to review the accountprune.log just to ensure that nothing important was deleted.
On my server I created a scheduled task that calls a batch file which says “IF EXIST C:\MDaemon\Logs\accountprune.log COPY c:\MDaemon\accountprune.raw C:\MDaemon\Queues\Rawfiles\accountprune.raw”, where accountprune.raw is a RAW file I build that emails my admin mailbox and uses the attachment feature to attach (and delete) the logfile.
The RAW file is pretty simple, mine looks like this:
TO <[email protected]>
FROM <[email protected]>
SUBJECT <AccountPrune>
X-Flag=ATTACH <D:\MDaemon\Logs\AccountPrune.log, ASCII> -x
The result is that I get to see the report each morning.