I run into trouble occasionally when I update a package that may be part of a task sequence. It seems that the TS collects the version number of the package at the beginning of the TS and then if the package is updated while the TS is running, it fails from a hash mismatch. The TS running on the client is looking for an older package (and hash).
I wonder when the package version is collected, and is there any command I can run to make the package number be recomputed during the TS. For instance, if I have a TS line that says Install Notepad, there is no package number listed in the TS - it just says install this package. At what point is the package ID/version captured? Can I get around this problem? I hesitate to update packages because in a place like mine, there is always someone running a deployment and there is no good time to update packages. Are there steps I can take to help mitigate this problem? The package might be called explicitly in the Task Sequence or it might be called by dynamic packages reference ie -- Package001=XXX00001a, Package002=xxx000067, etc. When does the version get captured for xxx00001a? Why not just in time? What do you do about this? ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________
