In more organization we use hundreds of Compaq/hp servers using RILOE, RILOE-II, ILO. RIB.CPL was only for RILOE; however we have successfully used it "sometimes" on RILOE-II's. I don't know why it works but sometimes it does - other times it says that it can't find sm2user.dll and asks me to install the management agents. Of course they are already installed on everything. Furthermore, I should mention that when RIB.CPL does work on RILOE-II's it's functionality is VERY limited. I think we can only set the IP, Subnet Mask, and *possibly* the user account. But you cannot set the Gateway address or change the nic to FULL DUPLEX. You can choose between DHCP and a hard IP as well as change from 100Mbps to 10Mbps. I have read the response by the "Junior Yharte" and he claims there are 4 ways to make changes on an ILO and he is correct - however F8 requires physical access, and the other 3 methods mean the ILO has to be ALREADY configured!!!! But THAT IS the problem. Some of our ILO's are not configured!! We have servers all over the place and often times we don't have server Admins in those locations that can be available outside of our hours of operation! It is very difficult to get with a user after 7pm and try to walk them through blindly setting up a remote board. Another interesting note about ILO's is that gateway addresses are far more important than they are on RILOE's and RILOE-II's. I don't know why this is but, in our network we use something called HSRP gateway addresses that allow switch redundancy for our teamed NICs on our servers. However, an ILO must be configured for the correct gateway before you can connect to it - even though you may already be able to ping it.
Well, I thought I would do a brain dump on remote boards since I've used them a lot. In any case, I think it is a WRONG to not be able to remotely configure these boards through the OS. I am petitioning HP/Compaq to reconsider this position - it has been a real PITA for our organization when we went through our servers trying to verify remote board connectivity and we couldn't even try a different IP on server that were not responding.
