I happened to have a windows server core (2012 R2) VM to test this on. Running this cmd command worked fine. I got a pop-up window with an installation progress bar for each component until it was completely installed:
start "" /w c:\temp\SSMS-Setup-ENU.exe /Passive SSMSInstallRoot=c:\test\SSMS
My SSMS was installed to c:\test\SSMS\
. To start it, I ran the exe:
c:\test\SSMS\Common7\IDE\Ssms.exe
Be aware that all kinds of stuff does not work in server core (no GUI). Later versions of windows server like 2016/2022 are more stripped-down, so they may not be able to display the various windows until rebooted, if at all
SSMS installation errors and such all get written to a log file in your %TEMP%
folder automatically. Look at it if your installation doesn't succeed:
notepad C:\Users\USERNAME\AppData\Local\Temp\SsmsSetup\SSMS-Setup-ENU_20220727124801.log
If you continue to have issues, try running the .exe directly to attempt to display the install wizard, which might show errors etc:
C:\Users\> C:\temp\SSMS-Setup-ENU.exe
or try running in quiet mode to hide the UI altogether if it can only display black boxes:
start "" /w c:\temp\SSMS-Setup-ENU.exe /Quiet SSMSInstallRoot="c:\program files\SSMS"
start "" /w "Z:\RawPrograms\MS-Windows\Programming\Database\smss-setup-enu19.exe" /passive ssmsinstallroot="c:\program files\ssms"
?Start-Process
needs an actual file path as the first parameter, not "". You might be better off using call like:& ".\ssms-setup-enu19.exe" /Install /Quiet /Norestart FOO="bar" ...
. I also recommend adding/Logs log.txt
, then checking the log file to see what the installer failed on