Outlook/Exchange question...

[jharrison]

We run an NT 4.0 network (server/workstation), Exchange 5.5, Outlook 98, TCP/IP.

I remember being able to setup a user's Outlook so that when they open the program it asks them which profile they want to use. I know the steps to do this, but what I've forgotten is what permissions need to be granted t allow the user access to a mailbox not their own.

For instance, Users A and B want to have their own mailboxes setup in their Outlook profiles but they also would like to have the option to go into User C's mailbox when Outlook starts up.

What permissions are required to allow Users A and B to open User C's mailbox on their own machines? I hear that it may be easier to do this in Win9x than in WinNT. Let me know what you think. Thanks.

[Goethe]

In Outlook go to Tools>Options and under General tab there is Startup Settings.
You can either choose default profile or to be prompted for one....
I hope this is helpfull.

[ctaylor]

Open the Outlook client software

select the TOOLS drop down menu

select OPTIONS

select the MAIL SERVICES TAB

go to the STARTUP SETTINGS group

click the radio button before PROMPT FOR THE PROFILE TO BE USED.

COMMENT: This will require that each individual log into the network BEFORE they will be able to select their profile from the preconfigured profiles. This is because the default authentication is NT DISTRIBUTED. You can change this through the same properties window used to create user logon profiles.

[jharrison]

Goethe and ctaylor,

Thanks for the help but as I said I know how to set it up. My question has to do with the permissions issues that may arise.

For instance, just yesterday I tried to setup someone with this method and all worked fine until I tried to go into the extra profile that I added. Outlook told me that I (the user) didn't have permission to view that mailbox.

That's what I'm talking about. Any ideas? I honestly can't remember what to do...

[ctaylor]

I place the users *.PAB file in thei rhome directory on the a server. I configure the path for the *.PAB file to point to the folder in the home directory. the user should have Read/Write/Create/Modify permissions for their home directory.

If you log in as yourself and try to access another's home directory you may be able to see the *.PAB file, but the Outlook/Exchange configuration (within an NT network) actually checks your BDC to verify that the user logged onto the client is the one associated with the Exchange Client account.

try loggin in with the user's name/password and opening the user's mail folder to test.

[Goethe]

OK, I understand now what you are asking...
This is security isue, ( I am having problems figuring out how to explain this...lol) whoever is loged in is the only person who can check their mail at that PC.
This is cuz in Exchange server you have to specify Primary Windows NT Account and if you try to check your mail logged in as someone else exchange can see that and it won't let you do it. So what you can do is (never did it but in theory should work), create new Distribution List, add users that you want to share e-mail,
Go to properties of each of those users and change their Primary Windows NT Account to
the new Distributoin List that you Just made.
Try this, I hope it works and let me know...

[Goethe]

If my previous sugestion doesn't work I have some more that I think should work.....

[ctaylor]

There is a way around this NT security issue which will allow a single user to check multiple users e-mail, but it is not user friendly

1. On the client end of the Outlook setup select the user's PROFILE from the list

2. Select the MICROSOFT EXCHANGE SERVER information service installed for that profile

3. click on the PROPERTIES button

4. select the ADVANCED tab

5. for Network Logon Security, select NONE.

What this will do is prompt the user to enter the USERNAME, PASSWORD, and DOMAIN of the Exchange client polling for mail.

Personally I refuse to do this because it results in too many calls from people who are entering the wrong values in the wrong fields etc....

For operators sharing a machine I have them LOG OFF the current user of the PC before loggin in as themself in order to check for mail using the default NT PASSWORD AUTHENTICATION.

The Exchange client needs to provide these three values to the Exchange server to poll for mail. with NT PASSOWRD AUTHENTICATION selected it will "remember" these values from when the user logged on to the network.

Does this sufficiently communicate what is happening? Seeing the options and playing with the three kinds of Outlook client authentication will let you "experience" the options available to you.

[Goethe]

Just as you said, it's not user friendly, so I like to stay away from something what would give me more calls from users http://sysopt.earthweb.com/forum/wink.gif. They have enough problems with logging in, this would create a chaos lol.