It was easy to launch Resource Monitor by simply hitting the Windows key on your keyboard, then typing the first few letters of the application’s name, and hitting enter (or maybe arrow-keying down a couple of entries, if there were ambiguous search results). In Windows 8, that shortcut no longer works by default, but Resource Monitor is not gone either. Some other websites out there have documented the fact that you can launch Performance Monitor navigating to the Performance node. On the Performance page, there is a link to open Resource Monitor; this spawns Resource Monitor into a separate window.
I’ve recently been trying to learn more about Active Directory Managed Service Accounts (MSAs), which are basically self-managing service accounts. You don’t have to manage the Service Principal Name (SPN) or password for MSAs, which makes them very good choices for running applications. You can read more about MSAs on Microsoft Technet at this URL.
Similar to MSAs are local “virtual accounts.” These do not have password to manage, and they can automatically manage their SPNs. These are not within the scope of discussion, however there are some links in the References section, which might help you to get more information about them.
Creating a Group Managed Service Account with PowerShell
I’ve been trying to create a MSA using PowerShell using the command below, but I kept getting an error. There is a Technet discussion forum post that addresses this same issue. In my scenario, I was running the command on a Windows Server 2012 domain controller.