Best posts made by Quazz

What do you mean boots into imaging but never starts multicast?

Where exactly does it go wrong? Before or after partclone? Any pictures you could take?

@george1421 I decided to go for 1.4.2 since it includes a couple of performance improvements and bug fixes.

Took a while longer because I forgot to include the hash file.

It’s finally compiling successfully, time for some more tests.

@Kiweegie You have to run installfog.sh while inside the bin directory otherwise it will fail in more way than one (just checked this on my installation to be sure)

@Junkhacker Sebastian and I discussed ZSTD a bit and the coin kind of fell on the “let’s keep ZSTD at this version until Buildroot catches up” to keep things a bit simpler and requiring less maintenance from the dev team.

There are other tools in the toolchain that could theoretically also be upgraded, but at the point you’re putting so much maintenance on the board for any future release that you have to question why you’re using a bundled package like Buildroot anymore.

@michaeloberg I’m guessing it ran out of IP addresses to hand out?

@MaMu No, I don’t believe ignore_resolvconf works for this problem.

You have to edit the startup script of dnsmasq in /etc/init.d/dnsmasq

And change

start_resolvconf()
{
# If interface "lo" is explicitly disabled in /etc/default/dnsmasq
# Then dnsmasq won't be providing local DNS, so don't add it to
# the resolvconf server set.
        for interface in $DNSMASQ_EXCEPT
        do
                [ $interface = lo ] && return
        done

        if [ -x /sbin/resolvconf ] ; then
                echo "nameserver 127.0.0.1" | /sbin/resolvconf -a lo.$NAME
        fi
        return 0
}

To

start_resolvconf()
{
# If interface "lo" is explicitly disabled in /etc/default/dnsmasq
# Then dnsmasq won't be providing local DNS, so don't add it to
# the resolvconf server set.
        for interface in $DNSMASQ_EXCEPT
        do
                [ $interface = lo ] && return
        done

        grep -qr port=0 /etc/dnsmasq.d/ /etc/dnsmasq.conf && return
        if [ -x /sbin/resolvconf ] ; then
                echo "nameserver 127.0.0.1" | /sbin/resolvconf -a lo.$NAME
        fi
        return 0
}

You can do this by editing /opt/.fogsettings with the relevant information and then running the FOG installer again.

https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

Please provide a screenshot of the failing deployment screen.

From what I gather George is on the right track with fixparts though.

Perhaps instead of the blue for active page, use the current orange? It looks nice, good contrast.

Maybe a darker color for text to improve legibility as well.

Given that it has issues putting back the partition tables, I’m guessing something went wrong in the capture process. Is it possible to recapture the image?

@latelier 7945 is several months old, not sure if XFS quite made it at that point. For the actual XFS partition it should be capturing under XFS mode, not RAW.

I don’t believer resizeable is an option for XFS, though, but could be wrong.

@Tom-Elliott You can bless them, but it’s not necessary if you use the fancy ISC-DHCP setup, FOG iPXE will simply show up as a boot option.

@Joe-Schmitt Even more universal, you can replace with %SystemDrive% so that if the drive letter of the windows partition is not C for some reason, it can still do it’s thing.

So

copy "%~dp0your.xml" "C:\ProgramData\Cisco\Cisco AnyConnect Secure Mobility Client\Profile\your.xml"

Becomes

copy "%~dp0your.xml" "%SystemDrive%\ProgramData\Cisco\Cisco AnyConnect Secure Mobility Client\Profile\your.xml"

@Joe-Gill Not sure if this would work but easiest way I can think off is to launch the installer with start /wait and then simply have shutdown /a as the next line, like so

start /wait \\nas\av\sophosinstaller.exe -commandlineswitches
shutdown /a

shutdown /a should cancel any reboot/shutdown command, provided it’s in time.

@cheisler8504 I don’t think that will help you.

The problem is that ‘joinsession’ will always try to ‘read sessname’ which is what the prompt is, essentially.

Quick ‘hack’ would be to edit that file directly, make it look more like

{
   $Send['joinsession'] = array(
       'cpuid --ext 29 && set arch x86_64 || set arch i386',
       'params',
       'set sessname sessionname',
       'param mac0 ${net0/mac}',
       'param arch ${arch}',
       'param platform ${platform}',
       'param sessname ${sessname}',
       'isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme',
       'isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme',
       ':bootme',
       "chain -ar $this->_booturl/ipxe/boot.php##params",
   );
   $this->_parseMe($Send);
}

And that will probably work, but will obviously be overwritten with an update.

As you can see, you have to hardcode the session name here, since (I’m not 100% certain) I don’t think the chained parameters (found in fog.multi) can be used to fill in the parameter in bootmenu.php

My best bet would be some kind of kernel parameter to set this value like that, I seem to recall something like that from some time ago, but don’t remember the specifics.

@Wayne-Workman You’d also need to change the interfaces in the relevant locations, no? I’m thinking of the storage nodes and multicast settings mostly.

@Shenanigan88

You can always boot to Audit Mode even after the OOBE, command is
%windir%\System32\Sysprep\Sysprep.exe /audit /reboot
When rebooted to Audit Mode and if you like to re-customize the default user profile, it will only affect all future user accounts but does not affect existing ones already present when you booted to Audit Mode. You can of course remove all existing user accounts if necessary before sysprepping

If rebooted to Audit Mode and existing user accounts are kept, you cannot use those usernames when back in OOBE after sysprepping. To create the initial user in OOBE you can for example simply create a dummy local user, let Windows finish the OOBE and boot to this dummy’s desktop, sign out and sign in to your original admin account and remove the dummy account. (in other words don’t forget to remove that account you create)

Sysprepping an upgraded Windows is of course possible and only needs a key and a DWORD deleted in the registry and changing the value of two DWORDs.

Next up make sure the following values are set to 7

Close the Registry Editor. Open Command Prompt, type slmgr /dli and hit Enter to open Software License Manager. Close it as soon as it opens, close Command Prompt.

I don’t know if the last step is necessary, though.

Good luck.

@Jay-Bosworth Are you sure there’s no DHCP running on your FOG server?

Check by

sudo service isc-dhcp-server stop

@Arrowhead-IT Just a fyi, you can modify it slightly to allow for spaces in share names/paths by putting quotation marks whenever the share variables are called. I tested this earlier and it works great.

Your script is pretty awesome