Topics created by Towndrunk

I was using the Factory image that came on the device from Lenovo. It was Win 10 and I updated it to Win 11 and we were getting the issues.

I wiped it clean, and loaded a new instance of Win 11, and everything worked fine afterwards. Looks like after disabling Secure Boot, all other issue were with the device. We now have a working images. Thank you for all the help.

@Towndrunk Please look at the chat bubble for additional information.

I’m not sure if I should delete the information in the /images/dev/ or if I just need to change a setting somewhere.

@towndrunk Understand that I’m talking about the Veeam backup agent not Veeam B&R. These are two different products, But they can work together very well. The FOG backup agent is used to backup physical machines to a local disk, CIFS share, or to your Veeam B&R server. It works much like any normal backup tool. From the local machine you can launch a backup or restore a file.

If you want to go the raid imaging route we can do that too. For YOUR raid system you will follow pretty much the raid document I create… 2 years ago (dang) for the intel built in fake-raid controller.
https://forums.fogproject.org/topic/7882/capture-deploy-to-target-computers-using-intel-rapid-storage-onboard-raid

Before I start this, I do have to say that FOG has not been tested to see if it can backup, or even restore a windows 2016 OS. I suppose I could test that in my home lab, but at this point I don’t know if the following process will be able to produce a viable system upon restore.

What you will do is this:

Register that server with FOG. Go into the host properties for this 2016 server and add in these kernel properies: mdraid=true Now schedule a capture or deploy (does not matter, we are going to do neither), but before you hit the schedule task button, tick the checkbox to debug. PXE boot the target system. After a few key presses you will be dropped to a linux command prompt (FOS) on the target computer. Kind of follow part 3 of the document I linked to find out if mdraid can see your array and what its called. It probably won’t be called md126

@Towndrunk also, any time an image is done inventory is also updated automatically

@Towndrunk said in Windows 10 Domain Issue:

I imaged a computer that was activated and on the domain. After applying that imaged to another computer it says that is on the domain when I log in locally, however there is no trust relationship.

If your image is already joined to the domain, you will have nothing but problems, and major ones at that. There is no imaging solution made by anyone that would suggest taking an image from a domain-bound computer. They all suggest exactly the opposite, take an image of an un-bound system.

@Tom-Elliott, thanks. I believe we can close this thread. Things are working now as far as a Capture/Deploy aspect goes. I’m having issues with my images not joining the domain. I have done some reading here and all of my settings appear to be correct. If I can’t get it working, I can start another thread.

Thanks for all of the help. There is no way that I would have got this working without you guys. Thanks.

This is normal and expected output for OU or any active directory operations from the group I have attempted to make resetting stick for groups so long as every host in the group already have this setting however this is only in the development version 1.2 did not have this feature