So the server name is entirely irrelevant to the key data that is saved to the client ? The name is only used to direct the installer to where to fetch the key from?

It would be nice to have a server-agnostic heartbeat client that could be pre-installed to an image, instead of the full-blown server-tied client.

Then the FOG server on that subnet would pick up that ping and list those machines that don’t have the full client installed. This would then allow the technician to be able to push the client on to those machines via the web interface at their convenience.

PS Exec from the “PsTools Suite” might do the trick, but it still requires that the technician knows the name of the destination computer; after it has been Quick Imaged. Kinda defeats the remote idea.

I have 80+ sites with 18 physical and a half dozen mobile virtual FOG servers. My images are hardware universal and are used at every site. They are created by role, not by site.

Each server of course has their own SSL/CA which means I cannot pre-install the new FOG Client into the image, it must be installed after sysprep and pointed to the correct server. Identifying which subnet and subsequently which server the client should be tied to requires a fixed script. If the subnets change… the script in the image must change to follow it. Not a longterm solution.

Is there a way to remotely install the new FOG Client to a Windows computer that is in a workgroup, via the FOG Server’s web interface? ie: The windows client system just came out of sysprep and knows nothing … Schultz!

We can export everything else.

How about the ability to export/import the SSL certificate by web GUI?

Beauty. Thank you.

Selecting the image proper, then from that image’s definition page selecting delete, then selecting to delete the image files as well, the image files are deleted, but the image definition remains.

Ironically I then go to the list all images, select the multiple images I just not quite deleted, to delete the leftover image definitions.

My quick test with build 8599 of capturing CentOS 7.2.1511 as:

/sda1 Boot xfs
/sda2 Swap swap
/sda3 / ext4

… it captured and deployed fine.

@Tom-Elliott Sorry for the delay… patch week and all that fun.

I ran with disabling dynamic memory for other VMs until today. I updated my dev server to build 8597 and kept the 4.6.2 that the installer downloaded today (2016/07/14) and the issue appears resolved.

4.5.3 also hangs.

Reading past conversations regarding similar issues, I rolled back to Kernels 4.1.4 and resizing now works in seconds.

It appears I’ve run into a ‘Resizing Filesystem’ problem on an ntfs disk Hyper-V 2012 R2 VM I’m trying to upload.

A half hour later and I’m still waiting on `Resizing Filesystem …’ to complete.

This is with Kernel 4.6.2 . I’m going to pop this one and start reverting kernels to see if I get some love.

If it is Hyper-V 2012 R2 and you are running a Generation 1 VM which uses the Legacy Network Adapter for PXE booting then 100 Mb is all you will get as the Legacy Network Adapter is only a 100 Mb NIC.

Having said that, some kernels in the past have on occasion switched to the 1Gb NIC for uploading … including right now. I just rolled back to 4.1.4 from 4.6.2 and I’m getting Gb.

To the idea of a dedicated FOG OS, can you imagine the resources required for that? Wanna watch Tom implode?

Why reinvent the wheel?

Scope creep …

I just finished watching the captured stream. Thank you very much for doing so.

Now I really regret missing it live.

I wasn’t certain I was going to make it anyways, but sorry I missed the show.

I’d love to see this become a regular monthly or even weekly event.

If anyone has trouble selling this to boss folk as a good use of work-time, consider telling them it’s an ideal chance for a one-on-one knowledge transfer between you, the vendor and other technical folks.

Anyways, I hope another is scheduled soon so you can see the wall behind my head too.

It can yes. I was using the easy method of eliminating one possibility before I dug deeper.

Indeed. Thank you again for such a prompt turnaround.

First time installation of build 7707 on CentOS 7.2.1511, when visiting by web browser for install/update your database schema.

http://#.#.#.#/fog/management

Error communicating with the database. Error: SQLSTATE[42000]: Syntax error or access violation: 1049 Unknown database 'fog'

Error does not manifest when installing 7707 over an existing system.

From /opt/trunksvn/fogproject/bin/error_logs/

passwd: all authentication tokens updated successfully.
Failed to stop FOGMulticastManager.service: Unit FOGMulticastManager.service not loaded.
Failed to stop FOGImageReplicator.service: Unit FOGImageReplicator.service not loaded.
Failed to stop FOGSnapinReplicator.service: Unit FOGSnapinReplicator.service not loaded.
Failed to stop FOGScheduler.service: Unit FOGScheduler.service not loaded.
Failed to stop FOGPingHosts.service: Unit FOGPingHosts.service not loaded.
Failed to execute operation: No such file or directory
Failed to stop mysql.service: Unit mysql.service not loaded.
Failed to start mysql.service: Unit mysql.service failed to load: No such file or directory.
● mysql.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)
Failed to execute operation: No such file or directory
Failed to stop mysqld.service: Unit mysqld.service not loaded.
Failed to start mysqld.service: Unit mysqld.service failed to load: No such file or directory.
● mysqld.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)
Created symlink from /etc/systemd/system/multi-user.target.wants/mariadb.service to /usr/lib/systemd/system/mariadb.service.```

VirtualBox will PXE boot quite happily with:
Oracle_VM_VirtualBox_Extension_Pack-5.0.18-106667.vbox-extpack

Even if the size of the drive data on the image is an unlikely 230 GiB it would still fit on a system running bare Win7 with VirtualBox and a 250 GB (roughly 232 GiB) dynamically expanding virtual drive because the virtual drive will only be the size of the data plus a few extra bits.

My favourite suggestion… have you tried zeroing the destination drive?

You alsop could create a virtual machine with a dynamically expanding 500 GB virtual drive. Image to that then recapture it as single disk resizable.