13.0

Table Of Contents
Chapter 10: Working with Custom commands
4. Enterthefollowingonthecommandline:
protectcmds.exe <dat-file-path> <vendor-name> [<vendor-contact-info>]
5. Onceyoupressreturn,afteranend-userimportsthesecommands,ifthatend-user
attemptstoview,copy,oreditanyofthem,thefollowingmessageindicatesthatthecom-
mandscannotbeedited:
The command was protected by<vendor-name>.
Please contact <vendor-contact-info>for more information.
IntheCommand Browser,thesamemessageappearsasthePreview Content inScript
mode.
Onceyouhaveprotectedthefile,youcanputitintotheData Distribution directoryfor
distributiontomultipleUserProfiles.Formoreinformationaboutdistributingsaved
commands,refertoCreatingtheDataDistributionDirectory,thenrefertooneofthe
followingtopicsaboutdistributingcommandstomultipleUserProfilesbyeither:
n UsingtheData Distribution Tool (DataDistributionTool:Addingandremoving
customcommands)
n Usingthensadmincommandlinetool(nsadmin:Addingcustomcommands)
266