After working with @Sebastian-Roth we discovered it was the latest init files that were causing my problem. I was able to copy the init files from a backup folder and all is working correctly. I am going to test the other backup builds to see where the error starts. I will post back here with what I find.

When I did mine, I just copied the images into the new images folder on your server. Make the permissions are all set 777 on the folder. Then when you add an image through your FOG interface, make sure the name is exactly the same is the image name. I know there is a forum post on this. I’ll see if I can find it.

@Tom-Elliott Dude, your so the man!! thanks so much. Just had the same issue…

@Wayne-Workman oh crap. lol my bad. checking now.

Don’t get frustrated. We all have to start somewhere. I think you’re doing a great job. The group here is super nice and knowledgeable. I would say just do it. Load a Virtual box, Load a server, load FOG and break it. Then fix it, then start over. lol. I know this sounds crazy but you can learn so much by just doing this. With the help of this group and a little diligence, you will be kicking FOG but in no time. Keep it up!!

I should do a better job of explaining things. I just reread what i put and it was pretty vague. TY @Wayne-Workman for being much better at this than me.

Have you looked at your compression. Fog 1.2 sets it default to level 9. I had the same issue after upgrading. Look under Fog configuration---->Fog Boot settings—>FOG_PIGZ_COMP. I bet it’s set to 9. Set it to 4 or 5. I run mine at 4 and all works great. Good upload and Download times. You can also set that config on the actually image management of the image itself. Hope this helps.

I have that setup here. Basically you just install your two NIC adapters. I have one setup for DHCP and hooked to the outside line. The other i assigned a static IP address and use it for my FOG server and run it into a image switch. I use just the one gateway from my DHCP so that i can access the Internet on the server adapter. The biggest thing for me was that when i was setting up the server, to make sure i assigned the correct interface name when installing the FOG server. In my Linux setup is wasn’t just ETH0 or eth1. It was a totally different net name. So make sure you use IFCONFIG to see what your interfaces are. If your using Linux that is.

If your running Ubuntu you should have some type of file editor installed already. I would assume that it has that loaded.

When you open your terminal you will be a local prompt, if your paths arent set you will not be able to access the file directly.

you will need to

cd /
cd etc
cd network
sudo vi interfaces

It will bring up the file in the VI text editor. Hit the insert key and then arrow down to the last line and enter

FOG Server IP (This is just a remark to remember what your doing)

auto (the name of the NIC you are using. You can use IFCONFIG to view the NICS in the machine) in my case its
auto p4p1
iface p4p1 inet static
address (your server address)
netmask(Your server netmask)
gateway(Your server gateway)

It should be some form of this. Hope this helps.

I have no clue exactly what happened. It got to that second partition upload and it just gave an error like , not a valid NTFS. I use gparted live to make all the partitions, all ntfs. I’m just going to have to start over and rebuild. Once i get it built this time, I will do a HD Clone on an external Duplicator just to be safe,.

Dell Precision 3430 btw.

Morning all. I have an issue that after the deployment of my image to a machine, it looks like it breaks the bcd boot stuff. Here is what I’m having to do to fix it.

bcdboot D:\windows /s Z: /f ALL.

So like it breaks the boot files maybe? Don’t get a FOG error per say. I thought maybe someone had seen this. Thanks so much.

Just wanting to make sure that the working branch fully supports the UEFI boot. I know that the older versions did not. I was spinning up a new instance of the server real quick to get a couple things imaged.

Ubuntu Linux BTW.

Morning Guys!!

Just wondering if the the latest versions of FOG support this and if so do we have a setup walk through for this?

Thanks in advance!!

Seems like all of a sudden all the fonts and headers and such are all off. Just me?

@george1421 synology would be a better option for sure. I’ll get right on it. Thanks so much.

@george1421 That’s beautiful sir. Can you link that. I want the DROBO to be the main /image location.

I don’t think so. I’m trying to look now.

Server

• FOG Version: 1.5.0-RC-2 6079
• OS: Ubuntu 16.04 Server

Client

• Service Version:
• OS:

Description

I am attempting to create storage node on a NAS and make that the default image storage. Since starting this, I have found that the DROBO can be a little interesting to get setup. Things I had to install on the Drobo to get started:

GIT
SUDO
BASH
OPENSSH

I have all these installed and running and can putty to the unit. I got the FOG install file 1.4.4 on the unit and was able to get the install to run. (This is where I’m stuck.)

I get through all the options in the sh and start the install and this is what I get.

Any Thoughts?