If Public Folders are going away..

[jim]

What would be the best/simplest solution for a user requesting a group
calendar to be used within Outlook. Ordinarily i would advise them to
create a calendar within the Public Folders hierarchy and then assign access
rights to anyone who needs it. I understand though that Public Folders will
be history with the next release of Exchange. The only thing i can think of
is to create a new mailbox, share the calendar, and then walk users through
adding it to their Outlook folder list. I suspect this isn't the best way
though. Any recommendations out there?

All clients are running Outlook 2003 in a native Exchange 2003 environment.

Thanks in advance!

*Oh, and my apologies for cross-posting. It's tough to know which group is
best suited to a particular question. I've tried to target it to the
smallest number of most relevant ones.

 

[Sue Mosher [MVP-Outlook]]

You understand wrong, which will probably be good news to you. Exchange 12 will continue to support public folders. It's the version after that where they'll go away.

In the meantime, if you want to do something different, you could use a Windows SharePoint Services events list to provide a read-only calendar to Outlook users that would be managed through its web interface.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Diane Poremsky [MVP]]

For future versions, a WSS calendar will be the perfect solution. It works
quite good with current versions of SharePoint server and Windows SharePoint
services - but lacks two way sync, which will be added to the next version.

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Coauthor, OneNote 2003 for Windows (Visual QuickStart Guide)

Need Help with Common Tasks? http://www.outlook-tips.net/beginner/



Subscribe to Exchange Messaging Outlook newsletter:
[email protected]

 

[jim]

Let me rephrase my question then. What's the best way to do it with Outlook
and Exchange only, and with the current 2003 environment? I.E., without
purchasing additional MS products or waiting for a future release.

For future versions, a WSS calendar will be the perfect solution. It works
quite good with current versions of SharePoint server and Windows
SharePoint services - but lacks two way sync, which will be added to the
next version.

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Coauthor, OneNote 2003 for Windows (Visual QuickStart Guide)

Need Help with Common Tasks? http://www.outlook-tips.net/beginner/



Subscribe to Exchange Messaging Outlook newsletter:
[email protected]

What would be the best/simplest solution for a user requesting a group
calendar to be used within Outlook. Ordinarily i would advise them to
create a calendar within the Public Folders hierarchy and then assign
access rights to anyone who needs it. I understand though that Public
Folders will be history with the next release of Exchange. The only
thing i can think of is to create a new mailbox, share the calendar, and
then walk users through adding it to their Outlook folder list. I
suspect this isn't the best way though. Any recommendations out there?

All clients are running Outlook 2003 in a native Exchange 2003
environment.

Thanks in advance!

*Oh, and my apologies for cross-posting. It's tough to know which group
is best suited to a particular question. I've tried to target it to the
smallest number of most relevant ones.

 

[jim]

What's the best solution when the only products i have to work with are
Ex3k3 and Outlook2k3?


You understand wrong, which will probably be good news to you. Exchange 12
will continue to support public folders. It's the version after that where
they'll go away.

In the meantime, if you want to do something different, you could use a
Windows SharePoint Services events list to provide a read-only calendar to
Outlook users that would be managed through its web interface.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Diane Poremsky [MVP]]

What version of Windows Server? 2003 includes WSS - so you could use a
SharePoint site to share calendars... but since Exchange 2003 has PF and
they'll only be depreciated in the next version (which won't be widely in
use for about 2 years) and removed from the version 5ish yrs away... I'd use
an Exchange public folder because creating new calendar items is so much
easier in Outlook than WSS. If it's a fairly static calendar, I would use
WSS, in part to introduce it to the employees... they might like it. If
you need document sharing and other SharePoint features, WSS is also a good
option over PF.

If you aren't familiar with SharePoint features - www.xsolive.com is a demo
site. You can subscribe the calendar and contacts to Outlook 2003 to see how
it works.

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Coauthor, OneNote 2003 for Windows (Visual QuickStart Guide)

Need Help with Common Tasks? http://www.outlook-tips.net/beginner/



Subscribe to Exchange Messaging Outlook newsletter:
[email protected]

Let me rephrase my question then. What's the best way to do it with
Outlook and Exchange only, and with the current 2003 environment? I.E.,
without purchasing additional MS products or waiting for a future release.

For future versions, a WSS calendar will be the perfect solution. It
works quite good with current versions of SharePoint server and Windows
SharePoint services - but lacks two way sync, which will be added to the
next version.

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Coauthor, OneNote 2003 for Windows (Visual QuickStart Guide)

Need Help with Common Tasks? http://www.outlook-tips.net/beginner/



Subscribe to Exchange Messaging Outlook newsletter:
[email protected]

What would be the best/simplest solution for a user requesting a group
calendar to be used within Outlook. Ordinarily i would advise them to
create a calendar within the Public Folders hierarchy and then assign
access rights to anyone who needs it. I understand though that Public
Folders will be history with the next release of Exchange. The only
thing i can think of is to create a new mailbox, share the calendar, and
then walk users through adding it to their Outlook folder list. I
suspect this isn't the best way though. Any recommendations out there?

