We’ve just started to rollout Deadline 3 across our network…some 75 odd machines…is there a unattended installation solution available??
Shane
Hi Shane,
In the future, please post any 3.0 related problems or discussions to the 3.0 beta discussion forum.
Here’s what we used to deploy Deadline 3.0 on our farm (this is for the 64 bit installer):
msiexec /passive /i \path\to\DeadlineClientInstallerWin64.msi REPOSITORYINSTALLDIR=\your\repository LICENSESERVER=yourserver
Our machines already had .Net 2.0 installed. If your machines don’t have this installed already, you’ll have to do this first.
Cheers,
- Ryan
Cheers, exactly what I was after
Shane
Hi,
I’ve been looking at this line for the longest time and I can’t seem to figure it out.
Does running this require an existing Deadline installation, essentially run this command on every Slave on the network with the Command Script Job script?
msiexec /passive /i \path\to\DeadlineClientInstallerWin64.msi REPOSITORYINSTALLDIR=\your\repository LICENSESERVER=yourserver
Say I’m installing Deadline for the first time on a 100-server farm, what would you recommend for an unattended solution?
Does running this require an existing Deadline installation
Yes, simply.
I have created a little utility that runs in the background on all our machines which allows me to perform remote command invocation, similar to psexec, except it executes within the context of the current user, which gives us access to the network drives, but that’s another story entirly…
Let’s see if we can break this down for you…
msiexec /passive /i \path\to\DeadlineClientInstallerWin64.msi REPOSITORYINSTALLDIR=\your\repository LICENSESERVER=yourserver
msiexec - is windows installation service. Look for any installer with msi (and even many exe) and they will be using this type of package…
/passive - instructs msiexec to execute without user interaction, ie unattended deployment.
/i - instructs the installer that we want to install the package, as apposed to uninstall or update…
\path\to\DeadlineClientInstallerWin64.msi - this is the location of the installation package on your network. It will need to be in a location that is accessible, obviously…
REPOSITORYINSTALLDIR - is a installation property, which should point to the deadline repository that you have already created
LICENSESERVER - is another installation property, which should point to server where you have you license server setup.
If you have nothing else, take a look at psexec. It is really simply to wrap it in a batch file or shell script to have it automatically push the installation out to the servers, or if you are lucky enough to have a deeper understanding of active directory, you might be able to use that instead.
I’ve come to use the msiexec command line options a lot more to perform automated installations of almost all our software onto our workstations and servers. I wish more installers offered this convince.
I hope all this helps!
Shane
i just want to deployment the deadline client in our renderfarm.but i found it’s diffculty to install the deadline services as startup if i use the msiexec /passive /i \path…\deadlineclient.msi …
i can’t find how to set up the install launcher as service option in cmd.
i use the following command to install the all render client . it’s can start services with user and pass
msiexec /passive /i \soursefolder\DeadlineClientInstallerWin64.msi LAUNCHERSERVICEACCOUNT=username@domain LAUNCHERSERVICEPASSWORD=password REPOSITORYINSTALLDIR=\deadlineserver\DeadlineRepository LICENSESERVER=portnumber@license serverLAUNCHERSERVICE=“1” LAUNCHERSERVICELOGON=“1”
Just to confirm, is the command you posted working for you now? We are aware of a problem that sometimes prevents the service account from being created properly, but we are working on this for the next release.
Cheers,
- Ryan
yes, i push the command to all client (160 blades server) , it 's ok.
i just want to push the clint as service startup, begin i edit the msi files with orac,but failed to push the client .
when i found the command in the support webpage, i think i find how to resolve the problem.