Help to add new modules/msu
Re: Help to add new modules/msu
actually I wanted the parent module and at least one good module as well as the bad ones.
Re: Help to add new modules/msu
At first glance I see
The release date is FAR to short. I am fairly sure that will cause a bit of an issue. Everything else seems fine. I can know more once you send the parent module and a good one.
The release date is FAR to short. I am fairly sure that will cause a bit of an issue. Everything else seems fine. I can know more once you send the parent module and a good one.
Re: Help to add new modules/msu
I would check the ReleaseDate used on your category and any subcategory apm files.
As a suggestion, using Critical, NonCritical, and Recommended as an example. I would do something like this depending on what you want first (top) to appear in the GUI...
...Critical would be ReleaseDate=00000001 -- if you should need a subcategory to display under this top-level apm you could use, 00000010, 00000011, etc
...NonCritical -- ReleaseDate=00000002 -- and the subcategories might be -- 00000020, 00000021, etc
...Recommended -- ReleaseDate=00000003 -- and the subcategories might be -- 00000030, 00000031, etc
The release date for the updates is the release date of the update -- remember, the release date associated with the patch is the order of installation - Jan 02, 2015 (01022015) will install before a Feb 03, 2015 (02032015) update.
The example would give you 3 top-level categories with each having 2 subcategories, which is likely more than you need.
HTH
Woops, looks like someone beat me to it, but yes, this issue is usually a collision of release dates used in parent and/or child apm files. It is best to get your categories and subcategories laid out first, make sure they display properly in the GUI.
My $0.02
As a suggestion, using Critical, NonCritical, and Recommended as an example. I would do something like this depending on what you want first (top) to appear in the GUI...
...Critical would be ReleaseDate=00000001 -- if you should need a subcategory to display under this top-level apm you could use, 00000010, 00000011, etc
...NonCritical -- ReleaseDate=00000002 -- and the subcategories might be -- 00000020, 00000021, etc
...Recommended -- ReleaseDate=00000003 -- and the subcategories might be -- 00000030, 00000031, etc
The release date for the updates is the release date of the update -- remember, the release date associated with the patch is the order of installation - Jan 02, 2015 (01022015) will install before a Feb 03, 2015 (02032015) update.
The example would give you 3 top-level categories with each having 2 subcategories, which is likely more than you need.
HTH
Woops, looks like someone beat me to it, but yes, this issue is usually a collision of release dates used in parent and/or child apm files. It is best to get your categories and subcategories laid out first, make sure they display properly in the GUI.
My $0.02
Re: Help to add new modules/msu
As usual chrisJ you are correct and beat off ignorance with an tsunami of information.