A package's properties dialog box has only one tab, General, as shown in Figure 1.
This tab doesn't have a lot of settings that you can edit. Most of the
information is retrieved from the package (or patch) itself:
Package Name
The name Microsoft gave the package
Comments
Allows you to add comments
Display Name
The name you will see in the Deployment Workbench; can be edited here
The next 10 fields of information are grayed out and cannot be edited:
Type
Shows the type of package; the one in the example is a SecurityUpdate package.
Processor Architecture
Displays the architecture the package is supported on; the example shows that the package is for a 32-bit OS.
Language
Shows the language of the package; Neutral represents English.
Keyword
Contains the searchable keyword (if you were to Google or Bing the KB article (Microsoft Knowledge Base Article).
Public Key Token
Pertains to the signature of the package.
Version, Product Name, and Product Version
These options are self-explanatory.
Package Path
Displays the physical path in which the MDT Deployment Workbench stored your package, along with the name of the package.
Package Guid
Displays the internal GUID used by MDT. You
normally don't use this GUID for patches, but for language packs you
could install a language pack using the GUID number with the property
called LanguagePacks001={GUID Number} in, for example, CustomSettings.ini.
Two options appear at the bottom of the tab:
Hide The Package In The Deployment Wizard (Only Applicable For Language Packs)
Choose this option only when you are deploying
language packs and you do not want to see a list of language packs to
install during the MDT Deployment Wizard.
Enable (Approve) This Package
This option, when selected (the default), enables the package; deselecting this option disables the package.
If you're having issues with packages being
installed during the deployment, it is a good idea to disable all
packages and then reenable them one at a time to determine which one is
causing the issue. In most cases, you shouldn't use this method to add
patches; it is much easier to let Windows do that for you at deployment
time. If you would like to control which Windows Server Update Services
(WSUS) server should be used, you can modify WSUSServer=http://SERVERNAME in CustomSettings.ini. You also need to enable the two Windows update tasks in the task sequence, since they are disabled by default.