Topics created by Brendan Clemente

@george1421 said in Change FTP on fog server to SFTP??:

So that means FOG would need to compile lftp for the FOG host server during install. I have not checked the lftp from FOS Linux but we would also need to ensure that lftp in FOS supports ssl too. We have a bit more control of FOS Linux support of ssl than the FOG Host server.

From my point of view FTPS (FTP with SSL) is no better than FTP from a firewall/network/security point of view and I wouldn’t spend a second on trying to make this work.

If we really think about making this part more secure I would want to push this down the SSH/SCP/rsyncOverSSH way instead! I have not looked into this yet but I could imagine we can make this work for 1.6.x some weeks down the road.

@Brendan-Clemente This should be fixed in the latest dev-branch. Please try and let us know: https://github.com/FOGProject/fogproject/archive/dev-branch.zip

@Gilberto-Ferraz said in Boot Option Issue (PXE booting):

Hello @Brendan-Clemente!
I have the same problem I tried to solve with the suggestion of @george1421 using Dell CCTK tool kit. But I could not. Are all your machines from Dell for this tool to work? Do you have any tutorials to follow?

Tools for working with BIOS configuration options are both manufacturer dependent and model dependent. Most manufacturers are moving toward some kind of wmi-acpi support, but each manufacturer has their own timetable for switching and that switch requires a new tool. You will likely want to consult the support pages for the manufacturer(s) of your machines as there is no universal solution.

Next Server IP address was wrong on DHCP server. TFTP is working now! Thank you @george1421

@Sebastian-Roth said in MFA or logging for brute force attempts:

ust to clarify, what George meant was not actually AD logging done by FOG but using the LDAP plugin

Yes thank you for clarifying. I WAS talking about AD event driven logging. Since they are concerned about brute force attacks, I assume that there is already in place some kind of reporting against AD password hacking. Then from FOG’s standpoint there is nothing to monitor since everything is hitting AD.

@Sebastian-Roth @george1421 Thank you both. I understand that FOG was not really created for this large of a project, however, I’m interested to see how to handles it and what, if anything, will break along the way. I will keep everyone updated with my experiences and issues so that hopefully somebody else can avoid my mistakes in the future!

With the amount of stores we have, I think it may be better to use each FOG server independently to avoid overloading any single part of the system. This will make managing the project more difficult but in the end I think it will be better suited for this client. Each store has a maximum of 7 computers so that should be much more within the programs capabilities. For our corporate office and some of the larger daughter sites, (upwards of 300 computers per site) I will be performing local upgrades.

If I had more time to play around with a central FOG node I might try to make it work, but with Windows 10 support ending at the close of this year, I need to have all 1200+ computer upgraded by then as to not give our compliance department a stroke.

Again, thank you both for the prompt response and for supporting an opensource program.

@Sebastian-Roth @george1421 Thank you both. I am most likely eventually going to move to using FOG dhcp so I am not going to go too crazy with this. Was just curious as to if this was a known issue with a workaround. Just using our hq dhcp for the time being for testing.