We recently migrated from Groupwise to Outlook 2003, but decided not to
utilize .PST files. When we distributed Office/w Outlook 2003, it created
say an OUTLOOK profiles under CURRENTUSER\software\microsoft\windows
NT\CurrentUser\Windows Messaging Subsystem\Outlook\....... We utilized the
%USERNAME%, so any user when they log onto someone's pc can get right into
their Outlook.

So now we have situations where the Admin people need to go into Control
Panel, mail and configure other profiles, which now we enable "prompt to log
in." This seems to not work well because we have had several people now lock
out their windows accounts. Say we have a resource mailbox as
CustomerService, so we configure a CustomerService profile that goes into
their mailbox. The next time I open Outlook, it prompts to log in. We
notice places a domain JULI\CustomerService. We place in the password and it
fails. If we overwrite the JULI\CustomerService with just CustomerService and
place the password, it works well. So then we go back into our mailbox and
it prompts with a JULI\JDOE, we type in the password and oftentimes it
fails...it is a pain. It almost appears if the domain name is in the name,
it doesn't resolve.

Are we doing something incorrectly?

One solution would be to grant the users who need access to the mailbox appropriate permissions either at the mailbox level with ADU&C. That way, their current Windows login will get them into that mailbox, without the need to remember (and enter correctly) a second login.

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

"SkyEyes" wrote in message ...
We recently migrated from Groupwise to Outlook 2003, but decided not to
utilize .PST files. When we distributed Office/w Outlook 2003, it created
say an OUTLOOK profiles under CURRENTUSER\software\microsoft\windows
NT\CurrentUser\Windows Messaging Subsystem\Outlook\....... We utilized the
%USERNAME%, so any user when they log onto someone's pc can get right into
their Outlook.

So now we have situations where the Admin people need to go into Control
Panel, mail and configure other profiles, which now we enable "prompt to log
in." This seems to not work well because we have had several people now lock
out their windows accounts. Say we have a resource mailbox as
CustomerService, so we configure a CustomerService profile that goes into
their mailbox. The next time I open Outlook, it prompts to log in. We
notice places a domain JULI\CustomerService. We place in the password and it
fails. If we overwrite the JULI\CustomerService with just CustomerService and
place the password, it works well. So then we go back into our mailbox and
it prompts with a JULI\JDOE, we type in the password and oftentimes it
fails...it is a pain. It almost appears if the domain name is in the name,
it doesn't resolve.

Are we doing something incorrectly?

Thanks Sue.
We are granting permissions in AD to the owners, but thought we had to set
up the profile on the owners machine in order to have them administer their
own security (for instance, adding other people to be able to manage the
mailbox or folders, etc.).

Are we not handling this correctly.
"Sue Mosher [MVP-Outlook]" wrote:

One solution would be to grant the users who need access to the mailbox appropriate permissions either at the mailbox level with ADU&C. That way, their current Windows login will get them into that mailbox, without the need to remember (and enter correctly) a second login.

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

"SkyEyes" wrote in message ...
We recently migrated from Groupwise to Outlook 2003, but decided not to
utilize .PST files. When we distributed Office/w Outlook 2003, it created
say an OUTLOOK profiles under CURRENTUSER\software\microsoft\windows
NT\CurrentUser\Windows Messaging Subsystem\Outlook\....... We utilized the
%USERNAME%, so any user when they log onto someone's pc can get right into
their Outlook.

So now we have situations where the Admin people need to go into Control
Panel, mail and configure other profiles, which now we enable "prompt to log
in." This seems to not work well because we have had several people now lock
out their windows accounts. Say we have a resource mailbox as
CustomerService, so we configure a CustomerService profile that goes into
their mailbox. The next time I open Outlook, it prompts to log in. We
notice places a domain JULI\CustomerService. We place in the password and it
fails. If we overwrite the JULI\CustomerService with just CustomerService and
place the password, it works well. So then we go back into our mailbox and
it prompts with a JULI\JDOE, we type in the password and oftentimes it
fails...it is a pain. It almost appears if the domain name is in the name,
it doesn't resolve.

