If you insist on not using sysprep, there is a fourth option. Select [SHIFT] + [SHUTDOWN].

I have also seen this error caused by the Antivirus in the image. Although it affected all deployments, effectively poisoning the image beyond repair.

No issues. It just worked.

The Gen1 (Legacy) adapter appears to still be only 100Mb.

Just so ya know, I’ve successfully used FOG 1.3.0 RC16 (svn5983, kernel 4.8.1) to deploy and capture Gen1 (Legacy) and Gen2 (UEFI) virtual machines using undionly.kpxe and ipxe.efi respectively on a new Windows Server 2016 Standard with Hyper-V installed.

Kewl …

Yah … I need more caffeine.

Server

• FOG Version: 1.3.0-RC-16 (svn5982/3)
• OS: CentOS 7.2.1511

Client

• Service Version: n/a
• OS: n/a

Description

More of an FYI. PXE Booting a Hyper-V 2016 Generation 1 virtual machine with both Legacy Adapter and Network Adapter present fails with:

Hyper-V
PXE Network Boot 09.14.2011
(C) Copyright 2011 Microsoft Corporation, All Rights Reserved.

CLIENT MAC ADDR: 00 15 5D F4 0C 01 GUID: 7D4E1889-FA13-4662-BA48-2C84FBBF8965
CLIENT IP: 172.19.244.25  MASK: 255.255.255.0  DHCP IP: 192.168.150.62
GATEWAY IP: 172.19.244.7  172.19.244.1
PXE-E32: TFTP open timeout
TFTP.....

If the Legacy Adapter is added into the VM as the second adapter, the VM PXE booting will pick up the IP on this second adapter but appears to be trying to tftp on the first adapter, the Network Adapter.

Removing the Network Adapter or setting its virtual switch connection to ‘not connected’ fixes it.

If all adapters are removed from the VM, then a Legacy Adapter is added/applied first, followed by a Network Adapter second, PXE booting works as intended.

So RC16 is svn5981 and this new RC16v2 is svn5982 ?

Ruhroh Shaggy … pulling then installing 5982, the header says running 5983.

It is indeed possible to OEM activate a non-OEM image.

How you do it depends on exactly what kind of OEM license it is, whether it’s OEM:SLP, OEM:NON-SLP or OEM:COA. Read this to see the differences.

‘Activation Backup & Restore 1.7 BETA 1’ can be used to extract OEM:SLP Licensing key and certificate which is tied to the manufacturer, the BIOS, the key, the cert and the OS from an original OEM image.

backup-cert.xrm-ms
backup-key.txt

You can then use the same program to restore the OEM:SLP key and cert to a non-OEM image (like GVLK aka KMS).

There are other tools and methods but you’ll have to do some careful digging.

Lookin’ forward to checking it out Monday morning. Thanks for all your hard work!

It exports the definitions (the pointers) as a image_export.csv (Comma Separated Value) text file.

This file can be edited!

If after exporting your complete list of images from one server, you want to then import just one of those images to another server you edit the original exported .csv . I use Microsoft Excel.

Delete the lines for the images you are not interested in, then save that new .csv .

On the destination server you then import the updated .csv. The contents of which are then merged into that server’s database.

One of the nicer bits about the exported .csv is that the creation date and image size are saved and imported along with all the other pertinent fields. Do not worry about the image ID #, that is not saved or imported.

Of course you will still need to copy the actual image files referenced by the image definition onto the destination server.

I think a regular predictable interval might help. Like the first Monday (or whatever) of every odd/even month. Something people can pop into without an invite.
More than just a hangout but like a (dare I say it?) mini-Genius bar for FOG.

I realize I haven’t made it to one yet, but will there be a Hangout 5?

The problem exists with RC14v3 (5974) also.

