Altiris® Connector™ 6.1 SP2 for Microsoft SMS Release Notes
|Article:HOWTO6661|||||Created: 2007-02-14|||||Updated: 2007-02-14|||||Article URL http://www.symantec.com/docs/HOWTO6661|
What do I need to know about Altiris® Connector™ 6.1 SP2 for Microsoft SMS?
Altiris® Connector™ 6.1 SP2 for Microsoft SMS
Minimum software requirements
- Altiris® Notification Server™ 6.0 SP3
- Altiris® Connector Solution™ 6.1
- Microsoft SMS 2003 SP2 or Microsoft SMS 2.0 SP5
Where to Download
You can download released versions of Altiris products from http://www.altiris.com/Download.aspx.
You can download beta versions of Altiris products from http://beta.altiris.com.
To install Connector for SMS
- Open the Altiris Console.
- Click the Configuration tab.
- In the left pane, select Configuration > Upgrade/Install Additional Solutions.
- In the right pane, click Available Solutions in the Solution Center window.
- Select Segments.
- Select Connectors.
- Select Altiris Connector for Microsoft Systems Management Server.
|Not Applicable||Not Applicable|
This service pack supports full upgrade from all previous versions of Connector for Microsoft SMS. To upgrade, follow the steps outlined in the New Installation section of this document.
There are no new features or feature enhancements in this release of Connector for Microsoft SMS.
The following issues were resolved in this release.
Forwarding to SMS does not work wit SMS 2003Previously, forwarding data to SMS 2003 would fail in certain circumstances, due to incorrect .MIF file generation. This issue has been resolved.
Connector for SMS not recognizing the latest version of Inventory Solution
Connector for SMS now recognizes the latest version of Altiris® Inventory Solution® software as being installed.
Upgrade may overwrite configuration informationUpgrading Connector for SMS to this version now maintains previous configuration settings.
System Administrator (sa) login error during full import
Previously, if an SMS computer was using a database on a different computer, the SWD import would fail. This issue has now been resolved.
Sub-collections with only users are no longer imported to Notification ServerSub-collections with only users are no longer imported to Notification Server
Connector for SMS not reproducing the OS name in the same way as SMS
Connector for SMS now reproduces the identical OS name used by SMS.
Pages need addtional security
The General, UI Integration, and Data Import pages now have additional security implemented.
Some package and program properties are not under SMS controlWhen packages and programs are set to Manage with NS, certain additional properties are available. When switched to Manage with SMS, the available properties now match SMS correctly.
Connector for SMS uninstall issue
Previously, when uninstalling Connector for SMS, an exception error was thrown in certain circumstances. This issue has been resolved.
Connector for SMS does not import software inventory when SoftwareFile.FileDescription is blank
The data import no longer crashes when SoftwareFile.FileDescription is left blank.
Software Delivery Data Import rule failed
Previously, when importing Software Delivery data the import would fail in certain circumstances. Connector for SMS is now correctly importing Software Delivery data.
Need a column added in 'NS Managed Items report'
The NS Managed Items report now has a column that indicates whether the item is a package, program, or advertisement.
Edits to a pre-existing tool cannot be saved with the same tool name
Pre-existing tool editing functionality now works correctly.
Refresh button on Data Import page wipes out password
The refresh button on the Data Import page now works as expected. The action no longer erases the password.
TCP/IP data import from SMS to Notification Server is faulty
Previously, imported computer TCP/IP information was discarded under certain circumstances. This issue has now been resolved.
The following are unresolved issues in this release. For additional information regarding a known issue, click the Article ID link.
|Known Issue||Article ID|
SWD wizard issue with SMS-imported software packages
There is a known issue with the Software Delivery Wizard and imported SMS packages, programs, and advertisements that prevents the straightforward use with the Software Delivery Wizard.
The work around for this is to switch the imported software packages from Manage from SMS to Manage from NS. If imported packages are left in the default state as Managed from SMS, they will not work in the Software Delivery Wizard.Example:
Altiris product documentation is available in Microsoft* HTML Help (.CHM) and Adobe Acrobat* (.PDF) formats. To view Altiris product documentation in .PDF format, use Adobe Acrobat Reader (available at: http://www.adobe.com/products/acrobat/readstep2.html).
Documentation files are installed in the following directory on the Notification Server computer:
C:\Program Files\Altiris\Notification Server\NSCap\Help.
The following documentation is provided:
Altiris Connector 6.1 SP2 for Microsoft SMS Product Guide (CHM)—smsconnector.chm
Altiris Connector 6.1 SP2 for Microsoft SMS Product Guide (PDF)—smsconnector.pdf
Altiris Information Resources
|Source||What Information it Includes||Location|
|Altiris Documentation||Information about new features, update instructions, and known issues for each release. Includes Altiris formal documentation such as release notes, help, reference guides, best practice articles, and technical reference articles.||http://www.altiris.com/support/documentation|
|Altiris Knowledgebase||Comprehensive collection of articles, incidents, and issues for Altiris solutions.||http://kb.altiris.com/|
an online magazine for Altiris users
|Best practices, tips and tricks, and articles for users of Altiris solutions.||http://www.altiris.com/juice|
|Online Forums||Forums for Altiris solutions and suites.||http://forums.altiris.com/|
|02/08/2007||The initial draft of this document was posted to the Altiris Knowledgebase.|
|02/13/2007||This document received a technical edit. The requested updates were made.|
|02/15/2007||This document recieved a formal edit. The requested updates were made.|
|03/08/2007||This document was published and released to the public.|
Article URL http://www.symantec.com/docs/HOWTO6661