@Logan

Problem solved :

I just disabled “fast boot” in the BIOS.

@george1421

Ok, let me try some things this week and let you guys know. Thanks guys.

@RusinovAA

1.) When preparing Windows 10 for cloning (for capturing an image using FOG), is there a need to run and apply the Sysprep /oobe /generalize /shutdown utility. Or FOG, when capturing an image, performs procedures for decoupling Pts from binding to equipment and resets the OS identifier?
Sysprep (system preparation) prepares a Windows client or Windows Server for imaging. Sysprep can remove computer-specific information from a Windows installation (aggregate) so that it can be installed on different computers.

FOG does not react with the target system OS. It is Microsoft’s best practice to sysprep your golden image before image capture. I can tell you from experience if you want to make a neutral image that can be deployed to any hardware you should sysprep the golden image. If you capture from a Dell 5430 laptop and then restore to another Dell 5340 laptop you can image this way without sysprep. Understand that just because it works doesn’t mean this is the best choice. For me always sysprep the image if going to the same hardware or not. That way (for my campus) I have 1 golden image for 12 different hardware platforms both laptop and desktops. I install the required drivers using a FOG post install script, but that is a different discussion.

Quick answer, must sysprep? Yes to different hardware between golden image and target computer. Imaging between the same hardware you should sysprep but I’ve seen people no sysprep cloning and it works.

2.) Does the current version of FOG have the ability to automatically add computers running Ubuntu Server / Ubuntu Desktop to the Active Directory domain when distributing an image?

Quick answer is no, fog will not do this. A bit longer answer is that you can do this when ubuntu boots, and make a bash script to add the computer to AD.

@Sebastian-Roth said in Host can’t join AD:

In a fair amount of cases people had to use domain\username in the username field but also specific the domain in it’s own field to make it work

You have totally right, it works with myDomain\userName.

Thanks Sebastian.

@cwufog Is there enough diskspace for this application to install? Assuming it is an installer package in teh first place…

It seems a windows based error code

@Sebastian-Roth

Hello Sebastian,

i will try to think about this feature and i will contact to you if need help 🙂

Best Regards
Youzersef

@hammerc807 I actually never use sysprep and just deploy golden images. We do that exactly, the images are not domain joined and completely local workgroups and no AV installed.

Once imaged to a new laptop, we rename hostname, join domain and add AV and for some reason have issues with VPN

@george1421 Thanks for that George, and also for all the help over the years!

Had a tinker with unattend.xml and it’s fine now. Thinking it was the mismatch with local admin acct setup in there vs what I’d set locally initially, but all ok now.

However have done none of the service off/restart it options post-sysprep (and was wondering even if I’d just put something in group policy later on that’d do it, as the last time I ran this having ANY setupcomplete at all broke the sysprep process) it was in fact just fine and happy. Maybe something in 22H2 Edu is just alright with it, or the stars aligned for me on that one.

Either way all working now and thanks for diving in there. 🙂

@Sebastian-Roth Ok so I found a fix for single boot. By a chance several of the devices worked after a complete reimage and have no issues. The other devices that still had issues had a slightly more strenuous issue.

Install Iso Image Via USB:
Windows 11 and Windows 10 (Version 1709 and newer):
Rebuild the BCD store.

First run the command below to back up the old BCD:

ren BCD BCD.bak

Now re-create it using this command:

bcdboot c:\Windows /s <boot letter>: /f ALL (You can add a switch before /s for the computer locale: /l <language code>. By default, /l en-us English USA is used.)

bootrec /rebuildbcd

@george1421 I’ll be damned, pardon my french.

So I guess I was just not patient enough. You guys were right, the acpi error has nothing to do with this other than distracting it from the real process.

After changing the log to level 7, I noticed at some point it says its resizing right before the acpi errors take over. I realized its not stuck, its just taking a while to proceed bc resizing always takes a little longer when capturing image.

So I just let it sit there and eventually it proceeds on capturing the image. It doesn’t look pretty with all the acpi errors but it still does what it suppose to do.

Thank you @george1421 and @Sebastian-Roth for helping on this.

@Sebastian-Roth said in Windows Keys Management Plugin:

overwrite each others settings

Yess…this was the cause …i’ve uninstalled the plugin and now all seems ok 🙂
10x dude 💪

@pauleb Intriguing. So you didn’t need to create a EFI entry for the drive? I wonder if it was already there for that drive from the previous image or something.

I guess mine did not work because I first imaged my test machine with an MBR image, which made the EFI entry no longer show up.

Good luck, and thanks for the info.

@Flyer I create users in the setupcomplete.cmd batch file. That gets executed at the end of the WinSetup process and before the first login.

You can also with the unattend.xml file define an auto admin login process for a specific user. You can set up a counter so the auto login process only executes X times then reverts to login required. This is configured in the unattend.xml file. There is also a first run section where you can do things to update the user’s current profile.

So the idea would be to have the setupcomplete.cmd file create the user with a predefined secure password, then in the unattend.xml file have this user account setup to auto login once or twice depending on what you need, then have the first run section do what is needed to the user’s profile.

One of the last steps in the unattend.xml file is to delete the setupcomplete.cmd and the unattend.xml to erase any clear text passwords that might be contained within. Finally reboot the computer.

These are just ideas on alternate ways to go about solving this problem. I agree that accounts you create before should still exist after winsetup, but M$ typically has other ideas for us.

@itmod This piece of information still has not made it to the official docs (which are under work anyway). So here you go with a forum link: https://forums.fogproject.org/topic/16703/dual-boot-2-disks-unable-to-boot-grub

@kalafina Thanks for the update.

Nevertheless I opened an issue on github to look into making the fog-client a 64 bit application at some point.

@RTOadmin Are those topics related? https://forums.fogproject.org/topic/16715/printer-assignment-problem

May I ask you to not do double/cross posts? I know we have not answered in more than a week but opening another topic is not going to help. No offense! Just want to give you a heads up.

@lukebarone Thank you very much.It worked!

@kalafina I don’t know how to mark the topic as solved…

@kansukee I have never used Intune/Autopilot but from what I read about it I guess you can image using FOG and manage the devices with Intune/Autopilot. Give it a go and let us know here!

Searching the forums I can find a few hints on it here and there.

Hello, had the same problem. Try this, it’ wil fix your problem normally. Run the command : “manage-bde-status” many times until you see 0.0% .
Then try again to capture your image.

fog image .png