It’s just that the boot sequence is particularly verbose, it’s pretty normal to see a lot of warnings like that when you are using the default kernel from version 0.32.

[quote=“Blackout, post: 424, member: 1”]It’s worth noting that if you run a KMS and a KMS serial you don’t need to do anything.[/quote]
As long as the number of workstations to activate is greater than 24, otherwise the KMS server won’t be activated.

It’s probably not advisable to be using the domain administrator account, better to delegate local admin rights to another AD account and then use that to install software.

Deploy a single snap-in to a group was something I always needed. I’ve a feeling someone has submitted code for this though. Connection restrictions would be good to, on a per snap-in level so large downloads from the server can be restricted, or ideally, throttled down. Add a reboot option to only reboot if no one is logged in so installing a snap-in won’t interrupt someone’s work but would ideally reboot if the computer was unused (maybe when they log out?).

I used to use .cmd snapins to install all the software I needed, post imaging. As long as the snap-ins are actually deployed (i.e. they are listed in active snap-ins) they will get run 6 minutes (by default) after the FOG service starts (assuming there are no host rename / domain join jobs to be done with the service - these will cause reboots so you will have to wait longer). In your case I think the only thing you need to do is make sure you script is executable from somewhere that is accessible to a non-domain PC and doesn’t reference any external files that are inaccessible to a non-domain PC. I have also used SFX self extractors and found them really useful. You may find the process a little more streamlined if you let FOG handle the naming and domain join though.

I think it would be more likely that a Ghost service would modify something in the OS or bootloader to do this rather than give you a true PXE boot. I’m only guessing though as I’ve never used Ghost. I believe Dell have a tool that will let you package config changes into executables that can be deployed. Other manufacturers may have similar tools and there are also more scalable solutions that can help such as Intel AMT.

I used to get a problem with the service not starting properly (or perhaps starting too early?) when my image included .NET Framework 4. Restarting the service would then cause it to act normally. Do you have .NET Framework 4 in your image?