I'm not very familiar with IDSU. However, when I try this on my DQ67EP (same BIOS, same IDSU version) I get pretty much the same error. The end result is, I can't tell if it's enabling KVM or not. I'm going to see if I can find someone who knows IDSU a little better than me.
In the mean time, there are a few alternatives to get KVM working. First, VNCViewer Plus is very easy viewer with IDEr support. It has a 90 day trial, but then you ahve to pay. One free option is to use a free VNC viewer and use this UCRD to enable KVM. Final free option I'm aware of is to use Managability commander. It's similar to IDSU so that might suite you're needs.
Thank You. I`ve solved this problem with Russian comunity and "Manageability Commander Tool". This one tool shows me that password that i want to install for remote kvm is bad. System Deffense gives very poor error text. Also it allows to enter passwords with mor than eight symbols.
Now i`ve got some other problems with this motherboard.
1) "Boot to BIOS" point anyway doesn`t work for me (System Deffense, Manageability Commander Tool, Radmin)
The error text in Manageability Commander Tool is:
"Call SendRemoteControl returned error:FAILED_WEB_CALL
BIOSSetup not supported"
2) Adaptec ASR-5405 Raid Controller doesn`t work in x16 slot. Motherboard doesn`t boot with this controller. With Intel PRO/1000 PT Desktop Adapter in this slot motherboard boots normaly, network adapters woks fine.
I just finished working on ISDU v2.0.3, it's available here.
Please give it a try and see if it fixes your problem. I am also looking for any other feedback.
This morning I worked on ISDU some more. Fixed network discovery issues and problems with large font support. Same link as before, still labeled v2.0.3 but the readme.txt file has more chages. Anyone using ISDU, please try it and comment!
My experience as a Linux user is that I needed a Windows program (Manageability Developer Tool Kit) to enable KVM. I used it to remotely connect to the vpro box and enable KVM (including the fixed 8-char password). Only after that, the box showed port 5900 open. I think it's weird that you can say "KVM: enable" in the BIOS but that that won't enable it.
I can't connect to the vpro box with "xtightvncviewer" (connection reset by peer) but I can with gtkvncviewer. I can see everything, including the BIOS and such. It's cool, but setup is non-trivial.