@Nika I don’t have predownload/preupload scripts built in, but I believe why @ch3i is confused is because you’re going to be overwriting the data after wiping the disk, which will do the same thing. Wiping the disk just adds extra time in the end that is more or less unneeded.

@arnaudrigole The message is clear, there is a Duplicate somewhere. We need you to search for it by searching for the MAC’s that @Joe-Schmitt gave you earlier.

You can even do a manual sql query if needed.

I’ve added the hostinfo.php script, though in a much different fashion. As I stated in chat and on the comments of the pull request, I have not added the setHostname due to security concerns. That all said, the information is now exposed as you requested.

@Tom-Elliott https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

The idea of FOG Torrent was to download the image via torrent, and the more that had to do the task, the more you had to seed the image around.

This actually works pretty well, but it also means you must create a location to download the image first. This means it would ONLY work for resizable images and you had to make some pretty weird guestimates.

I accidentally broke it (although for good reason) by switching the filenames around from the resizable rec/sys .img formats to use the common filenames now of d1p1 and whatnot.

I’m not overly concerned about removing it and it was really just an idea that started to spin a wheel down the road, but hasn’t really gotten much traction as you can see.

If you’re running the new FOG Client it will automatically register new hosts with whatever the hostname of the system is. Do not use Quick Registration to do this as all it does is make it so people don’t have to type anything and it’s purpose is to set the hostname.

I can try to look at a method of pulling the windows hostname out autonomously but this is more a feature request than a “problem”.

I think the new FOG Client installed on your systems would do better what you’re asking.

When the new client checks in, if host register is enabled, it creates the host entry into the FOG system under a “pending” status. This pending status should have the windows hostname as the hostname of the host within fog. All you would need to do is approve it.

Added as requested. This make sense to me. I’ve also added the total clients a Group can have.

@jgurka What you’re saying is wrong. I coded it, I know what it’s doing. I’m trying to help.

I feel I should add all Enabled nodes will send wol. Non enabled won’t cause they’re not enabled lol.

@jsmith if you go to the host and uncheck domain join and recheck it it will do the work for you.

FOG Mobile works perfectly fine.

I’ve been maintaining it, and even test it.

it isn’t as robust as the “main” page, but this is kind of the intent.

I’m not going to remove it simply because I think it’s highly useful when restricted to a phone.

@Wayne-Workman yes. This is because the Storage Nodes can also be responsible for the “Checking in/Completion” of tasks.

Added the plugin to the plugins in the working branch.

%WINDIR%\Panther\unattend.xml

@george1421 et all. I’m still around. I can probably help

@Arrowhead-IT I’m aware of what the problem is, and it’s because I am forcing the directory of snapins to contain the ssl files.

In the code, particularly the decrypt code, I’m specifically searching the /opt/fog/snapins/ssl folder to do the decryption, or the global FOG_SNAPINDIR setting if it is set. Maybe this can help fix the problem? I will see about making an entry to allow for dynamic use and find of the ssl folder/files. For now, I’d recommend adjusting the global value. I’ll work on making it more dynamic and adjustable per node.

@scgsg There are may things that impact the speed, regardless of the manager in use.

1. Network, the most obvious one here, would play a big factor.

2. System, as decompression is handled on the client.

3. Disk read/write speeds, this one is probably the largest factor on most modern systems.

4. Compression type, ZSTD compresses and decompresses much faster than gzip when in multithreading.

5. Compression Ratio, 19 is the maximum I’d recommend for any zstd as the memory required for any higher makes it nearly impossible to perform on most systems. 0 is the minimum, it still compresses but is nearly nothing. This impacts speeds because of the data that would need to transfer over the network. 1GB plain on a 1gbps will take anywhere between 5-10 seconds on a “perfect” network. 1GB compressed to 50% would take half the time to transfer because the data size would be only about 500MB. The speed it writes to disk would primarily be slowed down by the system decompressing the system. You must think of this when capturing too because while it will ultimately mean faster deploy’s, this setting can slow the capture process quite a lot.

6. Hops over network. The most direct route to a system will give you the fastest speed. If you have to jump through 10 switches to get to the host, your delays are somewhat related to the network as the data has to traverse the different points to reach the target.

These, obviously, aren’t everything that might impact speeds, but a basic list of what I can think of for right now.

As you’ve seen with the many other posts however, your case appears to be the exception. I understand there may be others with similar results to your own, but please understand we aren’t making these changes to make your day go longer. If anything we’ve made these changes so the vast majority of people will have a faster deploy/capture time. It also helps that partclone is in active development where partimage seems to have lost their develoment.

@lebrun78 https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

Just for tracking purposes for those that would like to try this:

https://github.com/FOGProject/fogproject/tree/working-RC-11

Under packages/web/lib/plugins/ldap you will find the plugin.

Easiest way to get it would be to simply install the ldap plugin after installing working-RC-11 branch. I don’t recommend this only because while it’s a “WIP” and addresses bugs and minor improvements/fixes around what’s being found from RC-10, it’s also meaning those on RC-11 would be returning info that’s rather irrelevant for the time being. I’d prefer people to work on RC-10 and get a thorough list of bugs and issues to work out. That said, any of the developers and moderators that would like to install please do, I can fix the things I miss due to it not being in the “mainstream” of things which can help make RC-11 that much more suitable for environments.

This one exception (ldap) is the only thing I’d like to see people testing from RC-11 as it could use VAST amounts of improvements and make using FOG in an AD Environment that much easier to control.

For example, with the new modifications (once fully completed), you can define ldap authentication from eDirectory, openldap, ldap, and Active directory. You can associate groups in your ldap choice to allow users mobile access, and your IT team admin access. I hope something like SSO of this sort will make it into FOG 2.0 as well, which is why I’m kind of excited for this plugin to get revamped.

@Fernando-Gietz, @george1421, and myself have had the most authoring done for this plugin and have been added to the author’s of this plugin. @x23piracy You helped tremendously a few months ago with testing and providing an open test ring for me to use although it may not have accomplished what the two of us had hoped for.

Thank you @george1421 for actually kind of kickstarting this plugin back into shape. Thank you @Fernando-Gietz for actually establishing the basis of the plugin.

Anybody who would like to try this out so we can make it much better, please do and keep us posted. Please, for the time being, don’t post this into bugs though. I’m aware of the issues LDAP plugin currently has which is kind of why the work has been started to make it into a truly usable plugin.

You’re absolutely correct. It’s chinese if it’s any help. It is not set until you set it, though I’m pretty sure I’ve made sure it defaults (now) to English.