Re: Outlook Messages are not leaving exchange for one user

Good work, Tristan.

--
Les Connor [SBS MVP]


"Tristan" <Tristan@xxxxxxxx> wrote in message news:CB7E2300-0E6B-49A8-B448-C8E3C9CEA52E@xxxxxxxxxxxxxxxx
Hi,

I decided to follow your advice and to just create a new user profile for this user, I didnt have to worry about doing the ESM mailbox changes. All worked fine just creating the users own profile.

Thanks for everyones help, much appreciated.




"Les Connor [SBS MVP]" <les.connor@xxxxxxxxxxxx> wrote in message news:AB3682D5-9585-4396-B85C-AAC2F01F1F96@xxxxxxxxxxxxxxxx
Hi Tristan,

ConnectComputer is only used to add a new computer, you're not doing that - you're just adding a user. The profile will be new, but shouldn't be hard to make work. User1 is going to be happy though, as now user2 isn't going to affect his desktop ;-)>

Create the new user in Standard Management using the add user wizard. If you have any custom security groups that user1 was a member of, then add the new user to these groups.
Go to the workstation, and log onto the computer with the new users domain account.
- you'll likely get a warning that applications can't be installed because of user permissions (the user isn't a local administrator).

If you want the user to be a local administrator:
- log off as user, and log back onto the workstation as the domain administrator, and add the new users' domain account to the Administrator Group.
- log back onto the workstation as the new user, and start outlook - it should be automatically configured to connect to exchange. Don't fret if the mailbox is almost empty.

If you accept that the user is not going to be a local administrator, then start outlook and provide the details to configure it to connect to Exchange. Don't fret if the mailbox is empty.

For the desktop (shortcuts, whatever), a user with Administrator priveledges on the workstation or domain can copy items from the previous users desktop folder to the new users desktop folder.

Log the new user off the workstation.

In ESM, go into your Mailbox Store | Mailboxes, and right click the users newly created mailbox and select Exchange Tasks. Continue on, deleting the mailbox. Refresh your view - the mailbox should now have a red X on it.

Do the same for the users *old* mailbox, and refresh the view.

Now, right click the users *old* mailbox, and select 'reconnect'. Enter the new users name, and click OK.

I think I got all the steps, but if I missed any then post back and someone will help out.



--
Les Connor [SBS MVP]


"Tristan" <Tristan@xxxxxxxx> wrote in message news:30E5263B-6B0C-4D0B-92A6-F4798E79B8BA@xxxxxxxxxxxxxxxx
Do I need to use connectcomputer to add the user. Will that hurt the othe users profile, or will they still be able to login ok?



"Les Connor [SBS MVP]" <les.connor@xxxxxxxxxxxx> wrote in message news:03093EBD-0FF5-4EEE-BC06-B0FD9133D370@xxxxxxxxxxxxxxxx
Hi Tristan,

User2 needs his/her own user account, and should log on as User2, not User1. There's far too much integration and security built in to try and split user accounts down the middle like that.

--
Les Connor [SBS MVP]


"Tristan" <Tristan@xxxxxxxx> wrote in message news:93BA98D0-1D11-43E6-A78B-7037FB3C47CA@xxxxxxxxxxxxxxxx
The thing is the actual logged in user is 'User1' and can send receieve emails fine in Outlook, access all network drives. Outlook has another profile setup for 'User2' who has taken over this machine while 'User1' is away for 3 months. So 'User2' still signs in each day using 'User1' username and password, then starts up outlook and signs in using his information.

This was all working until we corrected the spelling of his account name and email address on the server.. then it all fell over.

Will try all the suggestions posted here today or tomorrow and post back.

Thanks



"Jim Behning SBS MVP" <jimbehning@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:id6713ltnr32ghfn270sgo7qca6i9u3cen@xxxxxxxxxx
Part two of Jacky's comments. I go to run and enter \\servername. If I
do not see all the shares on the server then I know there is an issue.
I go to Control Panel\User Accounts and get to the Advanced and manage
passwords area. I clear all passwords. I log off and log back on. I
try to \\servername again. If it still fails I try with the domain
administrator account. If it still goofs up which almost never happens
then I know the workstation has issues. If any other user can log on
and see all the shares then the user account is the problem. Also test
the user account at a good workstation.

Things I also look for:

I set the Network Location Awareness service to automatic. Requres a
reboot.

I make sure the local area network nic is at the top of the binding
order. Reboot for that also.

Those two clicks usually fix the inability to see \\servername which
in turn will probably fix an Outloook problem.

On Wed, 04 Apr 2007 09:41:11 GMT, v-jaluo@xxxxxxxxxxxxxxxxxxxx ("Jacky
Luo [MSFT]") wrote:

Hi Tristan,

Thanks for posting back.

Have you tried other two suggestions?

1.use the account to login another computer ,create corresponding outlook
profile, then to see if the issue still occur.

2.if the issue persists,create a new account by add user wizzard,on the
problematic client,disjoin domain,then use the new account rejoin the
domain,outlook profile should be ready,then test again to see if the new
account can send email by outlook on the problematic client.

so we can draw the conclusion if it is a client side issue.


Thanks for your time, Please try the suggestions above and let me know the
results at your earliest convenience. I look forward to hearing from you
soon.


Best regards,

Jacky Luo (MSFT)
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
====================================================
PLEASE NOTE: The partner managed newsgroups are provided to
assist with break/fix issues and simple how to questions.
We also love to hear your product feedback! Let us know what you think by
posting

from the web interface: Partner Feedback
from your newsreader: microsoft.private.directaccess.partnerfeedback.

We look forward to hearing from you!
====================================================
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from this issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
====================================================






.

Relevant Pages

  • Re: Outlook Messages are not leaving exchange for one user
    ... I decided to follow your advice and to just create a new user profile for this user, I didnt have to worry about doing the ESM mailbox changes. ... and log onto the computer with the new users domain account. ... If you accept that the user is not going to be a local administrator, then start outlook and provide the details to configure it to connect to Exchange. ...
    (microsoft.public.windows.server.sbs)
  • Re: Outlook Messages are not leaving exchange for one user
    ... The profile will be new, but shouldn't be hard to make work. ... and log onto the computer with the new users domain account. ... Don't fret if the mailbox is almost empty. ... If you accept that the user is not going to be a local administrator, then start outlook and provide the details to configure it to connect to Exchange. ...
    (microsoft.public.windows.server.sbs)
  • Re: Russ Grover & Dave Nickason - RPC over HTTP and Outlook Cont
    ... Delete that profile. ... will open their own mailbox. ... When Outlook is open, go to Tools/email ... have access to OWA - it's an account property. ...
    (microsoft.public.windows.server.sbs)
  • Re: Outlook 2003 and XP SP2
    ... profile, ... You can only have one exchange account ... Diane Poremsky [MVP - Outlook] ... Outlook & Exchange Solutions Center: http://www.slipstick.com ...
    (microsoft.public.office.setup)
  • Re: Outlook 2003 and XP SP2
    ... Milly Staples [MVP - Outlook] ... account will be deleted without reading. ... || Vote for your favorite Outlook and Exchange utilities in the ... to the profile, ...
    (microsoft.public.office.setup)