Outlook 2003, how to prevent first run

Hi,

I've created a script that sets up RPCoverHTTP on any computer, matching a
certain setup, and it works fine.

However on machines where Outlook 2003 has never run, I get the first run
wizzard popping up. That's something I'd like to stop.

The internet is overflowing about how to force First run, not how to avoid it.

So here's what I do myself.

1. run the script
2. cancel the Outlook first run wizzard
3. kill the script
4. re-run the script.

However, this is totally unexplainable for the average user.

I've been looking for registry keys to stop this, I've been thinking of
re-writing the script to launch Outlook and then kill it and then run the
original script.

I've exported registry before and after, but cannot pinpoint exactly where
the changes are

So any input, pretty please.

Kim

Try;

HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook
Value name: FirstRunDialog
Type: REG_SZ
Value: False

Note that everything is case sensitive.

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

http://www.msoutlook.info/
Real World Questions, Real World Answers

-----

"MijakiDK" <MijakiDK.TakeThisOut@discussions.microsoft.com> wrote in message
news:40E7B1B8-2843-4E9F-BDCB-3A9869D7FB62@microsoft.com...
> Hi,
>
> I've created a script that sets up RPCoverHTTP on any computer, matching a
> certain setup, and it works fine.
>
> However on machines where Outlook 2003 has never run, I get the first run
> wizzard popping up. That's something I'd like to stop.
>
> The internet is overflowing about how to force First run, not how to avoid
> it.
>
> So here's what I do myself.
>
> 1. run the script
> 2. cancel the Outlook first run wizzard
> 3. kill the script
> 4. re-run the script.
>
> However, this is totally unexplainable for the average user.
>
> I've been looking for registry keys to stop this, I've been thinking of
> re-writing the script to launch Outlook and then kill it and then run the
> original script.
>
> I've exported registry before and after, but cannot pinpoint exactly where
> the changes are
>
> So any input, pretty please.
>
> Kim