No idea, haven’t used Windows in a year.

@zfeng said in How to do remote management:

How can that be possible if they are not under the same network?

Fog of course needs a network path to the target.
Beyond that, you can make things more efficient with storage nodes, which are sort of like remote fog slave servers under the control of the master server - they hold images so that you don’t have to image across a WAN. Also there is the FOG Client which allows for OS level management of all the workstations you’re managing.

Look at these wiki articles for some insight:

• https://wiki.fogproject.org/wiki/index.php?title=Location_Plugin
• https://wiki.fogproject.org/wiki/index.php?title=Managing_FOG#Storage_Management
• https://wiki.fogproject.org/wiki/index.php?title=FOG_Client
• https://wiki.fogproject.org/wiki/index.php?title=Snapin_Examples
• https://wiki.fogproject.org/wiki/index.php?title=SnapinPacks

@JGwinner Please create a new thread with all the details of your problem.

Posting this as just informational. Seems to be some sort of problem with installing on Arch.

It seems to be the caused by a change in Arch Linux, not FOG, as installation of three different FOG branches are failing all on the same day today. I’ll keep an eye on it, and see if the same thing happens again tomorrow before I invest time into looking at it.

@developers @moderators I was able to get the daily installation tests to test upgrading from FOG 1.5.5. Mostly this is going good, but 1.5.5 didn’t install correctly on Fedora 30 or RHEL7. Those two are totally jacked, but everything else seems to be working right.

I need to write some new scripts to make the setup more easy though.

@Sebastian-Roth said in FOG install overwrites /etc/exports with no warning:

Upgrade install with a clean /etc/exports file: either we use checksum or regex to make sure it is not modified and move the file to /etc/exports.d/fog.exports (and maybe create an empty /etc/exports)

Just check if it exists.

if [[ ! -f "/etc/exports.d/fog.exports" ]]; then 
    echo "do stuff"
fi

I’d suggest asking the user to confirm the actions to be taken, with a default answer of “y”.
Maybe something like “it’s detected that fog configuration exists in /etc/exports. Would you like the installer to move this to the new location for you?”

Just kicking around ideas…

@george1421 said in FOG install overwrites /etc/exports with no warning:

Questions: what happens if we have 2 exports.d file that contains the same fsid? Will that break something?

In what scenarios do you see having two?

@EduardoTSeoane It sounds like you’re using groups to deploy several snapins at once? If that’s the case, as a work-around, I might suggest deploying 1 snapin at a time with groups. That way they happen in the order needed. Not optimal, I know.

@EduardoTSeoane I think snapins have always executed in alpha-numeric order.

@george1421 said in Change the boot order automatically:

But we do it this way to make sure we don’t reimage the CFOs computer by accident (again) if everything was automatic.

That must have been a bad day.