"SyntaX TerroR" <SyntaXTer***@discussions.microsoft.com> wrote in message
news:ECA2602E-7593-438C-99E8-4ED939246EE2@microsoft.com...
> Next to the meeting room doors in our office we have placed small TFT's
> which
> are connected to low power Linux pc's.  Our intention is to have to pc
> show
> the booked meetings for that meeting room by showing the Outlook Web
> Access
> calendar for that specific room (ie. user).  The displayed webpage
> containing
> the calendar refreshes every 10 minutes.
>
> Everything is setup and works just fine, except for one tiny problem.
> Upon
> accessing the calendar a domain username and password is requested.  I've
> already given the user "Anonymous" access to this room's account, but to
> no
> avail.
>
> Naturally the problem arises because the pc's are Linux based and aren't
> part of my domain.  So either I need to be able to access the Outlook Web
> Access anonymously or I need to find a way to put the Linux pc's in my
> Windows domain.  I'm hoping for the first. :-)
>
> I tried to be clever and put username and password in the URL of the page
> which gets loaded (and refreshed) and in fact this works, but only
> sometimes
> (and never when refreshing).  Saving the password in the local browser
> (Seamonkey) isn't an option either because then you still need to press OK
> every 10 minutes on each pc (and the pc's are supposed to be view only, so
> no
> mouse or keyboard is connected).
>
> Anyone know how I can access OWA without any credentials whatsoever?
>
> Thanks in advance!

"SyntaX TerroR" <SyntaXTer***@discussions.microsoft.com> wrote in message
news:EC81C7AC-4CF0-48DA-AA92-CD33C7D91BC6@microsoft.com...
>> How are you doing the refresh?  If you have credentials in the URL, it
>> should work each time.
>>
>> Lee.
>
> Because I didn't want to set up a webserver, the file is hosted on our FTP
> server.  The refresh is done in HTML (<meta
> content="60;URL=ftp://username:password@FTPserver/folder/file.htm"
> http-equiv="refresh" />), which basically tells the file to reload itself
> after 60 seconds (right now).
>
> In the same HTML file we load the calendar into an iframe: <iframe
> id="calendar" src="http://username:password@mailserver/exchange/name
> meetingroom/calendar/?cmd=content&f=calendar&view=daily"
> scrolling="no"></iframe>
>
> So now I'm wondering if there's no way to make said calendar accessible to
> unauthenticated users.  That way there shouldn't be any problem
> whatsoever...

"Lee Derbyshire [MVP]" wrote:

> "SyntaX TerroR" <SyntaXTer***@discussions.microsoft.com> wrote in message
> news:EC81C7AC-4CF0-48DA-AA92-CD33C7D91BC6@microsoft.com...
> >> How are you doing the refresh?  If you have credentials in the URL, it
> >> should work each time.
> >>
> >> Lee.
> >
> > Because I didn't want to set up a webserver, the file is hosted on our FTP
> > server.  The refresh is done in HTML (<meta
> > content="60;URL=ftp://username:password@FTPserver/folder/file.htm"
> > http-equiv="refresh" />), which basically tells the file to reload itself
> > after 60 seconds (right now).
> >
> > In the same HTML file we load the calendar into an iframe: <iframe
> > id="calendar" src="http://username:password@mailserver/exchange/name
> > meetingroom/calendar/?cmd=content&f=calendar&view=daily"
> > scrolling="no"></iframe>
> >
> > So now I'm wondering if there's no way to make said calendar accessible to
> > unauthenticated users.  That way there shouldn't be any problem
> > whatsoever...
>
> I've never use ftp:// in a meta refresh tag like that.  Does
> ftp://username:password@FTPserver/folder/file.htm
> actually show a web page in your browser.  I guess it should, since it
> probably doesn't care how it gets the file.  You may be able to do it if
> your calendar was in a public folder, but even then, I don't think OWA will
> allow it.
>
> Is there a reason you can't host the original .htm file (the one you are
> getting via ftp) on the default web site of your Exchange server?
>

"SyntaX TerroR" <SyntaXTer***@discussions.microsoft.com> wrote in message
news:73F16695-5B70-466B-9C79-86773A40256A@microsoft.com...
>
>
> "Lee Derbyshire [MVP]" wrote:
>
>> "SyntaX TerroR" <SyntaXTer***@discussions.microsoft.com> wrote in message
>> news:EC81C7AC-4CF0-48DA-AA92-CD33C7D91BC6@microsoft.com...
>> >> How are you doing the refresh?  If you have credentials in the URL, it
>> >> should work each time.
>> >>
>> >> Lee.
>> >
>> > Because I didn't want to set up a webserver, the file is hosted on our
>> > FTP
>> > server.  The refresh is done in HTML (<meta
>> > content="60;URL=ftp://username:password@FTPserver/folder/file.htm"
>> > http-equiv="refresh" />), which basically tells the file to reload
>> > itself
>> > after 60 seconds (right now).
>> >
>> > In the same HTML file we load the calendar into an iframe: <iframe
>> > id="calendar" src="http://username:password@mailserver/exchange/name
>> > meetingroom/calendar/?cmd=content&f=calendar&view=daily"
>> > scrolling="no"></iframe>
>> >
>> > So now I'm wondering if there's no way to make said calendar accessible
>> > to
>> > unauthenticated users.  That way there shouldn't be any problem
>> > whatsoever...
>>
>> I've never use ftp:// in a meta refresh tag like that.  Does
>> ftp://username:password@FTPserver/folder/file.htm
>> actually show a web page in your browser.  I guess it should, since it
>> probably doesn't care how it gets the file.  You may be able to do it if
>> your calendar was in a public folder, but even then, I don't think OWA
>> will
>> allow it.
>>
>> Is there a reason you can't host the original .htm file (the one you are
>> getting via ftp) on the default web site of your Exchange server?
>>
> Getting the page to show from an FTP server is indeed no problem at all.
> Like you said, showing the OWA page of a public folder calendar might
> prove
> to be difficult.  That's why I went with a user per meeting room.
>
> I put the file on our FTP server because I didn't want to provide access
> to
> our Exchange Server (also Domain Controller) for the person who
> occasionally
> needs to update these HTML files.
>
> Just now I discovered something.  When I put the username and password in
> the URL of the iframe, the calendar loads correctly, but starting from the
> first refresh, I need to enter my credentials each time.  When I don't put
> the credentials in the URL, I need to provide them the first time, but I
> don't need to enter them again when the page refreshes...  Strange...