A number of customers reported an issue with ParagoAgent that causes the first upload to fail to be uploaded correctly preventing the Parago system from adding the new PC to the system. The issue resolves itself within a month and there is an easy work around but in some circumstances (such as Computers for Pupils) this is unacceptable. Improvements were also made in the compatibility with Microsoft Windows Vista™ and multi-proxy support was added to allow ParagoAgent to work better in a portable environment.
Rationale
This release fixes the detection of the different versions of Microsoft Windows Vista™ and Server 2008 (previously Longhorn) an issue with the initial upload to the Parago system and a number of minor stability issues. It is recommended that customers using these operating systems or critically require that the initial uploads always work (such as schools being part of Computers for Pupils) upgrade at this time.
Details
- Issue with the misidentification of Microsoft Windows Vista™ versions.
- Issue with initial upload to the Parago website not appearing under some circumstances is fixed.
- Some data about network cards was occasionally not uploaded even when changed.
- Concurrency issue that caused a few random crashes under stress test was fixed (this is unlikely to have caused any issue in normal operation).
- Better handling of uploads and upgrade requests when the Parago website is being upgraded.
- If upgrading through a proxy fails, ParagoAgent will now try to upgrade directly.
- Ability to restrict the valid sources of the machine identity to handle cases where the manufacturer has failed to set the required information.
- Multi-proxy support added.
Required actions by the customer
Since release fixes issues with the initial upload and detection of Microsoft Windows Vista™ it is a strongly recommended update for all customers deploying on new systems or running this operating system. It is still recommended that all current systems are upgraded to this release.
Customers running the automatic upgrading module should automatically get this release over the next couple of weeks if they have specifically switched to this release unless they are currently running a version prior to 2.03.
Customers who have not enabled the Automatic Upgrading module, or who are using the batched mode, must manually deploy this update. Users running versions prior to 2.03 will also need to deploy this update manually due to issues in the automatic upgrading module in those versions.
Risk
This release fixes a few small issue that affect releases before Mar 1st, 2007 and mainly on Laptops running Microsoft Vista. The only significant operational change is the addition of multi-proxy support, building on the existing proxy fallback feature. For these reasons there is more risk in not deploying this update.