Posts made by d4rk3

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.

@mr626 Awesome, I’m glad they’re keeping their site up to date. Cheers!

https://forums.fogproject.org/topic/3945/sysprep-windows-8-1-image-and-upload-to-fog-1-2/2

None of the steps have changed on Windows 10. I still use my 8.1 answer files when sysprepping 10

Awesome! I’m glad this is helping people update to php7.0…the performance increase is very worth it!

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

@MRCUR No…just hopes and dreams.

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

I’m running pure PHP 7.0 on four different Ubuntu Server 15.10 servers…let me know how I can help!

@Tom-Elliott As always, no worries, Tom. You the man! Everything is fixed

Unfortunately nothing new is coming into the Apache error log when trying to export anything or look at reports.

Exporting hosts/groups/images/snapins all lead to a blank page.

Reports - various pages (Inventory, Host List, etc.) all lead to a blank page that says:

Invalid type

Same issue here. I was able to deploy by setting it to Single Disk - Multiple Partitions.

Then, out of sheer curiosity I re-uploaded that image as Single Disk - Resizable…and it now deploys fine but it still behaves like a Single Disk - Multiple Partitions image…the disk doesn’t expand to full capacity post-deployment.