Topics created by fry_p

Marking this as solved.

The spikes aren’t that big (50Mbps). These are most likely clients that are booting up and are passing through network boot first, the spikes are them pulling the boot ROM from the fog server.

@Sebastian-Roth

That’s kind of odd from my point of view as the tools used to do the actual up- and download (udp-sender for multicast download and NFS for upload and unicast download) haven’t changed much in a while!

we’ve made changes to how compression/decompression is handled to better utilize the processing power available

@Jbob Thanks a million! Now I sat down and made the described changes from the wiki and it works flawlessly.

@Wayne-Workman I am not in the business to hack FOG either. But as I work in healthcare and we are a small shop one of my many hats is security, with PHI concerns I think about all possible attack surfaces. We have regular audits of our security and have to justify any thing that is of questionable nature. Right now I am working on closing up a few other areas, and I have been thinking of ways to harden software deployment through snapins. Currently we have a separate vlan for FOG and only deploy snapins at time of imaging, then remove the log and use the client just for user tracking and rebooting basically. I will push small single file snapins, if I need to, but nothing that needs to connect to a share due to not having a good way to do so. I love FOG and it works great, just like to include my thoughts on things to help further FOG and keep it as secure as possible along the way.

FOG 2.0 will be a huge advancement again I am sure. Just like 1.3 is truly leaps and bounds better than .3x was. I thought .3x was great, but the issues were definitely addressed. With all software there is always compromises to maintain backwards compatibility for longer than any @Developers would really want to do. In my opinion 1.3 is not just a decimal increment to 1.2, it is much closer to a 2.0 version. But with the true 2.0 they can finally drop support for the legacy client, partimage, and it sounds like move away from PHP. It will definitely be a more robust and modern system.

The message “Object not set to instance of Object” means that you are trying to use an object which has not been initialized. That is, you either set it to null, or you never set it to anything at all. The runtime throwing a NullReferenceException always means the same thing: you are trying to use a reference. The reference is not initialized (or it was initialized, but is no longer initialized).

Antonio

@Jbob Luckily (not best practice) 95% of our PC’s use the legacy client as part of our old images (recently moved to trunk). We have a handful of test machines that the new client is on for building new images. We also tested that if you don’t uncheck the option to put fog.log at the root of the 😄 drive, everything is ok. Thanks for your help!

@Tom-Elliott @ch3i I changed it to my password. Thanks, I was thinking there was something like that, just didn’t know where.

Thanks!

@Tom-Elliott Just tested it and its working fine again now. Thanks!

Thank you, I updated and the client is back. However, I am still unable to get the service working due to that same “invalid host certificate error”. I will start a new thread for that.

Ah OK, I wasn’t aware of that function. Thank you for your prompt reply. I will give this a try tomorrow!

Ah thank you! Also, yes I realize I am on the bleeding edge of FOG and I do expect bugs. Been on Trunk for 2 weeks, flawless so far.

Thanks!