If slartibartfast's answer isn't feasible for you for some reason (like not wanting to set up your first-ever intranet web server...), consider the following.
If the file server is based on Unix/Linux/MacOSX using Samba: Create a shared network directory that is read/write for the publishing user(s). Let's name the share pdf-rw, and one of the publishing user(s) pdfpublisher. In Samba's config file smb.conf
set this up like this:
[pdf-rw]
comment = Writeable for pdfpublisher(s) only (and not browseable for users)
path = /path/on/unix/system
browseable = no
writeable = no
write list = pdfpublisher, domainname\\who.ever, onemoreuser
guest ok = no
Create another shared network directory that is readonly for everybody else. Let's name the share pdf-ro. In Samba's config file smb.conf
set this up like that:
[pdf-ro]
comment = Read-only for users (as well as browseable)
path = /path/on/unix/system
browseable = yes
writeable = no
guest ok = yes
map to guest = bad user
The trick is to define 2 different share(name)s with 2 different settings:
- the readonly share is also browseable and even accessible for guest users without a password (and may be mapped as a network drive if you want);
- the read/write share is hidden and does not appear in the network neighbourhood (it can be accessed if you know the
\\servername\pdf_rw
UNC path, plus if you know how to provide one of the named users' credentials; it may also be mapped to a network drive).
If the file server is based on Windows: Pick one of the suggestions made by other users and test if it works for you.
Big caveat:
Be aware that any update to the PDF document by the publisher will not be automatically noticed by the clients. Depending on their PDF viewer software + version, they may still see the old version of the file unless they re-load it.
3Why in the world are you using a pdf to hold a calendar? Talk about the wrong tool for the job. – Joel Coehoorn – 2010-07-29T01:25:34.227
1@Joel: I wouldn't jump the gun on this. PDFs have advantages in some office environments. Just because it was implemented wrong here doesn't mean it's a bad idea. – hotei – 2010-07-29T05:15:01.780