AD uses the network location for the source of the application. It does not copy
the source locally. The disadvantage would be the additional use of disk space
to support that. Of course the advantage is that for those users that are
frequently disconnected from the network, the source is always available since
it's on the local disk.
Some application setups have tried to find a middle ground for this as well.
Office 2003 has its own local cache mechanism that will cache files from the
network onto the local disk for future use during install on-demand and repair
scenarios.
- 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>
"oscarmok" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Carolyn
>
> Is there a way we can have the source files in local HD than pointing
> it to network in AD environment? I was told if we use deployment
> software like Altiris or Zenworks, it copies the source to local HD.
> What's the disadvantage of those deployment tools that copy the source
> to local HD than network?
>
>
> "Carolyn Napier [MSFT]" <(E-Mail Removed)> wrote in message
> news:<(E-Mail Removed)>...
>> What are you referring to as the local cache? The location of the source
>> files
>> for the installation? The Installer maintains a cache of the databases it
>> uses
>> for the installation. However, it does not cache the source files from the
>> install. The source location will be the launched from location for the
>> package.
>>
>> With AD, the source will always be the network location since that's how AD
>> works. As for self-repair, a properly authored setup shouldn't always invoke
>> self-repair. It should only require access to the source location if it
>> intends
>> to use features/components that were not installed or if the user has
>> manually
>> deleted a required file (typically a keypath of a component).
>>
>> - 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>
>>
>>
>> "oscarmok" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>> >I hope someone can help us.
>> >
>> > When I use AD to publish the app (MSI), the apps install fine.
>> > However, I noticed the local cache is point back to the server (not in
>> > the local hd). The make self-repair happen, the application must find
>> > the location of the original file. How can I put the local cache in
>> > local hd and make the self-repair happens in local hd?
>> >
>> > We are pushing by workstation, not user. We are running Windows
>> > 2003/2000 mix environment.
|
Similar Threads
