![]() ![]() That would form the following command (cmdlet - session - resourceuri): Once we have the session established, we can then use the Get-CimInstance cmdlets to query various properties by passing in a WSMAN/WinRM ResourceURI.įor example, if we just wanted to query the general BIOS properties, we could use the following URI: $Dracsession=New-CimSession -Authentication Basic -Credential $DracCred -ComputerName $DracIP -Port 443 -SessionOption $cimop -OperationTimeoutSec 10000000 Then using the above variables and new session object we can create a new CIM session to the iDRAC $cimop=New-CimSessionOption -SkipCACheck -SkipCNCheck -SkipRevocationCheck -Encoding Utf8 -UseSsl We can then create a new CimSessionOption object, which for the Dell Hardware the below works nicely $DracCred = new-object -typename -argumentlist $UserName,$SecurePass $SecurePass = ConvertTo-SecureString $Password -AsPlainText -Force #DELL IDRAC LICENSE IMPORT COMMAND LINE PASSWORD#Use some variables to store the IP, username and password for the iDRACĬonvert the username and password into a PS Credential This is accomplished by using the New-CimSession and New-CimSessionOption cmdlets. Before we can use this command however we first need to establish a remote CIM Session to the hardware. The key PowerShell command for querying is Get-CimInstance. However, since the latest iDRAC and CMC are built around WSMAN and DMTF standards, I prefer a more PowerShell only approach. I've been "playing" with some Dell hardware recently and as with everything I like to try and automate as many tasks as possible.ĭell have a really useful tool called Racadm which is a command line utility which you can call from a script to read and write various properties of Dell iDRAC and CMC (Chassis Management Controller).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |