Need some help, I have never used distribution of
software with group policies. The more I read about it
the more confused I am.

1- How do I package a *.exe into *.msi using wininstall?

2- Do I create an new OU to test the distribution?

3- How do I schedule and point to my new OU for
distribution?

I know its alot of question, but I am really confused.

Thanks

WinInstall LE included on the Windows 2000 CD works via snapshot technology. You
basically start with a clean install of the operating system. Then create a
snapshot. You then install your application (using the setup EXE). Create a new
snapshot. Then run wininstall to generate the diff. WinInstall LE is what is
known as a repackager. It takes an existing exe setup and converts it
(repackages it) into a MSI package. Note that you should avoid repackaging
native MSI installations.

There are instructions for software deployment available on the web.
Instructions on how to use WinInstall LE from the Windows 2000 CD are available
at <
http://www.microsoft.com/windows2000...nt/veritas.asp >.
Note that there's now a new free version of repackaging software for WinInstall
at < http://www.ondemandsoftware.com/ >. You may find other information on a
variety of repackagers at < http://www.installsite.org >

As for instructions on software deployment, check out <
http://www.microsoft.com/windows2000...ent/siamwp.asp
>.

Hope this helps,
- Carolyn Napier
Microsoft Windows Installer Team

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

MSI FAQ:
<http://www.microsoft.com/windows2000/community/centers/management/msi_faq.mspx>


"Sylvain" <(E-Mail Removed)> wrote in message
news:7c7701c43142$810f6990$(E-Mail Removed)...
> Need some help, I have never used distribution of
> software with group policies. The more I read about it
> the more confused I am.
>
> 1- How do I package a *.exe into *.msi using wininstall?
>
> 2- Do I create an new OU to test the distribution?
>
> 3- How do I schedule and point to my new OU for
> distribution?
>
> I know its alot of question, but I am really confused.
>
> Thanks

Thank you Carolyn,

Actually I would like to be able to push anti-virus hot
fix's and also Microsoft updates. From what I can see I
will not be able to use WinInstall.

How to convert an MS Patch exe into an distributable MSI
via AD.

Thanks
Sylvain
>-----Original Message-----
>WinInstall LE included on the Windows 2000 CD works via
snapshot technology. You
>basically start with a clean install of the operating
system. Then create a
>snapshot. You then install your application (using the
setup EXE). Create a new
>snapshot. Then run wininstall to generate the diff.
WinInstall LE is what is
>known as a repackager. It takes an existing exe setup
and converts it
>(repackages it) into a MSI package. Note that you should
avoid repackaging
>native MSI installations.
>
>There are instructions for software deployment available
on the web.
>Instructions on how to use WinInstall LE from the
Windows 2000 CD are available
>at <
>http://www.microsoft.com/windows2000...fo/planning/ma
nagement/veritas.asp >.
>Note that there's now a new free version of repackaging
software for WinInstall
>at < http://www.ondemandsoftware.com/ >. You may find
other information on a
>variety of repackagers at < http://www.installsite.org >
>
>As for instructions on software deployment, check out <
>http://www.microsoft.com/windows2000...fo/administrat
ion/management/siamwp.asp
> >.
>
>Hope this helps,
>- Carolyn Napier
>Microsoft Windows Installer Team
>
>--
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>Please do not send email directly to this alias. This
alias is for newsgroup
>purposes only.
>
>MSI FAQ:
><http://www.microsoft.com/windows2000...nity/centers/m
anagement/msi_faq.mspx>
>
>
>"Sylvain" <(E-Mail Removed)> wrote in
message
>news:7c7701c43142$810f6990$(E-Mail Removed)...
>> Need some help, I have never used distribution of
>> software with group policies. The more I read about it
>> the more confused I am.
>>
>> 1- How do I package a *.exe into *.msi using
wininstall?
>>
>> 2- Do I create an new OU to test the distribution?
>>
>> 3- How do I schedule and point to my new OU for
>> distribution?
>>
>> I know its alot of question, but I am really confused.
>>
>> Thanks
>
>
>.
>

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

MSI FAQ:
<http://www.microsoft.com/windows2000/community/centers/management/msi_faq.mspx>


"Sylvain" <(E-Mail Removed)> wrote in message
news:9a9e01c4343d$789dbf70$(E-Mail Removed)...
> Thank you Carolyn,
>
> Actually I would like to be able to push anti-virus hot
> fix's and also Microsoft updates. From what I can see I
> will not be able to use WinInstall.
>
> How to convert an MS Patch exe into an distributable MSI
> via AD.
>
> Thanks
> Sylvain
>>-----Original Message-----
>>WinInstall LE included on the Windows 2000 CD works via
> snapshot technology. You
>>basically start with a clean install of the operating
> system. Then create a
>>snapshot. You then install your application (using the
> setup EXE). Create a new
>>snapshot. Then run wininstall to generate the diff.
> WinInstall LE is what is
>>known as a repackager. It takes an existing exe setup
> and converts it
>>(repackages it) into a MSI package. Note that you should
> avoid repackaging
>>native MSI installations.
>>
>>There are instructions for software deployment available
> on the web.
>>Instructions on how to use WinInstall LE from the
> Windows 2000 CD are available
>>at <
>>http://www.microsoft.com/windows2000...fo/planning/ma
> nagement/veritas.asp >.
>>Note that there's now a new free version of repackaging
> software for WinInstall
>>at < http://www.ondemandsoftware.com/ >. You may find
> other information on a
>>variety of repackagers at < http://www.installsite.org >
>>
>>As for instructions on software deployment, check out <
>>http://www.microsoft.com/windows2000...fo/administrat
> ion/management/siamwp.asp
>> >.
>>
>>Hope this helps,
>>- Carolyn Napier
>>Microsoft Windows Installer Team
>>
>>--
>>This posting is provided "AS IS" with no warranties, and
> confers no rights.
>>Please do not send email directly to this alias. This
> alias is for newsgroup
>>purposes only.
>>
>>MSI FAQ:
>><http://www.microsoft.com/windows2000...nity/centers/m
> anagement/msi_faq.mspx>
>>
>>
>>"Sylvain" <(E-Mail Removed)> wrote in
> message
>>news:7c7701c43142$810f6990$(E-Mail Removed)...
>>> Need some help, I have never used distribution of
>>> software with group policies. The more I read about it
>>> the more confused I am.
>>>
>>> 1- How do I package a *.exe into *.msi using
> wininstall?
>>>
>>> 2- Do I create an new OU to test the distribution?
>>>
>>> 3- How do I schedule and point to my new OU for
>>> distribution?
>>>
>>> I know its alot of question, but I am really confused.
>>>
>>> Thanks
>>
>>
>>.
>>

Unless the hotfix was provided in MSI format, there's no true support for
deploying it as an MSI. However, that's not to say that it can't be done. You
basically use the MSI package as a wrapper that runs a custom action (generally
deferred + no impersonate). There's a KB article that briefly discusses this is
at < http://support.microsoft.com/default...b;en-us;320539 >. The
update.msi package included with the service pack installations can be used as a
rough guide as well.

Going forwards, Microsoft is recommending the use of Windows Update Services or
SMS for deploying hotfixes. You can find more information about Windows Update
Services at < http://www.microsoft.com/windowsserv...s/default.mspx >
and < http://www.microsoft.com/windowsserv...s/wusbeta.mspx >.

Hope this helps,
- Carolyn Napier
Microsoft Windows Installer Team

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

MSI FAQ:
<http://www.microsoft.com/windows2000/community/centers/management/msi_faq.mspx>


"Sylvain" <(E-Mail Removed)> wrote in message
news:9a9e01c4343d$789dbf70$(E-Mail Removed)...
> Thank you Carolyn,
>
> Actually I would like to be able to push anti-virus hot
> fix's and also Microsoft updates. From what I can see I
> will not be able to use WinInstall.
>
> How to convert an MS Patch exe into an distributable MSI
> via AD.
>
> Thanks
> Sylvain
>>-----Original Message-----
>>WinInstall LE included on the Windows 2000 CD works via
> snapshot technology. You
>>basically start with a clean install of the operating
> system. Then create a
>>snapshot. You then install your application (using the
> setup EXE). Create a new
>>snapshot. Then run wininstall to generate the diff.
> WinInstall LE is what is
>>known as a repackager. It takes an existing exe setup
> and converts it
>>(repackages it) into a MSI package. Note that you should
> avoid repackaging
>>native MSI installations.
>>
>>There are instructions for software deployment available
> on the web.
>>Instructions on how to use WinInstall LE from the
> Windows 2000 CD are available
>>at <
>>http://www.microsoft.com/windows2000...fo/planning/ma
> nagement/veritas.asp >.
>>Note that there's now a new free version of repackaging
> software for WinInstall
>>at < http://www.ondemandsoftware.com/ >. You may find
> other information on a
>>variety of repackagers at < http://www.installsite.org >
>>
>>As for instructions on software deployment, check out <
>>http://www.microsoft.com/windows2000...fo/administrat
> ion/management/siamwp.asp
>> >.
>>
>>Hope this helps,
>>- Carolyn Napier
>>Microsoft Windows Installer Team
>>
>>--
>>This posting is provided "AS IS" with no warranties, and
> confers no rights.
>>Please do not send email directly to this alias. This
> alias is for newsgroup
>>purposes only.
>>
>>MSI FAQ:
>><http://www.microsoft.com/windows2000...nity/centers/m
> anagement/msi_faq.mspx>
>>
>>
>>"Sylvain" <(E-Mail Removed)> wrote in
> message
>>news:7c7701c43142$810f6990$(E-Mail Removed)...
>>> Need some help, I have never used distribution of
>>> software with group policies. The more I read about it
>>> the more confused I am.
>>>
>>> 1- How do I package a *.exe into *.msi using
> wininstall?
>>>
>>> 2- Do I create an new OU to test the distribution?
>>>
>>> 3- How do I schedule and point to my new OU for
>>> distribution?
>>>
>>> I know its alot of question, but I am really confused.
>>>
>>> Thanks
>>
>>
>>.
>>