12
Mar
MDaemon mobile clients : Recommended connection methods
As MDaemon has evolved over the years there have been many different ways to setup syncronisation with mobile devices and with the the recent introduction of ActiveSync push email there is a new kid on the block but does this now make ActiveSync the best all in one method for email, calendar and contact syncronisation for all customers who can use it?
Read on to see our recommendations for each mobile platform and what advantages and disadvantages different methods have.
14:27 /
MDaemon
Hopefully you're already aware that one of the great new features coming in BackupAssist version 6.4 is the native support for 
Over the past few years we've used a variety of different virtualisation tools but have historically always stuck to a mixture of either VMWare tools (esxi, Player and Workstation) or Microsoft’s Hyper-V platform.
These have worked really well for building larger virtual server platforms but recently I was looking for a quick and easy to configure tool that I could use on my own desktop PC. I was just looking to build some simple test machines for evaluating software in a range of scenarios.
After some browsing I came across 
I don't often get asked about the MailStore proxy, as most of our customers tend to use a local email server of some kind such as MDaemon or Microsoft Exchange where it's not needed. Every so often however, I'll be asked about creating a centralised archiving solution for an off-site POP3/ SMTP service which is where it provides a simple but effective solution.
Typically customers using these services will have have been using simple, user-based archiving such as the manual creation of local PST files which may or may not be include in a wider backup strategy - by no means an ideal solution.
We had an interesting support call the other day that I thought might be useful to share.
The customer who called was using BackupAssist on multiple sites and using rsync jobs to backup from a number of Windows machines, to a central one running CWRsync. Everything was working well but there was some confusion as to how much space each job was taking up on the rsync server.