Hopefully someone here knows the answer, as apparently MS does not (I've seen it asked a few times on their various forums with no answer).

1) If you run the setup.exe from the Network with the precache option, what happens if you then run setup.exe from the network later? My guess is that it will recache, instead of "know" that it's already cached?

2) What happens if you run the setup.exe from the network and something happens (for whatever reason) and the cache isn't completed successfully (ie, PC reboots in the middle of the file copy, etc.) and then you follow the official MS docs that state you run the setup.exe from the LOCAL cache? I am assuming you get an error?

3) In the above scenario, is there a way to ensure that the files are all cached before the install actually kicks off (other than simply running setup.exe from the network without precaching)?
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


All those scenarios would be simple to monitor with a file monitor. If it were me, I'd set up a test environment and - as they say - suck it and see.
Answered 03/25/2009 by: VBScab
Red Belt

Please log in to comment