Just wanted to shoot you guys this message about the new agent. Not sure if this is by design or if this might be a bug of some type. I'm testing the new SAM agent installation in our environment and ran into a small snag. Luckily there is a workaround so it isn't too big of a problem. Here is the story:
I'm running the installation manually and at the "Orion Server Connection Details" screen I type in my Orion admin credentials. We use Windows domain accounts with admin rights to Orion but they don't work. I tried both the "domain\userid" and "userid@domain" formats with no success.
The result:
"Failed to connect to the Orion Server. The server name or address could not be resolved".
What threw me for a loop was the text "The server name or address could not be resolved". I could PING the IP address of the Orion server just fine and DNS was resolving the IP address and hostname of the Orion server just fine. Also, just in case, I used telnet to do a port check for 17778 too which was successful - so I knew this wasn't a network\firewall connectivity issue.
After a few minutes I tried a new approach - create a brand new local Orion user account with admin rights and try again. Sure enough that worked without any issues:
The result:
Just thought this was a strange problem and wanted to let you know about it.