1 of 1 people found this helpful
I am unable to answer the title of this post for certain without more information - but my best guess is that maybe an inventory scan hasn't updated the record in the core database yet.
However I can answer the body of the post.
The error you are getting is because the 220.127.116.11 update added new client features for software deployment that the core believes a 18.104.22.168 client would be unable to handle. The core is only checking its database record to determine this, not actually asking the client for its version number to reduce the number of network calls made. This would eventually correct itself when the inventory record updates correctly.
The proper work around to avoid these errors and have a successful deployment regardless of version mismatches would be to follow these steps:
1. In your console click Tools -> Distribution -> Delivery methods
2. Open each of your deployment methods and change the Downgrade options to support older clients.
This will then proceed with your deployments and ignore any new features that the client might not support.
Hope this helps,
Sorry I wasn't very specific regarding the version numbers.
When I go to help -> about landesk in the management console that's where I see 22.214.171.124, but when right clicking on the client and selecting status, the version shows up as 126.96.36.199.
Ah, to answer that half:
The core version will not match the clients at all times. If a fix was released just for the clients through patch and compliance it would change the client version forward, but the servers would not change unless a patch is provided for it as well. The opposite can occur as well.
In addition to that you will also see Windows clients and Mac clients have different version codes depending on their individual bug fixes.
On the community site here under downloads you can find sustaining core and client updates that you might be missing.
*Update: For your core version, your clients should be 188.8.131.52 - this explains why the downgrade issue was occurring as well. So look for an update under patch and compliance.
Hope this answers your question,