I must say i never used the silent installer however i do know it installs the “Stand alone” package (which installs portal, enterprise and server at once).
You can also install it through the gui –> just select and install “Stand alone” if/when there’s no other SolidCP module installed yet.
To do this with silent installer:
SilentInstaller.exe /cname:StandaloneServer /ServerAdminPassword:mypassword
Other available variables for StandAlone server:
So I’ve got the silent install option working ish… the command I use is:
“C:\Program Files (x86)\SolidCP Installer\SolidCP.SilentInstaller.exe” /cname:Standalone /ServerAdminPassword:P@ssw0rd /DbServerAdmin:sa DbServerAdminPassword:SQLP@ssw0rd
However other than the “/cname:Standalone” parameter and value, the rest don’t work. I’ve tried using double quotes around the values, as in the value used in the WebPI feed, but that didn’t work either.
Loading the portal on first use asks for the password for both serveradmin and admin.
If I installed SolidCP using the GUI and provided SQL credentials, such as ‘sa’ then the connection under ‘Servers’ would be SQL instead of Trusted.
Hmm your right the other values don’t seem to work.
thats odd tho as i can see them defined in the source..
In some archives i do see: /passw:”mypassword” that should work but i can’t find that back in the code at all.
Once one of my Dev environments frees up i will check it out (currently busy with Sharepoint and Skype for Business codes).
Thanks, this works.
I tried to read the code, but without any C# knowledge I wasn’t getting far.
To add detail, I tried to cheap by using the stored procedures to change the password, but the SP requires an encrypted password and I have no idea how to encrypt it.
If you do get this sorted please update this thread, that way I can add the extra arguments in.
I have been working on a script for SolidCP to enable easy installation and setup of everything on new servers.
The script is still being tested, but as part of this I wanted to include the installation of the SolidCP components when installing other software and features on the server (such as IIS, FTP, MySQL, Perl, Python, MSSQL etc), so I have managed to find out the following so far:-
webip # General – The IP Address that you want the SolidCP Component to be bound to in IIS
webport # General – The Port Number that you want the SolidCP Component to be bound to in IIS
webdom # General – The FQDN that you want the SolidCP Component to be bound to in IIS
uname # General – The Service Name account that you want to use for your SolidCP deployment
upassw # General – The Service Name password that you want to use for your SolidCP deployment
udomaim # General – The Domain Name that you want to use for your SolidCP deployment – *** If this is used then the above username and password will be added to Active Directory ***
passw # Server Password – Used on the Server and Enterprise Server Components ONLY
dbname # Enterprise Server – Database Name
dbserver # Enterprise Server – Database Server (IP or Hostname)
dbadmin # Enterprise Server – Database Username
dbapassw # Enterprise Server – Database Password
esurl # Portal Server – Enterprise Server URL – Used on the Portal Installation Component ONLY
cname # “Server”|”Enterprise Server”|”Portal”|”WebDavPortal” – This is the component you want to install
So for example if you wanted to deploy the Server component on a machine with the password of MyLittleServer you would issue the following via a DOS prompt:-
cd “C:\Program Files (x86)\SolidCP Installer\”
./SolidCP.SilentInstaller.exe /cname:”Server” /passw:”MyLittleServer”
This would install the server component on the machine you issued the command from as long as the SolidCP Installer application was already installed on the machine.
The most important thing to remember is the switches need to have the variable contained in double quotes and rather than using an = sign to specify the value you need to use the :(colon) sign.
The script is released and available for people to try out on new server installations.
You can download it from here:-
There is also an Auto Upgrade Script which will upgrade your WSP enviroments to SCP, that can be downloaded from here:-
There is a video guide explaining how to use the Auto-Upgrade PowerShell script here:-
Please feel free to let us know how you got on.
- Views3669 times
- Answers10 answers