One of the most interesting things about Power BI is that it covers a wide range of areas. Therefore, it can help a wide range of different users to analyse and understand their businesses easily. For instance system administrators can use Power BI to analyse their Microsoft Windows Active Directory. As a matter of fact, Power BI and Active Directory can work together very nicely so that a system administrator can create high level reports and dashboards.
In this , we’ll create a report of the following charts:
Total number of computers by Operating System/Service Pack
Total number of computers by year and Operating System
Total number of computers
Print pages per minute by printer
Total number of printers by year and driver name
As a system administrator you can create heaps of other useful reports.
On Power BI Desktop click “Get Data” then click “More”
Click “Other”, click “Active Directory” then click “Connect”
Enter a Domain name then click OK
As you can see there are 374 tables you can select to create heaps of reports. In this post I use “Computer” and “PrintQueue”
When we are talking about using a new technology we need to understand it first. Power BI Personal Gateway is not an exception. Despite you can easily install the Power BI Personal Gateway, knowing the following important points is crucial. I believe the following 5 points are significantly important to prevent you getting into troubles with the installation process as well as using the gateway:
Power BI Personal Gateway is only available on 64-bit Windows operating systems
Once you install Power BI Personal Gateway you don’t need to install another one as just one gateway works for any number of supported data sources
You CANNOT install the Power BI Management Gateway on the same machine as Power BI Analysis Services Gateway
If you’re trying to install the Power BI Personal Gateway on a network having Active Directory make sure that the account you’re using to install the Power BI Personal Gateway is able to “Logon as a Service”. In some cases the “Logon as a Service” policy is prevented on Active Directory for security reasons. The “Log on as a Service” should be applied to those accounts that are NOT under an Active Directory. So even if you are using a Local Account you should make sure that the local account is added to the local security policy “Log on as a Service”. If the account used to install the Power BI Personal Gateway is banned from the “Log on as a Service” policy you’ll get “Service ‘Data Management Gateway Service’ (DIAHostService) failed to start. Verify that you have sufficient privileges to start system services.” error message.