Client Management Suite

I cannot seem to get MST files to be seen when I import a software release.
Steps taken:
Manage -> Software
Navigate to Releases
click "Import"
Change source to "Access package from an existing UNC"
Enter the location of the package
click "Display location"
Click "Next"
leave "Update an existing software resource" checked
click OK
go to Add Command, make sure command type is "Install" and click "Edit" and... the "Add" button under "Add transforms to be applied to the MSI at run time" is greyed out.

I've never imported a transform file, only msi's and .exe. If it is an existing resource, try including the transform in the location, and see if it shows up. I know I've done this in the past, but I may be oversimplfying it.

on the pro\cons of the Software Library. If you use the 'software library' as the source, it is actually copying the files to a GUID folder, that the NS can then access. So, it makes sense that you would be able to 'see' the files there.

However, it seems you've stumbled upon something here. If you select UNC path, and the msi and mst are in a designated folder in that path, it doesn't see the transform?

Correct

If I use the Software Library as my source vs the existing UNC path I am able to use the transform. We have a MASSIVE existing structure of source files. The idea of not being able to use it does not make me a happy monkey.

for your specific scenario - AKB51642. I suggest providing some detailed feedback to the article, although I will flag the thread for Symantec to take a look at. I have asked support to take a look.

I've subscribed.

I guess it's one reason to stick with the library.. we have a huge ammount of MST files we rely on.

This other post may prove interesting for you too:

https://www-secure.symantec.com/connect/forums/benefits-using-software-library

Rhys