Resetting ILO's from Command Line

For resetting ILO's from Command Line.
It saves a lot of time when working remotely

You can use  telnet or plink utility to login to the ILO.

HP Servers

Telnet or Plink to the ILO ip with ID/Password.

telnet x.x.x.x  or Plink  userid@x.x.x.x -password xxxxx

 

it will take you to the prompt :

</>hpiLO-> cd /map1
status=0
status_tag=COMMAND COMPLETED

</map1>hpiLO-> reset
status=0
status_tag=COMMAND COMPLETED
Resetting iLO.

CLI session stopped.

 

You can even shutdown/restrat the server from here.

For more commands   type "help"

Dell Servers

cmd> Telnet xx.xx.xx.xx 23/22

Login with the remote console userID/Password.

>Racadm racreset

IBM Servers

cmd> Telnet xx.xx.xx.xx 23/22

Login with the remote console userID/Password.

>resetsp

 

 

Azam

http://social.technet.microsoft.com/profile/mohdazam89/?type=forum&referrer=http://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverpowershell

Reparing WMI

When the WMI gets corrupted. You wont be able to install patches and the system will not work as expected.

Below is the recommendation from microsoft for rebuilding the reposittory

Actions to try
First try the following actions to see if they resolve your issue:

a. Re-register all of the dlls and recompile the .mofs in the wbem folder and re-registering WMI Service and Provider. You can use the following script by saving to txt file then renaming to .bat and running from command prompt with admin right and changing focus to following directory: C:\Windows\System32\Wbem.

@echo off
sc config winmgmt start= disabled
net stop winmgmt /y
%systemdrive%
cd %windir%\system32\wbem
for /f %%s in ('dir /b *.dll') do regsvr32 /s %%s
wmiprvse /regserver
winmgmt /regserver
sc config winmgmt start= auto
net start winmgmt
for /f %%s in ('dir /s /b *.mof *.mfl') do mofcomp %%s

b. Reboot the machine and test WMI
Next, check the repository for consistencies:
For Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2, you can run winmgmt /verifyrepository from a command prompt.
For Older OS like Windows XP and Windows Server 2003 run: WmiDiag tool with the checkconsistency option. For example: WmiDiag checkconsistency
If repository is found to be inconsistent:
a. For Vista and newer, run from elevated command prompt:
Winmgmt /salvagerepository
Note this command will take the content of the inconsistent repository and merge it into the rebuilt repository if it is readable
If the above doesn’t work, then run:
Winmgmt /resetrepository
Note this will reset repository to the initial state when the OS was first installed
For Windows XP and Windows Server 2003, there are no built in switches to rebuild the Repository, so you must do it manually.
Warning: Rebuilding the WMI repository has resulted in some 3rd party products not working until their setup is re-run & their MOF re-added back to the repository.
If /salvagerepository or /resetrepository does not resolve the issue, then manually rebuild repository

1. Management Instrumentation (WMI) Service to disabled
2. Stop the WMI Service; you may need to stop IP Helper Service first or other dependent services before it allows you to stop WMI Service
3. Rename the repository folder: C:\WINDOWS\system32\wbem\Repository to Repository.old
4. Open a CMD Prompt with elevated privileges
5. CD windows\system32\wbem
6. for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
7. Set the WMI Service type back to Automatic and start WMI Service
8. cd /d c:\ ((go to the root of the c drive, this is important))
9. for /f %%s in ('dir /s /b *.mof *.mfl') do mofcomp %%s
10. Reboot the server

Source : http://blogs.technet.com/b/askperf/archive/2009/04/13/wmi-rebuilding-the-wmi-repository.aspx