That sounds like it would be useful.

For the record, there is an official version on the MS site (for R2 CU3)…..
                
https://gallery.technet.microsoft.com/SCCM-Configmgr-2012-R2-CU3-3a66c547


From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Andreas Hammarskjöld
Sent: 18 January 2015 19:30
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Status Messages Reference

Found it, I could create a small tool that sucks out all the standard MS 
messages ID’s if that would be of use to people?

I bet the DLL’s have a lot of old stuff in them that is not in use any more 
though, so unsure how beneficial that would be?

//A
http://2pintsoftware.com
https://twitter.com/AndHammarskjold

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Andreas Hammarskjöld
Sent: den 17 januari 2015 22:50
To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>
Subject: RE: [mssms] Status Messages Reference

Think I found a C++ reference somewhere… will have to look through the SDK 
again…

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Christopher Summers
Sent: den 17 januari 2015 16:00
To: mssms
Subject: Re: [mssms] Status Messages Reference

You can (pseudo code) 500..50000 | <custom function for GetStatusMessage> which 
is the output Sherry replied with. It only outputs the description template for 
each message id though. The 2007 spreadsheet from John is all I've been able to 
find that joins the message id with the component or list the attribute types.

On Sat, Jan 17, 2015 at 1:57 AM, Andreas Hammarskjöld 
<jun...@2pintsoftware.com<mailto:jun...@2pintsoftware.com>> wrote:
Wasnt there some code floating around that pulled them all out of the the 
.dlls? Seem to remember that…

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] 
On Behalf Of Christopher Summers
Sent: den 17 januari 2015 00:15
To: mssms
Subject: Re: [mssms] Status Messages Reference

Anyone know if there's any status attributes higher than 427? My db doesn't 
have but want to double check.

On Fri, Jan 16, 2015 at 5:53 PM, Christopher Summers 
<ch...@csfanclub.com<mailto:ch...@csfanclub.com>> wrote:
Thank you Sherry, I'll compare it to what I pulled with Powershell. Was hoping 
to have something that includes the component as well. I'll probably finish 
having it all mapped out this weekend and I'll share the results.

On Fri, Jan 16, 2015 at 4:54 PM, Sherry Kissinger 
<slkissin...@sbcglobal.net<mailto:slkissin...@sbcglobal.net>> wrote:
The attached is from someone @Microsoft, who used the SDK and powershell, to 
create it.  For CM12 R2 CU3

He confirmed it was OK to share publicly.

On Friday, January 16, 2015 2:05 PM, Christopher Summers 
<ch...@csfanclub.com<mailto:ch...@csfanclub.com>> wrote:

Anyone have access to the full list of current status messages? Latest I've 
found is John Nelson's 2007 SP2 spreadsheet.

--
Regards,
Christopher Summers
http://www.myitforum.com/csummers311






--
Regards,
Christopher Summers
http://www.myitforum.com/csummers311




--
Regards,
Christopher Summers
http://www.myitforum.com/csummers311





--
Regards,
Christopher Summers
http://www.myitforum.com/csummers311
---------------------------------------------------------------------------------------
Information in this message is sent in confidence and is intended only for
the use of the individual or entity to whom it is addressed.  If you are not
the intended recipient, any use, distribution or copying of the information
is strictly forbidden.  Please notify the sender immediately by return email
or telephone 01823 721400. If you received this email in error please delete 
it and any copies of it from your system.

Viridor Waste Management Limited
Registered Office: Peninsula House, Rydon Lane, Exeter EX2 7HR
Registered in England No. 575069
---------------------------------------------------------------------------------------

Reply via email to