For instance, PowerShell makes scripting WMI much easier, for example, try: Get-WmiObject win32_BIOS. PowerShell will achieve the same results as VBScript, but with fewer commands.As you may know, the Task Manager will display all the processes, yet with PowerShell you can not only list all processes, but also group them by company (Microsoft, HP and Roxio). On a good day such a script would even cure the problem – magic!To come back down to earth, let us start with a trivial example to illustrate the capability of PowerShell. With PowerShell you can run queries that are not possible from the GUI. I can foresee running PowerShell scripts that will diagnose server problems. Think of learning PowerShell as a more convenient method of configuring the server than using the corresponding GUI.PowerShell is free, therefore all you need is a spare half hour to experiment with the potent new Verb-Noun pairs at the PowerShell command line. When you want to interrogate your Microsoft operating system, three lines of PowerShell will replace twenty lines of VBScript. However, I believe that the pressing reason for learning PowerShell is for issuing WMI commands. One trigger for dabbling with Windows PowerShell is so that you can configure Exchange Server. Take the guess work out of which WMI counters to use when scripting the operating system, Active Directory, or Exchange Server. Fortunately, SolarWinds have created a Free WMI Monitor so that you can discover these gems of performance information, and thus improve your PowerShell scripts. Windows Management Instrumentation (WMI) is one of the hidden treasures of Microsoft’s operating systems. Guy Recommends: Free WMI Monitor for PowerShell List of PowerShell Cmdlets in Exchange 2010 Server.ISE (Integrated Scripting Engine) or GUI. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |