Asking Jeff for frames...

from: Deadline-{version}-windows-installers.zip
install: DeadlineRepository-{version}-windows-installer
MongoDB prompt, install or connect to an existing one
Create Encryption certificates & password
Create Admin User Credentials
install process about 5mins

from: Deadline-{version}-windows-installers.zip
install: DeadlineClient-{version}-windows-installer
prompt: check Set full read/write access for files for all users
prompt: check Remote Connection Server (required for AWS portal)
prompt: Connect to local repo using previously created Certificate and Password
Check the TSL certificate has Read/Write Permissions
Create User Admin
Prompt: Install Launcher as Service, unchecked
Prompt: RCS user and ports, accept defaults
Generate HTTPS certificates & pass
Installation process 10 mins

check both certificate files have Full Control access for the active user:
C:\DeadlineDatabase10\certs\Deadline10Client.pfx
C:\Program Files\Thinkbox\Deadline10\certs\Deadline10RemoteClient.pfx
search for DL Launcher app and open it
Launcher and Monitor might fail for on the first launch, due to file permission. If permissions are set well, all should work on the second launch.
Right click the Launcher taskbar icon and start the worker to check its also working.
The title window from both Monitor and Worker should be pointing to C:\DeadlineRepository10, and the worker should be listed as idle on the monitor’s worker list

Launch RCS through the launcher if not already running
Monitor: click Switch Server, and switch to remote
add the IP of the current machine along with the certificate previously set (ProgramFiles)
reboot the Worker
The title window from both Monitor and Worker should be pointing to {ip_address:port}

log in to AWS console with a root user or whatever works for you
Navigate to Access Management > Users, add user
The User policy is more important than the name, but be descriptive enough
Select Attach Existing Policies Directly
search for ‘admin’ and attach ‘AdministratorAccess’ policy
Create Access Keys, go to users and select the user, look for create key, select first option (CLI), ignore the recommendation and download and keep the csv

in the AWS console
Navigate to Access Management > Users, add user
The User policy is more important than the name, but be descriptive enough
Select Attach Existing Policies Directly
search for ‘AWSThinkbox’ and attach ‘AWSPortalAdminPolicy’ and ‘DeadlineResourceTrackerAdminPolicy’
Create Access Keys, go to users and select the user, look for create key, select first option (CLI), ignore the recommendation and download and keep the csv

Make Sure Monitor and RCS are running. The installer may fail the first time, try again:
from: Deadline-{version}-windows-installers.zip
install: AWSPortalLink-{version}-windows-installer
For the account user and pass, use your windows administrator user and MS account password. Or whatever works for u
Skip IP override
Allow firewall ports
AWS credentials, insert Keys from AWS Admin User csv.
Confirm Windows Credentials
skip Root Directories
install
on Windows Services, check for 2 AWS services running

https://www.youtube.com/watch?v=tgelsbaXpYE&list=PLhYsMveWZwEQ2DokGzhqaMJhIuOEJivWD&index=1
https://docs.thinkboxsoftware.com/products/deadline/10.1/1_User%20Manual/manual/download-deadline.html

Alex Doss