This is untested… But well, what can go wrong?! What do you think about adding the same thing to the registration script if things fail?

Old thread - new news.

Had this error show up when uploading from an EliteBook 8730w with Win10 on it.

While I was digging up the commands in the wiki to fix it, when the laptop rebooted on it’s own (due to error), it began uploading!

How strange?

@Tom-Elliott

Thanks Tom, I figured that might be the case I just wanted to double check.

Probably not a huge priority, but would it be worth adding something to the install script that checks to see if any schema changes are needed, and if not the step about going to the URL to update it is skipped? Or at the very least, add a notice to the step that confirms that going to the URL and not seeing a schema update page is by design if there are no updates, and that you can just continue on with the installer.

I think I can make this tool into a plugin… just a thought…

Ok, together with Jbob I seem to have figured out a working set of libraries (SharpPcap and PacketDotNet) and C# code to send and receive the packets we want. Hopefully we’ll have the first alpha version of a tool ready soon!

OK, after upgrading kingston SSD firmware, changing SATA cable and port, everything seems fine 😉
Thanks !
Matthieu

It’s great that it’s done, but simply directly updating would work too. Backups are always recommended, but such complex steps are not necessary.

@VincentJ So this kinda died.

I was so busy this week… it’s just madness at work and I’ve been spending every spare second I have trying to rebuild my win 7 SOE with a new way to manage drivers (I’m going to make a new thread for win 7 deployment, or maybe update my old one, and maybe a win 10 guide too).

Anyway I’m not really sure what the upshot of this thread was. But I will make a virtual appliance, at some stage. Honestly work is just so busy and shows no signs of slowing up… we have to replace our entire core and edge network (which is huge) plus new core server infrastructure at two main sites all this year… on top of just trying to keep everything running and setting up new businesses everywhere…

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!

@ITCC Are those the absolute-exact logs on your system? If not, please post your logs.

@Wayne-Workman

Ubuntu 14.04

| version_compile_os | debian-linux-gnu | | wait_timeout | 28800

@Jbob Thanks for your detailed answer. I agree that string filtering the MACs on the client is not wise! Shouldn’t do that. Detecting physical devices only sounds like a way better approach. See what you can do if you find the time and let me know if I can give you a hand.

@Sebastian-Roth
this is quite a challenge ahaha I don’t have enough knowledge in lvm management but I can take a look at it definitely 😉

Anyway thank you for your time and effort.

@Wayne-Workman YUP.

@Sebastian-Roth said:

Removed from wiki as I don’t feel like anyone really cares about running FOG on a Mac OS X server…

And I feel free and open work should be run on a free and open operating system. Just my thoughts on the matter.

@Junkhacker What if a regular image was decompressed & then mounted on the FOG server, and then it’s raw data sent out via a torrent task ?

I still think that sticking the standard partition data at the end of the drive is perfectly acceptable. Torrent task type is made to overcome network issues, not HDD issues.

@Wayne-Workman
Yes, after open all ports, it works

@Tom-Elliott This could be needed for security purposes. A wipe will make sure the entire disk is over written before putting down an image. With just re-writing the image you can’t ensure that forensic tools won’t be able to recover old files. I can see what he is asking for, maybe if there was a way to modify the download task to do a normal or full wipe then download to give assurance that all data has been over written at least once. This should be able to be accomplished a couple of ways, either one have the fog inits run a normal wipe then run the download, or possibly with the a hooks you could have it auto create a deploy after the wipe finishes so when the client reboots it will pull the image automatically.