thank you

Thank You!

Sometimes you just feel a little slow on the uptake. I put the pieces together and realized something. In the wiki entry on using FOG with FreeNAS, the instruction is to create 2 separate datasets --> images and images/dev. This is what sets up the different mount points that gives a problem with ftp in FreeNAS.

I deleted the 2nd dataset from FreeNAS and then went into the shell in FreeNAS to recreate the dev directory under images. I recreated the .mntcheck file and set the permissions for the FOG user. The rename of a directory from the windows ftp client now works to rename from images/dev/test to images/test so now the FOG image should work.

Would someone please update the wiki to not create 2 datasets, please?

Yeah, sorry about that.

I meant to merge into a different branch, accidentally switched to dev-branch, it was late sorry.

@Frank said in Unable to join to domain - build 3331:

I guess public key is at “/var/www/fog/management/other/ssl/srvpublic.key”

Just dropping a friendly moderator line here - in FOG 1.4 the public key is here on the main fog server:
/var/www/fog/management/other/ssl/srvpublic.crt
You should be able to view the public certificate via the below URL, replacing x.x.x.x with your FOG Server’s IP address or FQDN.
http://x.x.x.x/fog/management/other/ssl/srvpublic.crt

@Wayne-Workman We move away from using preset names because it left room for error.

@JGallo YEs, that is correct. rc-3 has the fix too and so it will remain going forward.

One server can be the master of several groups. This is how I setup exactly what you’re doing at my old job.

So say you have servers A, B, C, and D, each one geographically separated at their own site. Say that A is the master and has uber amounts of space. Say that B, C, and D have limited space.

Site A’s fog server would be the main server & the master of four groups.

Group 1 - has all images in it and would be the primary group for all images. The master of group 1 is server A, and Server A is the only member of this group.

Group 2 would be for site B. You’d create another ‘storage node’ using FOG’s web interface. You’d use the same IP address, same user & pass, same /images directory. All this would be all the same - but you would name it something like Site B Master. Then you’d configure Site B’s storage node out at the remote location to be a non-master and a member of Group 2. With this setup, only images shared with Group 2 would replicate to site B.

You would repeat this sort of setup for C and for D.

Make sure the main server has plenty of space and compute power. At my old job, with most locations using the same image - and with the shear number of images we had - we burned through 400GB in a flash. I’d suggest you shoot for 1TB or larger - even 2 or 4TB - because you’ll eventually get that one model where no image type works except for RAW and you wind up with a 500GB image file just to support that one dumb model.

Fog was listed as DNS server. We figured out the problem. Someone had entered the address of the Fog machine as a DNS server in IPv4 properties on the workstation. User error, totally unrelated to Fog. Please close or delete this topic. Thanks!

@irishfoguser

not sysprepped

This is possibly the problem. Not everyone syspreps here, but I recommend trying it and see if that alleviates the issue.

@Joe-Schmitt said in SmartInstaller on mac ERROR !:

https://download.mono-project.com/archive/4.3.2/macos-10-universal/MonoFramework-MDK-4.3.2.macos10.xamarin.universal.pkg

Waho… it’s work ! Realy Thank’s !

If you followed this you wouldn’t have the problem: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

George is right. Without these things we can’t help much.

@finvader Yes, set your boot order in all the machine’s firmware to Network First, HDD second. By default, if there are no jobs in FOG for said machine, it’s sent to the HDD to boot.

This “sending to hdd to boot” is controlled by the exit type in the FOG Web interface. The default can be set in FOG Settings. The setting can be altered per-host or mass-applied via Groups. The default is SANBOOT and works on most things, for most of the ones SANBOOT doesn’t work on, GRUB usually works. And then there are other options for the really difficult boxes.

I set the boot order in the firmware for 500 systems at my old job. I didn’t do it all at once, I modified the machines one by one as I needed to image them. Over the course of a year and a half, I got them all.

Of course I was also planning on modifying all new machines to boot to the network first as we received them - but then I got a new job.

I’m sorry your post isn’t clear. This is what I think I read.

“We had fog setup in a test environment running on vmware workstation 8”

“We setup a new FOG server with the same settings of the test environment.”

The “we have another server for pxe boot” and “paste into my new fog dhcp server” are confusing.

I have some questions back to you.

I your test fog server (running on vmware workstation) on the same subnet (network) as your new FOG server? On your network where your new fog server is installed, does that network already have a dhcp server installed?

We really need to know about your network to be able to help you.
On the network where new fog server is installed is FOG acting as the dhcp and dns servers?

in the interim, you could always setup rsync until toms worked his magic :-)…

Good news this morning I rebooted the server gave it another try and it all worked.

Tom, Wayne and George, THANK YOU!!!

It’s all good now. And I learned a lot. And archiving this on my end with my notes. Until next time.

I apologize for bugging so much… 😞

@fry_p Your current efforts has not gone to waste. When the other method is proven, you will just move your patched fog.mag.reg to the fog server postinits directory and add in the postinit scripts to copy it over each time. What you have created to day will work just fine moving forward, you just won’t have to unpack and repack the inits after each change.

@darkrelic said in installing now everthing is updated Failed!:

@george1421 that solution works thank you

(Lucky guesser) == George 😉