Good news, Single Disk (Resizable) uploads and deploys normally.

The problem was with my automated .xml I use with WDS. I had to manually set the partition types/sizes in the .xml and apparently FOG didn’t like something I had set.

Anyway, I turned off the automated setting, re-deployed to my image station, wiped out all partitions and let Windows automatically create the partitions. Once that was done I re-uploaded without issue. Then I deployed without issue

After this deploys I’m gonna try the newer init_32.xz, I have a feeling it will be fine now

Turn legacy booting off. Then set the bootfile to any .efi file and try again.

Update (don’t install yet) to the latest trunk via Git or SVN, then…

Edit /opt/fog/.fogsettings (or just comment out this line):

packages=''

Purge everything php5:

sudo service apache2 stop

sudo apt-get purge -y php5 php5-common php5-json php5-gd php5-cli php5-curl php5-mysqlnd php5-fpm php5-mcrypt php5-readline libapache2-mod-php5

sudo rm -rf /etc/apt/sources.list.d/ondrej-ubuntu-php5-5_6-wily.list
sudo rm -rf /etc/apache2/mods-enabled/php5.conf
sudo rm -rf /etc/apache2/mods-enabled/php5.load

Install php7.0:

sudo add-apt-repository -y ppa:ondrej/php-7.0

sudo apt-get update

sudo apt-get install -y libapache2-mod-php7.0 php7.0 php7.0-phpdbg php7.0-readline php7.0-cgi libphp7.0-embed php7.0-cli php7.0-common php7.0-curl php7.0-fpm php7.0-json php7.0-mcrypt php7.0-mysql php7.0-opcache php7.0-gd php php-cli php-common php-curl php-gd php-mcrypt php-mysql php-readline

Edit /lib/ubuntu/config.sh (lines 19-23, 81, delete line 82):

php_ver=7.0
php_verAdds="-7.0"
repo="php${php_verAdds}"
[[ $php_ver != 7.0 ]] && phpcmd="php" || phpcmd="php"
[[ $php_ver != 7.0 ]] && phpfpm="php-fpm${php_ver}" || phpfpm="php7.0-fpm"

[[ $php_ver != 7.0 ]] && phpini="/etc/$phpcmd/$php_ver/apache2/php.ini" || phpini="/etc/$phpcmd/$php_ver/apache2/php.ini"

That’s it then install the current trunk that you already updated to and the install should finish without errors.

If I had to guess I’d imagine that my work on config.sh could be simplified or improved but this always works and I don’t ever have to worry about php5 trying to re-install via .fogsettings.

Please feel free to use any/all of these steps as any of you please. I’m no expert on php but I can’t see any reason why the latest FOG shouldn’t be pure php7.0.

Feedback is always welcome

IT WORKS!!! You guys are amazing!

I did have to set Host Primary Disk to /dev/mmcblk0 but that was it

Single Disk - Resizable works!

@mcgonigiggle It is really that simple enjoy the many hours you’ll save with this trick ;D

@MRCUR No…just hopes and dreams.

Of course I’m running FOG on them lol…two normal servers and two storage nodes.

1. Re-package your desired software that you normally deploy with PDQ deploy into MSI’s (test all of them to confirm they install correctly).
2. Create Snapins and have them auto-deploy when desired.
3. ???
4. Profit!

I should mention that the Dell .exe driver packages will not work as-is. Make sure you extract them first.

This is the driver folder structure I use for all of my images:

AHCI
Audio
Chipset
LAN
Video
WiFi

I used 14.04 for about 6 months on two FOG servers, then fresh installed 14.10 on both of them.

I’ve been running 14.10 for over 8 months on both now with no issues. Don’t sweat it, IMO…

@Tom-Elliott No need to apologize brother! Thanks again to you and everyone who helped get these working

Every host is changing their hostname first and then joining AD awesome job, thanks man! Feel free to mark this as solved.

@Joe-Schmitt Wow that was fast…yes, I’ll get back to you later this morning.

@Joe-Schmitt You rock, thanks man! Great work, by the way

0_1466521312568_fog.log

You’ll see it under the first Hostname Changer entry.

Also, it’s worth noting that I’ve seen this same issue before…maybe twice in the last year…but before too long you’ve always fixed it

I was hoping the v0.11.0 client would fix it but it did not…

1. Setting Group Bios/EFI Exit Type works for any group. However, if you refresh any group page both exit types always default back to “Please select an option” instead of the group exit type that’s actually set.

2. Disabling a service for a group works but enabling a service never sticks.

Sorry, yes. Go ahead. Thank you both

Lol…

Signed, sealed and delivered!

Yes. For example, I can check any station’s login history and see when user “x” logged in…but searching for user “x” always returns no results.

I’ve tested this on at least 5-10 users and all of them return nothing (and yes, they are all logging in).

This has been broken for a while but I was hoping it would eventually be caught and fixed. Anyway…

Doesn’t work as in when any username is selected the search always ends with no results found.