Hello Everyone,
Model: Sharp Copier/Scanner MX-M365N
We recently moved our Sharpdesk NST tool from our user's desktop to our server. This way when someone uses the scanner tool, the file will be sent to the network folder as needed. Before this, our user would have to be logged into his account at his local machine for the file to be sent to the correct network folder.
So now that NST is on our server, everything seems to be working just as expected. However there is one potentially major issue we are coming up with.
Users create a filename at the scanner before scanning the document. If that filename already exists in the network folder, then the NST pops a duplicate filename error on the server machine. This can be easily fixed if you're sitting in front of the server machine. However, from an end user perspective, all scanned files end up in limbo, waiting for that error message to be resolved on the server machine. Once the error message is resolved, all pending scans get processed.
Obviously this isn't an issue if you let the scanner decide the name of the file. But we really need to name our files at the scanner, and it can be difficult to tell if there is a duplicate file ahead of time.
Is there a setting in NST, or the printer web setup, that will allow user entry of the filename, but automatically append (#) it if the filename exists? Has anyone else encountered this issue before? Are there any other creative workarounds?
Right now we told the end users about the correct procedure to take to ensure not creating duplicate files. (Check for duplicates first, or rename the file after it is scanned.)
Thank you for your time.
Nate
Model: Sharp Copier/Scanner MX-M365N
We recently moved our Sharpdesk NST tool from our user's desktop to our server. This way when someone uses the scanner tool, the file will be sent to the network folder as needed. Before this, our user would have to be logged into his account at his local machine for the file to be sent to the correct network folder.
So now that NST is on our server, everything seems to be working just as expected. However there is one potentially major issue we are coming up with.
Users create a filename at the scanner before scanning the document. If that filename already exists in the network folder, then the NST pops a duplicate filename error on the server machine. This can be easily fixed if you're sitting in front of the server machine. However, from an end user perspective, all scanned files end up in limbo, waiting for that error message to be resolved on the server machine. Once the error message is resolved, all pending scans get processed.
Obviously this isn't an issue if you let the scanner decide the name of the file. But we really need to name our files at the scanner, and it can be difficult to tell if there is a duplicate file ahead of time.
Is there a setting in NST, or the printer web setup, that will allow user entry of the filename, but automatically append (#) it if the filename exists? Has anyone else encountered this issue before? Are there any other creative workarounds?
Right now we told the end users about the correct procedure to take to ensure not creating duplicate files. (Check for duplicates first, or rename the file after it is scanned.)
Thank you for your time.
Nate
Comment