Perhaps we can be given the option to change the timeout length?
Is there a PHP edit we can do to change it? Maybe the FOG web GUI can pull this value from a file, instead of it being hard-coded into the PHP ?
Perhaps we can be given the option to change the timeout length?
Is there a PHP edit we can do to change it? Maybe the FOG web GUI can pull this value from a file, instead of it being hard-coded into the PHP ?
[quote=“sudburr, post: 43309, member: 4706”]I have an svn3077 Fog server with three HDD setup. 1=OS+Fog, 2=PublishedImages, 3=Sandbox&WorkImages
2 and 3 are on their own separate HDD.
2 is Storage Node “DefaultMember”, Master, attached to storage group “Default” with image path “/images”
3 is Storage Node “other”, not master, attached to storage group “Other” with image path “/other”
I have several other Fog servers, each on their own subnet; each with their own PXE, DHCP etc, to be set up identically.
I want to keep a live mirror of the master server’s 2=PublishedImages and the associated image file definitions on all the other servers.
I’m not sure Fog can do this or how to do it if it can. According to a thread from August 2014 my best bet is to cron or manually rsync, then manually alter the image definitions on each server.
Am I wrong? Can Fog do what I want?[/quote]
Hyper-V replication ?
That’d be a live mirror, but it’d be in the off state till the main server became unresponsive. Others may have better solutions, but that’s my solution. My FOG server is in Hyper-V and is replicating to another server in case things go south… I’m pretty big on safety and fault tolerance.
[quote=“cspence, post: 43021, member: 28749”]Good to hear. I’ll be able to test it tomorrow.[/quote]
Bump.
Any updates?
So,
There’s a chance that I might be setting up FOG for my school district using the location plugin.
What’s the current recommended FOG revision ?
I want a solid version with as few known problems as possible.
I was considering using 2920 or 2922 because I’ve had zero serious issues with it so far, and it’s all I’ve used as of yet.
Also, I have to at least use 2920 because of the custom multicast address changes and Fedora support that it implemented.
I personally do not use SysPrep.
I find that maintaining several images is exceedingly easy. I keep track of about… emmm… 9 or 10 images I’d say.
There’s just something about using a Linux utility instead of a Microsoft one that makes my day.
I also looked into the Capone plugin for you… right here: [url]http://fogproject.org/wiki/index.php/Capone[/url]
But, Capone is actually depreciated in the current SVN, and it’s recommended that newer versions use what I described earlier. Here’s the text from that:
“[FONT=sans-serif][COLOR=#000000]As of FOG v1.3.0-r2651 the fog user can now add Quick Image to the Fog iPXE Menu(For All Hosts) and then select the exact image desired without having to do any registration. BUT intervention is still required to start imaging.”[/COLOR][/FONT]
[FONT=sans-serif][COLOR=#000000]But, if you’re using an earlier version, Capone might be for you.[/COLOR][/FONT]
It’s tough to automate because you’ve probably got all these different models coming in, probably flaky hardware, flaky HDDs, and all sorts of CMOS settings…
It’s understandable from a business perspective why you’d want to streamline & automate this but, I don’t see how all user interaction could be totally avoided.
How do you do it in you’re wipe environment? Boot-n-Nuke disk, flash drive? Is that network based?
[quote=“Mark Pickard, post: 43224, member: 609”]Not sure what I’m looking for but I’ve attached a screenshot.[/quote]
Look at Tom’s signature. It says where everything is.
Well, I don’t think FOG has anything to do with forcing you to setup another local admin account, and that’s why I suspect SysPrep.
Maybe you chose the “Out of the box experience” option accidentally?
Because you Sys prepped the image and don’t have answer files set up?
If I remember correctly, I think Dell allows you to choose your CMOS configuration, and the factory will set it as you like for bulk orders.
You could just have them all come with network boot as 1st boot device, and PXE booting enabled…
You could make the “Quick Register” the default… which would be overridden if there was a task waiting. In the Web GUI, go to FOG Configuration, then iPXE New Menu Entry. You can make an entry there for quick register, and set it as the default item, and choose to have this menu only show for un-registered clients.
Why isn’t your Dell distributor imaging your bulk orders for you?? Ours did it for us…
Just my ideas. Others might have better ones.
Well, when you say you’ve “got a lot more invested in it this time and don’t want to re-install”, what do you mean?
Do you have your database backed up? Can you just log into the FOG server and back it up manually? Can you copy your images from it to a different location?
You could do a rebuild if you could get your database & images backed up. I believe that importing a database is straight forward. After that’s done, you’d just place the images where they should go.
I’ve found this in the WiKi: [url]http://fogproject.org/wiki/index.php/Restoring_FOG_from_Backup[/url]
If you’re confident with it, it might be the way to go. Esp. since it seems like only the Web login is broken.
Also, for the record, I would advise anyone to virtualize their FOG server. Mine’s running in Hyper-V, and I take snap shots before any major change. It’s a safety net.
So, I’m going to assume that since you’re asking for help here, you don’t have this FOG server virtualized, and don’t have a snapshot of it when it was working?
Just a stab at this but,
take the machine you made this image from, and re-install the FOG client, Make sure the IP address is correct when it asks for it. Then make a second image from that. Then, try again.
A simple fat-fingered entry that you didn’t realize could be causing all this… or even a bad FOG Client install, although a bad install has never happened to me personally, but it’s possible.
Also, there’s a FOG Client log on the clients, it’s usually here: C:\fog.txt
It’d be interesting to see what’s in there after you’ve tried to image & join to domain.
I was intending to get some documentation for imaging Macs smoothed out, but yeah, whatever works. FOG server on a Mac, wild but OK!
Anything involving FOG & Macs should go here.
[quote=“Junkhacker, post: 43087, member: 21583”]perhaps this should be moved to a new “fog on mac” thread, so we’re not cluttering up the “requests for wiki access” thread[/quote]
Done.
[url]http://fogproject.org/forum/threads/official-fog-on-a-mac-thread.12532/[/url]
This thread is for the development of an eventual update to the WiKi “[URL=‘http://fogproject.org/wiki/index.php/FOG_on_a_MAC’]Fog on a Mac[/URL]” page.
Relevant questions are welcome. Relevant Documentation is especially welcome.
I was reading through this and thinking it was a DNS issue…
When you join clients to the domain manually, do you have to use the FQDN, or just domain name?
Specifically, in this building you’re having issues in.
[quote=“Uncle Frank, post: 43001, member: 28116”]Sounds good! We might just write things up as we get you going on this…
[B]How to best name this article?[/B]
EDIT: Just found this in the wiki: [url]http://fogproject.org/wiki/index.php/FOG_on_a_MAC[/url]
Could be the starting point…[/quote]
It’s funny that this one-line article has been viewed almost 6,000 times lol.
Clearly a little interest in it.
I think it’s a good name.
Does he maintain the sites, as far as subscription/bandwidth goes?