@TBCS this device can afaik only boot uefi you habe to disable secure boot also.
Like george is telling you, you need to get efi booting working.
@Daryl-Lee try to reset encryption data for the specific host and try again, should be found in the host definition.
@Daryl-Lee try to reset encryption data for one host and test again, should be found in the host definition.
@andre_x Then use a fog snapin to deploy a cmd file to the target computer. The only issue here is that you must have a single key for all Office installs.
(like most AV software). If you install these first then every cloned machine will have the same application GUID which will >probably confuse the management console for the software.
for example ESET’s Agent is creating a unique key, even if you sysprep it’s still the same, the solution was to generate a new uuid and change it in the ESET’s Agent db file on the local hd.
Sysprepping is always the best idea anyway.
Awesome. Exactly the reply I needed.
Another thing I have had trouble with is in the past I tried editing that dhcp file but then after I did so, I did not get the FOG PXE boot anymore.
By default my FOG server is giving clients addresses on the same network as the FOG server and I need to change this without breaking it.
For example: A client will receive the address 10.10.2.6.
I need the DHCP to hand out addresses on my 10.10.222.0 network.
I will keep trying and report any issues I come across.
on your ip a s output below i see 10.10.2.65/24 that means 255.255.255.0
but you told us that you want the dhcp to serve 10.10.222.0 how should that work?
You need a route to have both networks communicating, FYI DHCP is a non routable protocol.
Or configure both the fog server and the dhcp range in the same subnet but exclude the fixed addresses (for example the fog server) from being served by the DHCP service.
Afaik fog doesnt display the dashes in the webif even if you paste a 29 sign key, ajax or whatever cool technique immediately removes the dashes visible in the edit field (at that moment i don’t know if it is stored as 25 or 29 sign key into db), lets say the readback works propperly then the only problem can be the fog client or the key itself.
Have you tried to activate manually? slmgr.vbs -ipk key (store the key) followed by slmgr.vbs -ato (activate key)
Btw. afaik you don’t need the windowskey plugin, it’s used for group deployments or volume license keys, if you have unique keys for each host your good to go with the hosts key definition.
Cross linking active post because the conditions sound very similar: https://forums.fogproject.org/topic/13084/activating-windows-10-pro-after-deployment
@andre_x if you review the fog client log on the target computer is there anything useful that mentions client activation?
@Sebastian-Roth mentioned in another thread that the fog client should be 11.6 else something with activation isn’t working propperly (afaik something about the parsing of the key (with, without the dashes) 25-29 signs.
Btw. i hate that the webif shortens the key from 29 to 25, the key contains that dashes and i think it should always be displayed with them, nice idea to save space in the db but hey it’s not 1980 :D
Hi @x23piracy, I don’t have the product key in the bios.
I’ve read the 2 links you’ve provided me, but they’re both relative to the bios keys. They are all pc provided without any license, we’ve bought them separately.
Is there a way to change the product key of a deployed image with the one inserted in the host definition under the “Host Product Key” field?
you should be able to add your keys into to each host definition in fog, then when you have the fog client in your image it should activate with the supplied key.
Since you haven0t used this feature, is there anybody else that can help me with this?
@x23piracy Do you have any input on this issue?
i need to know if @andre_x has computers for rent with product key in their bios?
If so he can read the keys from bios and activate em.
Method one, active key reading in fog options (you need to dig a little) then when you register a host the key will be read and added to the host definition:
Method two, find a tool that can read the bios key through command line (i can give you the binary), pipe the output into a script (slmgr.vbs -ipk KEY, followed by the activation itself slmgr.vbs -ato):
@Valer i know that some bios let the „windows boot manager“ always go on position 1 if found afaik this can be turned off to keep your current order: