to: MSFT.. Info rights management (IRM) Failing with office 2003

K

kevin Foster

hello,

I am trying to send an Email that is restricted (no forward, not printable
etc) from outlook2003 through my ISP account (POP3) to an AOL account and I
am running into some unique issues with the IRM functionality in Office
2003.. so here's the repro & setup, in case someone can give me a hand.
the overall goal is that when we send email to people on the internet they
are not able to print it out, forward it etc. regardless of email client or
what they are running (we do require then install the IE6 Plug-in for IRM to
view the docs)

PC #1 Win XP client
Office 2003
latest patches and hotfixes

PC#2 Win 2003 server
new install, all hotfixes
AOL software
wordpad only (never any office)


PC #1
start up word 2003, create a simple doc file.. click on "file" permission
then select "do not distribute" and only give access to (e-mail address removed)
go under "more info" and select the box that says "allow users with earlier
versions of office to read with browser supporting
information rights management (increases file sizes)" save document.. At
this point word 2003 then prompts that I need to link my ISP email address
with Passport server account.. so I can use MSFT's free IRM server on the
internet.. it then downloads some certificate for IRM on my box (see
screen1.jpg attached for details) go through this process, then fireup
outlook and send the attached document file and digitally sign it (verisign
s/mime signature - ok I'm paranoid) it leaves PC#1 with no problems..

PC#2
referance the following instructions on MS website
http://www.microsoft.com/office/editions/prodinfo/technologies/irm.mspx

since this 2nd PC doesn't have office 2003.. we install the IE6.x plug-in
per the link below
http://www.microsoft.com/windows/ie/downloads/addon/

then fireup AOL and download the email we recieved with the attached
protected word2003 document.. we then doubleclick on the document file and
wordpad starts to fire up (which loads IE6) to attempt to view the file..
IE shows the document is protected then an error in IE6 that "the document
has been corrupted" something about MHTML (the file is a doc file)
unfortunately I can't attach a screen shot as I can't hit alt-print screen
or use IE print to a file as IE shows the document is protected and disables
this functionality..

Are we doing something fundimentally wrong, we thought the purpose of MSFT
setting up the IRM server on the internet for public use was for this
purpose?
or does the end user in addition to installing the IE6 plug-in also need to
register his email address (the (e-mail address removed)) with MS Passport and MS Free
IRM server as well? (to match what we set in the word document in the first
place)


Second issue:
we attended the Office 2003 launch the other day.. we saw examples of
sharepoint services site for Contoso Pharmacy. when people tried to right
click on images on the site to save to a hard drive.. or use IE print
functionality.. or open word document links in the website ..IRM would
pop-up and say "sorry dude" . The example was an internal /workgroup
senarion we are looking to implement similar but on the internet...

one of the problems we have right now is people stealing images, etc from
our website or pulling HTML coding... we try to circumvent this by using
Java script that prevents right clicking on our images, but if people are
smart there is a workaround.. we also Digimarc our images, but this only
allows us to track where people are posting them (newsgroups, websites) and
persue legal action against the author.

if we were to have a basic "public" site.. but then a private that prompted
for login to our backend AD then could this be possible.. are there any
deployment guides or suggestions on this.. The MS demo and slides on
http://www.officesystemlaunch.com seem to show "what can be done" but not
really how to do build the site from ground zero.

thanks
kevin
 
M

Milly Staples [MVP - Outlook]

These disparate groups are peer-to-peer support and not officially monitored
by Microsoft. If you want support from Microsoft directly, then you can use
the Product Support Services webmail support or telephone support.

IRM is sufficiently new that there can be some caveats if you are not using
supported products. I am not sure if WordPad is supported under IRM.
Contact Microsoft for the definitive answer on this.


--
Milly Staples [MVP - Outlook]

Due to the Swen virus, all e-mails sent to this account will be deleted
w/out reading.



After searching google.groups.com and finding not answer:
kevin Foster <[email protected]> asked:
| hello,
|
| I am trying to send an Email that is restricted (no forward, not
| printable etc) from outlook2003 through my ISP account (POP3) to an
| AOL account and I am running into some unique issues with the IRM
| functionality in Office 2003.. so here's the repro & setup, in case
| someone can give me a hand. the overall goal is that when we send
| email to people on the internet they are not able to print it out,
| forward it etc. regardless of email client or what they are running
| (we do require then install the IE6 Plug-in for IRM to view the docs)
|
| PC #1 Win XP client
| Office 2003
| latest patches and hotfixes
|
| PC#2 Win 2003 server
| new install, all hotfixes
| AOL software
| wordpad only (never any office)
|
|
| PC #1
| start up word 2003, create a simple doc file.. click on "file"
| permission then select "do not distribute" and only give access to
| (e-mail address removed)
| go under "more info" and select the box that says "allow users with
| earlier versions of office to read with browser supporting
| information rights management (increases file sizes)" save
| document.. At this point word 2003 then prompts that I need to link
| my ISP email address with Passport server account.. so I can use
| MSFT's free IRM server on the internet.. it then downloads some
| certificate for IRM on my box (see screen1.jpg attached for details)
| go through this process, then fireup outlook and send the attached
| document file and digitally sign it (verisign s/mime signature - ok
| I'm paranoid) it leaves PC#1 with no problems..
|
| PC#2
| referance the following instructions on MS website
| http://www.microsoft.com/office/editions/prodinfo/technologies/irm.mspx
|
| since this 2nd PC doesn't have office 2003.. we install the IE6.x
| plug-in per the link below
| http://www.microsoft.com/windows/ie/downloads/addon/
|
| then fireup AOL and download the email we recieved with the attached
| protected word2003 document.. we then doubleclick on the document
| file and wordpad starts to fire up (which loads IE6) to attempt to
| view the file.. IE shows the document is protected then an error in
| IE6 that "the document has been corrupted" something about MHTML
| (the file is a doc file) unfortunately I can't attach a screen shot
| as I can't hit alt-print screen or use IE print to a file as IE
| shows the document is protected and disables this functionality..
|
| Are we doing something fundimentally wrong, we thought the purpose of
| MSFT setting up the IRM server on the internet for public use was for
| this purpose?
| or does the end user in addition to installing the IE6 plug-in also
| need to register his email address (the (e-mail address removed)) with MS
| Passport and MS Free IRM server as well? (to match what we set in the
| word document in the first place)
|
|
| Second issue:
| we attended the Office 2003 launch the other day.. we saw examples of
| sharepoint services site for Contoso Pharmacy. when people tried to
| right click on images on the site to save to a hard drive.. or use IE
| print functionality.. or open word document links in the website
| ..IRM would pop-up and say "sorry dude" . The example was an
| internal /workgroup senarion we are looking to implement similar but
| on the internet...
|
| one of the problems we have right now is people stealing images, etc
| from our website or pulling HTML coding... we try to circumvent this
| by using Java script that prevents right clicking on our images, but
| if people are smart there is a workaround.. we also Digimarc our
| images, but this only allows us to track where people are posting
| them (newsgroups, websites) and persue legal action against the
| author.
|
| if we were to have a basic "public" site.. but then a private that
| prompted for login to our backend AD then could this be possible..
| are there any deployment guides or suggestions on this.. The MS demo
| and slides on http://www.officesystemlaunch.com seem to show "what
| can be done" but not really how to do build the site from ground zero.
|
| thanks
| kevin
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top