Client has a three server Remote Desktop Services environment running on Server 2016 (3 Session Hosts, 1 License Server/Connection Broker/Gateway). Server 1 runs all services, Servers 2 & 3 run only Session Host. Also running on Server 1 is a SQL Server 2012 instance. Logins currently disallowed on Server 1; Servers 2 and 3 service user logins currently. User Profile disks are enabled, pointing to a common share mountpoint on Server 2.
Client requested installation of a second SQL Server 2012 instance, Reporting Service Native mode only, to host another reporting services site.
Things I noticed right off hand:
mstsc /admin /v:server1 logs me in with a temporary profile. I figure I'll tackle this problem later, since getting the new RS instance is the "priority". I go through a typical SQL 2012 RS installation, apply service pack 4, and then go through the configuration process. New RS instance use a different host header to direct traffic to, server1alias.mydomain.com, rather than server1. All of this seems to work as expected.
All this appears to work as I expect... until I attempt to connect to http://server1alias.mydomain.com/Reports or http://server1alias.mydomain.com/ReportServer, I am repeatedly prompted to login credentials (yes, I am supplying the correct username and password ;) when I attempt this).
Upon further investigation, it appears the "NT SERVICE\ReportServer$INSTANCENAME" account, when the Reporting Services instance is started, like the Administrator account, "logs in" with a temporary profile. I see a "Temp.NT Service.001" directory under c:\users. Also, if I attempt to restore a encryption key through the RS configuration utility, I receive an error message telling me the profile is "temporary".
If I go into the user profile list (Control Panel -> System and Security -> System -> Advanced -> User Profiles) I can see "NT Service\ReportServer$INSTANCENAME" is listed as a "Local" "Temporary" profile.
I am assuming this has something to do w/ this server also being a Remote Desktop Services Session Host, since I have installed dozens of MSRS instances over the years and have never seen this issue before. This is the first time I've been asked to establish a new MSRS instance on a server which also serves in a RDS capacity.
Short of uninstalling the session host service, does anyone have a suggestion on how I can go about fixing this problem?