Jump to content

Recommended Posts

Posted

Hello,

 

I am having trouble installing msi files to computers using group policy. I have created a partition on the domain controller which stores all msi installation files in folders for each software (e.g. F:\java\java.msi) and the drive is shared with domain admins = full control. Security permissions also have domain admins = full control and the rest are defaults.

 

When I assign an msi file in gp and assign that gp to the OU, the computers usually see the file when they restart, (installing managed software...) but then goes off straight away and does not install anything.

 

Basically, can anyone tell me if I'm going wrong somewhere, perhaps permissions wise...

 

Thanks for any help.

Posted

I have pointed the software directly in the gp (\\server\share\java\java.msi). What do you mean about mapping the drive?

 

I will try assigning the software on a XP pc.

 

Thanks.

Posted
Has the "Everyone" group got read and execute permissions? If you check the event logs of the machine which isn't installing is there an error relating to permissions or packages?
Posted
No everyone does not have read and execute permissions. I will add it and try it. Does it also need to be in share permissions?

 

Thanks.

 

Try adding authed users with read and execute permissions. You will need this in the NTFS security settings on the server and allow access when sharing the folder also. once you have it working you should find that you can start restricting permissions to make it a little more secure. Also deny everyone but administrators from viewing folder contents (list folder:deny it) that way if they do come accross the folder they cant see sub folders of files.

Posted

If its an MSI install on startup, you need to allow 'Domain Computers' read (and possibly write) access to the installer and as an apply to in the GPO pane shown above. As its applying before logon.

 

So domain computers need acces in the share, security and GPO windows.

Posted

Your folders need read access for everyone.

 

If your installing by GPO the PCs will be processing the GPO before anyone logs in so the instalation packages need to be accessible to the workstation. I dunno if a workstation counts as "authenticated user" I have mine set to just be everyone read.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...