How to Wake Up External LCD after Waking Up from Standby - T61?

[EAkamai]

I'm having a remote video issue with T61 that I don't have with other desktop systems.

When I remotely wake up the T61 from standby, the external monitor doesn't automatically wake up (turn on) from standby.
If T61 is off (not in standby mode) it will wake up (turn on monitor) properly. But why not from standby?

In other words, after I remotely wake up T61 from standby the remote program RAdmin (Remote Administrator) won't show video
until I physically move mouse or keyboard on T61 which wakes up external LCD from standby.
Of course that totally defeats purpose of remote access. None of my desktops exhibits that behavior.

I was able to find a work around using Dennis' excellent portable WOSB (WakeupOnStandby) product,
however, It's adding another program to the works. WOSB has a setting 'Turn on monitor' after system wakes up.

I want to find out why external LCD isn't automatically waking up the when T61 wakes up from standby.
Am I missing a setting somewhere in the Intel onboard graphics drivers, or is this by design somehow?
If it's by design, I can live with using WOSB. If not, what am I missing here?

P.S. I don't suspect Radmin's settings since they are exactly same for all systems.
All desktops using ATI Radeon cards. I suspect the integrated Intel graphic driver settings or something specific to the t61.

P.P.S. I'm using the Adv Docking Station with the DVI interface for external monitor (t61 lid is shut).

[EAkamai]

As You Were!

In spite of Dennis' WOSB program fixing the video problem, it added a new one.
No matter what, it would go back to sleep after about 2 minutes no matter what we were doing on t61.
So we had to deal with that one. But I figured out that one after digging into WOSB settings:

Discovered it was part of Dennis' WOSB program doing this.
Was able to overcome it and we're back to normal.

As an aside, it didn't matter if monitor was on, standby or completely off.
This behavior was unaffected by that. Internal settings in WOSB helped us fix it.