Posts made by Jarli

Just confimed.

The above steps do work as described.

Let me know if you need further help.

Here are the fog image settings I’ve used. [IMG]http://s29.postimg.org/h982niygn/linux.png[/IMG]
With a stock install of ubuntu 14.04, using Ext4, and the full single disk installation.

Create or register the host on the Fog server using either the WebIf, or the boot menu (WebIf is as simple as it gets) then create the image settings as shown above.

Schedule an upload from the new Ubuntu host. (If powered off, magic packet should power on the device and boot to iPXE), the imaging process will begin. If not have your system boot to iPXE and then it will begin. My total image is only 5.9 GB

The upload then begins.

I will test this image shortly once this is finished and provide the final answer.

A nightly image report of this would be wonderful.

Something I’ve been toying with (idea anyways) is to image a set of machines on a nightly basis, so that any casual employee changes become undone during the nightly restart.

And having my machines grouped, with an email notification of Success / Fail and percentages would be an extremely useful tool.

So you’d have a separate linux box running clonezilla, and have that has your “oh shit” box.

Got it. But why not use another fog server?

How would you go about making a backup of your fog server, so that if something happened, you had a way to restore to non-similar hardware.

Including the following items
[LIST]
[]Boot Menu
[]Images
[*]OS and OS updates (Ubuntu)
[/LIST]
Where would you backup and how would you restore it?

I haven’t done this myself but it is something I was looking into doing.

I’ll try on my end and see what I can figure out.

What version of Ubuntu are you trying to image?

Thank you very much for clarifying that.

I was very concerned about the general security of that password field…

I will be testing today if not tomorrow for the full AD join.

“hostname early change” is already active though… maybe it needs to be disabled?

After imaging a laptop, the laptop gets renamed to the device-id within FOG (perfect time saver here) and also attempts to join our AD domain.

We don’t have any AD credentials stored in the fog settings, and our images are of machines that aren’t connected to AD. (just prepared and ready to go “standard” laptop images)

So where is fog getting the credentials to attempt to join AD? (it adds the domain name, but doesn’t complete the registration within AD, [U]can’t sign in as a domain user[/U])

If we wanted this feature I know where to enable it and add the details, but have concerns that the account passwords are view-able in plain text when (clicking the eye lid in any such password field).

Does anyone else use FOG to join their freshly imaged machines to their ADDomain?

Do you have a separate account just for FOG so you can join these computers to your domain?

Is it possible to turn off the AD join portion and leave the computer renaming portion of FOG imaging active?

We are now looking at these, thank you for the guide.

Sorry for coming back to this so late,

But how would you add a menu list outside of this using the Advanced Menu option within the PX E settings

We attempted to use the Advance Boot menu, but were unsuccessful.

Given our above example which prompted your note. Copied below.

[CODE]
}
else if ($option == ‘fog.systest’)
{

        print ":$option\n";
        print "kernel memdisk iso raw\n";
        print "initrd diags.iso\n";
        print "boot || goto MENU\n";

[/CODE]

How would we add additional boot options to the advanced boot menu.

We ended up using this ISO [url]http://downloads.dell.com/diags/DELL_32-BIT-DIAGNOSTICS_5114-2_R206154.exe[/url]
[LIST]
[]With the above installer you need to run “Create a bootable image”
[/LIST]
[LIST]
[]This image gets saved on the fog server (at least with a stock install to) /www/fog/service/ipxe
[/LIST]
And adding this to the boot menu to BootMenu.Class.Php

[CODE] }
else if ($option == ‘fog.systest’)
{

        print ":$option\n";
        print "kernel memdisk iso raw\n";
        print "initrd diags.iso\n";
        print "boot || goto MENU\n";

[/CODE]

Well with the smaller Dell Diagnostics, which is now (dell.img) i get an message which is “Bootstrap to large to load”

Still testing, just providing an update for anyone who may be monitoring this ticket.

It very well may be, but I’ve dropped the iso I originally found, and have a bootable version now that I am working on configuring.

I found an older version of the ISO, which is much much much smaller at only 4MB. Will let you guys know what happens from here.

The iso is just over 1011MB
It can be found here [url]http://www.dell.com/support/home/us/en/555/Drivers/DriversDetails?driverid=W0R66[/url]

OK well that should be fine then.

The system is connected to a 1G LAN connection.
Has 4GB of RAM
and has a i5 with 2.5 Ghz

Any ideas on what would cause the system to load up until [B][COLOR=#ff6600]“Memdisk to large to load”. [/COLOR][/B][COLOR=#ff6600][COLOR=#000000]When I can run Memtest86+ without issue?[/COLOR][/COLOR]

Hi All,

I’ve recently rebuilt my fog server using Ubuntu 12.04 LTS, and Fog 1.1.1 after some minor tweaks, and research I’ve got it working perfectly.

I’ve added DBAN and NTPassReset successfully.

Trying to add Dell Diagnostics as a additional ISO that we can use.

It’s installed, and even starts to run, but I get

Memdisk: loading ok
Dell.iso: loading ok

[B][COLOR=#ff6600]“Memdisk to large to load”[/COLOR][/B]

[COLOR=#000000]Which is where the issue comes in. [/COLOR]

[COLOR=#000000]Is there a limitation that restricts how large an ISO can be that Fog can load onto a local machine? [/COLOR]

[COLOR=#000000]If so can it be raised safely without potentially crashing the system?[/COLOR]

[COLOR=#000000]Can Grub4DOS run Dell Diagnotics successfully? If so is anyone willing to provide some insight on how to [/COLOR]

[COLOR=#000000]1) install Grub4DOS [/COLOR]
[COLOR=#000000]2) point Dell Diagnostics to Grub4DOS?[/COLOR]

[COLOR=#000000]All without ruining this wonderful Fog server we have. [/COLOR]

[COLOR=#000000]Thanks in advance. [/COLOR]