Hey all,

I've got a deployment of Office 2003 SP2 (slipstreamed) that I'm about
to start. All of the Outlook settings are done by the .MST (cached
exchanged mode, server name, etc).

The thing is, I've got a script that I want to start when Outlook runs
for the first time that contains info I can't embed in the .MST. So the
question is, can I embed a call to the script somehow so that it runs
the first time Outlook does? I've seen the "firstrun" & "first-run"
keys in the Outlook registry, but I don't undertstand what they do.

Any thoughts welcome!

Rich

Those registry values are used internally by Outlook to perform its own firstrun chores. You can't hook yours into it.

One technique that I've experimented with is incorporating a script like yours into a folder home page (web page associated with the Inbox or another Outlook folder) and using a login script to set the registry values (you can look them up in the Outlk11.adm file) that set the startup folder so it's the Inbox and set the FHP on the Inbox to the web page that runs the script. The script can turn off the FHP on the Inbox as part of its actions.

--
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

wrote in message ups.com...
Hey all,

I've got a deployment of Office 2003 SP2 (slipstreamed) that I'm about
to start. All of the Outlook settings are done by the .MST (cached
exchanged mode, server name, etc).

The thing is, I've got a script that I want to start when Outlook runs
for the first time that contains info I can't embed in the .MST. So the
question is, can I embed a call to the script somehow so that it runs
the first time Outlook does? I've seen the "firstrun" & "first-run"
keys in the Outlook registry, but I don't undertstand what they do.

Any thoughts welcome!

Rich