Configuration Manager–Importance Of Properly Naming Packages With A Descriptive Name

I was recently troubleshooting an issue at a client where we had about 2,000 error messages for the Distribution Manager about a package that it couldn’t process.

image

According to this error message I was looking for a package named “.NET Framework”.  I dug through every package we had, but couldn’t find one called that exactly, all I could find for anything .NET related were the following packages.

image

What’s important to note is that the display name you see in the console is actually derived of 3 components.  The Name, Version, and Manufacturer.  What you see in the status messages is only the Name.  Hmm, not the greatest and something that does not lead to quick and easy troubleshooting.

image

I typically don’t ever recommend using the Version field, I always make sure the Name is fully descriptive of the package.  This also ensures what you see the the status messages helps you easily and quickly identify the package, so you don’t have to dig through several hundred or thousand packages trying to figure out which one is causing the issue.

image

Unfortunately, you can’t use the version in both the Name and Version field or you will end up with a funky looking Display name like this:

image

So, the thing to remember is that it’s important to using a standard naming convention for all your packages, and that you use a fully descriptive Name for each package, remember this is all you will see in the status messages, besides the package ID, which you can’t really search for easily in the console when your packages are under numerous folders. 

Leave a Reply

x

We use cookies to ensure the best possible experience on our website. Detailed information on the use of cookies on this site is provided in our Privacy and Cookie Policy. Further instruction on how to disable our cookies can be found there.