We have a in house windows service installed by a WiX installer. Since our users on these remote systems are not administrators, this install is actually "brokered" by the same service. That is, msiexec is called by the service itself, and the installation is called with /quiet /norestart as we do not want the user to see anything nor to have the OS reboot immediately, as the user will be confused/lose work, etc. by this. Unfortunately under some circumstances the installation fails because the files from the service (e.g. its EXE and its remoting proxy library) are in use. I don't care if it takes a reboot to finish the installation; but I do want to ensure the files are eventually updated and the service continues working. What is the most reliable way to do this? I take it that if the installation were to be manual the FilesInUse dialog would do the trick, but with the unattended, SYSTEM brokered install this won't of course work. So what will "click OK" there and do the shutdown and restart of the service? Is it passable as a property in the installer itself?
Thanks, Keith Douglas Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6 keith.doug...@statcan.gc.ca Telephone | Téléphone 613-854-5589 Facsimile | Télécopieur 613-951-4674 Government of Canada | Gouvernement du Canada ------------------------------------------------------------------------------ Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
