From where to where did you update?? Version 1.2.0 to current SVN? I did that lately and thought that FOG had deleted my files but it just moved them (to /tftpboot.prev and /var/www/fog.prev if I remember right)…

Just throwing this out there check the AD user make sure its not locked and try to login manually and see if you can join the domain with that user manually.

You know of a better way to ensure the proper files are sent at the right time?

[quote=“Jaymes Driver, post: 41711, member: 3582”]I also vote for staying on 12.04.

When you ran your svn commands to download the svn, did you do so with sudo?

you may not have write access to the folder if you ran it as sudo.[/quote]

… lol… figured that one out right before I saw your reply!

…reminds me of a bad joke!

Guy: Make me a sandwich
Wife: Make it yourself!
Guy: sudo make me a sandwich
Wife: Ok.
😄

I’ve noticed the same thing, Ben

🆒
cheers

I have not, but I’m constantly (as you can guess) on SVN so if there was some issue, I would have likely corrected on spot. That said, I don’t recall this being an issue. Thats not to say there isn’t one.

[quote=“Dallas Caudell, post: 41659, member: 28406”]I’ve been using FOG for a while no with no issues. We recently received new machines we will be using for now on. I have no idea why, but these machines will boot to the menu, but when it attempts to mount file system it fails. I get an error: RPC: Remote system error - Network is unreachable
mount: mounting 192.168.0.100:/images on /images failed: Bad file descriptor
Error during failure notification:

Then it just slowly moves up the screen. When I try to quick register, it does something similar without the mounting error, but it just sits there slowly moving up the screen while not gathering any information.

It’s with this specific machine only, so I’m stumped.

Any idea? I know the error is pretty vague, I’ve been googling for hours and I can’t find anything. I’m wondering if it’s a bios setting, as these are new machines with an updated bios with way more options.[/quote]

What OS are you running? From the information I’m gathering it’s a Redhat Based distribution.

Make sure rpcbind is running before nfs.

[code]chkconfig rpcbind on;
service rpcbind start;
chkconfig nfs on;
service nfs start;[/code]

Thank you for the answer!

The change was quite resent so if you did put in the key using 2922 then yes there maybe an issue when updating to 2966.

[quote=“Tom Elliott, post: 41564, member: 7271”]Details, details, and more details all lacking.

First, Multi Part image (single or all disk) will attempt to capture the partition as is, not bit by bit, but from the structure of the partition table it will require a disk at least the same size or larger to image back.

Second, what version of FOG did you install? Latest is not an answer, be specific. If you installed SVN Trunk FOG what revision are you at? (in the cloud lies the version number for current versions of fog).[/quote]

Thanks for the speedy reply. I have figured it out by searching the forum and finding this [quote]

Download Fixparts for Windows from here:

[url]http://www.rodsbooks.com/fixparts/[/url] (look for the link “download page”)

Unzip the file and execute it with administration privileges. A command window will now pop up.

Type in “0:” (this command is just for Windows!) to define your first (and in my case only) HDD to be the one to analyse.

Now the tool suggests to delete the GPT signatures and asks you to confirm. If you want to use Linux as well as Windows on your disk you probably should not delete those signatures. But in my case I only want to use Windows, so I say yes.

After that exit the tool by typing “w” (write changes to disk and quit). Restart your computer to check if it still works.

Sysprep the OS and upload the image to FOG.[/quote]

Hi all,

I finish my labo With Windows storage node with few problems of permission at first. Like the need to grant permission to create and delete files and [COLOR=#ff0000]DIRECTORY[/COLOR] on the ftp user (user filezilla).
At the end of the capture task, FOG needs to rename the image file. Then, if my storage path is:
c:\images
c:\images\ dev
With filezilla, I must create a user by giving all rights to c:\ , c:\images, and c:\images\dev to complete my lab.

Should I do the same thing for the user that I created on the NAS? because when I create, on the NAS, a user with RW on my share “images”, it’s not allow me to capture or deploy an image. I am forced to use the administrator account of my NAS to make this happen. So like with Filezilla, in my NAS the ftp user must have full access to the root ? (and i did not see this option in QNAP)

Thanks in advance 😄

The changes Tom made corrected the issue. Thanks again!

Fixed Tom teamviewered in and edited the database to remove the orphaned task. Side note if you have existing snapins remember to add them to a storage group before attempting to update them.

Thank you, you guys are awesome and are doing a fantastic job.

[quote=“AllenP, post: 41471, member: 24073”]I don’t know if you found a solution to this but after goggling the problem for days and days. I thought to myself what could have changed between .32 and 1.2. So I looked at the boot setting in the DHCP server and saw that the file name had changed from .32 to 1.2 so make sure you check DHCP settings edit option 067. I really hope this helps someone else bc it drove me nuts. I wish that someone would big red flags and fireworks going off anything to draw more attention to the change in the file name.
[FONT=Ubuntu][COLOR=#444444][SIZE=14px]Open up the scope of your DHCP server and edit these settings:[/SIZE][/COLOR][/FONT]
[LIST]
[]Edit option 066 and enter the IP address of your FOG server.
[]Edit option 067 and put a string value of[COLOR=#ff0000] undionly.kpxe[/COLOR] or undionly.kpxe.INTEL
[/LIST]
[/quote]

Part of the installation script that tells you that you need to update your DHCP Scope.

I believe the secure boot is causing the issue I disabled it in bios but dose not seem to be actually disabling it.
These are also blocking my linux usb boots such as gparted and linux mint

I got on Hangouts with Tom last night and we figured it out. Fixed in 2944.