I have to take back, what I said earlier.
When I first tried to migrate the database, I apparently did something wrong while exporting the db, because the size of the dump wasn’t nearly as big as it is now, when I tried it again. I now was able to successfully import the database and I have hosts, image definitions and users showing up properly in the web interface.
The next step is to perform all of this on my actual FOG server, as this was only a test with a VM.
Thanks for the help everyone!
By this time, I’m pretty sure, that the problem lies in the different database structures in FOG 0.32 and 1.3.x. After I imported the hosts from 0.32, not only are they not listed on the web interface, but I also can’t add a host manually anymore, so the import from 0.32 apparently messes up the databases somehow. I installed phpmyadmin to check the databases after the import and the field hmHostID from hostMAC is completely empty. If you add a host manually (it works before the import), this is not the case and it shows up properly on the web interface.
I guess, as long as someone doesn’t write something up, that particularly makes it possible to import from the old into the new database structure, we won’t be able to successfully import the hosts from 0.32.
If someone comes up with a way, that is working, please share.
The command
DELETE FROM `hosts` WHERE `hostID` NOT IN (SELECT `hmHostID` FROM `hostMAC`);
deleted all hosts I had imported, so I guess there is something wrong with the hostIDs? Any idea how I can fix this while importing hosts from 0.32?
I now have a VM with Ubuntu Server 16.04. and FOG 1.3.2 for testing.
I exported the hosts from 0.32 (via MYSQL dump) and imported them into 1.3.2. If I go into the fog database from the command line, I can see, that the hosts are actually there (names, MACs, descriptions etc.), but in the FOG web interface no hosts are showing („0 results found“). Any ideas?
Hi everyone,
I’m currently on
and would like to upgrade to
I’m looking for best practice tips to do that. I do have a VM to test it all with. This VM is not my actual FOG server, so no worries here. I already read on the wiki that it is recommended to freshly install Ubuntu instead of upgrading. Has anyone successfully upgraded Ubuntu and FOG instead of a fresh installation?
Would the following procedure work?
Should I go with FOG 1.3.0 or directly to 1.3.1 RC?
Any other tips?
Thanks in advance.
@Joe-Gill
I currently update from an external source and have no experience yet how it affects the Sophos console.
We use Sophos AV, too, and before sysprepping and pulling the image I uninstall Sophos AV, but just the program itself, not the Auto-Update application, which is separate.
After putting the image on another PC, Sophos AV is automatically installed via the Auto-Update, that was still on the image (including the update information, i.e. where to download it from). Has always worked for me this way.
With older Optiplex models (745, 755, 760, 780), I’ve had the experience, that strangely some will work with FOG (in my case 0.32), others won’t (regardless of BIOS versions). In this case, I don’t think you should put too much attention on the error message, because as you said other models on the same network are working properly with FOG. I’ve never been able to solve this problem. In a few cases, alternative kernels helped me out, but most times I wouldn’t be able to make it work.
The only work-around I know, is to put the HDD of the PC you want to image in another PC, that is working with FOG, and then after imaging (with shutdown afterwards) is done switch it back to the original PC.
A quick question:
Will there be no final 1.30 release? The last time I read about future goals, this seemed to be the next step.