Seems like the wagon got away from the horse and took off down the path on its own. The underlying issue with this is all the 'maybes' and 'supposed tos'. Some info indicated that there are \Program Files differences, so maybe there are just some files to move.
Therefore I am not sure if the PBIRS install just updates the existing ReportServer DB installation or if a whole new DB is created. I did note in the current online PBIRS documentation (all added 6/12/17) that there is supposed to be a 'migration' required to go from straight SSRS to PBIRS, but then all the Next Steps links went to regular SSRS topics. I may actually go with the 180-day eval version of the install once my TEST and PROD environments are upgraded to SQL 2016 and stable, starting with an install in TEST. I will provide any updates I find about VLSC product listing info/product key location when I find something. I am moving forward with my SQL Server 2016 Enterprise upgrade (doing TEST right now) and have created a separate project for the PBIRS installation which I will be pursuing ASAP. Make sure that the installation account is a member of the.
My IT manager confirmed the same thing - no item in the product list for Power BI Report Server. The license key for Power BI Report Server, check where you can find the Power BI Report Server key.
