Re: connect exchange on startup
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 30 Jan 2008 19:24:03 -0500
rostie <rostie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
im not sure if its because of the roaming profile but i got informed
about this after i switched the profile to roaming (my users dont
have the good habbit to note all their problems at once, they stapple
them nd then say it all happens since some time :S)
Oh yes. Understood.
anyways.
running exchange 2003 SP2 on winxp sp2 machines with outlook 2003 (as
provided with sbs 2003 prem r2)
this is the only user that has a flexible workspace and must use
several computers.
OK - see my notes re roaming profiles and be very careful.
im pretty sure its an outlook message telling it cant connect to the
exchange server for some reason but when i click connect its being
asked again when i start outlook.
outlook states exchange as "connected"
the message is:
"exchange is now being executed in recoverymode.
you can connect to exchange over the network, work offline or ignore
this message"
i hope i provided enough details to help you solve my problem
Ah, this is different. That's the OST file. Make sure the user is logged in
only at this one computer. Disable cached mode, delete the OST file, restart
Outlook and re-enable cached mode.
Users with roaming profiles shouldn't log into multiple computers at the
same time, note. check the event logs for more clues.
"Lanwench [MVP - Exchange]" wrote:
rostie <rostie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
as of some days one of my clients is being asked to "connect or work
offline" after logging onto his desktop system or when starting
outlook
i guess something went wrong when his profile became "roaming" but
im not sure about this.
after choosing connect the system logs onto exchange correctly.
anyone knows how to solve this?
This has to be an Outlook message (does he have Outlook in his
startup?) but I don't see how it could be related to the fact that
he now has a roaming profile-- unless he's having larger login
problems behind the scenes of which you are not yet aware.
He should be using OL2003 or 2007 in cached mode - right?
Take a look in his mail profile (control panel, mail) and check the
properties of the Exchange service. In the General tab,
"automatically detect connection state" should be ticked.
If it is, then check the workstation event logs for clues. I'm
listing my boilerplate on roaming profiles below just in case it
helps.
--
General tips:
1. Set up a share on the server. For example - d:\profiles, shared as
profiles$ to make it hidden from browsing. Make sure this share is
*not* set to allow offline files/caching! (that's on by default -
disable it)
2. Make sure the share permissions on profiles$ indicate
everyone=full control. Set the NTFS security to administrators,
system, and users=full control.
3. In the users' ADUC properties, specify
\\server\profiles$\%username% in the profiles field
4. Have each user log into the domain once from their usual
workstation (where their existing profile lives) and log out. The
profile is now roaming.
5. If you want the administrators group to automatically have
permissions to the profiles folders, you'll need to make the
appropriate change in group policy. Look in computer
configuration/administrative templates/system/user profiles -
there's an option to add administrators group to the roaming
profiles permissions.
Notes:
* Make sure users understand that they should not log into multiple
computers at the same time when they have roaming profiles (unless
you make the profiles mandatory by renaming ntuser.dat to ntuser.man
so they can't change them). Explain that the
last one out wins,
when it comes to uploading the final, changed copy of the profile.
* Keep your profiles TINY. Via group policy, redirect My Documents
at the very least - to a subfolder of the user's home directory or
user folder. Also consider redirecting Desktop & Application Data
similarly..... so the user will have:
\\server\home$\%username%\My Documents,
\\server\home$\%username%\Desktop,
\\server\home$\%username%\Application Data.
Alternatively, just manually re-target My Documents to
\\server\home$\%username% (this is not optimal, however!)
If you aren't going to also redirect the desktop using policies,
tell users that
they are not to store any files on the desktop or you will beat them
with a stick. Big profile=slow login/logout, and possible profile
corruption.
* Note that user profiles are not compatible between different OS
versions, even between W2k/XP. Keep all your computers. Keep your
workstations as identical as possible - meaning, OS version is the
same, SP level is the same, app load is (as much as possible) the
same.
* Do not let people store any data locally - all data belongs on the
server.
* The User Profile Hive Cleanup Utility should be running on all your
computers. You can download it here:
http://www.microsoft.com/downloads/details.aspx?familyid=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en
Roaming profile & folder redirection article -
http://www.windowsnetworking.com/articles_tutorials/Profile-Folder-Redirection-Windows-Server-2003.html
.
- References:
- Re: connect exchange on startup
- From: Lanwench [MVP - Exchange]
- Re: connect exchange on startup
- From: rostie
- Re: connect exchange on startup
- Prev by Date: Re: Small Business Server 2003 lockups
- Next by Date: Re: offline files
- Previous by thread: Re: connect exchange on startup
- Next by thread: Re: Moving mail to new user
- Index(es):
Relevant Pages
|
