Just a quick status update (and closure).

To answer Wolfbane8653: yes, it was possible. Everything worked.

I got everything working on the day that FOG released version 1.0.1
I think I was still high of the sweet victory, when I (later that same day) decided to ditch 0.32 and go for version 1.0.1
So I got version 0.32 to work and it was fully tested, but it has never been used.

Instead I deployed version 1.0.1 and started from scratch again (I didn’t have any other option because the update messed up the whole system).
I ran into some new problems, but fortunatly the error messages in 1.0.1 are a little bit more detailed so I could fix everything. Since yesterday our new (international) FOG environment is ready to deploy. For those interested I will give a summary of our FOG configuration.

Thank you all for your support. I will try to keep in touch on this forum, and don’t forget to have fun with FOG!

Our company FOG setup:

General network: we have multiple locations (in Belgium and The Netherlands) we are all connected in one big network.
Thanks to FOG we are now able to auto-install any computer on our network, no matter where they are.

Location: Antwerp. This is our main site. The (one and only) FOG server is hosted here and the PXE boot-service comes from that server. This is a virtual ubuntu 12.10 that runs on VMWare. We also have a Windows 2008 server located here that functions as a storage node. The reason behind this is because of the backup. Backups are made on tape and our tapedrives / software are not supported in Linux.

Location: Schiphol. This is one of our two main sites in The Netherlands. A Windows 2008 server functions as a storage node. It is equiped with a tapedrive and makes a weekly backup.

Location: Amsterdam. This is the second main site in The Netherlands and has not yet been configured. This will probably become a virtual windows 2008 server, with backup possibilities on tape.

I’ve found the solution!

I followed the procedure at this site: [url]http://virtuallyhyper.com/2012/06/configure-windows-2008-nfs-share-vmware-esx/[/url]
and now everything works.

Well, I can’t create or change anything in the mounted folder.
So it seems I’m struggling with a security/sharing/permission setting.

I’m off to find some more information about NFS and sharing issues between Linux & Windows.

Hi,

I have those security in place, but that didn’t solve the problem
At this moment I’m stuck at the following stage:

• Checking Mounted File System … Done
• Using image blablabla
• Looking for Hard Disks …Done
• Using Hard Disk : /dev/sda
• Preparing bakcup location …Done
  #####################################

An error has been detected!

#####################################

Unable to create /images/001aa0…

Thank you very much for the tip.

I’ve compared our settings against yours and it helped. Anonymous login was not configured on the server.

Unfortunately, another error has popped up: unable to create /images/MAC-address.
Also, I’ve discovered that I’m not able to write anything from the Linux server to the Windows server via NFS. “Permission denied” shows up every time, so I’ll probably have to look into that a little bit further.

Another difference in our settings was kerberos. We don’t have any mentioning of that on our server. Is that necessary?

Hi everyone,

I’m finally turning to this forum for a solution because I’m all out of ideas. I will try to give you as much information as possible, but don’t hesitate to contact me for more information. Please keep in mind that I’m a newbie in Linux.

The Setup:

I have a Ubuntu 12.10 machine with FOG 0.32 installed on it. Everything works fine: computers can boot through PXE and can register themselves in FOG.
The image storage is located on a Windows 2008 R2 machine. NFS Server is enabled (took me a few days to find out that was a requirement). The folder on the server is shared (with Services for NFS Sharing) as “10.0.0.72:/Belgium”. Anonymous access is allowed and all machines have Read-Write access (ANSI encoding), also root access is allowed.

The Problem:

When trying to upload an image to the server I get the following messages:

• Preparing to send image file to server.
• Mounting File System … Done
• Checking Mounted File System …
  ############################################

An error has been detected !

############################################

Fatal Error: Failed to mount NFS Volume.

##############################################

Information:

/etc/export contains:
/images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure)

On the windows 2008 machine:
there is .mntcheck file in the root directory of the share and one in the “dev” directory. I’ve also created a subdirectory called images, with .mntcheck files and “dev” subdirectory.

The FOG configuration:
There is only 1 storage node and it has 10.0.0.72 as ip address and /Belgium/ as Image location. It is enabled and is a Master node. It is also assigned to the default storage group.
There is an image assigned to the host and it is also in the correct group.

On the FOG Dashboard:
I can’t pull any information about the storage node’s disk information.

The Big Question:

What’s happening here? I assume it’s some kind of a rights problem, but I have almost no knowledge of NFS and security.

Problem is solved!

I have updated the kernel (Other Information - Kernel Updates - 3.8.8 Core) and reverted the settings in /etc/exports and now the image is running …

Thnx very much for the advice!

Just made the adjustments, but still no luck…

Ok, I’m not sure on how to gather all the information you need, so I’ve included some screenshots on how far the systems starts. At this moment we have turned back the settings for the hard-drive. So we are back at error #2.

We are still using the kernel that was included in the default installation. I assume there is a way to update that kernel to a new version?

[url=“/_imported_xf_attachments/0/524_WP_20140129_006[1].jpg?:”]WP_20140129_006[1].jpg[/url][url=“/_imported_xf_attachments/0/525_WP_20140129_004[1].jpg?:”]WP_20140129_004[1].jpg[/url]

Hi guys,

First of all, the problems exist before FOG starts to pull the image from the computer. (Since this is our first device of that type, we’ll need to upload a working image first).

@ Tom:
Currently we are using FOG 0.32 on a Ubuntu 12.04 server (32-bit). Is it possible to upgrade Ubuntu without having to reinstall the whole thing again? And will that have an impact on the drivers during the PXE boot?

Hello,

today I was trying to take an image from a new DELL E6440 laptop, but somehow it wasn’t able to start up fog.
I ran into all kind of problems and I seem to be stuck …

First problem: There was an error caused by the USB 3.0 chipset, which caused the system to stop. After disabling the chipset in the BIOS, the system continued to boot.

Second problem: There was an error while mounting the hard drive. Returned to the BIOS and selected another Drive emulation (changed it to ATA instead of e-raid). The system continued to boot …

Third (and last) problem: the system now halts on an error concerning the LAN-drivers. Apparantly it can not load the correct drivers for the network card thus stopping the startup.

Does anyone have an idea on how to solve this? My company won’t like it if I have to disable all the new features in the BIOS in order for the imaging to work. Enabling them afterwards is not an option, because FOG allows us to let users connect their own devices and we can control them from abroad. If we have to change the BIOS before and after every installation, the advantages of FOG will disappear.

wkr,

David Van Uffelen