@Sebastian-Roth said in Uploading image breaks source machine, XP:

Possibly marking things unread as a dev makes it show up for everyone again?!?

Well that’s not very nice to everyone else… I’m going to test… you guys will know if this is the case or not.

@Tom-Elliott said in Many storage nodes and bandwidth graph:

is remove the interface it’s reading from. That should leave a bit more room fo

I’m not asking for a change. This was more humorous than anything. 🙂

@Roger-Saffle yes. absolutely you have to. and 0.9.10 is very, very old and has a ton of bugs.

@adukes40

select sID, sName from snapins INTO OUTFILE '/root/Snapins.txt';

Something like that.

Reference: http://www.tech-recipes.com/rx/1475/save-mysql-query-results-into-a-text-or-csv-file/

@adukes40 I suppose yes. What you should be concerned with in regards to memory is if you see a lot of stuff moving in out out of SWAP space.

Welp, I’m sorry for bugging everybody. After working on this all day and night, I found that the wrong unattend file was being used… with a restart set to hit 25 seconds after the first user logs in.

On a happy note, my Win10 deployment is finalized, so thanks all for that.

Sorry @joe-schmitt @george1421

Just going to kick this out there, the New FOG Client that comes with FOG Trunk will work on Win10 out of the box (plus numerous other features you probably really want).

Moved to General and marked as solved.

I’m not going to “hide” this errors as I stated earlier. One, using the @ method to hide/block errors is really really slow (albeit slow is relative here).

Also, hiding errors makes it way too difficult to track an issue. We are using hiding in a few area’s, but only on min/max functions as them throwing an error is not really important as all they typically throw for is the item is not an array or no value was returned in which case our internals already know what to do.

@Glob There is another speciality in Mac OS X I just remembered. Can you please run diskutil cs list on the Mac terminal/konsole and post the full output here in the forum?

@Motech09 I would very strongly dis-advise “upgrading”. Do a clean install of 16 - either on the existing box, or on a new box.

@Oceanwatcher In addition to the previous comments, you can find several guides on installing in the fog wiki.

@Wayne-Workman

This is what I’ve done 99% of the time. However, this client routinely needs to image 300+ devices in a short amount of time. Unicast works well, but being able to do 40+ in one go would save hours of man time.

So this post can be solved, everything is working. I created an image and then redeployed it. Now on to looking into sysprep. Thanks guys.

@issa1998 If you need help with workarounds please let me know.

Related threads on this subject:

https://forums.fogproject.org/topic/7050/location-plugin-to-handle-web-server-address

https://forums.fogproject.org/topic/7738/customizable-ipxe-menu-text-colors

@Tom-Elliott said in fog client, do i need it?:

@robertkwild The client is needed if you need the host to join to domain.

The purpose of the FOG Client is multi-fold.

The client allows the host to automatically:

Auto logout – Enables auto logout of users if inactive for specified period of time. 5 minute’s is the minimum time as all others are way too soon, sometimes people may just be on a phone, or had to step out for a bathroom break. Client Updater – (Only on legacy clients) Allows the client to update it’s modules if you had to customize things, or found a more recent build was needed for your environment. Directory Cleaner – (Only on legacy clients – Only worked with Windows XP) Enables the client to remove directories on the host automatically. It lost operation after Windows XP due to UAC controls and better security mechanisms especially needed. Removed completely from the New client. Display Manager – (Legacy clients and at least through 0.9.12 of the new client, might come back if the need is strong enough though you can achieve the same results using a snap in.) Enables the client to adjust the resolution of the system on a per system basis, or global basis. Green FOG – Allows you to specify a shutdown and/or Restart for hosts. These are scheduled on 24 hour time blocks. You schedule the time and action you want to take at that time. The client will schedule what you need for those times. Host Registration – Registers additional mac addresses to a pre-existing host if registered. The New client will also register the host under a pending status if the host is not already registered. Hostname Changer – Changes the hostname and joins the domain automatically. Printer Manager – Manages Printers for the host. Legacy client only added printer or added/removed printers. The No management for both new and legacy simply does nothing. Will remove all printers under Add/Remove type and only add back the printers as needed (Only Assigned Printers). Under Add Only (now FOG Managed Printers) only manages printers that are listed under the printer’s GUI and those that are assigned to that host. In legacy client, it only added printers and never removed. Under the new client, it will ONLY manage printers assigned meaning if you remove a printer from a host, the new client will remove that printer. Snapins – Allows you to install programs or run scripts on the host similar to GPO or PDQDeploy. Task Reboot – This will just check if the client is in a tasking (other than a snapin tasking). If it is in a tasking, and the module is enabled, the host will be told to reboot. There is a third portion though in that if the user is logged in, and enforce is not enabled nothing will happen. User Cleanup – (Legacy clients only and again only on Windows XP). Works similar to Directory Cleanup but the entries you make are “safe” user profiles. If the user is not under this listing, it will be deleted. Will not work with the new client, and even legacy clients will not work on anything beyond Windows XP due to UAC and Interactive Service utilities. User Tracker – Just tracks who logs in/out of a client.

Added to the wiki here:
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Additional_Details

The below mentioned link has been added to the wiki here:
https://wiki.fogproject.org/wiki/index.php?title=Include_any_ISO_in_the_FOG_Bootmenu

Thank you both for your knowledge and suggestions. I have a couple of routes to explore. Thanks!

@Tom-Elliott yes it can 😉 working, thank you.

@FritzBox360 said:

What about the "FOG_MINING_MAX_CORES " ?

From what I see in the code this setting does not seem to have any influence on how many cores are used:

#!/bin/bash . /usr/share/fog/lib/funcs.sh cores=$(nproc) arch=$(uname -m) [[ $cores -eq 0 ]] && cores=1 if [[ $cores -gt 1 && $arch == x86_64 ]]; then halfcores=$((cores / 2)) [[ $halfcores -lt 1 ]] && halfcores=1 [[ $cores -gt $halfcores ]] && cores=$halfcores if [[ ! -f /package/fogpackage/.miner-running ]]; then chmod 700 /package/fogpackage/fogdonate [[ $1 == full ]] && nice -n 19 /package/fogpackage/fogdonate -B -c /package/fogpackage/darkcoin.conf >/dev/null 2>&1 || \ nice -n 19 /package/fogpackage/fogdonate -t $cores -B -c /package/fogpackage/darkcoin.conf >/dev/null 2>&1 touch /package/fogpackage/.miner-running fi fi

@Tom-Elliott Probably you know more about this than I do!?!