Trying to install .msi via PowerShell but only Operational parameter box opens u

Welcome Forums General PowerShell Q&A Trying to install .msi via PowerShell but only Operational parameter box opens u

This topic contains 4 replies, has 4 voices, and was last updated by

 
Participant
2 months ago.

  • Author
    Posts
  • #157970

    Participant
    Topics: 2
    Replies: 3
    Points: 19
    Rank: Member

    Hello All,

    I am putting together a script that will install an application (.msi) but every time I run the command line the only thing that happens is the Optional Parameter box pops up and the install never happens. I even rebooted the test computer and looked for some activity in the event viewer but nothing. Also, fyi – I used to "Start-Process" command because from my understanding it will let the script finish that first process (installing the e-rmsclientsetupx64.msi) before it moves on to the next command in the script (how that will be constructed is explained below).

    This will be part one of a scripted software install. Another thing to point out is, when this software installs, it creates a folder called "C:\Program Files (x86)\Edibar\ERMS Client" and on this folder I need to give the current user full control of the folder because I software will write to that location so they much have full control to that folder. Anyway, I'll cross that bridge once I get this piece figured out.

     

    PS C:\> Start-Process msiexec.exe -Wait -ArgumentList "/i D:\MySharedSoftware\Software\By Project\Edibar Systems\ERMS Client\e-rmsclientsetupx64.msi /quiet"

  • #157974

    Participant
    Topics: 42
    Replies: 77
    Points: 29
    Rank: Member

    Use the PowerShell Application Deployment Toolkit for this, it will make life SOOO much easier for you.

    https://psappdeploytoolkit.com/

    As an SCCM Admin, I have been using this for years now and it is a FREE tool and is kept up to date and well worth it.

    BTW, you don't need SCCM to use it, but it works great with the SCCM application model.

    A doc is provided with the downloaded that is a very easy reference and explains how to use it.

    Basically, it is a framework for PowerShell to simplify application deployments/installs.

    You do not need to reinvent the wheel, which is ALWAYS great in our line of IT work.

    Also, you can script in icacls to change the discretionary perms on that directory location for that user.

    You can checkout a post here that covers some of this: https://community.spiceworks.com/topic/1677590-powershell-and-icacls

  • #157980

    Participant
    Topics: 3
    Replies: 266
    Points: 89
    Helping Hand
    Rank: Member

    This should work for you.

    $filepath = "D:\MySharedSoftware\Software\By Project\Edibar Systems\ERMS Client\e-rmsclientsetupx64.msi"
    Start-Process -FilePath $filepath -ArgumentList "/quiet" -Wait
    
  • #157985

    Participant
    Topics: 1
    Replies: 1430
    Points: 2,131
    Helping Hand
    Rank: Community Hero

    Your MSI file path has spaces in it ... so you have to wrap it in quotes.

  • #158124

    Participant
    Topics: 2
    Replies: 3
    Points: 19
    Rank: Member

    Use the PowerShell Application Deployment Toolkit for this, it will make life SOOO much easier for you.

    https://psappdeploytoolkit.com/

    As an SCCM Admin, I have been using this for years now and it is a FREE tool and is kept up to date and well worth it.

    BTW, you don't need SCCM to use it, but it works great with the SCCM application model.

    A doc is provided with the downloaded that is a very easy reference and explains how to use it.

    Basically, it is a framework for PowerShell to simplify application deployments/installs.

    You do not need to reinvent the wheel, which is ALWAYS great in our line of IT work.

    Also, you can script in icacls to change the discretionary perms on that directory location for that user.

    You can checkout a post here that covers some of this: https://community.spiceworks.com/topic/1677590-powershell-and-icacls

    Nice! I can't wait to try this.

    Here is what I am trying to do:

    1. package the application for deployment in SCCM – Not a prob I know how to do that
    2. once the application installs the user will need to have full permissions to the "ERMS Client" folder (D:\MySharedSoftware\Software\By Project\Edibar Systems\ERMS Client)
    3. Inside of that directory is an xml file with a line that points to localhost and I need to have it point to an actual server that will be used.

    So, in short, my goal is to at least be able to have PowerShell 1) install the app 2) give the user full control to the ERMS folder after it is created by the install.

    I will play around with the PS Automation tool Surprised I have never heard of it before.

You must be logged in to reply to this topic.