A few issues during postman installation

[aristosv]

I think there’s a couple of things that are not working as they should during postman installation.

1. it installs silently without requiring any options (eg. /s /silent /q)
2. It installs under AppData\Local\Postman without asking where it should install.
3. after it installs it just runs itself, which is an issue for silent installations

Is there any way to fix any of the points above. It’s really causing issues with automated installations in corporate environments. I install many software silently, this is the first time I come across such behavior from a software.

Thanks

[allenheltondev (Allen Helton)]

It looks like the silent install isn’t quite supported yet

How to Distribute Postman in SCCM

Hi @AtakanTan and welcome to the community! Postman currently doesn’t have SCCM or MSI support for deploying the software to managed machines. The ability to deploy the client silently or centrally is something that has been requested by other users: Support multiple channels for installing/ updating Postman app. · Issue #4576 · postmanlabs/postman-app-support · GitHub. As a workaround, I’d recommend checking the GitHub thread above or look at the option brought up here: Deploy Postman …

Just curious, if you want it to install silently, then is number 2 really a problem?

[aristosv]

Thanks for your reply. If I want to install silently, number 1 is not a problem.
number 1 & 2 can be a combined problem. Since I don’t get any prompts I can’t select an installation folder, which is actually a more serious problem, because there are cases where I want to install on drive D:.

Number 3 is the most serious problem. Why would the program start after its installation? What’s the logic behind this? I know I installed it, I will start it at my convenience. No need for it to start automatically. This messes up the whole unattended installation for me.

Also, I use this command to install all my software.

Start-Process -Wait -FilePath $PSScriptRoot\software\Postman-win64-7.12.0-Setup.exe

Postman is the only software that ignores the -Wait option. And the weird part is that during its removal it does not ignore the -Wait option.

Start-Process -Wait -FilePath “${env:LocalAppData}\Postman\Update.exe” ‘–uninstall -s’

For someone automating software installations, this is very weird behavior of a program.

[allenheltondev (Allen Helton)]

I can see the use case either way.

You can always just add this to your powershell script

Stop-Process -Name "Postman" -Force

[aristosv]

That won’t work, for the same reason it ignores the -Wait option.
It does not wait for the postman installation to finish, and it tries to stop the process, so obviously it fails.

Here’s an example script with a few of the software including postman.

https://raw.githubusercontent.com/aristosv/software_install_powershell/master/ps1

[aristosv]

Even this is not working

$started = $false ; Do {If (!(Get-Process Postman -ErrorAction SilentlyContinue)) {Start-Sleep -Seconds 1} Else { Stop-Process -Name “Postman” -Force ; $started = $true }} Until ( $started )

[technique (technique@gimel.fr)]

Hi there,

As nobody supplied a solution, here is mine.
This is not a perfect installation. Let’s say it works at 99%.

First of all a few details about the problem and what I need:

• the postman installation program cannot do unattended installation
• the postman window is a non-standard one so it is (almost) impossible to control it automatically
• the postman program does not have any import switch to load some settings

These are pretty annoying limitations really! I had to do a lot of click here and there to install Postman on all my servers.
So here is what I do to install the tool and automatically import a collection.

1. I installed Postman manually and I created a collection with the requests I want to use. This populates folder %USERPROFILE%\AppData\Roaming\Postman\Partitions
   I backed up this directory for later use.

2. I wrote an Autoit script/program that runs the Postman installer. Note I am using version 10.12.0. When the program is installed it automatically opens its window.
   Autoit detects a window called “Postman API Platform”.
   It closes the window, hence the program.

3. I wrote a .bat script that does this:

• if %userprofile%\AppData\Roaming\Postman does not exist (it means it is not installed) so I run my Autoit script/tool
• when Postman is installed, I copy my backed up “Partitions” folder over the one that was created in %USERPROFILE%

This is it. As Queen said, it’s some kind of magic

Philippe Ferrucci

[docking-module-admi8 (Eartha Strickland)]

Dear Postman Community,

It sounds like you’ve encountered a few concerns with Postman’s installation process, particularly with silent installs. The fact that it installs without offering any command-line options like /s or /silent and defaults to AppData\Local\Postman without asking for a location can indeed be frustrating, especially when trying to customize the installation path. The automatic launch post-install is another issue that complicates silent deployments. To avoid these limitations, I would recommend trying installation management tools or installers that offer more flexibility and control during the setup process. These might help streamline installations for tools like Postman.

Thanks for Regards…!!