Software installation

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

OK I'll ahve a go at this.

I'm not really sure but I'd ahve thoguht that hiding these files means that they are hidden from the user, but not the system.Therefore there shouldn't be a problem.

I knwo that on a local system there's administrative shares which are hidden with the $ sign.They can be accessed by programs which require them, but not by users browsing the network.

So I think the deal is that although your hiding files and shares from users, the system of course can still find them because it is the system itself.I mean you can't hide yourself from yourself :?

That's all probably wrong AJ.Just thought I'd have a go

I'll learn something when the experts come along to sort us out I'm sure.


---------------------------------------------

You can publish or assign an installation to a user, but you can only assign an installation to a computer.This is ebcause a computer can't choose when it wants to install the application, it just installs it automatically at startup.
It can't one day decide that it wants to install the application, that is what publishing it does, let's the user choose when they want to install it.

 

I would agree with you on this one flex, assigning the software install would mean that it's assigned to the machine and not the user so it should work fine and install the software at reboot,

However that depends on wheather the GPO is assigned to a machine or to a user, I imagine that the s/ware will be rolled out to machines so you should have no problems.

....................Does that make sense ???????? :?:

 

Interesting point raised here though, got me thinking.

I think software installs is sort of like task scheduler, whereby you specify who the task will run as.The task may require admin priviledges, but it can be run automatically under the user acocunt.The task will run in hidden mode.

However in software installs, we don't specify who the install will run as, I think it automatically runs, well just as installer based on policies, not based on the rights of the user account.

So although the user may not have the 'right' to access the files, the policy higher up will allow installer to run.

I'm going to try this on ym lab I think.

 

When a prog is installed via the use of a GPO (I'm assuning your using this method by your description of the darlings moving around the school and the apps following them.... couldn't see them moving the PCs ) the system installs the application not the user, can't remember the service in question but take my word for it, ( as a side issue.... we nailed down our desktops at my previous place of work and the lusers couldn't change anything.... they complained to start of with but the old tag line.... Corporate policy, shut them up )

Yes the drive is hidden, similarly to a SHARE$ or C$ is hidden but if you map a drive to computername\c$ you gain direct access to the drive.
Soemthing I'm sure some of the darlings are well aware of so if you haven't already thought about it secureing the file system on the local machine will also need to be tackled.