Tag Archives: Windows

Tracking Down AzureAD Device Sign-Ins

I recently needed to track down who had recently used a device bound to AzureAD. We don’t tend to make use of the Primary User field, since our devices tend to be handed out in bulk to large groups of people at once, rather than one-at-a-time. This meant I had to track down who was using which device in a more roundabout method.

To accomplish this, you’ll need to use both Microsoft Graph and Microsoft Endpoint Manager.

Lookup the Device ID

First you’ll need Azure’s device ID for the computer.

Go to https://endpoint.microsoft.com

Click Devices on the left then Windows Devices.

Search for the device you are looking for.

Click on it

In the address bar of the browser, the last part of the URL will be the device ID. Select and copy it.

Query Device Sign-In Information

Now that you have the Device ID, you can lookup the login history using Microsoft Graph.

Go to https://developer.microsoft.com/en-us/graph/graph-explorer

Make sure to sign into graph, or you’ll only see the sample data.

Query type: GET

Version: beta

URL: https://graph.microsoft.com/beta/deviceManagement/managedDevices/[device ID here]

Click Run Query

You’ll only see the first several lines, which probably won’t show the logged on users.

Click the Expand button

Scroll down to where it says usersLoggedOn then select and copy the ID inside of the quotes.

Go back to Endpoint Manager

Click Users on the left.

Paste the user ID into the search field. This should tell you the name of the user who logged into that device. If there were multiple people recently signed in, they’ll all be in the usersLoggedOn array.

Windows 10 High CPU Usage Fix

I noticed recently that Windows 10 was using a high amount of CPU.

Checking Task Manager, could see this was coming from Runtime Broker.exe

A bit of Binging around and I found this solution posted in the Microsoft forums.

Click Start->Settings

Click “System”

runtimebrokerfix1Click “Notification & actions”

runtimebrokerfix2Finally turn off “Show me tips about Windows”

runtimebrokerfix3Runtime Broker should immediately go back to normal.

I’m sure Microsoft will patch this soon, but this should get you by until then.

UPDATE 2016-03-21:

I haven’t had this problem since this post, but it did crop up again in Insider Preview Build 14291.rs1_release.160314-2254.

Repeating these steps, toggling the “Show me tips about Windows” on the off again seems to have fixed it.

I am, however, also seeing high WMI Provider Host cpu usage. It’s constant around 5% on 3 virtual CPUs.

32/64 Bit drivers for Windows Printing

As it’s kind of tricky, here’s the process to get 32 and 64 bit drivers working for Windows 7 clients from a 32-bit Server 2003 print server.

First, sign into the print server. Download the HP 32 bit Universal PCL print driver
Run the self-extractor to unzip the printer drivers
Go to the properties of one of your printers
On the Advanced Tab, click the New Driver button
Choose the driver extracted earlier

Now got a Windows 7 64 bit client
Download the HP 64 bit Universal PCL print driver
Run the self-extractor to unzip the printer drivers
Browse to \[print server]
Click the “View Remote Printers” button just below the address ┬ábar
Right click on the printer you installed the Universal driver for
Windows will tell you that no driver is available and ask if you’d like to install one.
Click yes and browse to the driver you extracted earlier
The printer should now install in Windows 7 64 bit

Finally, go back to the 2003 Server
Go to the properties of each printer
Under the advanced tab, click the dropdown list with the driver names
Choose the Universal PCL driver
This will automatically use both the 32 and 64 bit drivers

**UPDATE** The HP Universal driver may mess with your default tray and tray paper settings

**UPDATE 2** It turns out that the Universal driver is setting the wrong paper type which is the cause of the default tray problems.
To fix this:
Go to the printer properties then Printing Preferences
Go to the Paper/Quality tab
Make sure Paper Type is unspecified