Lansweeper URL vs SSO

[bostjanc]

Hi guys.
Currently on trial mode.
We have an excel document where we wanted to put hyperlinks to assets, something like that "http://lansweeper:800/asset.aspx?AssetID=137" but if you click in this url inside excel document it throws you to login page of lansweeper, and that when you sucessfully login to page it throws you on first dashboard page instead of opening the desired asset.
Please advise how to solve this?
We have also tried enabling SSO but that is also not working.
We have added http://lansweeper to trusted sites in IE (version: 11.540.15063.0; OS: win10 pro) and then in IE under Security, custom level / user authentication / logon; we have chosen to AUTOMATIC LOGIN WITH CURRENT USER NAME AND PASSWORD, but it still throws you LOGIN page.
How to achieve that clicking on assests direct hyperlink would really throw you there and not to primary dashboard after you login?

[bostjanc · Accepted solution]

Well enabling authentication on IIS EXPRESS (https://www.lansweeper.com/kb/30/How-to-enable-authentication-for-IIS-Express..html) did the trick, now urls are being redirected ok.

Before doing that I also found a workaround if you have anonymous access you can get redirection working by compiling URL's to asset like this:
http://SERVERNAME/quicksearch.aspx?q=COMPUTERNAME
With that kind of URL's even after you login it throws you to the asset and not to dashboard.

[bostjanc]

Thanks for the reply.
-I dont seem to have Lansweeper on IIS.
-Even if I put http://lansweeper:PORT on local intranet sites if I click inside Excel document to a link:
EXAMPLE: http://lansweeper:PORT/asset.aspx?AssetID=137

It throws me to login page (by the way we have disabled BUILTIN ADMIN account because we don't want everyone accessing lansweeper), after we login we are thrown to default/dashboard site instead of redirection to ASSET: http://lansweeper:PORT/asset.aspx?AssetID=137

PRINTSCREEN:
https://drive.google.com/file/d/0B_Cst0SCMGxWTmRpUGVfMEVDaHM/view?usp=sharing

[AZHockeyNut]

I think it might work better in the "Local Intranet Sites" versus the Trusted sites? here is a screen cap of my setup with the app in its own folder and not at the root of a site. I am showing the authentication settings on IIS for you.