If you receive this error – Alert! iDRAC6 not responding. Power required may exceed PSU wattage.
Try these steps to resolve it:
1. Turn off your server and disconnect all power. This step is important as it clears the iDrac memory! Wait a minute or two before reapplying power.
2. Hit Ctrl-E when the iDrac boots.
3. The first option in the menu is “iDRAC6 LAN”. Highlight this option then push the spacebar to select it “on”.
4. Push ESC key save changes and exit.
IF THESE STEPS DO NOT WORK THEN PROCEED BELOW:
1. Download the latest version of Dell Systems Build and Update Utility(this updates the firmware for all the devices in your server) To find the latest version go to Dell.com search drivers and downloads for “Dell Systems Build and Update Utility” then arrange by date to see the latest version. The current search link is – http://search.dell.com/results.aspx?c=us&l=en&s=dhs&cat=sup&cs=19&k=dell+systems+build+and+update+utility&rpp=12&p=1&subcat=dyd&rf=all&nk=f&sort=-date&ira=False&~srd=False&ipsys=False&advsrch=False&~ck=anav
2. This will give you an ISO which you need to burn to DVD.
3. Boot your server to this DVD. This may require changing the boot order in your server.
4. When the DVD boots select “Dell Systems Build and Update Utility”.
5. Select firmware update.
You try to connect to a Windows 8 PC and receive the following error: To sign in remotely, you need the right to sign in through Remote Desktop Services. By default, members of the Remote Desktop Users group have this right. If the group you’re in doesn’t have this right, or if the right has been removed from the Remote Desktop Users group, you need to be granted this right manually.
If you have verified the obvious like turning off the firewall and making sure remote desktop is enabled then check the group policy. Group policies overwrite those settings and could be causing conflicts that you cannot see. This can either be a local group policy which you can check by running gpedit.msc. However, it could also be a domain policy which you need to run gpmc.msc from a domain controller. In my case someone had specified this setting and the group that they specified had been deleted. So remote desktop groups were being pushed down but with an invalid group.