Shared folder, shared calendar & shared address book (contacts)

Discussion in 'Windows Small Business Server' started by Zazi69, Sep 24, 2006.

  1. Zazi69

    Zazi69 Guest


    I am new to SBS 2003 and have just lately installed it. We used to have a
    workgroup with one Shared Folder under one PC and of course all staff had a
    mapped network link to work on that folder as a central location. In fact,
    all documents of the office are saved there.

    This PC represents the main PC of the office were all contacts are saved
    under Microsoft Outlook’s Contacts but there was no sharing of these
    addresses. We used a third party web based free calendar for sharing!

    I have been going through several posts here some are very useful but I
    would to ask about the easiest and best practices to migrate to SBS in order
    to simply have a shared calendar, a shared address book (contacts) and a
    shared folder (representing a document repository) accessible to all staff as
    in the previous setup, except of course, that all is now central under SBS!

    Note: as a first step, I would not like to the staff to use SharePoint which
    I was able to remove, even from the RWW.

    Thanks for all your help.
    Zazi69, Sep 24, 2006
    1. Advertisements

  2. In
    Have you moved all the data to the server? You shouldn't need to use a
    workstation as an ersatz server any longer.
    Put them all in a shared public contacts folder in Exchange. You can control
    permissions granularly. is not
    SBS-specific but should help. In fact, you likely have a public contacts
    folder already, if you did a default setup.

    You can do the same for a public calendar folder (but there will be no
    syncing of mailbox calendar/public calendar data, note - so you may wish to
    instead have everyone share their own mailbox calendar in Outlook.
    <cringe> I wouldn't have done that. If you didn't want them to use it, you
    could have denied access to it - but you have now likely done something
    which will make future SPs and updates unhappy. Note that your having
    Sharepoint installed on the server doesn't have any impact on what your
    users access in Outlook/Exchange whatsoever. Since you're new to SBS, you
    should be very careful what you do with it. It's a tightly integrated
    system, and will start misbehaving if you don't use most of its defaults.
    Lanwench [MVP - Exchange], Sep 24, 2006
    1. Advertisements

  3. Zazi69

    Zazi69 Guest

    HI Lanwench,

    Thanks for the quick answer. However I need more clarifications on few

    1. Shared Folder: what I have done is partitioned the C into C & D where D
    is mainly for data, it has a shared folder as a documnet repositiry
    (replacing the old shared folder & containing all office's documents already)
    and of course I mapped this drive with a shortcut on client's desktops.

    Is this a secure and good practice? Do you think that any PC on the network
    but not on the domain can easily access it? Or is there any other better

    2. Sharepoint: so do you advice me to reinstall sharepoint so as future
    updates & SPs function properly?

    Then what I will do is simply remove it from the list of Web Services Page
    upon configuration using the CEICW? Does this work without any interruption
    of updates and SPs?

    Thanks again for your great help.
    Zazi69, Sep 25, 2006
  4. In
    On the server?
    Or use a mapped drive via a login script.
    If you set up your share & NTFS permissions properly, have a good password
    policy, physical security of the server (as in, locked room), it's a good

    Do you think that any PC on the
    Why would you have PCs on this network that weren't part of your domain?
    I'm not sure if that will help you - might want to post that as a new
    Yes. But that will just prevent external access to it. If you want to
    prevent internal access to companyweb (and I'm not sure why, when you can
    instead change the permissions in it!) you may need to change the security
    in IIS so that even the internal subnet can't access it. Nlot 100% sure as
    I've never attempted this.
    Lanwench [MVP - Exchange], Sep 26, 2006
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.