Applications are not installing using provisioning package

Question

Hi, we are using provisioning package in our environment. I have build a provisioning package to install below applications and it was successfully deploying app. However, I am renewing the package with the updated version of below app and both the below apps are not getting installed if i run the package at OOBE level.

Docker : Below command is used to install.

cmd /c "dockerdesktopinstaller.exe" Install --quiet --accept-license

VS professional

cmd /c copy "vsprofessional.exe" %Temp% && cmd /c %temp%\vsprofessional.exe --installpath C:\VS_Pro ^ --includeRecommended --quiet --wait

cmd /c copy vsprofessional.exe %Temp% && cmd /c %temp%\vsprofessional.exe --quiet

Please help me, what is wrong with the above command? Any help will be highly appreciated.

Just FYI, i have another .exe installer like git, pgadmin, vscode. All these are successfully being installed.

Answer 1

Hi Ritesh Sharma,

Thank you for posting in the Q&A Forums.

1. Docker Installation Command

Your Docker installation command uses dockerdesktopinstaller.exe, which appears to be for the Windows version of Docker Desktop. This command format should be correct, but make sure:

The dockerdesktopinstaller.exe file does exist in the preconfigured package and is in the correct path.

The --quiet and --accept-license parameters are supported by the Docker Desktop installer. Typically these parameters are used for silent installations and automatic acceptance of license agreements, but make sure that they are compatible with your version of the installer.

2. Visual Studio Professional Installation Commands

For Visual Studio Professional installations, there are several potential issues and improvement points:

Path and parameter separators: On the Windows command line, the path separator should be a backslash (), but you have a mix of forward slashes (/) and backslashes in the --installpath parameter. While the Windows command line can usually handle this mix, it is best to be consistent.

Escape characters: In PowerShell scripts, if you need to use ^ directly on the command line as part of an argument (although it looks like an attempt to escape -- in this case, it's not necessary), it's usually not needed (or may not be supported). However, in the cmd environment, ^ is used as a line continuation character, but the usage here seems redundant.

The copy command: you used the copy command twice, the first time with the --installpath argument, the second time without. If the second install command (without --installpath) is a backup or special case, make sure this is expected. If not, you may want to remove the duplicate commands or merge them.

Best regards

NeuviJ

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.