@ srashidi,   We tried the script in 2 different machines. One having Excel 2013 and one having Excel 2016. On both machines script has worked fine and Inventory sheet is created. Seems to be an issue with excel installation or permission in your machine.   To see the exact error thrown by PowerShell while creating the excel object, un-comment the 3 rd line from below piece of code in the script ( line number 128 in the script) and then execute the same. This should capture the exact error thrown by the system.   Catch { Write-Host "Can't create Excel spreadsheet, is Microsoft Office installed?" # Write-Host "Error equals: ${Error}" Write-Host "Exiting..." Write-Host "" exit ... View more

@ srashidi,   We tried the script in 2 different machines. One having Excel 2013 and one having Excel 2016. On both machines script has worked fine and Inventory sheet is created. Seems to be an issue with excel installation or permission in your machine.   To see the exact error thrown by PowerShell while creating the excel object, un-comment the 3 rd line from below piece of code in the script ( line number 128 in the script) and then execute the same. This should capture the exact error thrown by the system.   Catch { Write-Host "Can't create Excel spreadsheet, is Microsoft Office installed?" # Write-Host "Error equals: ${Error}" Write-Host "Exiting..." Write-Host "" exit ... View more

Hi, It looks like scripts are using old PowerTool modules ("CiscoUcsPs"). Could you please try replacing the old PowerTool module references("CiscoUcsPs") with the new PowerTool module names which is "Cisco.UcsManager" and try to run. if you still face any issue, please let us know about the scripts you tried so that we can look into those. Thanks & Regards, Rishi ... View more

Hi Sam, You can use the below command for setting onetime boot device. Get-ImcOneTimePrecisionBootDevice | Set-ImcOneTimePrecisionBootDevice -Device "VICPXE" -Force Thanks, Rishi ... View more

Hi Kevin, You can use below cmdlets for adding SD Card in boot policy. In the below example, I have created a boot policy "testboot1" and added SD Card at order 1 and Virtual Media at order 2. Start-UcsTransaction $mo = Get-UcsOrg -Level root  | Add-UcsBootPolicy -Name "testboot1" $mo_1 = $mo | Add-UcsLsbootStorage -Order 1 $mo_1_1 = $mo_1 | Add-UcsLsbootLocalStorage $mo_1_1_1 = $mo_1_1 | Add-UcsLsbootUsbFlashStorageImage -Order 1 $mo_2 = $mo | Add-UcsLsbootVirtualMedia -Access "read-only-local" -LunId "0" -Order 2 Complete-UcsTransaction I have used ConvertTo-UcsCmdlet feature of powertool for generating cmdlets from GUI operation logs. You can also refer the same for any other cmdlets required. ... View more

Hi Heather, You can use below cmdlet for keyring regen. Add-UcsKeyRing -Name test1 -Regen true Use "Get-help Add-UcsKeyRing -Detailed" for getting the details about cmdlets and parameters. You can also use the ConvertTo cmdlet for generating Add command. Get-UcsKeyRing | ConvertTo-UcsCmdlet Thanks, Rishi ... View more

Hi,   First method is same as IMC as mentioned above. Just pass the get cmdlet to ConvertTo-UcsCmdlet and get the corresponding Add/Set cmdlet.   Another method is to record the XML log while doing the operations in HTML5 GUI and then pass the Logs to ConvertTo-UcsCmdlet and it will generate the corresponding cmdlets of the operations done on UI.   Steps to generate Logs from HTML 5 UI and passing it to convertto.   In the HTML 5 UI of UCSM, press Ctlr+Alt+Q twice. “Record XML link” will appear on the top of the screen, a little right from the center. Click the link and it will initiate the recording of GUI operations. Do the operations you want to do on UI. Once done with the operations on UI, click the same link which now says “Stop XML Recording”. On clicking the link, a popup will come to provide the name for xml log and save. Once the log is saved, same can be used with ConvertTo-UcsCmdlet as mentioned below.   ConvertTo-UcsCmdlet -Xml -LiteralPath C:\Users\administrator\Downloads\<RecordedFileName>   ... View more

ConvertTo-ImcCmdlet:-   Cisco IMC GUI does not support XML logging like UCSM. To generate Cmdlets, ConvertTo-IMC Cmdlet rely on the output of the Get cmdlet and generate Cmdlets to replicate the same object hierarchy.   Generate cmdlets for the specified MOs. Example 1– PowerTool C:\> Get-ImcRackUnit | ConvertTo-ImcCmdlet   #INFO: Review the generated cmdlets before deployment.   $rackUnit  = Get-ImcRackUnit -ServerId "1" | Set-ImcRackUnit -AdaptorSecureUpdate "Enabled" -AdminPower "up" -AssetTag "ABCD-1234" -ResetComponents "components" -UsrLbl "test-lbl2" –Force   Example 2 – Get-ImcBiosSettings -Hierarchy | ConvertTo-ImcCmdlet To Save the cmdlet output in file – Get-ImcBiosSettings -Hierarchy | ConvertTo-ImcCmdlet -OutputPath "C:/OutputFile.txt"   For some more details and a small demo on the same please refer below link. https://communities.cisco.com/docs/DOC-51321 ... View more