We had a major storm through here recently and we suffered damage to the house roof and ceilings. I just received the quote to repair. I’m hoping that a small fraction of the 80,000 odd people that download SDIO and/or Desktop Info every month won’t mind chipping in a few dollars to help out. Click on the big blue button at the bottom of the page to help us keep a roof over our heads, literally!
Guests have read-only access to our forums. If you wish to participate you will need to register. Be sure to activate your account from the email sent to you when you register.
Glenn, loving the progress with scaling. I have been able to scale back my on-load sections more and more, so thanks a TON!
However, I have been struggling for a while now with recent versions and getting pending reboots to not show any info unless reboots are pending. I also believe that the embedded pending-reboot.ps1 process runs incorrectly within the ini.
If I take the code as-is and create a stand-alone ps1 file and have DTI run it, I indeed see I need a reboot due to pending file renames.
But the same code within the ini does not report that, it's blank in the right column (I removed the else option to prevent output).
It also seems to ignore the hide-no-result:1 setting as the text is always there even when using an actual script file to do the work.
The pending updates section seems to work properly though, so that is a win. One less file to maintain!
Here is a blurb of said code:
# check for password expiration date does not work for intune/azure devices so I hide it
The thing with cmd always showing is because it always returns 1 row with the error / return codes even if the output from the command is empty. So hide-no-result won't work. By default CMD has a display template of "display:%4". I'll add code to suppress the output *if* you null the display *and* put hide-no-result: "... display:, hide-no-result:1".
I'll have to study that powershell stuff to figure why it's not working...
well i studied it and i can't figure it out. some kind of syntax error as best I can determine. maybe someone who's better than I with powershell can check it out
