Daniel,

I just arrived to the same conclusion as well... was too deep in the 
powershell-land and asked the question prematurely ha ha!

New course of action is to steal the SQL query from the canned SSRS report and 
incorporate it into a custom report built by powershell script (mainly due to 
flexibility + I want to be able to view the report directly in embedded HTML 
versus having to open attachments in the 21st century :) ). Thank you!

Nile Gilmanov
Systems Administrator
Wabash National Corporation
[email protected]<mailto:[email protected]> | O: 
765.772.2691 | M: 765.414.7402 | F: 765.449.5381

From: [email protected] [mailto:[email protected]] On 
Behalf Of Daniel Ratliff
Sent: Wednesday, June 17, 2015 4:09 PM
To: [email protected]
Subject: [mssms] RE: PowerShell: Deployment Status Details/Results

Why not SSRS instead, especially since you are moving them to HTML reports 
anyway?

So much easier to just pull the data from SQL and drop it in an SSRS report?

Daniel Ratliff

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Gilmanov, Nile
Sent: Wednesday, June 17, 2015 3:22 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] PowerShell: Deployment Status Details/Results


Hi all,



I am looking for a way to consume information via powershell that you typically 
access via GUI in the <Deployments>, pick a deployment (e.g. May 2015 patches), 
review tabs <Compliant>,<In progress>, <Error>, <Unknown>.



<Unknown> has two sub-categories, Active and Inactive with a list of systems in 
each (if applicable).



Is there any way to get these lists of machines via PowerShell? I would like to 
produce this as an HTML report weekly instead of remembering to review in GUI 
(which by the way I can't copy systems out of... so it's down to manually 
copying problematic machines... yuck!)



Nile Gilmanov

Systems Administrator

Wabash National Corporation

[email protected]<mailto:[email protected]> | O: 
765.772.2691 | M: 765.414.7402 | F: 765.449.5381


The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information 
in error,
please contact the sender and delete or destroy the material/information.




Reply via email to