Topics created by zaboxmaster

The purpose of me using Capone for me is because we use all hps so I already have Capone configured to serve the golden image based off of the system-manufacturer matching HP

@zaboxmaster Well we are going to need your assistance to help debug this. I can give you the steps needed to collect the information to help debug this.

Schedule a new deploy/capture task, but before you tick the schedule task button, tick the debug checkbox. Now schedule the task. PXE boot the target computer. After several screens of text you need to clear with the enter key, you will be dropped to the FOS Linux command prompt. This next 3 steps will help with remote debugging and for copying the results out to post here. Key in ip a s and collect the IP address of the target computer. Reset root’s password with passwd Give it a simple password such as hello This password will be reset at the next reboot. Now connect to the target computer using ssh, either ssh from linux or putty from a windows computer. Key in and post the results here of the following commands
uname -a
lsblk
lspci -nn
grep -i -e firm /var/log/syslog Keep the debugging session open for additional commands.

@zaboxmaster Another opiton might be to access the windows registry to read out the version. Within the FOG OS (FOS) linux there is the linux reged program. That can be used to read/edit the windows registry.

Below is an example from one of my tutorials on post install scripts to update a registry key. That is only meant to show you what is needed to make the program work.

egfile=“/ntfs/Windows/System32/config/SOFTWARE” key=“\Microsoft\Windows\CurrentVersion\DevicePath” devpath=“%SystemRoot%\DRV;%SystemRoot%\inf;”; reged -e “$regfile” &>/dev/null <<EOFREG ed $key

The question is how would I go about doing this if at all possible?
Where would the best place be to run it from? FOG.MAN.REG ???
Is the Windows mounted at all during registration?

Is it possible, yes

Best place, yes probably a customized version of fog.man.reg (I have a tutorial on how to slide an updated version of that into FOS Linux at deploy time). To make the inventory also query the target OS.

No windows os partition is not mounted during inventory. For FOG inventory its not needed. BUT I have a tutorial on how to find and mount the partition during a post install script for driver injection that you can use as the basis for the inventory process.

@zaboxmaster Just in case you haven’t found out about post deploy scripts yet: https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script

@zaboxmaster The history of the report should still show the fact that it was imaged, though the links to the “host” element are done based on the existing of the physical host in the database.

I believe this is known and could be relatively easily fixed by just planting the current device name along with the hostID.

The reason that this isn’t done, however, is that it’d still be relying on a database entry, and there are cases where people deploy an image to a device that isn’t registered. What name do you use for that particular case?

@george1421 said in Certificate of Data Destruction:

e also trivial: https://www.geeksforgeeks.org/php-send-atta

Thank you so much . Makes perfect sense. Let me try that way .

@zaboxmaster The short answer is no. That wiki page refers to FOG 0.3. That feature is already built into FOG 1.5.9 through a different method. At the FOG iPXE menu, you can select Deploy Image. You can thus deploy an image without registering the computer with FOG. A system reseller might use this feature to load a base OS on a computer then never see it again.

There are a few caveats with this method. The big one is that the FOG client can’t be used because the target computer is never registered with FOG. So this means your image deployment needs to be complete and not use any function provided by the FOG Client. I can tell you in my environment I don’t use the FOG client. I use the windows unattend.xml to name the computer and connect it to AD. I use a FOG Post install script to update the unattend.xml file with deployment time settings (computer name, Domain OU, timezone, keyboard mapping, etc). So it can be done rather well without the FOG client.

@george1421 Thank you so much … I updated the to the latest ipxe and it sorted out the issue .

@zaboxmaster You might want to tweak your deployment strategy if you are using the fog client. If you are not using the fog client then you can use the system builder method of load and go by pxe booting into the iPXE menu and pick the deploy image menu. Once the image is deployed using this method the reference to the computer is removed from FOG. There is no need to register and deploy using this method.

The down side of “load and go” is that you can’t use the fog client to make changes to the target computer like system renaming or snapin deployment, that requires the target computer to be registered in FOG.

@zaboxmaster said in USB to ethernet adapter:

I know this has been covered multiple times, but I have tried various methods, from the API post-deployment to remove the host to the I.M.I option or the I.M.C option. I cannot seem to get it right.

I am afraid we can’t help you without more details. Please start by telling us the FOG version you use. Then let us know in more detail what exactly you’ve tried and what didn’t work (error messages, pictures, …).

There has been discussion about using a different identifier (other than MAC address) which would help in your case. But there is some major work to be done and no one seems to find the time to do it: https://github.com/FOGProject/fogproject/issues/198

@zaboxmaster said:

I know about dban etc… just nothing seems to work

What exactly have you tried and what was the outcome/error?

Just a quick note: FOG is made up of several open source tools to also allow for wiping disks. BUT we only provide those tools and have no share in them producing any kind of report or proof for you. So we probably won’t be able to help you with that point.

@zaboxmaster That command is surely possible if the existing hard drive contents are available. My previous post was only considering a bare metal install where there was no previous windows install to reference. If you have access to the previous disk content and it matches the smbios key then it makes things a bit easier.

If you look at this post for a post install script example you will see a command that is already built into FOS linux called reged https://forums.fogproject.org/topic/8889/fog-post-install-script-for-win-driver-injection/57 In this example I’m poking a value into the registry. While I haven’t looked it may be possible to read with reged too. As for hivesh it could be added if the source code could be found. It could be integrated into FOS Linux. It might take a little work, but its possible if that IS the solution.

edit: man page for reged http://manpages.ubuntu.com/manpages/bionic/man8/reged.8.html

@zaboxmaster /usr/share/fog/lib/funcs.sh

@Norm said in Help with Mac imaging:

When I upgraded to Fog 1.5.8 it broke.

Can you please give us some more details on where it breaks. Please take a picture of the screen and post here.

@zaboxmaster Lets switch over to IM chat because there are a few questions I have. Look at the chat bubble and the top-right of the forum tool bar

@boyan-biandov said in How to PXE boot to a Windows PE ISO:

Has there been any development on the ability to boot into one’s custom WinPE ISO on a UEFI system?

Not booting the ISO directly but if you pull apart the ISO you can pxe boot the wim file with FOG.