User Collaboration on Files/Procs/Locking/Session Sharing

Home Forums Server Operating Systems Windows Server 2000 / 2003 / 2003 R2 User Collaboration on Files/Procs/Locking/Session Sharing

Viewing 1 post (of 1 total)
  • Author
    Posts

  • humbletech99
    Member
    #129125

    I have users who constantly run in to file sharing problems where one person is holding open a file they need to use which results in support calls to find the person and possibly terminate their process to release the file.

    This kind of thing lends users to actually sharing sessions so that if 1 user goes on holiday, another user can pick up their work, check that long process they are running is still working or collect the results. If somebody is out of the office for whatever reason, they tend to call a colleague to watch their process is working or make modifications and re-run it, so there is a lot of collaboration between users. If the user’s process is hung, it holds the lock on the file and this causes problems too if the other user in the office cannot access the session of the first user.

    I’d like to know how people out there handle these kinds of issues.

    How do your users collaborate?

    Some more background:

    Users run big intensive processes in things like Visual FoxPro on DBF files. These processes can run for many hours, overnight, through the day etc…

    Users are using Windows 2003 Terminal Servers with their own sessions logged in with their individual user accounts. There exist a small amount of shared access accounts that all users know the password to and they can just dive in and share processes and things in this way, much to my reluctance, but this follows the business structure of people working in teams for clients and sharing work.

    Some work is done on workstation class machines with a single shared account, although I am really trying to stamp this out in favour of the terminal servers.

    Does anyone have any ideas on this whole collaboration between users including ideas on how to deal with:

    – File Locking
    – Process Sharing (ie let one user control another’s process)
    – Session sharing

    I’d really like to maintain separate accounts and eliminate shared accounts or some users having to tell other users their passwords to access their sessions and processes.

    Ideas and Feedback welcome

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.

Don't leave your business open to attack! Come learn how to protect your AD in this FREE masterclass!REGISTER NOW - Thursday, December 2, 2021 @ 1 pm ET

Active Directory (AD) is leveraged by over 90% of enterprises worldwide as the authentication and authorization hub of their IT infrastructure—but its inherent complexity leaves it prone to misconfigurations that can allow attackers to slip into your network and wreak havoc. 

Join this session with Microsoft MVP and MCT Sander Berkouwer, who will explore:

  • Whether you should upgrade your domain controllers to Windows Server
    2019 and beyond
  • Achieving mission impossible: updating DCs within 48 hours
  • How to disable legacy protocols and outdated compatibility options in
    Active Directory

Sponsored by: