Solved Task Scheduler failing to start task with merged network locations

I have two routers I usually connect to (work and home) and each have wireless access. That means there are essentially 4 network locations I have listed. I have merged each respective network location (wired and wireless) into their own singular network location - "Work" and "Home".

I also have set up two tasks; one is set to run only when connected to "Work" and the other, to "Home". The 1st maps network drives and the 2nd disconnects the drives. So essentially when I get to work and log in, the scheduler should attempt to map the network drives. When I go home and log in again, it should disconnect the mapped drives.

Currently if I plug in to a physical LAN connection this works...however if I'm running on wireless, the task scheduler doesn't trigger the scripts! I don't know if this has to do with the fact that I'm using merged network locations and it's only using ONE of the profiles or whether it has to do with something else.

So to summarize, the scripts themselves are working just fine - it's the "Start only if the following network location is available" condition that fails when using 1) merged networks and 2) wireless.

Try recreating the tasks. Sometimes task scheduler glitches. So, just try recreating and post again.

Oops...bonehead move; I didn't make sure that the task could run when the laptop was on battery power. Disregard post :S

Well I'm glad you figured it out.