@Wayne-Workman Why a Saturday, will it always be a Saturday?

@Wayne-Workman ahem @Testers aren’t welcome too?

I am 99% sure that the 1.3 instructions there are valid for 1.2.

Granted I would recommend updating to the trunk version. I think that if you just change the ip in the fog settings it might just take care of the rest for you.

@Arrowhead-IT Another quick update on this.
I confirmed that it’s the kkpxe vs kpxe that causes the local disk boot issues.
So I would say it’s not a bad idea to reccomend ipxe.kpxe as the default boot file and use .kkpxe with dhcp reservations as needed.

In other words, the answer to @Wayne-Workman’s question, is that we ought not default to a .kkpxe file, because on some models the local disk boot option fails on all exit types. However ipxe.kpxe includes all the undi drivers and what not, so perhaps that is a better choice.

@MRCUR Oooh, cool. However it wouldn’t let me enter audit mode either until I found this script. I did read something about using audit mode to get rid of modern apps, but I had to remove them to get to audit mode.

@Psycholiquid You are a beautiful person and I love you.
You may have just ended my 5 year hate war against sysprep.

Maybe I wasn’t looking hard enough, but everytime I tried sysprep or tried to customize it to my needs it failed miserably. Destroying customizations, getting stuck at oobe screens, just overall breaking everything. However, I just used your xml as a template and was able to successfully run sysprep on my windows 10 image and it worked pretty well and now I think I will be able to better search for the bits of the unattend.xml I need.

Also, a problem I ran into in windows 10 with sysprep is it sometimes gives an error about a metro app (movies and tv aka Microsoft.ZuneVideo for example) not being provisioned for each user or something. I had to run this powershell script I found in a microsoft tech forum (that I can’t seem to find again right now, but I saved the script for future use) on each user and it worked.

$AppsList = "Microsoft.Bing" , "Microsoft.BingFinance" , "Microsoft.BingMaps" , "Microsoft.BingNews"`
            , "Microsoft.BingSports" , "Microsoft.BingTravel" , "Microsoft.BingWeather" , "Microsoft.Camera"`
            , "microsoft.microsoftskydrive" , "Microsoft.Reader" , "microsoft.windowscommunicationsapps"`
            , "microsoft.windowsphotos" , "Microsoft.XboxLIVEGames" , "Microsoft.ZuneMusic"`
            , "Microsoft.ZuneVideo" , "Microsoft.Media.PlayReadyClient"

ForEach ($App in $AppsList)
{
    $PackageFullName = (Get-AppxPackage $App).PackageFullName
    if ((Get-AppxPackage $App).PackageFullName)
    {
        Write-Host "Removing Package: $App"
        remove-AppxProvisionedPackage -online -packagename $PackageFullName
        remove-AppxPackage -package $PackageFullName
    }
    else
    {
        Write-Host "Unable to find package: $App"
    }
}

Save that guy as a .ps1 file and run it on each user if you’re getting an error when trying to run sysprep on windows 10 (or 8/8.1 for that matter)

Also, this might still be a thing
https://wiki.fogproject.org/wiki/index.php/Auto_driver_Install

Most likely @ITSolutions is right and it is a bios setting that is different. The storage options/Sata emulation setting of AHCI, IDE, and or RAID needs to match on all the computers. Just like if you change that setting after installing an operating system it won’t boot then either.

Some other possibilties…

Do you do any form or shape of sysprep? I imagine you don’t since you’re going on the same hardware and you shouldn’t need to in that case, just checking.

Have you tried booting straight to the hard drive (i.e. skipping the network pxe boot)?

Assuming this is windows, Can you boot to a windows install disk and see if the installation shows up in the repair options?
Also in a windows install disk, if this is a bios/mbr image (not efi, this doesn’t work on efi/gpt) you can try these commands in a command prompt.

#shift+F10 to bring up command prompt anytime in windows install disk
bcdboot C:\Windows
bootrec /rebuildbcd
bootrec /fixmbr
bootrec /fixboot

Also in a windows 10 install disk you can check if the disk for some reason is not active

diskpart
list disk
#select your proper disk
select disk 0
select partition 1
detail partition
#look for active details

If these type of commands work then that’s a weird issue, but I figure why not give you all the options. I haven’t had to utilize that kind of stuff in a long time because fog takes care of mbr problems during the imaging process.

commented out if isset {...} stuff in index.php of management and it worked again.

Just a little update on this.
I’ve had ipxe.kkpxe as my default bootfile for the last month or so now.
For the most part things seem to go faster and better and all is well.
However on a few select computer models, all exit types fail to boot to hard drive. It’ll boot to the fog menu and to any fog tool, just not to the local disk.
I have ran into this on 2 models.
The HP 280 G1 and HP Prodesk 400 G1
The fix for both of these was giving the computer a dhcp reservation and setting the filename option for just that computer back to undionly.kpxe and it worked again. (I haven’t had a chance to try ipxe.kpxe to see if this was a kkpxe vs kpxe boot file issue)
In one instance on the HP 280 G1 the local disk boot worked with a Grub exit type on ipxe.kkpxe when using F12 to boot to network, but it didn’t work when network boot was set as first in the boot options.

So I ran into a weird problem on 2 computer models using ipxe.kkpxe as the default.
I haven’t run into any computer that wouldn’t boot at all with this bootfile. Just the random local disk from pxe menu not working on the 2 models out of probably about 20 different models or so. It’s a pretty diverse network.

I just updated to fix the printer issue and have a new problem now.
In every client I am seeing an error like this

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 4/7/2016 11:23 AM Client-Info Version: 0.9.12
 4/7/2016 11:23 AM Middleware::Communication URL: http://fog-server/fog/management/other/ssl/srvpublic.crt
 4/7/2016 11:23 AM Data::RSA FOG Server CA cert found
 4/7/2016 11:23 AM Middleware::Authentication Cert OK
 4/7/2016 11:23 AM Middleware::Communication POST URL: http://fog-server/fog/management/index.php?sub=authorize
 4/7/2016 11:23 AM Middleware::Communication Unknown Response: 
 4/7/2016 11:23 AM Service Sleeping for 120 seconds

Specifically 4/7/2016 11:23 AM Middleware::Communication Unknown Response:
This particular computer is my own. I tried resetting the encryption for the host and now it won’t authenticate.
I saw the message on another computer that then got all it’s printers but kept getting this error.

TL;DR
Unknown response error keeps new hosts from authenticating, but if host was already authenticated the client works with the error posting.

If you want to make it so you don’t have to comment out port=0 then you can fix this by fixing the resolvconf missing dns server issue.

See this old post for a ton of detail…
https://forums.fogproject.org/topic/2799/dnsmasq-kills-dns-lookup-on-fog-server/6
I know I’ve posted it in a more readable form more recently, but found that one first.

TL:DR
just edit the interface-order at /etc/resolvconf/interface-order to have your main ethernet adapter at the top and be sure to have nameserver lines defined in your static ip definitions if not using dhcp.

So this problem definitely relates to a windows xp to windows 10 file transfer issue and is nothing to do with fog.
From what I found here http://helpdeskgeek.com/office-tips/fix-office-2010-cannot-verify-license-error-message/
I discovered that the file tokens.dat is indeed a part of activation.
If you happen to have a similar problem…

stop the service osppsvc
Delete or rename tokens.dat and cache.dat found at C:\ProgramData\Microsoft\OfficeSoftwareProtectionPlatform
Start the service osppsvc
Open any office program and let it do the self repair

This also fixes the problem of the office installer autoclosing when trying to repair or uninstall.

So I thought I had this figured out, but then it happened 4 more times.
While re-imaging only takes about 5 minutes, plus the time to restore the user’s files, It would be nice if I could find a way to prevent this weird anamoly

@ch3i Thanks, I read that too. However having now fixed that up and enforced ntp domain server settings with a gpo, I think it fixed it.
That and I discovered there was a token based activation .dat file from xp that was trying to restore when the error happened. So it may have been a mix of a few things. But I believe I remedied the issue and it wasn’t related to Fog at all. It was either my network time settings or my migration from xp to windows 10 restore snapin trying to restore something. (Located here from xp…
All Users\Microsoft\OfficeSoftwareProtectionPlatform\tokens.dat)

So if this happens to anyone else, check your time settings, set a internet time setting on your image, follow this guide if you need help with a active directory ntp setup http://blogs.technet.com/b/nepapfe/archive/2013/03/01/it-s-simple-time-configuration-in-active-directory.aspx
and don’t backup the above mentioned file when migrating from xp.

I have a new theory that I’m testing. I was troubleshooting an unrelated issue that may relate to time settings and it looks like my AD clock is like 2 minutes slow. I didn’t look at the time on the computers that broke, but I have seen the clock be wrong on an imaged computer once or twice.

TL;DR - After imaging office 2010 fails to activate and can’t be activated, is fixed by re-imaging.

So I have been having a really weird problem recently.
It’s only happened 3 times out of the last 13 computers imaged in the last few weeks, but 2 of those were yesterday.

Here’s what goes down.
I image the computer and all seems to go well. But then I try to open any Microsoft Office 2010 program. It pops up and then after a second or two it pops up an error about office activation failing and a repair attempt failed (the office 2010 setup splash screen pops up and disappears right before that)

If I go to the kms server and look at VAMT, I can add the host and update the license status and the kms server successfully activated windows 10 no problem but it doesn’t even see Office 14 (2010) as an activated device.

I played with the office ossp.vbs activation tool to manually add the kms host and port and attempted to activate but it keeps claiming no key is installed. I tried to use ossp.vbs to manually install the GVLK kms client key and it says the key is invalid. I tried adding it in the command line with and without dashes to no avail. Tried a MAK key too that also is claimed to be invalid, but I know that both keys are valid. I tried to look at the cmid (client machine id) and it says it doesn’t exist.

In the event viewer there was some error about not being able to register to proof of purchase or something like that.

Now here’s the kicker. The quickest way to fix this is to just re-image it and then it works. So why would sometimes office work perfectly fine and other times not so much. Could a weird network error cause this, like a part of the image doesn’t make it to the computer?maybe the ethernet cables are just that old? The first time this happened I had discovered the machine was plugging into the network with a cat 5 cable and we just upgraded the switch to a gigabit switch, so I swapped it out with a newer cat 5e so it could image faster and that’s when I discovered after reimaging the problem was fixed. The first time this happened I was unicast imaging 2 other computers that both worked fine. But when it happened yesterday the computers were being imaged individually.

I’m already trying to fix this on the image configuration level by completely uninstalling all office programs and reinstalling them clean to make sure the built in repair mechanism can open if it happens again.

Thoughts?

@Wayne-Workman Couldn’t this just be locally scripted? I mean personally if I update fog on my main server I run the update on my node too. But I only have one node, so it’s no big deal. But if you have a script to update fog you could probably have one script that runs it on each node after the first one finishes. I don’t know off the top of my head the command for it, but I’m pretty sure you can do it with an ssh command in a script. Would need to deal with the ssh key setup and stuff first, but it can be done.
I suppose that since fog should already have some access to the storage nodes, the fog installer could say hey I’m updating, and look at the database and say hey look storage nodes and force a git pull or svn up on each and run the installer with -y on each one.

So it would take some effort but I’m pretty sure it can be made into a script. I think a self made script would be better, because eventually Fog will be a stable release without so many updates.

Of course if you were only updating the kernel and not the whole installation, adding an optional scp or rsync command to all storage nodes after updating on the main server would be fairly easy I imagine.

Needed to not use root as msqluser for storage node.
Set it back to fogstorage with password from the fog webgui fog config →fog settings → storage node settings (something like that)
Put that in the storage node servers /opt/fog/.fogsettings and redid the install again. All is well again

@Tom-Elliott Did anything change on the installation of storage nodes in the recent updates per chance? I didn’t see anything in the committs but I didn’t look too closely