Problem running program as a member of the group users.

[t]

Hello,

I am an admin for a network (NT 4 server, 7 XP Pro WS, 1 Win 2000 WS, 3 Win
98 WS). My problem is this, we have a report software package which is
installed on the server and all of the work stations. The database is on
the server. Since the implimentation of the XP work stations the other
Admin and I have been pulling our hair out. We want to restict our users
that are members of the users group so that everyone can't install software
on the workstation. The problem is that when we set users as a member of
the users group they can't open the database file on the server. If we make
them a member of the power users group or the admin group it works fine, but
then they can install software. We do not have any problems with the other
workstations, just the XP work stations.

Any suggestions would be gratly appreciated.

[Robert Moir]

t wrote:
> Hello,
>
> I am an admin for a network (NT 4 server, 7 XP Pro WS, 1 Win 2000 WS,
> 3 Win 98 WS). My problem is this, we have a report software package
> which is installed on the server and all of the work stations. The
> database is on the server. Since the implimentation of the XP work
> stations the other Admin and I have been pulling our hair out. We
> want to restict our users that are members of the users group so that
> everyone can't install software on the workstation. The problem is
> that when we set users as a member of the users group they can't open
> the database file on the server. If we make them a member of the
> power users group or the admin group it works fine, but then they can
> install software. We do not have any problems with the other
> workstations, just the XP work stations.

In the first instance why not ask the people who made the software for an
updated version that runs correctly on Windows XP?

[Roger Abell [MVP]]

This is commonly seen from applications that fail to meet=20
the Windows logo certification requirements.

The first thing to try is to grant the Users group modify=20
on the area where the application has installed, usually=20
a folder within Program Files.

If this is insufficient, then very often one or both of the=20
next increased grants to Users group helps
1. some folder outside of the app install point where=20
attempts are made to create temp files
2. the registry keys of the application

The regmon and filemon tools from www.sysinternals.com=20
can help one determine what accesses are being attempted=20
but are denied to Users only accounts.

--=20
Roger=20

"t" > wrote in message =
...
> Hello,
>=20
> I am an admin for a network (NT 4 server, 7 XP Pro WS, 1 Win 2000 WS, =
3 Win
> 98 WS). My problem is this, we have a report software package which =
is
> installed on the server and all of the work stations. The database is =
on
> the server. Since the implimentation of the XP work stations the =
other
> Admin and I have been pulling our hair out. We want to restict our =
users
> that are members of the users group so that everyone can't install =
software
> on the workstation. The problem is that when we set users as a member =
of
> the users group they can't open the database file on the server. If =
we make
> them a member of the power users group or the admin group it works =
fine, but
> then they can install software. We do not have any problems with the =
other
> workstations, just the XP work stations.
>=20
> Any suggestions would be gratly appreciated.
>=20
>
>=20
>