Reputation: 348
I have tried to configure release management to work across different servers with untrusted domains using the steps described in the below article.
But when I tried to configure RM agent with ghost account, it was throwing error mentioned in the title. Please see the error screen attached..!!
I am searching for a solution for last few days...!!! Experts please help me.
Upvotes: 5
Views: 2807
Reputation: 2517
write it down as
Correct way:- http://(server):(port)
Incorrect way:- http://(server):(port)/ReleaseManagement
Do not write "/ReleaseManagement/" or any other URL segments after . This will solve your problem.
Upvotes: 1
Reputation: 41
Logging in as the shadow account may not be possible depending on how you setup the service account. Release Management site uses windows authentication so if you setup your credentials in Credential Manager on the agent server that will work. Just specify the fully qualified domain name for your Release Management server and your domain credentials for the RM server's domain.
Upvotes: 0
Reputation: 348
Finally the issue has been resolved by logging in as shadow account. Changed RM server name with IP in MS deployment agent....!!
Thank you very much @Daniel Mann for the tips you have provided.
Upvotes: 3