I don’t see how this is a fog issue…

but I create a default profile too. But I don’t do it per machine.
I create a default profile and stick it in a secured SMB/UAC shared folder - and I have startup scripts that copy down the profile to a host locally, and then make necessary registry & permissions edits and install the default profile.

I have a scheme I use to push a new default profile anytime I want to every machine in the building. It’s totally custom - but I’d be willing to share my documentation on it.

@atarone I believe the answers you seek lay ahead… https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit

@csavo Nope. It will function exactly how it is now. FOG doesn’t bother with your dnsmasq configuration - but I’d still make a copy of the configuration just because it’s good practice to have copies of configurations.

@anthonyglamis said:

I am open to updating fog, I am not sure what version of Trunk to run. Would I just download that from Sourceforge and install it on top of fog 1.2.0?

Basically, yes. Here’s a guide: https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

I did figure out even though the fog server and my Ubunutu box have the same time displayed, they are off by about roughly 5 hours.

Check out this article: https://wiki.fogproject.org/wiki/index.php?title=Time_off

@boeleke Please post a copy of your report for us to read!!!

@Sebastian-Roth said:

Marked as solved as the CentOS 7 article will hopefully be updated soon!

https://wiki.fogproject.org/wiki/index.php?title=CentOS_7

@anthonyglamis Honestly, fog trunk has drastically greater and wider support for more devices, and newer devices. Including newer style HDDs and newer boot methods.

I won’t lie, there are bugs sometimes, but they are usually minior. You just report them here in the bugs section, say “Hey ABC happens when I do 123, here’s the error and the version I’m on.”

1.2.0, while mostly stable, is really old. It won’t install out of the box on newer Linux OSs, and doesn’t support newer devices, and has basically zero GPT support.

My org has been using FOG Trunk since February 2015. We haven’t looked back.

Just the massive speed improvements alone in FOG Trunk make it worthwhile.

@Buddy Try a different HDD Exit type (host’s general page). Or, disconnect your USB adapter to allow the device to boot on it’s own. FYI Surface Pros are UEFI, so you only need to play around with the Host EFI Exit Type field.

@ManofValor Now try to deploy that image to another machine of the same model.

@Arrowhead-IT said:

Do I sound full of myself if I say that I never messed that up? Because well, I never messed that up. It just kinda worked as it should anytime I’ve done that.

No. Would I sound full of myself if I said I haven’t, either? lol. But a lot of people have messed it up.

@cemicolin FOG has wiping functionality. Quick wipe just deletes the partition tables. normal does one pass, full does 4 passes. You’re free to change the full wipe mechanisms in the inits (requiring decompress -> change -> recompress) and make it so that it does a 7 pass.

You can also try an older version of DBAN.

Happy fogging.

@anthonyglamis I think this is a bug. Tom’s doing a whole lot of work/improvements on the upload/download scripts at the moment.

@Tom-Elliott

RAID has to be involved somehow I think, either hardware raid or software raid. And software raid isn’t all that great.

This isn’t so much a fog question, it’s more a Linux question. Maybe this can get you started: http://askubuntu.com/questions/7002/how-to-set-up-multiple-hard-drives-as-one-volume

It contains terminology that you can use to do more Google searches.

@ManofValor Bad idea… use Clonezilla for that.

@anthonyglamis said:

“The security database on the server does not have a computer account for this workstation trust relationship”.

Check to see if your image is already bound to the domain.

Also, inside of your /opt/fog/.fogsettings file, make sure there is not two fields for CaCreated=

Message: 1
Date: Wed, 18 May 2016 16:44:39 +0100
From: Simon Kelley simon@thekelleys.org.uk
To: dnsmasq-discuss Dnsmasq-discuss@lists.thekelleys.org.uk
Subject: [Dnsmasq-discuss] Announce: dnsmasq-2.76
Message-ID: 573C8DE7.3030603@thekelleys.org.uk
Content-Type: text/plain; charset=utf-8

I’ve just released dnsmasq 2.76.

Download from http://thekelleys.org.uk/dnsmasq/dnsmasq-2.76.tar.gz

It’s more than nine months since the last release, so get the new code
quick, there’s lots to go at.

Cheers,

Simon.

@ManofValor If you go to this address via a web browser, what is the output?

http://10.10.1.40/fog/service/ipxe/boot.php?mac0=48:0f:cf:27:72:6f

For you and future readers, you’ll see I have a MAC address at the end of that URL. This is how you can manually ask the fog web server to generate what WOULD be the iPXE boot script for whatever clent’s MAC you plug into that spot. Multiple MACs can be passed via standard POST syntax, like this for example (fake but valid example) http://10.0.0.4/fog/service/ipxe/boot.php?mac0=48:0f:cf:27:72:6f&mac1=14:fe:b5:df:fc:7e

@anthonyglamis said:

With the new client 0.9.10 do the new clients intended to be deployed and auto joined to the domain need to be created in AD before deployment?

No. When they join, they will appear in the default OU, whatever that’s configured as. On an unchanged AD setup, this is the “computers” OU. I always change mine though.

@Sebastian-Roth Added: https://wiki.fogproject.org/wiki/index.php?title=Location_Plugin

Also, @Sebastian-Roth when things are hash tagged wiki, after I add them I edit the hash tag and remove the hash symbol. Just an FYI so you can do the same if you wanted.