Nathan_K

Forum Replies Created

Viewing 10 posts - 1 through 10 (of 73 total)
  • Author
    Posts
  • in reply to: Embedded PowerShell Scripts #5441
    Nathan_KNathan_K
    Participant

    I think most of my issues were the single vs double quotes. I did figure out how to set the query inline as well.

    parameters:-Command "& {$query='Local Fixed'; %bitlocker-status%}"

    That seems to work correctly.

    in reply to: Embedded PowerShell Scripts #5433
    Nathan_KNathan_K
    Participant

    Here is my “SET-SECTION” block.

    and

    in reply to: Embedded PowerShell Scripts #5431
    Nathan_KNathan_K
    Participant

    Here is my code block from the config. You can see the result in the attached screenshot.

    CMD=interval:10,text:Local Fixed Disks,read-as-csv:1,csv-header:1,file:powershell.exe,parameters:.\scripts\BitLocker-Status.ps1 -query "Local Fixed",trim:1,show-window:0,color:ffbb77,chart:bar2 scale:linear max:100 series1:{{((%Size%-%FreeSpace%)/%Size%)*100}} threshold:90 0000FF,hide-no-result:1,display:%Name% {{%Size%-%FreeSpace%}}[1.0b]B / {{%Size%}}[1.0b]B ({{((%Size%-%FreeSpace%)/%Size%)*100}}[1.0d]% used) %chart%| BitLocker Status: %BitLocker%

    That calls the external PS1. If I use the same line and replace the PS1 with my SET-SECTION variable, I get no output data. If I hard code “Local Fixed” into the PS block, I get all bad data.

    in reply to: OSBUILD2 – Items Not Hidden #4724
    Nathan_KNathan_K
    Participant

    Windows 2012 R2 doesn’t have that key. It wasn’t introduced until Windows 10 and even then not until 20H2. Before then, the ReleaseID key was used, which works fine in 2016 and 2019, but 2012 R2 doesn’t have that key either. I expected that since both keys are absent it would just mark it as “null” (or whatever value triggers the triple braces to work).

    in reply to: Windows 11 Support #4652
    Nathan_KNathan_K
    Participant

    I can honestly say I’ve never seen mine do that, but I’ve never tried it on a SurfaceBook either. It may have to do with the screen scaling. I always keep my systems at 100%, so I’m not a good test for that.

    in reply to: Windows 11 Support #4646
    Nathan_KNathan_K
    Participant

    Darn, found a bug. Triple curly brackets “{{{ %variable }}}” don’t work in OSBUILD2.

    in reply to: Windows 11 Support #4644
    Nathan_KNathan_K
    Participant

    I’m good with the new functionality.

    This:

    Verses this:
    OSBUILD2=interval:0,color:ffdd99,text:Operating System,display:%1 (%2)|%15.%17.%16 (%18)

    I’d call that a vast improvement. Thanks Glenn!

    • This reply was modified 9 months, 2 weeks ago by Nathan_KNathan_K.
    in reply to: Windows 11 Support #4629
    Nathan_KNathan_K
    Participant

    Can something similar to this be done with REG keys too? Something like the example below:

    REG=interval:0,value:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion,set:MajorVersion=%CurrentVersion% CurrentBuild=%CurrentBuild% MinorBuild=%UBR% DisplayVersion=%DisplayVersion%,hidden:1

    in reply to: Windows 11 Support #4611
    Nathan_KNathan_K
    Participant

    When I renamed the file to “appraiserres.dll_bak” it worked fine to disable the checks. I even installed it on an older 3rd Gen Intel Core-i5 with a TPM 1.2 without issue. You do have to make sure that you completely close and re-launch the installer. I ran it from a USB drive.

    in reply to: Windows 11 Support #4609
    Nathan_KNathan_K
    Participant

    Here is the custom Operating System and Build# section I’m using. Feel free to use what you want.

Viewing 10 posts - 1 through 10 (of 73 total)
Glenn's Page