All clients are running Outlook 2003 in a native Exchange 2003
environment.

Thanks in advance!

*Oh, and my apologies for cross-posting. It's tough to know which group
is best suited to a particular question. I've tried to target it to the
smallest number of most relevant ones.

 

[jim]

Dumb question: wss = windows sharepoint server?

We're running Win2k3. Where can i find wss?

What version of Windows Server? 2003 includes WSS - so you could use a
SharePoint site to share calendars... but since Exchange 2003 has PF and
they'll only be depreciated in the next version (which won't be widely in
use for about 2 years) and removed from the version 5ish yrs away... I'd
use an Exchange public folder because creating new calendar items is so
much easier in Outlook than WSS. If it's a fairly static calendar, I would
use WSS, in part to introduce it to the employees... they might like it.
If you need document sharing and other SharePoint features, WSS is also
a good option over PF.

If you aren't familiar with SharePoint features - www.xsolive.com is a
demo site. You can subscribe the calendar and contacts to Outlook 2003 to
see how it works.

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Coauthor, OneNote 2003 for Windows (Visual QuickStart Guide)

Need Help with Common Tasks? http://www.outlook-tips.net/beginner/



Subscribe to Exchange Messaging Outlook newsletter:
[email protected]

Let me rephrase my question then. What's the best way to do it with
Outlook and Exchange only, and with the current 2003 environment? I.E.,
without purchasing additional MS products or waiting for a future
release.

For future versions, a WSS calendar will be the perfect solution. It
works quite good with current versions of SharePoint server and Windows
SharePoint services - but lacks two way sync, which will be added to the
next version.

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Coauthor, OneNote 2003 for Windows (Visual QuickStart Guide)

Need Help with Common Tasks? http://www.outlook-tips.net/beginner/



Subscribe to Exchange Messaging Outlook newsletter:
[email protected]


What would be the best/simplest solution for a user requesting a group
calendar to be used within Outlook. Ordinarily i would advise them to
create a calendar within the Public Folders hierarchy and then assign
access rights to anyone who needs it. I understand though that Public
Folders will be history with the next release of Exchange. The only
thing i can think of is to create a new mailbox, share the calendar,
and then walk users through adding it to their Outlook folder list. I
suspect this isn't the best way though. Any recommendations out there?

All clients are running Outlook 2003 in a native Exchange 2003
environment.

Thanks in advance!

*Oh, and my apologies for cross-posting. It's tough to know which
group is best suited to a particular question. I've tried to target it
to the smallest number of most relevant ones.

 

[jim]

Oh wait, never mind, i figured it out.

Dumb question: wss = windows sharepoint server?

We're running Win2k3. Where can i find wss?

What version of Windows Server? 2003 includes WSS - so you could use a
SharePoint site to share calendars... but since Exchange 2003 has PF and
they'll only be depreciated in the next version (which won't be widely in
use for about 2 years) and removed from the version 5ish yrs away... I'd
use an Exchange public folder because creating new calendar items is so
much easier in Outlook than WSS. If it's a fairly static calendar, I
would use WSS, in part to introduce it to the employees... they might
like it. If you need document sharing and other SharePoint features,
WSS is also a good option over PF.

If you aren't familiar with SharePoint features - www.xsolive.com is a
demo site. You can subscribe the calendar and contacts to Outlook 2003 to
see how it works.

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Coauthor, OneNote 2003 for Windows (Visual QuickStart Guide)

Need Help with Common Tasks? http://www.outlook-tips.net/beginner/



Subscribe to Exchange Messaging Outlook newsletter:
[email protected]

Let me rephrase my question then. What's the best way to do it with
Outlook and Exchange only, and with the current 2003 environment? I.E.,
without purchasing additional MS products or waiting for a future
release.


For future versions, a WSS calendar will be the perfect solution. It
works quite good with current versions of SharePoint server and Windows
SharePoint services - but lacks two way sync, which will be added to
the next version.

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Coauthor, OneNote 2003 for Windows (Visual QuickStart Guide)

Need Help with Common Tasks? http://www.outlook-tips.net/beginner/



Subscribe to Exchange Messaging Outlook newsletter:
[email protected]


What would be the best/simplest solution for a user requesting a group
calendar to be used within Outlook. Ordinarily i would advise them to
create a calendar within the Public Folders hierarchy and then assign
access rights to anyone who needs it. I understand though that Public
Folders will be history with the next release of Exchange. The only
thing i can think of is to create a new mailbox, share the calendar,
and then walk users through adding it to their Outlook folder list. I
suspect this isn't the best way though. Any recommendations out
there?

All clients are running Outlook 2003 in a native Exchange 2003
environment.

Thanks in advance!

*Oh, and my apologies for cross-posting. It's tough to know which
group is best suited to a particular question. I've tried to target
it to the smallest number of most relevant ones.