1

Hello,

I’m running a trial of Atera and really want to like it. The promise of the product vs. cost is awesome. I’m having some issues and I’m hoping that someone can help me out.

I tried running the " windows 11 prepare (tpm and uefi checker)" script on a test PC and got this back:

f1ff8f45-4508-4f1b-bd49-e4c7a77b2a02-temp.JPG
f1ff8f45-4508-4f1b-bd49-e4c7a77b2a02-temp.JPG800×186 19.5 KB

I ran the command manually from the same machine both with an elevated prompt and a non-elevated prompt and neither answer matched up to the answer in Atera:

11460a82-ea94-48fc-8882-7515fed77879-manual_win_11_checker_script_elevated_prompt.JPG
11460a82-ea94-48fc-8882-7515fed77879-manual_win_11_checker_script_elevated_prompt.JPG800×114 15.8 KB

and non-elevated prompt:

e5563464-84f7-4eaa-aa4b-9c482a20da20-manual_win_11_checker_script_non-elevated_prompt.JPG
e5563464-84f7-4eaa-aa4b-9c482a20da20-manual_win_11_checker_script_non-elevated_prompt.JPG800×119 15.2 KB

This machine does not have a TPM chip, but that is what I’m looking for as well as the version of TPM on machines that do have a chip. Looking at the batch file as presented in Atera’s interface:

9589f62a-1c12-4610-a192-4e5e393aacea-attera_win_11_checker_script.JPG
9589f62a-1c12-4610-a192-4e5e393aacea-attera_win_11_checker_script.JPG800×334 28.9 KB

There are no variables being passed, and the For uefi #9 seems to be skipping down to line #9 but I don’t remember a # being a function of .BAT files or the FOR command syntax being used like this. Given it’s been a decade or so since I’ve done anything but the simplest batch files, but this batch file and results make no sense to me. I’ve got a couple of questions related to this as I move forward with my eval of Atera:

  1. Is there a document covering specific quirks, syntax, etc. of BAT files running in Atera?
  2. Will Atera recognize and elevate a prompt as needed? As you can see from above, the WMIC command fails without an elevated command prompt.
  3. Is the result stored in Atera’s data somewhere or is the pop-up results window all that I get? Ideally, I’d like to have the data populate somewhere in Atera so I can view/compare/download it. If the data isn’t available outside of the pop-up window after running a script, is there a way to download it, or am I relegated to creating a spreadsheet and manually parsing the data from the results window?
  4. More like a 3a. question, but if the data isn’t recorded in Atera has anyone looked at ways to pipe the data/results into a file via variables and screen output or something similar? The scripting is a great function, but it’s use for data collection is very minimal without a way to capture the data in a useable format.

I’m going to play with this a bit today, so I may answer some of these questions myself and will post them, but I’m hoping the Atera veterans here will be able to point me in the right direction without me reinventing the wheel.

Thanks,

Jeff

1 Spice up
2

The “FOR UEFI #9” line when commented out (i.e. REM FOR UEFI #9) out seems to have fixed the script, but this is the script in the shared library, are they supposed to be non-functional and you are required to edit them? I haven’t found anywhere outside of the pop-up results window where the results are stored and the screen output is very bad:

4c62c70e-9035-4eac-8a09-2a4cdc1b36aa-fixed_win_11_checker_script_results_window_output.JPG
4c62c70e-9035-4eac-8a09-2a4cdc1b36aa-fixed_win_11_checker_script_results_window_output.JPG800×549 45.9 KB

I suspect it can be cleaned up with ECHO ON/OFF and ECHO output commands, but at least it can be copied and pasted to notepad to view.

@Atera

@adamyosilewitz-atera

3

Okay, I played with it and here is what I came up with:

@echo OFF
set loader=
set tpmchip=

call BCDEDIT | findstr "winload.exe" && (set loader=LEGACY, )
call BCDEDIT | findstr "winload.efi" && (set loader=EFI, )
call WMIC /namespace:\\root\cimv2\security\microsofttpm path win32_tpm get * /format:textvaluelist | findstr "No Instance(s) Available." && (set tpmchip=NO_TPM, )
call WMIC /namespace:\\root\cimv2\security\microsofttpm path win32_tpm get * /format:textvaluelist | findstr "SpecVersion=2.0" && (set tpmchip=TPMv2, )
call WMIC /namespace:\\root\cimv2\security\microsofttpm path win32_tpm get * /format:textvaluelist | findstr "SpecVersion=1.0" && (set tpmchip=TPMv1, )
cls
echo %computername%, %loader% %tpmchip%

The output results look like this:

53489d3f-437c-4081-8166-f130b6c98b63-CHK4TPM-UEFI_Output_Summary.jpg
53489d3f-437c-4081-8166-f130b6c98b63-CHK4TPM-UEFI_Output_Summary.jpg800×284 21.2 KB
Not bad, but not great. The CLS command is ignored. Since I can’t pipe the information to FINDSTR and NUL (I tried), the extra information is above, but I can copy and past the last line into a notepad or something. Obviously not ideal.
  1. Ideas on how to use the findstr command while not outputting data to display?
  2. Any way to pipe/pull/push the info into Atera where I can manage it?
  3. if not Any ideas on pushing this this to a web resource like MS Forms to automatically push the information into a database like format? I was tempted to make an open share and try to push the appended output to a file on an admin computer, but this is a sketchy idea and most likely a security problem.
  4. Any URLs for a deep dive into Atera scripting? What I’ve found so far is overview stuff.

That is the extent of my get up and go over the weekend. I hope that Atera will or some veterans of Atera here on Spiceworks can give me some guidance.

Thanks,
Jeff