Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
DiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWord
DirectoryUser Groups
Related Topics
Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ...

MS Office Forum / Outlook / Calendaring / October 2004

Tip: Looking for answers? Try searching our database.

requirements for sharing

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
John - 22 Oct 2004 13:43 GMT
Correct me if I'm mistaken, but if the users are in different workgroups,
they will not have any, or they will have limited access to the calendars of
other users? For full functionality, all users must be in the same workgroup,
correct?
Sue Mosher [MVP-Outlook] - 22 Oct 2004 15:04 GMT
Outlook can't share its files directly. See
http://office.microsoft.com/en-us/assistance/HA011477571033.aspx for an
article by Outlook MVP Eric Legault on various ways to share Outlook data.
YOu'll also find a list of third-party sharing tools and other information
at http://www.slipstick.com/outlook/share.htm.

Signature

Sue Mosher, Outlook MVP
Author of
    Microsoft Outlook Programming - Jumpstart for
    Administrators, Power Users, and Developers
    http://www.outlookcode.com/jumpstart.aspx

> Correct me if I'm mistaken, but if the users are in different workgroups,
> they will not have any, or they will have limited access to the calendars
> of
> other users? For full functionality, all users must be in the same
> workgroup,
> correct?
John - 22 Oct 2004 16:29 GMT
The users are in a workgroup controlled by the version of  windows server
2003 with MS Exhange. So, the advertising I've seen indicated that no
third-party software is needed to see/share calendars/ contacts.
I think I will repost in another area.
Thanks, I will look for a follow up to this in a bit.

> Outlook can't share its files directly. See
> http://office.microsoft.com/en-us/assistance/HA011477571033.aspx for an
[quoted text clipped - 8 lines]
> > workgroup,
> > correct?
Sue Mosher [MVP-Outlook] - 22 Oct 2004 16:57 GMT
Your original message didn't mention Exchange. Users will need to use a
domain login to access their Exchange mailboxes. If they're using workgroup
logins, they should get a prompt for domain credentials when they start
Outlook with a profile that includes Exchange.

Signature

Sue Mosher, Outlook MVP
Author of
    Microsoft Outlook Programming - Jumpstart for
    Administrators, Power Users, and Developers
    http://www.outlookcode.com/jumpstart.aspx

> The users are in a workgroup controlled by the version of  windows server
> 2003 with MS Exhange. So, the advertising I've seen indicated that no
[quoted text clipped - 18 lines]
>> > workgroup,
>> > correct?
John - 23 Oct 2004 12:37 GMT
You're  correct, my apologies. I was thinking it, but I guess that doesn't
count. Would users be required to be in the same workgroup?

> Your original message didn't mention Exchange. Users will need to use a
> domain login to access their Exchange mailboxes. If they're using workgroup
[quoted text clipped - 23 lines]
> >> > workgroup,
> >> > correct?
Sue Mosher [MVP-Outlook] - 23 Oct 2004 20:25 GMT
As long as the users can log into the domain when they start Outlook and are
prompted for their credentials, it should work fine.

Why do you have workgroups if you're running Exchange and Active Directory?
Signature

Sue Mosher, Outlook MVP
Author of
    Microsoft Outlook Programming - Jumpstart for
    Administrators, Power Users, and Developers
    http://www.outlookcode.com/jumpstart.aspx

> You're  correct, my apologies. I was thinking it, but I guess that doesn't
> count. Would users be required to be in the same workgroup?
[quoted text clipped - 4 lines]
>> logins, they should get a prompt for domain credentials when they start
>> Outlook with a profile that includes Exchange.

>> > The users are in a workgroup controlled by the version of  windows
>> > server
[quoted text clipped - 20 lines]
>> >> > workgroup,
>> >> > correct?
John - 26 Oct 2004 16:31 GMT
It's a church environment; is it practical to setup active directory for a
small organizatoin? Won't their (local) user profiles change when going froma
workgroup to a domain? (Why does it have to change? At least, it does in
Win2000)
Since most users are on laptops that go home and use separate workgroups at
home (I don't think any of the end users have their own home-based domain
<G>), they have then rejoin the domain each time they come in, and then join
their home workgroup when they go home. That would appear to be impractical
for these users, to ask them to change their domain/workgroup before
connecting to the church's network. If I'm having a GCE (Gross Conceptual
Error), please let me know, and where to best get a better understanding.

Thanks,
John

> As long as the users can log into the domain when they start Outlook and are
> prompted for their credentials, it should work fine.
[quoted text clipped - 33 lines]
> >> >> > workgroup,
> >> >> > correct?
Sue Mosher [MVP-Outlook] - 26 Oct 2004 18:07 GMT
I'm confused. You said you were using Exchange. Exchange requires Active
Directory, unless you're using an older version that doesn't require AD and
has its own address list.

Users in a workgroup can provide domain credentials when prompted to by
Outlook.

But if you don't have AD and don't have Exchange, it's a moot point. Maybe
we need to hear what you really are trying to accomplish?

Signature

Sue Mosher, Outlook MVP
Author of
    Microsoft Outlook Programming - Jumpstart for
    Administrators, Power Users, and Developers
    http://www.outlookcode.com/jumpstart.aspx

> It's a church environment; is it practical to setup active directory for a
> small organizatoin? Won't their (local) user profiles change when going
[quoted text clipped - 62 lines]
>> >> >> > workgroup,
>> >> >> > correct?
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.