William M. Smith said:
Hi Chris!
The Outlook Settings Control Panel will open even without Exchange
connectivity, so don't take this as a sign that your Mac is talking to
Exchange just yet.
While in Outlook Settings, select Microsoft Exchange Server from the
Services tab and then click the Properties...button. Click the Check Name
button to verify connectivity.
If Outlook won't open because of a problem with personal folders, try
removing any personal folders from the list of Services in the Outlook
Settings Control Panel. You can add them back later.
You might also verify that your Hosts files still exists if you were using
one and that your TCP/IP Preferences still point to this Hosts file.
Hope this helps! bill
Bill,
Rob BRown here from Pearson PLC. The domain login screen does not show
up, it states "The set of folders can not be opened. The attempt to
log on the the Microsoft Exchange Server Computer has failed." This is
immediatley followed by "Microsoft Outlook could not be started. The
attempt to log on the the Microsoft Exchange Server Computer has
failed." This is immediatley after setting up an account and
validating it through the Outlook settings control panel. If I delete
the the Outlook Exchange Preferences and Profiles from the Preferences
folder and launch the application it give the Microsoft Outlook cannot
write information needed to complete installation error. I can run it
if the Outlook application is copied and run off a seperate
partition(while booted off the same system of course.) This only has
occured to me after imaging a master drive that outlook was working
fine on after the 10.3 upgrade and restoring that image another
machine. Of note is that when it is run off another partion or off a
mounted read/write disk image a file called rpcreg.bak is created with
these contents:
\Root\Software\Description\Microsoft\Rpc\UuidPersistentData=
\Root\Software\Description\Microsoft\Rpc\UuidPersistentData\ClockSequence=15486
Please let me know anything that you can think of, I have been beating
my head against a wall for 3 weeks trying to figure this out, and we
have to deploy 10.3 on 500 systems in the next month. Considering we
still have a 5.5 backend and won't be upgrading to AD and 2003 until
the middle of the next calendar year this has the potential to affect
a few thousand more systems.
Thanks in advanced,
Rob Brown