Tuesday, December 21, 2010
Thursday, December 16, 2010
FIX: Altiris Deployment Solution 6.9 SP3 is unable to import jobs that were exported from versions prior to 6.9
When attempting to import a job that was exported from a version of Deployment Server prior to 6.9, the import will appear to complete successfully, but nothing will be imported.
CauseThe compression mechanism used for job bin files changed between version 6.8 and 6.9. Deployment Server 6.9, 6.9 SP1, and 6.9 SP2 support both the new and legacy compression mechanisms. Starting in 6.9 SP3, support of the legacy compression mechanism is removed.
SolutionAttached to this article is a utility named axBinFix.exe. This utility can be used to update an exported Deployment Server Job .bin file to 6.9 SP3 compatibility.
The syntax to use the utility is: axBinFix.exe source destination.
If the destination file already exists, it will be overwritten. The destination file name may be the same as the source, in this case an in-place conversion will be performed.For example, "axBinFix.exe samples.bin samples.bin" will update the samples.bin file, replacing the old one. "axBinFix.exe samples.bin samples2.bin" will leave the old file and create a new one named samples2.bin that is 6.9 SP3 compatible.
Article URL http://www.symantec.com/docs/TECH43843
Thursday, December 9, 2010
Overview: Corporate IP address range (eg. 10.x.x.x/24) and NextG (eg. 10.x.x.x/8) are the same. The issue arises when the PPP connection adds a default route of 10.0.0.0/8 to PC forcing all traffic including corporate-network intended traffic through NextG route.
Resolution: Use split tunneling and have specific routes configured on VPN concentrator for all corporate subnets.
Remove the 10.0.0.0/8 route from the routing table and reinstate after connection is dropped using scripts.