Trying to install Portal Link on an Intune joined device. When I reach the section on the installer to enter a service account. The account I am using is an admin account and the credentials are correct. I am entering it as domain\user (ran whoami and verified it was the same). I get the error “Credentials are not valid”, however I used them to login.
Has anyone got this working in an intune environment?
does it work without the ‘DOMAIN\user’ form and just ‘user’ format? have a feeling i hit a similar problem
I tried with just the username and on-prem UPN but it did not work.
Try running:
on the machine you’re trying to install the portal on. Also try deadlinecommand pools, just to confirm that your install of Deadline can hit your database.
For the format of the username, if you use what whoami returns it should work.
This is what returns when I run those commands. Tried this on another machine and got the same results. Both return the same error when attempting to install.
Got it, so it’s just that command that’s kicking back an error exit code, not running deadlinecommand.
After digging into what causes that command to error out, is there an infrastructure running on your farm at the moment? That command should fail if there’s any stacks listed. If you go into a Monitor, open an AWS Portal panel and delete any and every entry listed there it should go through. If those are clear, go into the AWS console, and make sure there are no stacks listed there.
Before trying to setup Portal Link, the clients were setup as a direct connection to the repo. I installed an RCS but didn’t switch the workers over. If I change from a direct connection to RCS, when trying to install I get that infrastructure error. Nothing is in our AWS portal panel and nothing is setup in the AWS Console.
I setup a machine that was bound to the domain and direct connected to the repo. I was just able to finish the portal link installer. Are there any issues having the machine that is running this directly connected to the repo?Or should it be connected via RCS?
That setup should be just fine. The AWS Portal communications are through an SSH tunnel from the machine running the service to an EC2 instance.
Something I just hit - were you running the installer as an admin, and if so was your RCS certificate on a letter drive? Like Z:\certificates\deadline_rcs_cert.crt? It could be that the installer wasn’t able to pull it.
Running that “%deadline_path%”\deadlinecommand PreInstallValidationsForAWSPortalSetup as an admin showed the error, where running it as a regular user didn’t.
Thanks for the help Justin. I setup a domain joined machine along with a new repository an was able to get past this error.
