Search the Community

Hello! I need a consistent way to pass information between the PreImage and the PostImage scripts. I'm deploying the corporate computers using an offline USB drive. In order to avoid modifications, I'm adding a md5 checksum on the PreImage task in order to detect if my configuration file has been tampered with or modified. If the verification fails, It shows an error message and forces a shutdown. But if the verification is successful, I need a way to tell that to the PostImage script. Normally I would do that using an environment variable, but the command window closes after PreImage script finishes (hence I lose all environment vars I may have been set for that session) and the 'setx' command is not available in Windows PE. I've been thinking in either writing a temporary file (which I don't like) or maybe setting a temporary registry key in Windows PE. So, my question is: is there a recommended way to pass information between the PreImage and the PostImage scripts? Maybe is there some undocumented 'setx' equivalent tool available somewhere in the SmartDeploy Windows PE environment? Thanks in advance and best regards, -- Javier Llorente

Hello, I'm deploying the corporate computers using an offline USB drive. In order to avoid modifications, I'm adding a md5 checksum on the PreImage task in order to detect if my configuration file has been tampered with or modified. If the verification fails, I need a clean and neat way to abort the deployment on this phase. Sure, I may request the user to just unplug the USB drive and shutdown the computer, but I guess there must be a better way to abort the process at this point. So, what would be the proper way to abort the deployment process from a script in the PreImage phase? Thanks in advance and best regards, -- Javier Llorente