Are we doing something incorrectly?

If the current Windows user's account has Full Access on the mailbox, that user can create a new profile that opens that mailbox directly without the need to provide credentials.

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

"SkyEyes" wrote in message ...
Thanks Sue.
We are granting permissions in AD to the owners, but thought we had to set
up the profile on the owners machine in order to have them administer their
own security (for instance, adding other people to be able to manage the
mailbox or folders, etc.).

Are we not handling this correctly.
"Sue Mosher [MVP-Outlook]" wrote:

One solution would be to grant the users who need access to the mailbox appropriate permissions either at the mailbox level with ADU&C. That way, their current Windows login will get them into that mailbox, without the need to remember (and enter correctly) a second login.

"SkyEyes" wrote in message ...
We recently migrated from Groupwise to Outlook 2003, but decided not to
utilize .PST files. When we distributed Office/w Outlook 2003, it created
say an OUTLOOK profiles under CURRENTUSER\software\microsoft\windows
NT\CurrentUser\Windows Messaging Subsystem\Outlook\....... We utilized the
%USERNAME%, so any user when they log onto someone's pc can get right into
their Outlook.

So now we have situations where the Admin people need to go into Control
Panel, mail and configure other profiles, which now we enable "prompt to log
in." This seems to not work well because we have had several people now lock
out their windows accounts. Say we have a resource mailbox as
CustomerService, so we configure a CustomerService profile that goes into
their mailbox. The next time I open Outlook, it prompts to log in. We
notice places a domain JULI\CustomerService. We place in the password and it
fails. If we overwrite the JULI\CustomerService with just CustomerService and
place the password, it works well. So then we go back into our mailbox and
it prompts with a JULI\JDOE, we type in the password and oftentimes it
fails...it is a pain. It almost appears if the domain name is in the name,
it doesn't resolve.

Are we doing something incorrectly?

So if we understand this correctly, say I grant JDOE OWNER access to the
Customer Service Resource Mailbox at the root are you saying we need on
JDOE's workstation to go into Control Panel, Mail, Profiles and Create a new
one labeled Customer Service Resource, but when we go into the E-Mail Account
tab and check name, it asks to log in with User ID and password, because on
these machines this person may manage multiple Resource Mailboxes besides her
own mailbox so we have Prompt for User ID and password checked.

Or, once we grant her access as OWNER, she goes into her mailbox, clicks on
Tools | email accounts | next button, | Change | More Settings | and add that
resource mailbox to the Advanced Tab | Open these additional mailboxes--once
we sees the mailbox and is able to manage through her own, can she grant
additional sharing for other people in that specific Customer Service
Resource mailbox.

We are very new to this and are not quite understanding the Outlook profiles
things versus adding additional mailboxes for people.

Thanks.



"Sue Mosher [MVP-Outlook]" wrote:

If the current Windows user's account has Full Access on the mailbox, that user can create a new profile that opens that mailbox directly without the need to provide credentials.

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

"SkyEyes" wrote in message ...
Thanks Sue.
We are granting permissions in AD to the owners, but thought we had to set
up the profile on the owners machine in order to have them administer their
own security (for instance, adding other people to be able to manage the
mailbox or folders, etc.).

Are we not handling this correctly.
"Sue Mosher [MVP-Outlook]" wrote:

One solution would be to grant the users who need access to the mailbox appropriate permissions either at the mailbox level with ADU&C. That way, their current Windows login will get them into that mailbox, without the need to remember (and enter correctly) a second login.

"SkyEyes" wrote in message ...
We recently migrated from Groupwise to Outlook 2003, but decided not to
utilize .PST files. When we distributed Office/w Outlook 2003, it created
say an OUTLOOK profiles under CURRENTUSER\software\microsoft\windows
NT\CurrentUser\Windows Messaging Subsystem\Outlook\....... We utilized the
%USERNAME%, so any user when they log onto someone's pc can get right into
their Outlook.

