O2K3 Multiple OSTs

[Guest]

When opening Outlook 2003 each day, some of our users are getting the
"Starting Outlook for first use" message. When I check the Outlook directory
in the user profile I can see many OSTs named outlook.ost, outlook0.ost,
outlook1.ost, etc.

Does anyone know why this is happening and how I can get it to stop?

Many thanks

 

[Roady [MVP]]

How are your mail profiles created? Manually or by script?

 

[Guest]

Script. If it can't find an OST it creates a new profile. If the the OST
exists (which it does in this case) it uses that.

How are your mail profiles created? Manually or by script?

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----

When opening Outlook 2003 each day, some of our users are getting the
"Starting Outlook for first use" message. When I check the Outlook
directory
in the user profile I can see many OSTs named outlook.ost, outlook0.ost,
outlook1.ost, etc.

Does anyone know why this is happening and how I can get it to stop?

Many thanks

 

[Roady [MVP]]

That is not a fail proof method. Profile settings are roaming settings while
the ost-file is only a local cache. If the user logs on to a different
machine your script will have adverse effects; it creates a new profile
since it can't find an ost-file and when the users logs on to his/her own
machine again Outlook will create a new ost-file since the ost-file and
profile doesn't match anymore.

Deploying Office with a mst or cmw is much more reliable.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----

Script. If it can't find an OST it creates a new profile. If the the OST
exists (which it does in this case) it uses that.

How are your mail profiles created? Manually or by script?

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----

When opening Outlook 2003 each day, some of our users are getting the
"Starting Outlook for first use" message. When I check the Outlook
directory
in the user profile I can see many OSTs named outlook.ost,
outlook0.ost,
outlook1.ost, etc.

Does anyone know why this is happening and how I can get it to stop?

Many thanks

 

[Guest]

It's not a fail proof method if the user is logging onto multiple desktops,
but this method is used for our laptop users. He's logging onto his own
laptop each day and this problem is occuring.

That is not a fail proof method. Profile settings are roaming settings while
the ost-file is only a local cache. If the user logs on to a different
machine your script will have adverse effects; it creates a new profile
since it can't find an ost-file and when the users logs on to his/her own
machine again Outlook will create a new ost-file since the ost-file and
profile doesn't match anymore.

Deploying Office with a mst or cmw is much more reliable.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----

Script. If it can't find an OST it creates a new profile. If the the OST
exists (which it does in this case) it uses that.

How are your mail profiles created? Manually or by script?

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

-----
When opening Outlook 2003 each day, some of our users are getting the
"Starting Outlook for first use" message. When I check the Outlook
directory
in the user profile I can see many OSTs named outlook.ost,
outlook0.ost,
outlook1.ost, etc.

Does anyone know why this is happening and how I can get it to stop?

Many thanks

 

[Roady [MVP]]

Note that runing the (logon?) script and loading the user profile (don't
confuse with mail profile) is a synchronous process in Windows XP. You can
change this in GPO. If this script is no longer required to run why not
simply disable it?

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----

It's not a fail proof method if the user is logging onto multiple
desktops,
but this method is used for our laptop users. He's logging onto his own
laptop each day and this problem is occuring.

That is not a fail proof method. Profile settings are roaming settings
while
the ost-file is only a local cache. If the user logs on to a different
machine your script will have adverse effects; it creates a new profile
since it can't find an ost-file and when the users logs on to his/her own
machine again Outlook will create a new ost-file since the ost-file and
profile doesn't match anymore.

Deploying Office with a mst or cmw is much more reliable.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----

Script. If it can't find an OST it creates a new profile. If the the
OST
exists (which it does in this case) it uses that.

:

How are your mail profiles created? Manually or by script?

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

-----
When opening Outlook 2003 each day, some of our users are getting
the
"Starting Outlook for first use" message. When I check the Outlook
directory
in the user profile I can see many OSTs named outlook.ost,
outlook0.ost,
outlook1.ost, etc.

Does anyone know why this is happening and how I can get it to stop?

Many thanks