We have a hospital up here thaty does not like the way these machines, or anything since the Km-3035 for that matter, scan using the SMB..they don't like the authentication, the shared folder, etc.

Also they do not like the FTP option with the 4.01 SFU because you cannot direct it to a networked local drive (in this case their H drive) Is there anyone else having problems with hospitals scanning due to "Hipaa" rules and if so did you find a solution?

We have been dealing with this issue for 2 ish years.

What's the problem with SMB? FTP also uses authentication and shared folders.

I've been using the FileZilla FTP server when I can't get SFU to work. I haven't tested it with a network share, but I doubt it would complain.

If you use SFU on the server it runs as a service and supports multiple destination folders. Unless they're using a non-windows o.s. this provides centralized management of the scan destinations and doesn't require the MFP to have network credentials.

Unlike many competitors that ONLY have SMB or FTP, the KMA SFU option is my preference - server side. If they want to go to workstations, SMB can use local credentials and there is a script that I wrote (and posted on this forum somewhere) to create the shared folder and the credentials to make deployment easier.
Maybe I could automate it further with AutoIT to create the Address book entries too - that would really make it cool....

Scotty I looked for your post on script for easier deployment smb and did notfind can you repost it. Thank You

SMB Client Setup Script

Awesome, thanks for your ideas..I will try them out and let you know how they work.

The biggest problem that I am running into is the main contact in the IS department does NOT want to run anything on any server that they have up there which seems ludicris to me.