I've seen this with a few different MSI's. Basically the Local System doesn't have proper permissions to something that the MSI is looking for. Do they have an EXE you can just throw switches at instead? That is usually what I had to do in those situations. Or somehow wrap it with something else that calls a User Permission.
....or install SCEP. *-----------------------------------------------* *Adam Juelich* Pulaski Community School District <http://www.pulaskischools.org> Client Management Specialist 920-822-6075 On Wed, Mar 25, 2015 at 2:57 PM, Sean Pomeroy <[email protected]> wrote: > Just created an application this week to deploy 10.6 SP3 with the latest > definitions. > Have three different MSIs depending on region. > We are using an MST to prevent reboot and set some registry values. > > 100% deployment success on the 150 servers I pushed it to a few days ago. > > On Wed, Mar 25, 2015 at 3:29 PM Daniel Ratliff <[email protected]> > wrote: > >> Permissions somewhere that LOCAL SYSTEM doesn’t have but administrators >> does. >> >> >> >> We have similar issues sometimes with certain WMI classes like >> win32_printer. LOCAL SYSTEM doesn’t have rights. Makes deploying via SCCM a >> pain. >> >> >> >> *Daniel Ratliff* >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Marcum, John >> *Sent:* Wednesday, March 25, 2015 3:17 PM >> *To:* '[email protected]' >> *Subject:* RE: [mssms] Deploy Trend >> >> >> >> Why would it work when ran as a real user but not when run as local >> system?????? >> >> >> >> *From:* [email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *Todd Hemsell >> *Sent:* Wednesday, March 25, 2015 1:30 PM >> *To:* [email protected] >> *Subject:* Re: [mssms] Deploy Trend >> >> >> >> looks like it cannto install isscript.dll or something >> >> yup that is what it is. a custom action inside of a dll. either cannot do >> the function or cannot install the dll. >> >> >> >> On Wed, Mar 25, 2015 at 12:55 PM, Marcum, John <[email protected]> wrote: >> >> Anyone deploying Trend OfficeScan from ConfigMgr using the msi generated >> using the client deployment tool? This is being deployed to Windows 7 x64. >> My msi installs fine when installing as myself but when installing as local >> system it fails with this helpful error message below. At the point of the >> failure there's nothing helpful in the msi log but I do notice just before >> it dies the log starts mentioning InstallShield. Once I click "ok" on the >> error message I see in my msi log " NOTE: custom action >> tmRestorePreviousClientSettings unexpectedly closed the hInstall handle >> (type MSIHANDLE) provided to it. The custom action should be fixed to not >> close that handle." followed by "CustomAction tmStartClientService returned >> actual error code 1603 (note this may not be 100% accurate if >> translation happened inside sandbox)" >> >> >> >> >> >> >> >> >> >> >> >> * ------------------------------ * >> >> * John Marcum* >> >> MCITP, MCTS, MCSA >> * Desktop Architect* >> >> * Bradley Arant Boult Cummings LLP* >> * ------------------------------ * >> >> >> >> [image: H_Logo] >> >> >> >> >> ------------------------------ >> >> >> Confidentiality Notice: This e-mail is from a law firm and may be >> protected by the attorney-client or work product privileges. If you have >> received this message in error, please notify the sender by replying to >> this e-mail and then delete it from your computer. >> >> >> >> >> >> >> >> >> >> The information transmitted is intended only for the person or entity to >> which it is addressed >> and may contain CONFIDENTIAL material. If you receive this >> material/information in error, >> please contact the sender and delete or destroy the material/information. >> >> >
