It would be usefull to allow the creation of StatusMessages for any event.
This could be tuned in DefaultClientSettings (just as hinv classes), but setting it only thru PSH would be a first step.
For example, when a user requests an app:
new-CMStatusMessageDefinition -class "SMS_UserApplicationRequest" -event "CreateRequest" -messageid 33333 -strings ($ciid,$username,$devicename,$usercomment...)
This is a complicated problem, and not one we plan to address at this time. There are some solutions today with varied levels of usability.
We do have a special status message class on the client designed for some extensibility: SMS_UnknownMessage. You can specify custom values for this and have it get processed by the management point. The management point has a list of status message types it accepts, and we have no mechanism for extending this at this time. You can also have a component that writes custom status messages directly to the site server inbox. You could theoretically write whatever you want here, but you need to take care to ensure that this is properly secured and monitored since you need to be a trusted user to write to the status inbox.
Keep in mind that even if you do get custom status messages processed by the site, they will not display properly in the status message viewer without extra work. Status messages themselves are very compact, and to convert message ID “33333” to some sort of readable text you would need to compile a resource DLL and distribute it with the console. This is not a process we document or support at this time.
Depending on the problem you’re trying to solve, you may be better served using a mechanism other than status messages — such as configuration items, or through an inventory query of some kind.