Windows Thread, Deploy Software Through GP And MSI in Technical; Hi all,
I am trying to send some software [dropped on my desk with very little notice] to stations on ...
29th October 2009, 03:53 PM #1
Deploy Software Through GP And MSI
I am trying to send some software [dropped on my desk with very little notice] to stations on the network. I am able to deploy ready made MSIs now without issue [hooray!]
However I would like to be able to send this down using Group Policy as there is very little time and re-imaging the number of machines involved is not an option.
I have used AppDeploy Repackager to capture the station changes when the application is installed [clean station with only AppDeploy Repackager and Sophos installed] when I send the new package to the stations I get these entries in the event log [attached]
The MSI does install the application if double clicked and as I said I can deploy other MSIs. What do I need to do to get my "home made" MSI to go to my workstations?
29th October 2009, 04:02 PM #2
Last time I had this was because of a permissions error in the folder containing the MSI and files, but that was 3 years ago ... possibly the same?
29th October 2009, 04:08 PM #3
Don't think so. I have just checked/compared the permissions for the folder where the MSI which is erroring with one that deploys OK and they are the same [but that is to be expected because they are inheriting their permissions from the folder above]
Originally Posted by GrumbleDook
29th October 2009, 04:17 PM #4
You need to set the folder to have 'domain computers' at read access at least, and also the gpo needs to be applyaple by domain computers.
As this is executed before a user logs on.
29th October 2009, 04:18 PM #5
Try and force permissions on the containing folder. It was exactly the same for me and completely bizarre. The other option is that it is trying to replace a file on the local computer that it does not have permissions to replace.
29th October 2009, 04:18 PM #6
Those error message don't look like permissions problems (error is generally "can't find file")
Turn on installer logging - details here Windows Installer Logging at Registry Guide for Windows and you'll get a logfile from the installer which should help
29th October 2009, 06:22 PM #7
As a general tip never install AV software when capturing. When you capture the changes your AV software may have updated etc and it just causes more issues. Your package for example could have bundled a sophos IDE that was deployed during the capture which would/could break installs.
29th October 2009, 06:42 PM #8
I had thought of that and I was able to complete the package creation in between Sophos updates. No IDEs were included. However tomorrow I will recreate the MSI on a station without Sophos and see how that goes.
Originally Posted by ZeroHour
29th October 2009, 06:45 PM #9
Further to my last post on this thread I will also look into this. Hopefully one of these approaches will give me the answer I am looking for?
Originally Posted by srochford
29th October 2009, 06:45 PM #10
Yeh its more as a general rule tbh. I would probably double check there are no weird windows files in the msi either tbh.
Originally Posted by DaveP
Do you know what installer the original installation used? e.g installshield?
30th October 2009, 01:32 PM #11
Ok looks like I have cracked it [sort of]
Step one: Ditch AppDeploy Repackager
Step two: Download and install WinInstall LE.
Step three: Build package and deploy through Group Policy.
I say 'sort of' at the start of the post because the finished package behaves oddly: It fails to deploy on first reboot and succeeds on the second [the deployed application does not require a reboot when installed manually] and even when the software is deployed at the station when the icon is double clicked it runs an install [first time run]
However it works so I will leave it at that.
30th October 2009, 01:45 PM #12
FYI with Wininstall do not call your build machine "software"! This then replaces all the registry key names with software in with %machinename% and breaks everything.
I did that in the past and wondered why all my packages never worked
30th October 2009, 01:57 PM #13
Thanks. I wasn't aware of that. Luckily I called my machine 'MSIBuild'
Originally Posted by DMcCoy
By DaveP in forum How do you do....it?
Last Post: 7th October 2009, 09:17 AM
By LOUD in forum Windows Server 2000/2003
Last Post: 13th August 2009, 03:56 PM
By sidewinder in forum Windows
Last Post: 5th June 2008, 12:04 PM
By ICTNUT in forum How do you do....it?
Last Post: 4th July 2006, 05:09 PM
By tobyhughes in forum How do you do....it?
Last Post: 18th June 2006, 07:53 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)