PHP Warning:  ftp_delete(): Delete operation failed. in /var/www/html/fog/lib/fog/fogftp.class.php on line 243, referer: http://devfog/fog/management/index.php?node=image&sub=delete&id=137
PHP Warning:  ftp_rmdir(): Remove directory operation failed. in /var/www/html/fog/lib/fog/fogftp.class.php on line 784, referer: http://devfog/fog/management/index.php?node=image&sub=delete&id=137
PHP Fatal error:  Uncaught Error: Call to a member function close() on null in /var/www/html/fog/lib/fog/image.class.php:194\nStack trace:\n#0 /var/www/html/fog/lib/fog/fogpage.class.php(2774): Image->deleteFile()\n#1 /var/www/html/fog/lib/fog/fogpagemanager.class.php(232): FOGPage->deletePost()\n#2 /var/www/html/fog/management/index.php(45): FOGPageManager->render()\n#3 {main}\n  thrown in /var/www/html/fog/lib/fog/image.class.php on line 194, referer: http://devfog/fog/management/index.php?node=image&sub=delete&id=137

From /var/log/httpd/error_log:

PHP Warning:  ftp_delete(): Delete operation failed. in /var/www/html/fog/lib/fog/fogftp.class.php on line 243, referer: http://devfog/fog/management/index.php?node=image&sub=delete&id=140
PHP Warning:  ftp_rmdir(): Remove directory operation failed. in /var/www/html/fog/lib/fog/fogftp.class.php on line 784, referer: http://devfog/fog/management/index.php?node=image&sub=delete&id=140
PHP Fatal error:  Uncaught Error: Call to a member function close() on null in /var/www/html/fog/lib/fog/image.class.php:194\nStack trace:\n#0 /var/www/html/fog/lib/fog/fogpage.class.php(2774): Image->deleteFile()\n#1 /var/www/html/fog/lib/fog/fogpagemanager.class.php(230): FOGPage->deletePost()\n#2 /var/www/html/fog/management/index.php(45): FOGPageManager->render()\n#3 {main}\n  thrown in /var/www/html/fog/lib/fog/image.class.php on line 194, referer: http://devfog/fog/management/index.php?node=image&sub=delete&id=140
PHP Warning:  ftp_delete(): Delete operation failed. in /var/www/html/fog/lib/fog/fogftp.class.php on line 243, referer: http://devfog/fog/management/index.php?node=image&sub=delete&id=140

Server

• FOG Version: RC14 (5968+5974)
• OS: CentOS 7.2.1511

Client

• Service Version: n/a
• OS: n/a

Description

Upon first attempt to delete an image via the Web GUI, the files within the folder for that image are deleted, but the folder and image definition remain.
Deleting the image a second time will then successfully delete the folder and the image definition as well.

Thank you.

So for now, a workaround must be employed post-installation to make up for the FOG installer until it is updated to fetch and install the proper PhP repositories for CentOS 7.2.1511.

Can we expect this in RC15?

It’s interesting to note that pre-installing PhP 7.x causes the installer to fail.

This reminds me of some testing awhile ago with an earlier version of FOG where even though PhP 7.x was already installed, the FOG installer forced the installation of 5.4 or whatever.

Upgrading to PhP 7.x after installation of FOG, then rebooting

rpm -Uvh http://rpms.remirepo.net/enterprise/remi-release-7.rpm
yum-config-manager --enable remi-php70
php -v
yum clean all
yum makecache
yum update -y
reboot

… then revisiting the web page appears to fix it.

ip addr prior to installation of RC14v3

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:15:5d:f4:0d:2e brd ff:ff:ff:ff:ff:ff
    inet 172.19.244.32/24 brd 172.19.244.255 scope global dynamic eth0
       valid_lft 517660sec preferred_lft 517660sec
    inet6 fe80::215:5dff:fef4:d2e/64 scope link
       valid_lft forever preferred_lft forever

Entries in /opt/fog/.fogsettings immediately after installation

submask='255.255.255.0'
routeraddress='172.19.244.1
172.19.244.1'
plainrouter='172.19.244.1
172.19.244.1'

Server

• FOG Version: RC14v3(svn5974)
• OS: CentOS 7.2.1511

Client

• Service Version: n/a
• OS: n/a

Description

First-time installing at the command to:

You still need to install/update your database schema.
 * This can be done by opening a web browser a
nd going to:
   http://172.19.244.32/fog/management
 * Press [Enter] key when database is updated/installed.

Visiting the web page elicits:

FOG Requires PHP v5.5.0 or higher. You have PHP v5.4.45

PhP was installed by the FOG installer itself.