Re: *A challange - Group Policy & Lockdown of Software Install Directory -*
From: blaxshep (Jim_Campau@bausch.com)
Date: 07/17/02
- Next message: J N Katzman-TCM: "Re: Visual Studio.Net"
- Previous message: John A Grandy: "asp.net security"
- In reply to: Morgan: "*A challange - Group Policy & Lockdown of Software Install Directory -*"
- Next in thread: James: "Re: *A challange - Group Policy & Lockdown of Software Install Directory -*"
- Reply: James: "Re: *A challange - Group Policy & Lockdown of Software Install Directory -*"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "blaxshep" <Jim_Campau@bausch.com> Date: Wed, 17 Jul 2002 14:35:20 -0400
You could hide the share by making it an administative (share$) share and
prevent copying the directory by making it read only. As for people
searching the registry you could set permissions on regedit.exe to prevent
that from running for all but selected personel.
"Morgan" <techmorg@yahoo.com> wrote in message
news:196c601c22daf$3fd07cf0$19ef2ecf@tkmsftngxa01...
> Okay, here's a stumper that none of us can figure out.
> ***Maybe >you< can?***
>
> The situation: We are trying to setup group policies for
> software control purposes. The group policies work great,
> only certain users have certain software available to them
> in add/remove programs based on what group policy they are
> assigned. No problem there.
>
> The PROBLEM: In order to allow the users to install the
> software through the group policy, they must be given
> access to the share where the software resides. (If we
> deny access, the installer will fail)
>
> We are concerned that if they find out where the share is,
> they will copy the software install directory and install
> it on other computers. We know that the only way they will
> find out where the software is actually residing is by
> looking in the registry for the key that contains
> the "install location" which will be created after they
> install the software initially. Then, they can browse to
> that location and grab the software. We can't lock down
> the registry because some of our customers are engineers
> who need access to their registries.
>
> Anyone have any ideas on how to solve this problem or have
> the software directory only accessable during the install
> process?
>
> *Any* input would be greatly appreciated!!
>
> Morgan
> Network Engineer
> techmorg@yahoo.com
- Next message: J N Katzman-TCM: "Re: Visual Studio.Net"
- Previous message: John A Grandy: "asp.net security"
- In reply to: Morgan: "*A challange - Group Policy & Lockdown of Software Install Directory -*"
- Next in thread: James: "Re: *A challange - Group Policy & Lockdown of Software Install Directory -*"
- Reply: James: "Re: *A challange - Group Policy & Lockdown of Software Install Directory -*"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|