The important thing is that you upgrade your server. Until you do that the clients won’t be able to talk to it. When you do update it, your clients will automatically upgrade to 0.11.2 if that feature is enabled.

@Wayne-Workman That’s odd. I know that I had to create a different profile for LTSB but it certainly worked in LTSB. The profile I made in Win 10 Enterprise CB won’t work in LTSB and vice versa. Gotta create a new one. It’s lame I know.
My login times are much longer than 4 seconds though. But I have a lot of customziations. Little common fixes and startup scripts and backgrounds and stuff, so my first login for any user is like 2 or 3 minutes, but only a few seconds after that first time.

Do you want best practices to to get FOG to deploy to this system? The answer is pretty different.

If you want FOG to deploy to this system then you can either use FOG 1.2.0 stable (with current kernels) or deploy FOG 1.2.0 trun (which is a dev release of the soon to be FOG 1.3.0). You can use FOG 1.2.0 stable (I’ll assume what you have installed already??). That will work with win7 no problem. If you want to deploy win10, gpt disks, or to a uefi system you will need to be on the trunk release.

We can go into best practices once its clear what you are shooting for.

@Paul-Storic They can be separate or you can configure FOG to name the target computer what you have the device registered in fog. To do that you need to either enable early host name change or use the FOG client (must be installed on the reference image) to rename the host and connect it to AD.

@davemaxwell FOG, I doubt, is the culprit. See FOG, while fast, doesn’t “break” things, not in the sense I think you’re thinking.

The Client might interrupt an otherwise normal post-imaging step, but it is not FOG in any form destroying the sysprep information. I’ve run into things as simple as the host is restarting due to hostname change or ad join (directly client related but not “FOG’s” fault persay), to AVG/Antivirus, to drivers causing the image to not load properly on “first boot”.

@cojohnson said:

It makes it through partclone then fails to update the database.

Well that sounds strange. Could you do a debug upload and check the connection to the server (ping x.x.x.x and wget http://x.x.x.x/fog/service/Post_Stage3.php) to see if the connection is really gone after the upload finished. Do you see the image being properly uploaded / moved to /images/<imagename> on the server?

Snapin templates have been added to FOG Trunk (future 1.3.0 release). They are very very easy to use.

@Quazz it uses slmgr.

Example:

private static bool InstallProductKey(string key) { Log.Entry(LogName, "Installing Product key"); return RunSLMGR("/ipk", key) == 0; }

Check Windows + R > slmgr.vbs /?

Regards X23

Marking this thread solved since the request in the opening post is not possible.

Is this resolved or do you still require help?

The recommended way to boot WinPE based media is to use wimboot.

With small ISOs you can sometimes get away with just using memdisk on the ISO, but that’s not feasible for W10 ISO for example. (since the entire ISO would try to unpack in the RAM at once)

Booting W10 installation over the network is possible, but requires a lot more work to get it going. The basic principle is to load a modified WINPE ISO and then mount the unpacked ISO path and manually call the setup file to run.

I’ve used davido38’s suggestion re: cctk. I can even remove the pxe boot from the boot order. Now, any boot other than the HDD requires the BIOS password, but I can use psexec to set the next boot to pxe and then use psshutdown to reboot so the PCs can be imaged. Great work-around.

Even though it states it, I can not find a partclone.log file in /var/log…

This is only on the client - temporary. As soon as you reboot after the error the log is gone. But there won’t be any valuable information other than what you have in the picture already!

I am getting this same problem/error on 3 different computers all with 80 GB hard drives.

Well then I guess your image is corrupted as I see this is failing on restore. Try uploading the image again! Maybe your FOG server disk is full? What do you get from df -h on the FOG server?

@Jbob said in no reboot after image, rename, add to AD:

Well I am confused. According to that log everything worked perefectly…

I’m about to pull down a few other images. I’ll post back.

@Quazz Thank you good sir, this will help me in my future endeavors. I have already re-mastered my image using these steps, but it will help with my next rebuild.

@jaffascake FGO 1.1.2 is quite old. Does not have the kernel debug options mentioned. You might look into bringing up a new FOG trunk server to see if this one is imaging your Dell E5570 fine.

@ChrisRaff Can you please try this again and check the Test Management in the web gui after some minutes. Lately we had some machines that did actually image but just didn’t show anything on the client screen. By the way, which FOG version are you running?

@jpaul 0.32 is VERY old, but I’m glad you got it working.

@Wayne-Workman I don’t know when the global max size stopped being used, but I’m fairly certain it was removed when 1.0.0 released. (more or less).

I’ll look through the code to verify if anything is using it anymore.

Thanks Sebastian, for your answer.
Friday I’ll be in the office is I will try as you suggested

@Wayne-Workman I remoted in and we found this was due to any webpage requiring ad auth to access. As that access was not granted it couldn’t download the file.

Bug confirmed, the culprit? There was a + typed in the code instead of a ,
https://github.com/FOGProject/fog-client/blob/master/Modules/GreenFOG/Windows/WindowsGreen.cs#L50

This will be patched in the next version.