SCCM PackageID (Cache folder) always increase after Re-RUN Advertisement.
Hi,
Is there a way to stop increasing the "PACKAGEID" version in cache folder?
What he is talking about ??
When you deploy a package through a colletion of wks in SCCM the source file are deposit in the cache folder. c:\windows\system32\CCM\cache , for this example we will use the package ID C0100004.5.Sytem. So the source are cache under c:\windows\system32\CCM\cache\C0100004.5.Sytem
If we RE-RUN the advertisement on the same package, a New cache folder is created but this time the packageID version increase ex: c:\windows\system32\CCM\cache\C0100004.6.Sytem (from 4.5 to 4.6). Is there a way to REcache in the same folder (C0100004.5.Sytem)
We use a custom script to launch our package, but this one must be in a static folder.
thanks for your help.
Is there a way to stop increasing the "PACKAGEID" version in cache folder?
What he is talking about ??
When you deploy a package through a colletion of wks in SCCM the source file are deposit in the cache folder. c:\windows\system32\CCM\cache , for this example we will use the package ID C0100004.5.Sytem. So the source are cache under c:\windows\system32\CCM\cache\C0100004.5.Sytem
If we RE-RUN the advertisement on the same package, a New cache folder is created but this time the packageID version increase ex: c:\windows\system32\CCM\cache\C010000
We use a custom script to launch our package, but this one must be in a static folder.
thanks for your help.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
MSIPackager
13 years ago
Hi there.
I'm not sure that you can disable this functionality. Couple of other options / suggestions though;
Can you not leave the files on the DP and have your script call it from there?
You could have an installation package copy / script to the files to elsewhere (e.g. c:\program files\myapp\myapp.exe) then have your script run it from there
I guess the bigger question is what are you trying to achieve (what does the script do etc) and why do you need to keep re-running the advertisment?
Cheers,
Rob.
I'm not sure that you can disable this functionality. Couple of other options / suggestions though;
Can you not leave the files on the DP and have your script call it from there?
You could have an installation package copy / script to the files to elsewhere (e.g. c:\program files\myapp\myapp.exe) then have your script run it from there
I guess the bigger question is what are you trying to achieve (what does the script do etc) and why do you need to keep re-running the advertisment?
Cheers,
Rob.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
