Outlook 2007 Add-in roll-out

We have created a new Outlook 2007 Add-in.

I want to know what instructions I would need to give network administrators
to roll it out simultaneously on all of their Outlook 2007 desktops.

For a single-user it's just a matter of double-clicking our setup.exe and
following the prompts.

Obviously for an enterprise this is not appropriate since they wouldn't want
the end users to have to read license agreements and install options etc.
Rather they'd want a silent install.

I don't know what the standard procedure is these days for rolling out new
software (e.g. on 50,000 plus desktops). I have heard of:

Group Policy Manager
Windows Deployment Services

I need to sound like I know what I'm talking about when I give them
written instructions...

Any suggestions?

TIA

Hello Mark,

What about creating your own .msi? Try WinstallLe, even it is older:
http://technet.microsoft.com/en-us/l.../bb742609.aspx

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> We have created a new Outlook 2007 Add-in.
>
> I want to know what instructions I would need to give network
> administrators to roll it out simultaneously on all of their Outlook
> 2007 desktops.
>
> For a single-user it's just a matter of double-clicking our setup.exe
> and following the prompts.
>
> Obviously for an enterprise this is not appropriate since they
> wouldn't want the end users to have to read license agreements and
> install options etc. Rather they'd want a silent install.
>
> I don't know what the standard procedure is these days for rolling out
> new software (e.g. on 50,000 plus desktops). I have heard of:
>
> Group Policy Manager
> Windows Deployment Services
> I need to sound like I know what I'm talking about when I give them
> written instructions...
>
> Any suggestions?
>
> TIA
>

Mark,
You need to provide them with an installation that runs silently. Ideally it
will install once per machine, and then run a setup per user.
Once you have done that, they will use whatever is their normal software
distribution method,
Anthony,
http://www.airdesk.co.uk

"Mark B" <(E-Mail Removed)> wrote in message
news:#(E-Mail Removed)...
> We have created a new Outlook 2007 Add-in.
>
> I want to know what instructions I would need to give network
> administrators to roll it out simultaneously on all of their Outlook 2007
> desktops.
>
> For a single-user it's just a matter of double-clicking our setup.exe and
> following the prompts.
>
> Obviously for an enterprise this is not appropriate since they wouldn't
> want the end users to have to read license agreements and install options
> etc. Rather they'd want a silent install.
>
> I don't know what the standard procedure is these days for rolling out new
> software (e.g. on 50,000 plus desktops). I have heard of:
>
> Group Policy Manager
> Windows Deployment Services
>
> I need to sound like I know what I'm talking about when I give them
> written instructions...
>
> Any suggestions?
>
> TIA

Thanks. I thought as much. Now the challenge is to try and figure out a way
to get the VSTO bootstraper to run silently.

It installs:

-.Net 3.5
- VSTO Runtime
-The Add-in (C#)

So far we haven't been able to get it to work with the /s switch.


"Anthony [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Mark,
> You need to provide them with an installation that runs silently. Ideally
> it will install once per machine, and then run a setup per user.
> Once you have done that, they will use whatever is their normal software
> distribution method,
> Anthony,
> http://www.airdesk.co.uk
>
> "Mark B" <(E-Mail Removed)> wrote in message
> news:#(E-Mail Removed)...
>> We have created a new Outlook 2007 Add-in.
>>
>> I want to know what instructions I would need to give network
>> administrators to roll it out simultaneously on all of their Outlook 2007
>> desktops.
>>
>> For a single-user it's just a matter of double-clicking our setup.exe and
>> following the prompts.
>>
>> Obviously for an enterprise this is not appropriate since they wouldn't
>> want the end users to have to read license agreements and install options
>> etc. Rather they'd want a silent install.
>>
>> I don't know what the standard procedure is these days for rolling out
>> new software (e.g. on 50,000 plus desktops). I have heard of:
>>
>> Group Policy Manager
>> Windows Deployment Services
>>
>> I need to sound like I know what I'm talking about when I give them
>> written instructions...
>>
>> Any suggestions?
>>
>> TIA
>