Latest FOG 0.33b
-
r1420 released.
Major change for this is Plugins…again.
I’ve removed the need for the run.php file as the initialization of the data should be the same. Right now the file assumes a plugin makes a schema change, but I don’t think there’s more than the two plugins we currently have (Capone and Location). So this revision moves the data necessary from the run.php files of both plugins and adds them directly into the plugin management page.
Also, this revisions adds the “image name” lookup feature to the Host search information. You can now search hosts by what groups they belong to, the image names, host names, serials, etc…
Hopefully all will enjoy.
-
I created a new image after I changed the ssd to port 0 and the mechanical drive to port 1. It restores the ssd but if the mechanical is bigger than the original it skips it. I have not tried a bigger ssd yet.
-
r1421 and 1422 released.
1421:
Changes FOG PXE Settings category to FOG Boot Settings. Fixes a reference to a deleted file (HostMACManager) so it points to the right place, sorry booting was broken for a little bit there. I only just found out.1422:
Just makes sure the reference label is done correctly for the MACAddressAssociation fields. -
Tom,
It looks like fog is looking for the wrong file names for the image of the second drive. Is my config wrong or is this a bug? In the pic you can see that it wants d1p2 and d1p5 but when I created the image it made d2p2 and d2p5.
Thanks
[url=“/_imported_xf_attachments/0/633_IMAG0057.jpg?:”]IMAG0057.jpg[/url]
-
d1 means disk one (the first disk it finds (/dev/sda))
d2 means disk two (the second disk it finds (/dev/sdb))
p# means the partition number’s it recognizes.From the picture you’re showing,
d1.mbr (the mbr backup for disk one.) is correct.
Disk one (from the pic) is only one partition on it: (d1p1)
Disk two has two partitions, /dev/sdb2 and /dev/sdb5 is my guess based on the labels of the image files.
Is this what you’re seeing when you run
[code]fdisk -l[/code] since changing ports? -
Disk two has sdb2 which is extended and sdb5 which is the Ntfs partition. That is correct.
-
I definitely found the error! Thank you erod.
-
The problem was it wasn’t increasing the disk number after the first pull of information.
-
r1423 released.
Should fix the MPA issue. Basically the intDisk variable was set to one, which is expected, but I forgot to add the iterative statement at the end of that loop to increase it when needed. This should now be fixed.
-
It works now. Thanks Tom. There is another problem. When I choose boot from drive from the Ipxe menu it just sits there. It never boots.
-
Is there a way to turn on services when a host is registered?
-
Never mind my error.
-
[quote=“wolfemi, post: 24964, member: 5740”]Is there a way to turn on services when a host is registered?[/quote]
I don’t know what you mean? What services are you referring to? Are you referring to the FOG Client Services (e.g. Printer Manager, Client Updater, User cleanup, Directory Cleaner, etc…)? Or are you referring to the Windows Services (e.g. telnet, Windows Firewall, etc…)? Or are you referring to the FOG Server services (e.g. FOGMulticastManager, FOGImageReplicator, FOGScheduler)?
FOG Client services can be enabled at any point in time, but can only be “enabled” to a host if the host is already registered.
Windows Services are not controlled in anyway by FOG.
FOG Services are controlled on the server regardless of if there’s none or a million hosts registered and can be started/stopped at any point in time.
-
r1424 released.
Fixes some install issues, I hope, with Ubuntu 13.10 and others I assume.
-
r1425 released.
Just add’s an “example” plugin and modifies the PluginManagementPage to include the run.php file if it’s found.
-
[quote=“Tom Elliott, post: 24972, member: 7271”]I don’t know what you mean? What services are you referring to? Are you referring to the FOG Client Services (e.g. Printer Manager, Client Updater, User cleanup, Directory Cleaner, etc…)? [/quote]
I am referring to the Client Services. I have them enabled on the server and enabled on the Fog Client software. But when I register and image a new host they are disabled under that host service settings. It won’t rename, join AD, install snapins or printers. Once I enable it on the host it all goes. Just wondering if I could eliminate the extra step of enabling it on that hosts page?
-
not exactly.
The point of the services on the different areas is for granular control. part of that means some extra steps involved to get things working perfectly.
-
[quote=“Tom Elliott, post: 24978, member: 7271”]not exactly.
The point of the services on the different areas is for granular control. part of that means some extra steps involved to get things working perfectly.[/quote]
Is there a way to make them auto enabled as a template and we can disable them for the devices that we don’t want to change?
Or maybe group control settings?
-
[quote=“Jaymes Driver, post: 24979, member: 3582”]Is there a way to make them auto enabled as a template and we can disable them for the devices that we don’t want to change?
Or maybe group control settings?[/quote]
This is what I was asking. I don’t mind all the granular control. I just wanted to know if it could be enabled by default instead of disabled. I believe in .32 it was enabled by default because I don’t remember having to turn them on every time.
-
r1426 released.
Just updates the “TomElliott” config files for kernels to include Hyper-V support.
