Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Assign Software Installations to Computers in GPO

Status
Not open for further replies.

MVD100

Technical User
Dec 10, 2008
49
US
I am trying to assign a software application to all computers in my SBS 2003 domain using the GPO editor. Under the Cpmputer Configuration > Software Settings > Software Installation I have created the object with a *.msi file and set the Deployment state to Assigned. The application is in the shared ClientApps folder and all Domian Users and Domain Computers have read access rights. When starting a computer connected to the domian, I see the screen that shows policy and user settings being applied and then the Sotware Application name as being installed. However, it only creates an install shortcut icon on the Administrators desktop. It does not install the app. How can I push out an application to all computers and have it install even if the user does not have adim rights to load software? Thanks.
 
You need to have the GPO apply the software installation on startup when there isn't a user session. That way it will install with elevated credentials and not in the user context.

Refer to an old FAQ of mine for deploying Office that should help you.

faq96-4996


I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at
Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.
 
He is setting it under computer configuration, so it should be installing at computer reboot.

You need to ensure the windows installer group policy settings are configured to always install with elevated permissions additionally.

Also, did you create a transform (.mst) file to provide any answers this application may normally ask during installation?

- Brandon Wilson
MCSE:Security00/03; MCSA:Security03
MCSA:Messaging00; MCP; A+
IT Pangaea (
 
Thanks for the feeback. However, I am still not able to install my application. I have set the Windows Installer setting to Always install with elevated permissions to Enabled within the GPO under both Computer Configuration and User Configuration. I have also created a .mst file using orca to set the password property. I'm not sure about the success of this .mst file. When reboot the client computer, nothing has changed. The application does not install and no warnings or error are displayed. Any other thoughts? Thanks.
 
Oh crap you know what...you are probably publishing the application...it needs to be assigned to the computer config section, and nothing for it assigned in the user config.

publishing will just give a link that will install it on first use basically.
assigning will install it.


so can you confirm these settings.

- Brandon Wilson
MCSE:Security00/03; MCSA:Security03
MCSA:Messaging00; MCP; A+
IT Pangaea (
 
Well I wish it was that simple. However, I am using the Assigned method of Deployment, not Published. Also, I have checked "Install this application at logon." Under the Modifications tab I have also adde the .mst file, still nothing.
 
I would get rid of the installation at user logon...it shouldnt really be needed at all.

What application is it?

- Brandon Wilson
MCSE:Security00/03; MCSA:Security03
MCSA:Messaging00; MCP; A+
IT Pangaea (
 
I have tried with and without the install at logon check. The application is EMC/Dantz Retrospect 7.5 Windows Client. I am also searching the EMC site KB for help. Maybe I can test with some other application. Any thoughts?
 
also, does that mst file answer all questions a user would normally be prompted to answer during the installation (install path and things of that nature)....

- Brandon Wilson
MCSE:Security00/03; MCSA:Security03
MCSA:Messaging00; MCP; A+
IT Pangaea (
 
To be honest, I am not sure I created the mst file correctly. This was my first attempt. The only part I changed was the password. I just read the following on the EMC site (dated 4-29-09):
Question: Is there any news on a package based installer? If so will this installer also allow the installation of the public key?
Answer: We are planning to rebuild the client interface later this year. At that time, we will probably do a new installer too.
 
Go ahead and enable userenv logging for the software installation client side extension:

stored in: %windir%\debug\usermode\appmgmt.log
reg values:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Diagnostics
Appmgmtdebuglevel=dword:0000009b

that should give us an idea if the policy is failing, or maybe if its a shortcoming in the app itself.

- Brandon Wilson
MCSE:Security00/03; MCSA:Security03
MCSA:Messaging00; MCP; A+
IT Pangaea (
 
The following is from the log file after administrator login:
The assignment of application Retrospect Client 7.6 from policy Small Business Server - Client Software Installation succeeded.
Calling the Windows Installer to install application Retrospect Client 7.6 from policy Small Business Server - Client Software Installation.
The install of application Retrospect Client 7.6 from policy Small Business Server - Client Software Installation failed. The error was : %1612
 
thats what I needed to see :)

Enabling windows installer logging may give more details as well...

Error 1612 = ERROR_INSTALL_SOURCE_ABSENT

So when you defined the server path, did you do it by name or by IP?
Did you use a drive letter for a mapped drive or anything like that, or did you use a UNC path?

- Brandon Wilson
MCSE:Security00/03; MCSA:Security03
MCSA:Messaging00; MCP; A+
IT Pangaea (
 
I checked the server path and it was using C:\ drive. I change the path to use servername\ClientApps\...
I think this helped but now the user is given a message during logon that the he can not install software without administrator rights. I don't have the exact wording. Maybe I should just try to use the publish method?
I also read that Retrospect needs to have ISScript9.msi installed first. If I can't solve it tomorrow I'll have to move on to a local install on each client. Thanks for your help.
 
no dont publish...get rid of the install on user logon check :) Of course, the user may still require admin rights to do any app config that is necessary (like with office apps)...

- Brandon Wilson
MCSE:Security00/03; MCSA:Security03
MCSA:Messaging00; MCP; A+
IT Pangaea (
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top