synchronize folders

Discussion in 'Server Networking' started by shank, May 17, 2009.

  1. shank

    shank Guest

    Trying to figure out how to make sure the working files in MyDocs are on the
    local computer, yet copied to the server. I have one user computer that
    appears to be setup correctly, but not sure. It was setup by the 'real'
    admin.

    MyDocs > Properties: Target H:\MyDocs (isn't this actually removing from
    local?)
    Enable Offline Files is disabled.

    Shouldn't the Target be set to the local C Drive and the Enable Offline be
    checked?
    Seems like the above example is opposite of what I want, correct?

    thanks
     
    shank, May 17, 2009
    #1
    1. Advertisements

  2. Not removed. It's just redirected.
    No - you couldn't do that. If it's local there's nothing to make offline.
    ;-)
    You *could* redirect My Docs as it is....and *then* enable offline files.
    I'm not a fan of offline files in general, but especially on desktops
    connected to the LAN. If this is a laptop, that's one thing - but users in
    the office should always be working from the server copies of their files.
    Offline files can cause problems and lost data. If you have both laptop &
    desktop users set up diferent GPOs and OUs for them so that not everyone has
    offline files.
     
    Lanwench [MVP - Exchange], May 17, 2009
    #2
    1. Advertisements

  3. shank

    shank Guest

    I did change target to H: and also enabled Offline files. But I'm not
    understanding how this works. Is the data file saved to the server, then
    copied back to the client? Or saved on the client and copied to the server?
    The reason I ask is I work with MS Access a lot. If it's being saved on the
    server and copied back to the client and I lose connection with it open, I
    see it getting hosed. However, if saved to the client and copied to the
    server, I think it'd be OK.

    We have a backup service installed that backs up every 15 minutes on the
    server only. I see pros and cons about storing PST files on client or
    server. I think the best way is to save on the client and copy to the
    server. However, I don't see any great way to sync it every 1/2 hour so we
    get the best restore options. I tried downloading MS Outlook Backup. That's
    just a backup and cannot work with Outlook open. So now I'm using the WinXP
    backup scheduled at 12:01am everyday to backup the entire profile to the
    network. It's looking like profiles are around 15-25GB. Is there a better
    way?

    thanks

    "Lanwench [MVP - Exchange]"
     
    shank, May 17, 2009
    #3
  4. But what's the reason you wouldn't just access it directly from the server
    anyway?
    That wouldn't work here, though - in that your changes would be uploaded to
    the server only opon logout (or manual sync).
    PST files should be avoided altogether in corporate networks. They must be
    stored/access on the local hard drive only - it isn't supported in any other
    way. Plus you can't sync them with offline files. Time for Exchange. If you
    can't swing this in house then look into hosted Exchange.
    Ugh. Yes, abandon that. Work directly from the server and do not back up
    workstations!
     
    Lanwench [MVP - Exchange], May 17, 2009
    #4

  5. PST and MS Access files, and other database files do not work with Folder Redirection and Offline files. If the users are desktop (not laptop) users, you can either opt to keep the desktop users out of the redirect policy as Lanwench suggested, and use or share the file from a central location, or if individual databases, meaning a specific user is the only one using that specific database, then keep it local to the desktop.

    Shank, I believe we talked about PSTs in another thread, didn't we? It sounds familiar. Storing a PST on the server, especially large ones, consumes quite a bit of bandwidth, and doesn't work with laptop users in and out of the office with a Redirect policy, as I mentioned. Keeping the PST on the laptop can lead to issues, such as lost emails if the drive were to go south, etc. If using Exchange, you can pump the PSTs into their mailboxes, but then if they are that large, it will consume a large portion of an Exchange database/store, and would probably require Ex2003 Enterprise due to the sizes alone, unless you were to use an archiving system that stores it outside of the Exchange database but are referenced through 'stubs' in their mailbox.

    Exchange archiving may be something to look into for email if the users require to keep all of their email from day one of starting with the company. I used to work in a pharma, and there are minimal FDA requirements reflecting similar requirements. We used Zantas EAS, but it is pricey. There are others out there.

    As for shared MS Access databases, you can leave them on the server, but for laptop users you may be better off with a VPN solution so they can access them when remote. I would suggest a hardware based VPN solution, such as a Cisco ASA5505, or whatever firewall/router/VPN device you already have in place, instead of a Windows solution. They are not that expensive, they are secure, and perform nicely.

    --
    Ace

    This posting is provided "AS-IS" with no warranties or guarantees and
    confers no rights.

    Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
    Microsoft Certified Trainer


    For urgent issues, you may want to contact Microsoft PSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    "Efficiency is doing things right; effectiveness is doing the right things." - Peter F. Drucker
    http://twitter.com/acefekay
     
    Ace Fekay [Microsoft Certified Trainer], May 18, 2009
    #5
  6. shank

    shank Guest

    Access is a good front end to SQL2005.
    Of course, we still use a few Access tables here and there though.

    To the above, I'm keeping the PST's on the local. Still backing them up at
    night to the server though.

    thanks
     
    shank, May 19, 2009
    #6
  7. That's good you are backing up the PSTs.

    Cheers!

    Ace
     
    Ace Fekay [Microsoft Certified Trainer], May 19, 2009
    #7
  8. I still say Exchange is the way to go. If you can't justify it in house go
    for hosted. See
    http://www.exchangefaq.org/faq/Exchange-5.5/Why-PST-=-BAD-/q/Why-PST-=-BAD/qid/1209
     
    Lanwench [MVP - Exchange], May 19, 2009
    #8
  9. shank

    shank Guest

    Hosted exchange would be our closest option, but damn, getting a new server
    going is nickel-diming us to death. I'm trying to figure out as much as I
    can about it to save us some cash. Of course, the toll and learning curve on
    me is a bit staggering and a bit annoying. But I figure if I ever get to
    retirement, it won't be so bad. :)
    thanks

    "Lanwench [MVP - Exchange]"
     
    shank, May 19, 2009
    #9
  10. Retirement?? Is that word still in the English dictionary????????
     
    Ace Fekay [Microsoft Certified Trainer], May 19, 2009
    #10
  11. Ace Fekay [Microsoft Certified Trainer]
    Sure. You can retire hardware. Just not yourself.
     
    Lanwench [MVP - Exchange], May 20, 2009
    #11
  12. Ahh, that explains it! I didn't look under 'hardware!'
     
    Ace Fekay [Microsoft Certified Trainer], May 20, 2009
    #12
    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.