[quote=“Joseph Hales, post: 46730, member: 18131”]Install FOG client for everyone you no longer need to run fog prep for fog 1.2 and up.[/quote]

Thanks for the reply! I let the virtual machine I make my image in run after sysprep and the test seems to indicate that installing for everyone is the way to go.

Thanks again.

I searched the forums and couldn’t find anything on this topic – apologies if I missed it.

I am creating a new Win 8.1 image and installed the FOG client. When I deploy the image, the FOG installer activates after login and tries to reinstall FOG.

I remember running into the same problem when I made my initial Win 8 images a couple of years ago, but can’t remember what I did to fix it.

I have two things I’m going to try, but I wanted to see if someone else has experienced the problem and can tell me without a bunch of trial and error.

The two things I am going to try next are installing FOG “for everyone” instead of “just for me.” I am also going to run FOG Prep, though I don’t do that for Win 7 and can’t remember doing it for Win 8 either.

Any suggestions?

I had the “press any key to reboot” problem for some of my machines. It turned out to be the exit style for the FOG menu. Go into the FOG configuration under PCE boot menu and there are three options. Grub seems to work for my machines. The default option didn’t work for any of them and the second option worked for about half.

I understand. FWIW, switching to the old bzImage and 32bit init file appears to make my Hyper-V server work again. I’m uploading a new image right now.

Oh wow…that’s pretty cool.

Also, am I correct in assuming the 32 bit kernel is required for 32 bit clients? Because I still have a small collection of 32 bit machines.

Gotcha. I would prefer to keep the 64 bit to retain the extra features, but if it turns out that dropping to 32 bit would enable the old bzImage to work with Hyper V, then I’ll take that.

Very interesting. Is there a way to change the init file to 32 bit to match the kernel? How does that work if you download one of the 32 bit kernels available? Or are those only meant for 32 bit servers?

So, I upgraded and now things still don’t work, but are a bit different.

First, I tried copying the old bzImage file from the old install, but it will not work with the new install (I confirmed it worked on the old install earlier today). It has the error “kernel panic – not syncing, no init found.”

Second, I tried the default kernel from the upgrade. It doesn’t work, but I get a different error than before. It says “BUG: using smp_processor_id() in preemptible [00000000] code:ntfsresize/”

Any thoughts?

Indeed it is.