It's not running in program mode that slows Mercury down, and it's not the Windows Server environment as such either. Obviously we need more information to figure out what the problem could be, though. If you can give specifications about the hardware used, other software running on the server, number of mail accounts, Mercury settings and things like that we can see if anything obvious comes to mind.

One thing that always is important is that there must be no antivirus software or similar that interferes with Mercury's access to queue, scratch or mailbox directories.

/Rolf 

I have been using mercury and Pegaus mail on Novell for many years, probably since 1996. 25-30 clients.

Recently we have wanted to move off the Novell server, to Microsoft 2003 server. I have little knowledge of MS 2003, and we have had consultants running those.

Last fall I asked him to install Mercury on the MS2003 box. He did that, and things got really really slow. So slow that you hit send, and 20 seconds later it would finish the screen.  Later I found out that he had not installed the License version but rather was running it as a client instead of a service. There was also some sort of issue with login to the server for each person.

I purchased a license, and he never installed it. We switched back to the Novell server to get back up and running.

Unfortunately, the consulting place and the guy don't want to do it. The want me to put in MS Exchange.

Now, I pay this guy north of $100 and hour. But he won't put it in, and I don't know MS 2003.

Is there anyone that i can get to do paid consulting and accomplish this?

I am running on borrowed time with the Novell box. We use Barracuda handing of mail to the Novell box and then to home directories.

I simply don't want to learn MS 2003, or at least I don't have time.

Thanks,

Bill Harris

We can certainly help with guidelines and hints for how to set up Mercury and Pegasus in a Windows 2003 Server environment, but I think you should learn how to handle a few basic admin tools on the server anyhow. One or two, at least.

There is a FAQ post about setting up Mercury and Pegasus in a Microsoft network here:

http://community.pmail.com/forums/thread/81.aspx

Some more details about the installation are needed to give specific advise, like how many users there are in the network, if there are one or more domains involved, if there is other software running on the server that might interfere. It might be easier to start with Mercury running in program mode rather than in service mode, actually. It's no problem to move to service mode later on.

Have a look at the FAQ post and come back with more details about how you would like to set things up, and we'll see what we can do to help.

/Rolf 

Running in program mode was a disaster. You hit send and the screen stoped on the clients for 20-25 seconds.  Happened on all the clients.

Mercury was so simple under Novell, and worked so well. My knowledge of MS2003 is so poor, perhaps I should try to find someone local who will do it.

My last attempt came up empty, but there must be someone willing to tackle this. We are in Blacksburg, VA which is very rural small town, but with a university.

The consultant we have with ALI is pushing hard to convert and move to ms exchange. Probably because that is all he knows.

It can not be that the server is very busy, even without the Mercury? How many percent of the load on the server? See Task Manager!