Nope, this does appear to be a bug and I could not find a work-around.
Interestingly, this appears to be the first time anyone has run into the
problem. I've checked past discussion group questions and trouble reports
and have not found anyone else reporting a problem; not because it doesn't
exist, but because no one has tried using safe printing.
Shel
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Shel Blauman [MSFT]" <sh******@online.microsoft.com> wrote in message
news:ee**************@tk2msftngp13.phx.gbl...
I've been checking the code. There may be a way to do this, but I haven't
been able to locate all the code. I'll post here if I can find the right
way to print using SafePrinting. If there is, then this is a
documentation not a code issue.
Shel
--
This posting is provided "AS IS" with no warranties, and confers no
rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Shel Blauman [MSFT]" <sh******@online.microsoft.com> wrote in message
news:u4*************@TK2MSFTNGP12.phx.gbl... I believe it's a bug. I filed a bug report, but haven't heard back on
it yet.
Shel
--
This posting is provided "AS IS" with no warranties, and confers no
rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Jody Gelowitz" <jo**@mail.visualstatement.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl... I was just wondering if anybody has been able to figure out how to get
Safe Printing working over an Internet Zone.
Based on what was mentioned from the previous thread titled "Safe
Printing", it was decided that this was a bug and that Safe Printing does not
work. I just need to verify that these findings are correct.
Thanks,
Jody
