Re: Security in a Terminal Services Environment
- From: "Rick Brandt" <rickbrandt2@xxxxxxxxxxx>
- Date: Wed, 19 Mar 2008 19:28:55 -0500
hawk_2001 via AccessMonster.com wrote:
Forgive me if this is an elementary question. I am still very green
with Access.
I am trying to implement security (through the built-in Microsoft
Access wizard) in a terminal services environment. We currently use
4 separate servers, each having a licensed copy of Access loaded onto
it.
And all your users have Access licenses as well right?
I have studied up on the "Microsoft Access Security FAQ" as well as
other sources, and feel I have a decent understanding of how security
is designed to work. My Groups, Users, etc. have been set up, and
permissions assigned.
Access ULS security is an ADVANCED Access topic that almost nobody gets
correct on the first few tries. If you are actually "green" to Access in
general then you are most likely over your head with security. The biggest
test is to try opening the file without using the secure workgroup. In most
cases for people trying security for the first time it will open right up.
If it does then you messed up.
My problem is this -- each user in our active directory has their own
specific default "path" to the workgroup.
You can set up a shortcut that specifies a workgroup that is not the user's
default. If all users have such a shortcut then it doesn't matter where
their default workgroup is located. Generally speaking it is best to not
muck around with default workgroup settings. Just leave people joined to
System.mdw and use a shortcut as described for secure files. The shortcut
would have the format...
"Path to MSAccess.EXE" /wrkgrp "Path to workgroup" "Path to MDB"
I want to be able to implement security across our network (for all
Access databases) without having to change each users default "path"
in each server.
Is this possible?
I have been reading this forum and keep seeing that in a terminal
services environment, every user shuld have thier own copy of the
front-end database. I would like to avoid doing this, if possible.
You can avoid it but you will almost certainly corrupt your file if you do.
I suggest LOTS of backups if you persue that strategy.
--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
.
- Follow-Ups:
- Re: Security in a Terminal Services Environment
- From: hawk_2001 via AccessMonster.com
- Re: Security in a Terminal Services Environment
- References:
- Security in a Terminal Services Environment
- From: hawk_2001 via AccessMonster.com
- Security in a Terminal Services Environment
- Prev by Date: Security in a Terminal Services Environment
- Next by Date: Access 2003 Login Question
- Previous by thread: Security in a Terminal Services Environment
- Next by thread: Re: Security in a Terminal Services Environment
- Index(es):
Relevant Pages
|
