Why can SEPsesam write to Network devices?
Under Windows, services usually run under the special SYSTEM account. This account has all local access rights, but for security reasons none for non-local, or network drives. The Administrator can access network drives in two ways, but with certain security risks: • Let the SEP sesam service run under an administrator account, which has all writing privileges for the network drive. • Share the network drive in such a way, that the user group Network has writing privileges. Due to increased security after Windows 2000/2003 and XP it is not possible to assign dedicated drive letters, e.g. e:\. Instead the path must be entered using UNC Notation. The backup is carried out over the associated network devices but only after entry of the UNC Names e.g //fileserver/install/Driver.
Related Questions
- I want to develop an application where information sent from different PDA devices should be collected on a single network workstation. Can I achieve this by using PocketLANce SDK?
- Is NetMosaic intrusive, i.e. does it write to or makes modifications on monitored network devices or computers?
- Why can SEPsesam write to Network devices?
