That might work... I am trying to do this with WSS 3.0, but I am not aware if there would be any unexpected effects from this approach. I wonder if anyone has tried it before.
Does a custom error for 503 work when applied just at the application level? I could not get it to work when I applied it to the web site (it behaved the same as it did in IIS 6.0, from what I saw).
Regards,
David