@brian-david said in [1.5.0-RC-10] Access to tmp folder denied:

I did in fact initially run these FOG snapins before installing any anti-virus

Was those successful?

@sudburr said in HP ProBook x360 11 G1 EE Notebook PC succeeds but fails at exit:

Manually selected tasks from FOG menu succeed but then fail to exit properly

Have you tried every exit type individually in the UEFI exit modes?

In the past I have had this issue when using certain anti-virus programs, but we now have exemptions in place for FOG. I adjusted the permissions on this folder to be open to everyone, but that did not change anything (and then I set the permissions back)

@brian-david That sounds like guesswork and like you’re not sure where the problem is. The way to troubleshoot this is like any other problem, you eliminate variables. Just uninstall antivirus from the machine and reboot to entirely eliminate the the AV variable. See if it works afterwards.

@redbob Typically that message is only given when you try to access the GUI on a storage node. Did you do a full server install or a storage node install? Make sure you do the right installation. It’s OK to re-run the installer to do the correct installation.

@fpausp said in Can FOG replace my urbackup Server ?:

I just would like to know if FOG can replace my urbackup Server ?

No. One’s a utility for backing up files, and the other’s for deploying operating systems. Two very different things.

@mwarner What version of FOG is this?

@sourceminer Most likely you overwrote the Betor10 image via a capture of Windows10Base without changing the assigned image of the machine you were capturing from.

@themcv I promise the steps to move the cert over work correctly. I’ve done it like 3 times myself.

Latest stable release as of November 21st, 2017 is FOG 1.4.4. Official announcement here: https://news.fogproject.org/fog-1-4-4-officially-released/

@fredlwal I would first recommend moving to the latest release - which is 1.4.4. There’s lots of bug fixes in every release, and you are way behind. the 1.4 RCs were very buggy. This issue might go away entirely if you update to 1.4.4

If you need help with updating FOG to 1.4.4, just ask for help here.

Also, if you want to help the mature 1.5.0 RC, we would be happy to help. 1.5.0 is just about ready for release, we just need more people to try it out. We can instruct you on how to upgrade to it.

I’ve not done any more work on this. The best solution is still to have permanent tunnels from site to site via a routing appliance like a Cisco router or checkpoint router or PFSense router or some other router solution.

@tom-elliott It was for reference so you wouldn’t have to look it up yourself…

Register the computer with the fog server - do a full registration. This is done from the FOG Boot menu on the computer when you boot to the network. Then after it’s registered, you’d use the FOG web interface to create a new image, assign that image to your computer, then start the capture.

@fredlwal Screenshot please - and FOG Version.

Moved to bugs, and pinging @Tom-Elliott to take a look and see what he thinks. Tom, here’s his previous thread concerning this: https://forums.fogproject.org/topic/10358/debian-9-0-capture-fails-and-destroys-client-image

@sabotage Put a small server at each site. The hardware can be your choosing. You could use small and low-end servers if you have the money, or you could use old desktops for it. Up to you. Then setup your main FOG Server at HQ, and install all the site’s boxes as fog storage nodes. The storage-node installation process allows you to attach it to a main fog server. Then setup the location plugin and configure all your locations. We have documentation for this in our wiki. But…

For now - you really should just setup a test FOG Server at your HQ and just try things out. Generally, newbies of FOG have lots of questions about basic stuff.

Sounds fine, you’re in charge of your stuff. We just try to help you do what you want to do as we are able and give our opinions or advice.

@george1421 said in Boot Windows or Linux with FOG?:

As for licensing, fog doesn’t manage licensing at all.

FOG does manage licensing - there is the Windows Key plugin that does this. Screenshots are below. Also, keys can be assigned to hosts via groups and not just one by one. However - FOG doesn’t know what kind of keys you use, it doesn’t care. You must be responsible and comply with the terms of your license keys.

@george1421 said in FOG thinks all servers are a single host.:

What I find strange is why all of your target computers have the same mac address? How is this possible?

Exactly what I was thinking - I really don’t think this is physically possible within this universe.

@mron said in Boot Windows or Linux with FOG?:

Is setting up dual boot so far out of the norm that I shouldn’t try it starting with so little experience?

Just dual boot is pretty trivial. Dual boot being captured and deployed properly with FOG isn’t really supported - it’s never worked right in the past for people and I would not recommend trying it.

To solve the problem of having Windows or Linux available quickly in your lab of 20 machines though, FOG can probably image those in a half hour if you had a half-decent gig switch to do it on.