Figured I follow up, I did find the view with the client push details in it, 
just missed it before (still don't understand where that stored procedure is 
coming from ).

So I wrote the following query for giving the client push status for all 
machines in a given collection with a last process attempt within the last 7 
days

select push.Name, push.LatestProcessingAttempt, push.LastErrorCode, 
push.Description, push.NumProcessAttempts
from v_CP_Machine push
inner join v_FullCollectionMembership Coll on push.MachineID = Coll.ResourceID
Where Coll.CollectionID = 'YOUR COLLECTION ID HERE'
And push.LatestProcessingAttempt >= DATEADD(day,-7,GETDATE())
And push.Description <> 'Complete'

Maybe this paired up with the following link for info on error codes may be 
useful to others.
http://myitforum.com/myitforumwp/2011/10/27/sccm-client-install-error-codes/

From: [email protected] [mailto:[email protected]] On 
Behalf Of Krueger, Jeff
Sent: Tuesday, November 18, 2014 11:51 AM
To: [email protected]
Subject: RE: [mssms] Client push reporting - need to make some custom reports

Yeah, I've created multiple custom reports already, but I can't find where in 
the DB  the client push information gets logged.  So I was hoping to find it by 
reverse engineering one of the existing client push reports.  If you get a 
chance look at the client push details report, you'll see it's using a dataset 
based of a stored procedure.  I'm trying to find where that SP is.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Mike Dzikowski
Sent: Tuesday, November 18, 2014 11:32 AM
To: [email protected]<mailto:[email protected]>
Subject: FW: [mssms] Client push reporting - need to make some custom reports


Hey Jeff,

When you create a custom report, there is an option to create new data source:


[cid:inlineImage0]


You should see something like this when you browse to select your data source - 
when you select the data source, your data source connection will be defined 
like this:



[cid:[email protected]]



Mike D-



________________________________
From: [email protected]<mailto:[email protected]>
To: [email protected]<mailto:[email protected]>
Subject: [mssms] Client push reporting - need to make some custom reports
Date: Tue, 18 Nov 2014 15:17:22 +0000
In hunting down issues with missing clients that haven't installed through the 
client push mechanism, I've found the built in reports to be quite helpful.  
But now I want to make some custom reports and am having a problem reverse 
engineering the building client push reports.  The dataset for the client push 
details report appears to be based on a stored procedure, but I can't find 
anywhere in the db or ssrs node where that might be stored.  Any ideas?  This 
is what I see as the dataset, also can't find where that data source is from 
either.  Some SSRS/SQL stuff that is beyond me knowledge at this point.
[cid:[email protected]]

Jeff Krueger
HFHS IT - Endpoint Design Services
[email protected]<mailto:[email protected]>
248.853.4466


________________________________

CONFIDENTIALITY NOTICE: This email contains information from the sender that 
may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected 
from disclosure. This email is intended for use only by the person or entity to 
whom it is addressed. If you are not the intended recipient, any use, 
disclosure, copying, distribution, printing, or any action taken in reliance on 
the contents of this email, is strictly prohibited. If you received this email 
in error, please contact the sending party by reply email, delete the email 
from your computer system and shred any paper copies.

Note to Patients: There are a number of risks you should consider before using 
e-mail to communicate with us. See our Privacy & Security page on 
www.henryford.com<http://www.henryford.com> for more detailed information as 
well as information concerning MyChart, our new patient portal. If you do not 
believe that our policy gives you the privacy and security protection you need, 
do not send e-mail or Internet communications to us.





Reply via email to