Connect-HPBIOS using iLO IP address



Connect-HPBIOS using iLO IP addressFollow below steps to Connect-HPBIOS target server using an iLO IP address.Create WinpPE ISO image using New-HPBIOSCustomWinPEImage, E.g., -------------------------- EXAMPLE 1 -------------------------- PS C:\> New-HPBIOSCustomWinPEImage -OutputImageType ISO_File –OutputImage "C:\WinPE.iso" –Log | fl StatusType : Ok StatusMessage : WinPE image path: C:\WINPE.ISO NewWinPELogPath : C:\New_HPBIOSCustomWinPEImage_2015021210464591.log This command creates a new WinPE image with .iso file output. -------------------------- EXAMPLE 2-------------------------- PS C:\>New-HPBIOSCustomWinPEImage -OutputImageType USB_Drive -OutputImage "D:" –Log | fl StatusType : Ok StatusMessage : WinPE image path: D: NewWinPELogPath : C:\New_HPBIOSCustomWinPEImage_2015021209451002.log This command creates a new WinPE image with USB drive output. 2) If the customized WinPE image is created using the .iso file option, modify the standard boot order in the server’s BIOS to boot from CD-ROM. If the customized WinPE image is created using the USB drive option, insert the created USB media into the target server. Modify the standard boot order in server’s BIOS to boot from USB drive.The standard boot order can also be modified from the iLO web→Virtual Media→Boot Order page. If the iLO cmdlets are installed, the Set-HPiLOOneTimeBootOrder cmdlet or the Set-HPiLOPersistentBootOrder cmdlet can be used to modify the boot order.3) Boot up the target server and enter HP customized WinPE environment. Booting up the server can be done using the iLO web→Virtual Media→Boot Order page. If the HPiLOCmdlets are installed, the Reset-HPiLOServer cmdlet can also be used to boot up the server. NOTE: When the server boots up into the HP customized WinPE environment for the first time, a one-time automatic reboot might occur and then it will automatically boot up into WinPE again.4) Once the Target Server boots the WinPE image insure that the WinPE console comes up on the Target Server. You can check this from the iLO Integrated Remote Console or using an SSH client like PUTTY connecting through iLO. 5) Before using Connect-HPBIOS insure that both the Management Client and Target Server networks are reachable on the network (PING). Make sure that if you have any IPv6 addresses on the Management Client disable or remove it as BIOS might use those address for accessing share and might result in failure of connection. – Need to be validated and remove this step.Insure that both Client and Server firewalls are disabled OrIf a firewall needs to be used then add a windows firewall exception for Remote WMI Connections using this windows command:Click Start, click Run, type cmd and then press Enter.At the command prompt or PowerShell, type netsh advfirewall firewall set rule group="Windows Remote Managrement" new enable=yes, and then press Enter.At the command prompt, type exit, and then press Enter. Run “Local Security Policy” go to Local Policies -> User Rights Assignment click on the policy "Deny access to this computer" settings and remove any users or groups from this list that need to use these cmdlets.9) On the WinPE prompt check whether Management Client IP address is reachable via Ping. If the Ping is failing work with your Network Administrator to resolve any issues. 10) Execute Connect-HPBIOS cmdlet with iLO IP address. If all the above conditions are met then connect will succeed and return the session object. 12.2 Connect-HPBIOS using a Windows Server IP addressUse the following steps to modify BIOS settings on a Windows Server OS system using the server IP address.1) Insure that both Client and Server firewalls are disabled Or If a firewall needs to be used then add a windows firewall exception for Remote WMI connections using this windows command:Click Start, click Run, type cmd and then press Enter.At the command prompt or PowerShell, type netsh advfirewall firewall set rule group="Windows Remote Managrement" new enable=yes, and then press Enter.At the command prompt, type exit, and then press Enter.2) On the Windows Server check to see if Management Client IP address is reachable (PING). If the Ping is failing work with your Network Administrator to resolve any issues. 3) Check whether Windows Management Instrumentation (WMI) service started on the Windows Server. 4) Check whether File Share Service is running on the Windows Server. If not started need to be started on the Windows Server from cmd using : net start "Server".5) Verify that the default net share is available using the following procedure.a. Open a command line or PowerShell window.b. Run the net share command and make sure the Windows default shares of C$, IPC$, ADMIN$ are listed as shown.c:\ >net shareShare nameResource Remark----------------------------------------------------------------------C$ C:\ Default shareIPC$ Remote IPCADMIN$ C:\Windows Remote AdminThe command completed successfully.If these shares are not listed, use the net share command to create them. For detailed help for net share, enter net share /?.6) Check if the network of target server is accessible from management client.7) Execute Connect-HPBIOS cmdlet with Windows Server IP address. If all the above conditions are met then connect will succeed and return the session object. 8) Using the step-3 session object the BIOS cmdlets can be run. . ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download