Create a custom registry key for version tracking?
Posted on 2014-12-03
What would be a good way to create a custom Registry key and data value to be something like "version 1.0" or "version 2.0" for my over all operating system deployment? Not the Windows version, but the build of the task sequence I deploy for the entire OS setup.
I'm deploying OS's with task sequence in SCCM, and while I do have an image version, the task sequence is what really completes and finalizes it.
Currently as a last step of the OS deployment, I have a batch script that generates a file to C-drive with a date time-stamp as its name (using powershell) to show when it was imaged.
But I'm wondering if I should go for the registry instead, and if so, which key should I add into that won't cause issues? Just something benign that I can refer to on remote registry scans going forward.