RE: Exchange Central Calendar Sharing[Scanned OK]

  • From: "Simon Bound" <Simon@xxxxxxxxxxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Thu, 2 Mar 2006 10:46:42 -0000

I am missing something - what's the problem with using a central shared
Public calendar ?

Simon

-----Original Message-----
From: Mike French [mailto:mike.french@xxxxxxxxxxxxxxxxxxx] 
Sent: Wed 01 March 2006 21:24
To: [ExchangeList]
Subject: [exchangelist] Exchange Central Calendar Sharing[Scanned OK]

http://www.MSExchange.org/

I hope this makes sense:
 
Exchange 2003 SP2 / Windows 2003 Server Domain / Windows XP Clients with
Outlook 2003
 
The idea is to have a central location where users can share their
Calendars
centrally for all to view? I have them configured to share in Outlook
and of
course this got someone thinking (Too much in my opinion). "We want a
centralized area so we can view everyone's Outlook calendar!?!, Like a
Public Folder area or something, Make it happen..."  I doubt this is
possible without a third party solution? I can give more depth if
needed....

 
I might as well through this out there too:
 
E-Mail disclaimers, apart from GFI anybody doing this? I'll check the
archives next, I bet this has been covered before.....
 
 
 

Mike French

Acclaim Networks
754 Port America Place
Suite 150
Grapevine, TX 76051
(888) 327-5647
(817) 488-1600
FAX (817) 488-1103
Mike.French@xxxxxxxxxxxxxxxxxxx
www.acclaimnetworks.com





------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp 
------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com
------------------------------------------------------
You are currently subscribed to this MSExchange.org Discussion List as:
simon.bound@xxxxxxxxxxxxxxxxxxxx
To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to info@xxxxxxxxxxxxxx


Other related posts: