6Foot2 Posted October 29, 2009 Posted October 29, 2009 Hi all, 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? Many thanks.
GrumbleDook Posted October 29, 2009 Posted October 29, 2009 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?
6Foot2 Posted October 29, 2009 Author Posted October 29, 2009 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? 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]
Domino Posted October 29, 2009 Posted October 29, 2009 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.
GrumbleDook Posted October 29, 2009 Posted October 29, 2009 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.
srochford Posted October 29, 2009 Posted October 29, 2009 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
ZeroHour Posted October 29, 2009 Posted October 29, 2009 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.
6Foot2 Posted October 29, 2009 Author Posted October 29, 2009 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. 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. Thanks.
6Foot2 Posted October 29, 2009 Author Posted October 29, 2009 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 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?
ZeroHour Posted October 29, 2009 Posted October 29, 2009 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. Thanks. Yeh its more as a general rule tbh. I would probably double check there are no weird windows files in the msi either tbh. Do you know what installer the original installation used? e.g installshield?
6Foot2 Posted October 30, 2009 Author Posted October 30, 2009 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.
DMcCoy Posted October 30, 2009 Posted October 30, 2009 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
6Foot2 Posted October 30, 2009 Author Posted October 30, 2009 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 Thanks. I wasn't aware of that. Luckily I called my machine 'MSIBuild'
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now