Should we use MSMQ3 in our application????

Experts

We are selling an application that needs a message queuing system.  

We have developed a reliable simple system where an ASP web page accepts a HTTP PUT/POST.   This information is written to a file that uses the data’s MD5 as the filename.

Another program monitors a directory using windows directory notification.  When we’re called we look for new files.  We read each file and erase them when the information is added to a database.  Basically we have a Message Queue using the widows file system.

This system is simple and relatively reliable.   No database connections nothing too complex.  If the file system is there it works.  

We have an opportunity to expand our system at this point, and were considering using Message Queue 3.0.   We like the idea of using the SOAP connector.

Our system will only run on a single machine and while we use a database we need to be sure that our system will keep running if the database is down for whatever reasons.

Our customers, have a hard enough time installing our existing system and often make mistakes that are fully documented in the manual.  

My questions are:

1) Is MSMQ3 a good fit for us?  
2) How difficult is it to install?
3) Can it run on a machine with other applications running on it.
4) Does it require a lot of Active Directory changes?


It all boils down to this: Are the obvious benefits of MSMQ going really add to our solution, or will it create more problems that are not easy to solve.

Our goal is to make something that average sesames can install and maintain.  We have to support it remotely.