Help wanted (paid): Network computer fax

[Benjamin Scott]

Hello, world!

  Replies directly to me (off-list), please.

  We suddenly need a computer-based fax solution at $WORK.  I'm pretty
sure Hylafax will meet our needs.  We even have a Linux server it
could be run on.  I'm sure I could figure it out myself, but I already
don't have enough time.  I'm looking for an experienced consultant who
can do the work on a contract basis.  I'd like someone who's done this
sort of thing before, so they know what to do, and what *not* to do.
A good showing will likely lead to future contract work.

  Goal: Receive all incoming faxes to a shared network directory
and/or email address (TBD).  Send faxes from most LAN client PCs,
prolly as the usual "fax software that looks like a printer" thing
(although if there are better ways, I'm open to suggestions).  Don't
need anything fancy like multi-fax or auto-routing or network fax
address book, etc.

  Environment: Predominately MS Windows network.  Handful of MS
Windows servers.  Active Directory.  Linux server running CentOS 5.4.
All MS Windows clients (about 100 or so).  Clients are all Win XP, but
Vista or Win 7 will happen within a few years.  Strongly managed
clients (no one has admin rights, software installed and managed by IT
staff).  $WORK can provide external faxmodem with RS-232 serial
connection, and phone wiring to server.  Everything else is up to
$CONSULTANT.  A viable plan to get client software deployed to
workstations will be required.  "Running around with an install disk"
is not considered viable.  We'll need a computer startup script or
point-and-print or MSI or some other sort of install automation.
Ideally, a way to make the fax server name independent of the current
fax server name would be nice, as we'll prolly be shaking up our
infrastructure in the not-so-distance future.

  I'm not married to Hylafax, so if you've got a compelling
alternative, I'll listen.

  Please email me off-list with questions/proposals/etc.  Referrals
also welcome.

-- Ben