/build/static/layout/Breadcrumb_cap_w.png

Silent install for RealPlayer 16.0

I am using SCCM 2007 to package RealPlayer 16.0.3.51. I am trying to create a silent install for RealPlayer 16.* This is what I've accomplished so far.

- Retrieved the alternate installer (this way I can use switches i.e. /s )

- In the script it deletes the Icon, supresses the EULA

But I'm getting this one issue.

Everytime I run the advertisement I get this issue. It only occurs on end-user accounts who don't have admin rights (which is everyone!) I've researched this issue and I can't find anything for SCCM, I've come across solutions for manual installs but that isn't my issue.

I'm confused because its running as the system and not user but still gives me this error.

Any help would be appreciated :)


0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: anonymous_89761 10 years ago
Third Degree Brown Belt
0

try to run the installer manually with the system account. you can use psexec (http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx) to do this.

  1.  open cmd as admin
  2. go to the location of the psexec.exe file
  3. typ: psexec -isd cmd.exe
  4. a new cmd opens, and run the installer
  5. the installer will now run as system

this method can be used to determine of the installation is really working with a system account.


Comments:
  • @petyrb I was really hoping that would install it but I get the exact same error...again - sudoman 10 years ago
  • Do you have a specific need for RealPlayer? I only ask because I find a lot of clients that can use another utility to play sound or video files. It just might be easier for you to cross this one off your ToDo list! - vjaneczko 10 years ago
    • i think VLC is more adequate to do the media job these days, and i found it easier to package/sequence - anonymous_89761 10 years ago
  • @vjaneczko I thought the same thing so I made a few calls to see if those users really needed it...turns out half of them didn't even know they had it installed. Although I believe it might have been a firewall issue. - sudoman 10 years ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