@Junkhacker You’re for-sure not most people.

@Dalton-Childers As soon as it’s solid. I can tell you we’re getting closer all the time though.

@joe-schmitt said in Dual boot - Linux hostname doubt:

What you could do is include a postscript, or a script in the Linux partition set to run on first boot, to take care of the host renamining and active directory join.

That’s not as hard as it sounds either. I automated automatic naming & domain joining with just a bash script at my last job. With the FOG API, you can get the correct hostname and add/change a letter in it. At an even earlier job, our hostname nomenclature included a ‘W’ for windows, ‘M’ for mac, and ‘L’ for Linux.

I’ve been following FOG Trunk revisions since 2922. I’m on 4196 currently.

My FOG server runs inside Hyper-V on Server 2012 R1

I’ve not had any issues related to Hyper-V.

I’m using Fedora 21 Server, 64 bit.

I did ask the partclone people for a custom message argument to be added to partclone, they responded yesterday. They said they are currently working on release 0.3.x and once this is done, they can look into this feature request.

@andyroo54 we made the forums group a little later, it sends out an email for anything concerning a fog hangout.

@imagingmaster21 My professional advice is to migrate to a new box: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG We could spend days trying to help you solve whatever problem you are having - and there is no guarantee we will even be able to solve it. Ditch this server. Treat servers like cattle, not cats. Follow that step-by-step guide to migrate and you’ll be back running again in no time. I strongly recommend you migrate to a VM. Then you can make your old T330 a VM host to house FOG. Debian 9 and CentOS 7 both have powerful VM hosting capabilities that are free. With VMs, you also gain the ability to snapshot before doing any more future updates as a safety net.

“host registration bypass” ? For what, to image without registering? You can do that with the Capone plugin. it’s available in 1.2.0.

In FOG Trunk (see link below), the Capone plugin is made obsolete by the “quick image” feature. You may choose to “quick image” from the boot menu - if the host is registered or not - and then choose the image you want to use.

https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

@rmurra81 We don’t appreciate being called stupid. There are already open source solutions that specialize in building machine images from scratch, notably packer. For the closed source crowd that likes paid support, there is MDT. WDS is a worse solution than FOG - and not everybody cares to keep images with current patches constantly - at my previous job we built images from scratch once a year manually. Others do a quarterly image via MDT. Still others use snapins to apply patches post-deployment. Still others use Group Policy coupled with WSUS to update systems.

@John-Johnson If you mean the FOG Client that runs on Windows machines, no. The legacy client has to first be removed, the machine rebooted, and then the new FOG Client installed. That said, the legacy client is compatible with FOG 1.3.0 but only for the purposes of allowing you to more easily transition.

If you mean the server, yes you can install ‘over the top’.

@quazz It does setup PHP 7 using the Remi repository.

@isaiah658 Thank you for finding this, it’s a very important bit of knowledge until FOG 1.3.0 is released.
Tom was able to find the new link to this thread. Thanks again, @Tom-Elliott

@econcepts Please try this.

Here is the new link: https://forums.fogproject.org/topic/3703/fog-is-inoperable-after-server-reboot

I only counted two or three people on the spiceworks thread that confirmed this worked, and one in the fog thread that confirmed it works. That’s more than enough to tell me that it works.

I’m going to work on putting this information in the WiKi so that it’s more easily found and never gets buried again. I think that it’s home belongs in the “Troubleshoot MySQL” article: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_MySQL

@educapole You can create a recurring WOL task with FOG, I’ve done this in the past to automatically turn on computer labs in a school building so everything was ready to go when class started. You’d put all the computers into one group, then use the group to setup a WOL task, configure the CRON area for the WOL task.

The below picture is how you would schedule a wakeup at 8 AM every day. For this to work right, the FOG Server’s OS date/time & timezone and PHP’s timezone (in fog settings web gui) need set correctly. Otherwise even though you define a schedule, it’ll fire off whenever the server thinks it’s 8 am.

That rebranding is super-slick. This means more integration/trust when the fog client does pop up to say something. It’s more official.

Also I’m very happy to see that settings.json bug worked out finally - apparently it was Microsoft’s fault because their writes aren’t truly atomic in nature as they promised, if I remember what Joe said correctly.

@stylus3530 In fact, you can deploy a 1.2.0 image and re-capture with 1.5.2. All you need to do is not allow the image to boot. Once deployed, immediately re-capture and all should work fine.

@Paul-Freeman said:

Well unfortunately when I loaded Trunk on my test setup it caused the fog DHCP server to stop functioning. I am going to start over on the test machine.

Or you can ask for help?

FOG Trunk will eventually be FOG 1.3.0 and you’ll either move to it when it’s released or be stuck on 1.2.0 forever or just use some other imaging solution - I’m indifferent with what you choose, but your decision to fleet away from trunk was quick and a snap decision - especially when there are people here that are willing to help.

If FOG Trunk doesn’t work for you, the @Developers need to know what happened and why.

When you run the trunk installer, run it like this:

./installfog.sh --help

There are now arguments for the installer, you’ll also notice the DHCP arguments.

@educapole group management - click group - basic tasks - advanced tasks - WOL - schedule cron style

Or something like that.

Good job, team. It was a long time coming but well worth the wait.

@kte Read through this: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

@aceindy

You create an upload task from the web interface.

The installer should have given you the web address, unless you didn’t complete the installer.

It should be x.x.x.x/fog/management