So now we have situations where the Admin people need to go into Control
Panel, mail and configure other profiles, which now we enable "prompt to log
in." This seems to not work well because we have had several people now lock
out their windows accounts. Say we have a resource mailbox as
CustomerService, so we configure a CustomerService profile that goes into
their mailbox. The next time I open Outlook, it prompts to log in. We
notice places a domain JULI\CustomerService. We place in the password and it
fails. If we overwrite the JULI\CustomerService with just CustomerService and
place the password, it works well. So then we go back into our mailbox and
it prompts with a JULI\JDOE, we type in the password and oftentimes it
fails...it is a pain. It almost appears if the domain name is in the name,
it doesn't resolve.

Are we doing something incorrectly?

So if we understand this correctly, say I grant JDOE OWNER access to the
Customer Service Resource Mailbox at the root are you saying we need on
JDOE's workstation to go into Control Panel, Mail, Profiles and Create a new
one labeled Customer Service Resource, but when we go into the E-Mail Account
tab and check name, it asks to log in with User ID and password, because on
these machines this person may manage multiple Resource Mailboxes besides her
own mailbox so we have Prompt for User ID and password checked.

I'm saying that you can turn off the prompting if JDOE has owner access on the mailbox he's trying to set up a profile for.

Or, once we grant her access as OWNER, she goes into her mailbox, clicks on
Tools | email accounts | next button, | Change | More Settings | and add that
resource mailbox to the Advanced Tab | Open these additional mailboxes--once
we sees the mailbox and is able to manage through her own, can she grant
additional sharing for other people in that specific Customer Service
Resource mailbox.

You can try that for yourself, but I don't think it will work. I think she'll need to use the direct profile to manage sharing for the Customer Service Resource mailbox.

We are very new to this and are not quite understanding the Outlook profiles
things versus adding additional mailboxes for people.

"Sue Mosher [MVP-Outlook]" wrote:

If the current Windows user's account has Full Access on the mailbox, that user can create a new profile that opens that mailbox directly without the need to provide credentials.


"SkyEyes" wrote in message ...
Thanks Sue.
We are granting permissions in AD to the owners, but thought we had to set
up the profile on the owners machine in order to have them administer their
own security (for instance, adding other people to be able to manage the
mailbox or folders, etc.).

Are we not handling this correctly.
"Sue Mosher [MVP-Outlook]" wrote:

One solution would be to grant the users who need access to the mailbox appropriate permissions either at the mailbox level with ADU&C. That way, their current Windows login will get them into that mailbox, without the need to remember (and enter correctly) a second login.

"SkyEyes" wrote in message ...
We recently migrated from Groupwise to Outlook 2003, but decided not to
utilize .PST files. When we distributed Office/w Outlook 2003, it created
say an OUTLOOK profiles under CURRENTUSER\software\microsoft\windows
NT\CurrentUser\Windows Messaging Subsystem\Outlook\....... We utilized the
%USERNAME%, so any user when they log onto someone's pc can get right into
their Outlook.

So now we have situations where the Admin people need to go into Control
Panel, mail and configure other profiles, which now we enable "prompt to log
in." This seems to not work well because we have had several people now lock
out their windows accounts. Say we have a resource mailbox as
CustomerService, so we configure a CustomerService profile that goes into
their mailbox. The next time I open Outlook, it prompts to log in. We
notice places a domain JULI\CustomerService. We place in the password and it
fails. If we overwrite the JULI\CustomerService with just CustomerService and
place the password, it works well. So then we go back into our mailbox and
it prompts with a JULI\JDOE, we type in the password and oftentimes it
fails...it is a pain. It almost appears if the domain name is in the name,
it doesn't resolve.

Are we doing something incorrectly?