Version identification

  • Thread starter Thread starter Doug G
  • Start date Start date
D

Doug G

Is there any easy way to assign a version to my XPE image that would be
easily viewable if I am out in the field and am wondering what image version
a given box has installed on it? My end configuration is fairly
full-featured, so I have Windows Explorer, the Start menu, and most other
desktop interface features available. I have updated the "Version" field in
the main page of the configuration, but I don't know what this is used for.
Under "Settings" I also see a number of strings under "Deployment
Identification Settings", but again I have no idea what these are used for
or where they end up on a target system.

Any ideas?

Doug G
 
Hi Doug,

You can maintain your version.txt file that you can read on these devices.
Or from TD you can write some your registry entry with meaningful values to you. Then during the runtime you can use regedit to view
them.

Best regards,
Slobodan

PS: There might be some better solution, but this is from the head.
 
You can actually use WERUNTIME.INI.
Just add a new filed there (Build#, Version Info, whatever you prefer). It won't break anything but will go with your image
automatically (unless you remove the file manually from your build).

The best, in my believe, would be to update the file through a simple CMI script automatically during build process (on build finish
event, say) increasing the build#. This way you can track all the changes you make.
Also, if you think about automating the build process (although automatic daily builds are not usual for XPe, unfortunately), the
script will save you a bunch of time tracing issues depending on build number.
 
And, btw, you can use "Device Serial Number" field under "Deployment Identification Settings" of the Configuration settings
(cmiDeviceSerial extended property of base instance/configuration).
This goes directly to DeviceSerial option of the [RunTimeID] in WERUNTIME.INI.

Either cmiDeviceSerial or your own extended property may be easy updated within your component script on cmiOnEndBuild event.
Let me know if you need more info.
 
Back
Top