ascoyne ✭✭✭✭✭

Yes, yes and double yes. Fantasic idea. If I could vote twice I would. Having software assets that can be linked to hardware assets would be brilliant.

100% agree. We are an emergency service and some of services are 24/7/365 WHD's current calendar / SLA makes no cognoscente of this. Not everyone works Mon - Fri 9 - 5.

Please implement this. Currently we have to manually set an mute schedule for all our servers for the deployment WSUS patches and subsequent server reboots. I understand we can set a Unmanaged Schedule, but we don't want to stop managing them, we want to stop the alerts ergo we want the ability to schedule mute alerts.

Sounds like a great idea - one could even take this one step further and have a league table of the Top 10 FAQ's.

Don't think this will ever get implemented. Its been 6 years

Thanks @"KMSigma.SWI" and @"mesverrum" I will do some more digging into our networking. I will feedback the outcome. I appreciate you taking the time to reply.

This fixed it for me too. SolarWinds support was not aware of this known issue. ThankfullyThwack came to the rescue! Thank you @"SteveK"

Thanks for your help Lawrence. Deleting the package and then recreating worked!

Thanks Lawrence. I will work on this on Monday and report back. Just to clarify for future reference - if I make an amendment to RULES only to a package do I have to republish or not?

Think I have found the problem; badly written installer. What I did to adi troublehshooting was enable MSI logging. Within the MSI log the installer calls a file that does not exist in package (this would explain the 1612 error), this instance the file was WordQ_3.msi. WordQ 3.msi exisited, but not WordQ_3.msi. All I did…

Hi Andrew, Thanks for coming back to me. I have run the bat file and the installer runs fine i.e. the software installs and returns an error code of 0. This is my point, if, after the software has downloaded to the Install folder, one double clicks the packageboot.exe the software installs fine and it performs all the post…

I'm somewhat glad that you have come to the same conclusions as me in as much as the rules are fine. I can confirm that in the process of creating the package I have been tweaking the package many times, but each time I amend it I use the Delete option when I republish. Believe it or not over the last four days during…

Hi David, I have resolved. I was stupid and enable had a value of 0. Changed to 1 and now OK. Also set the other two values as 3 and now working OK

Hi guys, Thanks for you help. I am nearly there. The commands work fine, but now I have hit a brick wall. I have been working on this problem for a whole day and I am no conveinced its a bug with PM. I have built my package and it downloads fine to the client, but it fails to run with an MSI error. The error 1612 means the…

Pre-req - Registry Key Exists: HKEY_LOCAL_MACHINE\SOFTWARE\Intel\AMT Applicable - Registry DWORD Value:HKEY_LOCAL_MACHINE\SOFTWARE\Intel\IntelAMTUNS\AMT State - Registry Value:AMT PROVISIONING STATE Equal to DWORD Value: 0

Thanks both for the information. I will work through this and report back when I fix it. Thanks again.

Excuse my ignorance, but there is this screen within Solarwinds. I cant find it.

Thank you. Perfect response. 

Yes, we have 157 free SAM component licenses free.

Hi Callidus, I have enabled logging, but nothing ever gets written to the folder, indeed the log folder never gets created. Very odd.

Yep - thats exact what I see. I will do a SNMP walk and see what I can find. Thanks for the reply.

Yes. I think it is a "undocumented feature". Deleted a content and readded and XML now updated. <raises eyebrows>

Fixed it. It was my syntax. Resolved as follows: Add reg.exe and <filename>.reg to package In the Package Boot Manager add a post package Run Program of reg.exe with a command line of Import <filename>.reg

Thanks LGarvin. I will give that a try today.

Thanks David

Thanks

Thanks for the reply Lawrence. The update is showing as Not Installed. I have done a manual sync on our WSUS, but still no joy.

We have collected numerous logs and have remote support sessions. Yesterday we had a reply from support to advise that "...we got more cases related to the same behavior so it could be a bug with some Linux Agent plugin." So it appears that there is a bug and its broke our monitoring.