-
1. Re: Different Status in Patch Management
Steve Gibbs Sep 27, 2017 8:06 AM (in response to Sriram Haasan)As of 9/27/2017 the Patch KB is 2.0.2.3442. Can you look at your master server and see what Patch KB is applied to that device? I have no idea what published means but curious if the KB package was downloaded and packaged for deployment... This may be a step prior to packaging that I never see because it typically works so fast but there may be an issue with packaging that KB article. If your Master server is not on the latest KB I would open a ticket ASAP. You do have an E:\Patches folder on the Master, correct?
You can also look at the logs on MV-BMCFPAC and filter on the Patch Management module and look for any errors or failures.
-
2. Re: Different Status in Patch Management
Sriram Haasan Sep 27, 2017 9:08 AM (in response to Steve Gibbs)Hello Gibbs,
yes my version is 2.0.2.3418 please find below screenshot, yes i have patches to E:\Patches, it would be great if you raise a ticket and help me on this.
my email id is srirama.haasan-v@abfrl.adityabirla.com
Regards
Sriram
-
3. Re: Different Status in Patch Management
Jason Prazeres Sep 27, 2017 10:15 AM (in response to Sriram Haasan)Hi Sriram,
The fastest way to open a ticket with bmc support is to send an email to the following address with your issue:
You will get a generated email with your bmc incident# for tracking your issue.
Regards,
Jason Prazeres
-
4. Re: Different Status in Patch Management
Sriram Haasan Sep 27, 2017 10:20 AM (in response to Jason Prazeres)Hello Jason,
Raised case 00406471 please help.
Regards
Sriram
-
5. Re: Different Status in Patch Management
Dario Soldera Nov 17, 2017 5:16 AM (in response to Sriram Haasan)Hi Sriram
Do you have a solution here?
Regards, Dario
-
6. Re: Different Status in Patch Management
Sriram Haasan Nov 22, 2017 10:17 AM (in response to Dario Soldera)Hi Dario,
Patch Management Database status had been automatically from Published to Up to date, not sure how this happened.
Regards
Sriram