Latest FOG 0.33b
-
[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.
-
r1430 released. 1427-29 all were tests/failures sorry.
Implements a couple new things. First, module status by host is now it’s own class. Files needed to recognize this have been modified as well.
Services (modules) are now enabled by default on registered hosts.
Lots of other changes to, just look at the sourceforge site to see the changes between the files.
-
r1431 released.
YOU ALL CAN LEAVE ME ALONE NOW!
GroupManagementPage now has Service checking. The checkboxes get checked if all hosts have the same services enabled, or if they’re all disabled by default. They are also unchecked if hosts have different services checked from one another within the group.
Hopefully this makes everyone happy!
-
Remember people that if you want the latest, get on the BTsync
You could have changes within 20-30 seconds of them being made.Read only Secret: BAU3NUY3XTKVMHHEZO6C7OH55AN2PCGJV
Have there been any more developments on UEFI?
-
I’ll admit I am drooling a bit for some UEFI love as well. I have started to accept having to strike UEFI support from our department’s three year plan though. FOG alone will solve so many issues for us, that UEFI would be a willing sacrifice.
-
r1433 released.
Moves many database calls to class calls within the files.
HostManagementPage uses many settings from the Host class rather than calling the respective class. It set’s the additional fields properly now.
-
r1434 released.
Just add’s a task additional field that stores a current task.
-
Potential issue found: On the Host Management page, deleting a host does not work. You are firstly taken to a confirmation page, once confirming the deletion you are sent to a blank page. Having navigated back to the hosts list still shows the host.
Using r1434. Downloaded via tarball.
-
r1435 released.
Fixes the host deletion issue described here. Also modifies code a little bit to remove items a little nicer.
-
Thanks Tom. I have tested this functionality and it works as expected. This also fixes an issue in the pxe menu whereby you could not delete a host.
Another potential issue for you, this one has a suitable work around though. If I Register a host through the pxe menu, allow the machine to reboot and load straight back into the pxe screen where it is configuring, I get a sequential list of errors and cannot boot. This only happens when I have allowed the kernel to reboot the system, if I do it manually it is fine. The work around is to just reboot manually.
It may be of note that this is only tested through VM’s in VirtualBox, I have not tried this setup on real hardware as of yet.
I will keep implementing and let you know if I have any more issues
[url=“/_imported_xf_attachments/0/643_Error.png?:”]Error.png[/url]
-
I’ve seen this issue as well, and it only happens on VM’s not on barebox machines from my testing. This seems an issue with the reset/reboot of the NIC. On mine, it seems that the restart doesn’t actually release the DHCP properly. I’m trying to see if this is a VirtualBox bug as I don’t see the same issue on VMWare. I know of the issue, i just don’t know of the fix. Real hardware seems to work perfectly and, from what I can tell, VMWare works fine. VirtualBox seems to be the culprit.
-
Hi Tom,
I have this problem in the inventory of my new computer (Intel NUC) :
[CODE]i8042 not found…[/CODE]
[CODE]
System Manufacturer # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
System Product # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
System Version # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
System Serial Number # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
System Type Type: Desktop
BIOS Vendor # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. Intel Corp.
BIOS Version # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. WYLPT10H.86A.0025.2014.0303.1008
BIOS Date # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. 03/03/2014
Motherboard Manufacturer # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. Intel Corporation
Motherboard Product Name # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. D54250WYK
Motherboard Version # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. H13922-303
Motherboard Serial Number # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. GEWY40300HP7
Motherboard Asset Tag # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
CPU Manufacturer # SMBIOS implementations newer than version 2.7 are not fully supported by this of dmidecode. Intel
Corp.
CPU Version # SMBIOS implementations newer than version 2.7 are not fully supported by this of dmidecode. Intel Core
i5-4250U CPU @ 1.30GHz
CPU Normal Speed Current Speed: 1300 MHz
CPU Max Speed ${cpu_mspeed}
Memory 7.73 GB
Hard Disk Model
Hard Disk Firmware
Hard Disk Serial Number
Chassis Manufacturer # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
Chassis Version
Chassis Serial # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
Chassis Asset # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
[/CODE] -
Okay.
What does this mean?