Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

CHROME-64 not installing silently

Created: 15 Jan 2013 | 9 comments
Sally5432's picture
1 Agree
0 Disagree
+1 1 Vote
Login to vote

msiexec.exe /i GoogleChromeStandaloneEnterprise.msi is the command line argument that came down with CHROME 64 PMIMport 7.1.385 and this causes the install to not install silently

CHROME 63 installed silently using msiexec.exe /i GoogleChromeStandaloneEnterprise.msi /qn /norestart

Can you update the command line argument so 64 installs silently?

Comments 9 CommentsJump to latest comment

Michael Grueber's picture

We will ask the data team to make this change. In the mean time, you can create your own custom command line to install the update according to your needs.

 

 

0
Login to vote
Sally5432's picture

I assumed if i changed the command line it would get overridden by nightly import, or is that only if there's a change on that bulletin?

---
Don't forget to mark posts as helpful if they are, and mark answers as solutions.

0
Login to vote
Michael Grueber's picture

Please note that I recommended the creation of a custom command line within a policy, rather than changing the default command line.  We confirmed that custom command lines are not overwritten when using incremental imports, provided that the Revise Software Update task is NOT set to run following the PMImport. 

We did not verify whether the custom command line will be retained if a full PMImport is performed, but I believe that it most likely would be.  I suspect that custom command lines are associated with bulletins/updates only within the context of a specific policies rather than being directly associated with bulletins/updates. 

There will be a slight change in behavior in the 7.5 release.  In 7.1 SP2, custom command lines currently get overwritten by a new PMImport if the Revse Software Update task is set to run the PMImport.  Beginning with the 7.5 release, the Revise Software Update task will no longer overwrite custom command lines following a PMImport.

0
Login to vote
Sally5432's picture

Looks like the PMImport was updated over night - thanks!

---
Don't forget to mark posts as helpful if they are, and mark answers as solutions.

0
Login to vote
Michael Grueber's picture

You're welcome.  Please note that I slightly revised my previous post above following some additional verification.

0
Login to vote
Roman Vassiljev's picture

Hi Sally5432,

You are right. Command line for update from CHROME-64 bulletin has been corrected in Patch Data 7.1.386 and now includes "/qn /norestart" arguments.

Thanks,
Roman

0
Login to vote
jellsworth's picture

Nice, I had this problem earlier. Looks like it's fixed, nice to know. Thanks for the post.

0
Login to vote
Sally5432's picture

@jellsworth - just fyi Chrome 65 has superseded 64 now - command line is good though :)  

---
Don't forget to mark posts as helpful if they are, and mark answers as solutions.

0
Login to vote
jellsworth's picture

Awesome!  Thanks for the heads up :)

0
Login to vote