@wayne-workman Good to know.

The people who would be looking at this wouldn’t have that sort of access, so I guess I’m feature requesting that it be made available in the GUI. 🙂

https://www.microsoft.com/en-us/Useterms/OEM/Windows/10/UseTerms_OEM_Windows_10_English.htm

In case anybody’s overly concerned. Here’s the OEM EULA. Notice, it states that you are allowed to transfer the license to another user so long as it’s with the device and the software is installed and the product key is given with it. There are no rules on what you can/cannot document. That’s like saying you can’t pull the serial number from the bios.

Just trying to get people to calm down. We know the device and software are owned by the person. We know how to obtain the information. We don’t know how the user intends to use it after it’s been stored, but that’s out of our hands. We cannot control what the admins/users do with the key once it’s know, but that’s out of our control to begin with. There’s plenty of ways for users to get that information to begin with, I don’t see anywhere in the EULA where it states we cannot store a copy of it for ourselves.

@sebastian-roth

0_1505338885213_FOG bandwidth.JPG

@x23piracy We would need one for Linux too. On most systems, that’s a simple realm leave -U username domainname

@goempie said in Read Windows Keys from Registry and BIOS (OEM Key) (FOG Client):

Hello
I’m trying to get your script working, but can’t get it to work.

Does the bat to exe converter also pack in the oemkey.exe or do i have to copy the oemkey.exe to a directory in my image?

Thanks

setkey.exe in the bin directory is the finished product. oemkey.exe is packed into setkey.exe while the script itself is also in oemkey.exe but executed from setkey.exe itself.

All you need is setkey.exe to be executed as admin (snapin) nothing i just uploaded everything together because people may leery when can’t see the source of it.

Regards X23

@juan-bertolotti Are you able to delete the image?

@robertd Checkout the below image, this is how you password-protect the entire fog menu. This will accomplish what you’re after. Technicians need only to enter the key-combination in order to be prompted for user/pass credentials. The accepted credentials are those in the FOG web interface users area.

0_1503530821572_hide menu password.png

You didn’t do anything wrong sir. I didn’t fully understand the question and mistook the request.

@fractal13 said in Single disk (resizeable) 1 partition restore:

each image overwrote the MBR, GPT partition types, and partition UUIDs.

Even if you set it to one single partition in the image settings before deploy? Shouldn’t do so I suppose.

And I just found the Access Control plugin- I think this is what I’m looking for.

@tom-elliott Yes, I just test it on RC5, perfect 😉

It should look like:

0_1501183211866_164a7593-af02-4c13-9471-599068c5051c-image.png

Added in working.

@sourceminer said in Using Host Tags as Variables in Snap-Ins:

use the host Tags as variables

+1for use the host Tags as variables

@Tom-Elliott

No problem. Yes it does prompt to update. Thanks!!

@Tom-Elliott

It’s funny, I noticed it a bit later after I posted this. 🙂 It’s looking good though!

That’s very promising to hear Wayne! I must admit that you shot beyond my skill set with your bash script and use of the API. I look forward to your “generic” solution!

@Tom-Elliott Thanks for your hard work - good to know it will be there in a future release.

I’ve updated the current 4.11.6 kernels to include both the vars and the boot editing elements.

Hopefully this helps.