A little background info on our environment before I begin with my question:

Ghost Server OS: Windows Server 2008 Standard 64-bit, SP1

Ghost Console Version: 11.5.0.2141 (According to the bottom of the Boot Wizard screen) ||| 11.5.0.2113 (According to Help -> About...)

Pre-OS: PC-DOS

OS Ghost Clients Are Running On: Windows Vista SP1

 I am having an issue with the version of the client console that is installed on our machines. This issue has been ongoing since the upgrade from GSS 2.0.2 to GSS 2.5. The first issue is with the versions. On most of my clients, I have been able to update the version of the console client listed under the client tab for each machine. The client version reads 11.5.0.2141, and the required version reads the same. This is how the client shows up in the console when connected to Ghost and booted into Windows. When you boot it into network/PXE boot mode, the status of the client changes in the console. The icon goes to the connected icon with the red exclamation point, and the client version changes to 11.0.1.1533, even though the required version is 11.5.0.2141. When you reboot the machine from PXE mode, it's status in the console goes back to the above status (both version numbers being current and matching) I've also noticed that when you run a task on a machine (this is the second issue btw) such as an image creation or cloning task, it runs two DOS client upgrades, and they always succeed without error. However, they never seem to stick as it has to run those two client upgrades EVERY time a task is run where the machine has to go into PC-DOS, which makes image creation tasks cumbersome. I'm thinking those two issues (the old version numbers and the multiple DOS client updates) are related. However, I cannot seem to figure out how to re-install the DOS client, if that's even possible. I've tried re-installing the ghost client on one of the machines from the GSS 2.5 disc, however that does not seem to fix the issue. I guess I'm looking an answer as to why this is happening or at least some suggestions as to what I should try to remedy this.

One other thing to note, this issue seems to occur not only with machines that existed before the upgrade from 2.0.2 to 2.5, but also with brand new machines added to the console since the upgrade.