When I did it I was looking for iTunes media folders not on the c:\ drive.
So the return value for non compliant machines was just the folder path on
the noncompliant machines.  No special formatting or anything needed

-----
Dwayne Allen
[email protected]
(479) 310-0027

On Thu, Feb 19, 2015 at 4:03 PM, Beardsley, James <
[email protected]> wrote:

>  So when you did this, did you have wscript.echo return just the number?
> Or did you format it in any way?
>
>
>
> For example, have it return “19,970.44” or just “19970.44”. Any reason not
> to format it? I’m assuming it’s a string so I wouldn’t be able to (easily)
> format it on the reporting side.
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Beardsley, James
> *Sent:* Thursday, February 19, 2015 4:52 PM
> *To:* [email protected]
> *Subject:* RE: [mssms] Query folder size
>
>
>
> Interesting… thanks for the ideas. I’ll play around with that.
>
>
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Sherry Kissinger
> *Sent:* Thursday, February 19, 2015 4:48 PM
> *To:* [email protected]
> *Subject:* Re: [mssms] Query folder size
>
>
>
> Yes, I've done exactly that before (well, not for mydocs).  Where I had,
> on purpose, wanted everyone to be non-compliant.  Just so that the results
> of the script that were echo'd with wscript.echo (or write-host
> w/posh) would show up in the DB.
>
>
>
> If you want to test it quick; just do a posh script ConfigItem where it
> just does a write-host "hello"
>
> but "what means compliant" is the phrase "goodbye".  and you'll see that
> the "non-compliant" value of hello will show up in your DB.
>
>
>
> in your case, the string that means compliant is say.. X so anything else
> would be wrong; and would show up in your db; the number you spit out with
> write-host
>
>
>
>
>
>
>
> On Thursday, February 19, 2015 3:40 PM, Dwayne Allen <
> [email protected]> wrote:
>
>
>
> You might be able to do it with a CI if you use a script (SCCM 2012). The
> output of the detection script actually gets written in the DB.  Check out
> the InstancePatch field in the
> vDCMDeploymentNonCompliantRuleDetailsPerClientMachine view.
>
>
>   -----
> Dwayne Allen
> [email protected]
> (479) 310-0027
>
>
>
> On Thu, Feb 19, 2015 at 3:11 PM, Beardsley, James <
> [email protected]> wrote:
>
>   I’ve been asked to see if there is a way to gather the size of
> everyones My Documents. Is there anything within SCCM that I’m not thinking
> of that could do that? I’ve done this before with a package that simply
> runs a Powershell script that writes the folder size into a text file and
> then copies the text file to a central location on a network server. Then
> using another Powershell script, gather and combine all of the data in
> those txt files to one spreadsheet. Before I did that again, I wanted to
> see if maybe I’m overlooking a better way to get this done. A co-worker of
> mine started down the road of returning the folder size as an exit code and
> report on that but that didn’t turn out right.
>
>
> Thanks,
>
>
>
> *James Beardsley |* Firm Technology Group
>
> Dixon Hughes Goodman LLP
>
>
>
> [image: cid:8644FC49-D5C9-45AE-B387-04FAFC0CC7A5] <http://www.dhgllp.com/>
>
>
>
> *Confidentiality Notice:* This e-mail is intended only for the addressee
> named above. It contains information that is privileged, confidential or
> otherwise protected from use and disclosure. If you are not the intended
> recipient, you are hereby notified that any review, disclosure, copying, or
> dissemination of this transmission, or taking of any action in reliance on
> its contents, or other use is strictly prohibited. If you have received
> this transmission in error, please reply to the sender listed above
> immediately and permanently delete this message from your inbox. Thank you
> for your cooperation.
>
>
>
>
>
>
>
>
>
>
>  ------------------------------
>
> *Confidentiality Notice:* This e-mail is intended only for the addressee
> named above. It contains information that is privileged, confidential or
> otherwise protected from use and disclosure. If you are not the intended
> recipient, you are hereby notified that any review, disclosure, copying, or
> dissemination of this transmission, or taking of any action in reliance on
> its contents, or other use is strictly prohibited. If you have received
> this transmission in error, please reply to the sender listed above
> immediately and permanently delete this message from your inbox. Thank you
> for your cooperation.
>
>
>  ------------------------------
>
> *Confidentiality Notice:* This e-mail is intended only for the addressee
> named above. It contains information that is privileged, confidential or
> otherwise protected from use and disclosure. If you are not the intended
> recipient, you are hereby notified that any review, disclosure, copying, or
> dissemination of this transmission, or taking of any action in reliance on
> its contents, or other use is strictly prohibited. If you have received
> this transmission in error, please reply to the sender listed above
> immediately and permanently delete this message from your inbox. Thank you
> for your cooperation.
>
>



Reply via email to