Posts made by Wayne Workman

@stiger Look at this post:

https://forum.acronis.com/forum/acronis-true-image-home-forum-older-versions/pxe-boot-possible

I’m copy/pasting the important part in case the resource goes away:

After the installation of Acronis on your Desktop DON’T create an ISO.
Start a creation of an USB stick. Then on the USB Stick you’ll find the files
dat3.dat / dat2.dat.
The file dat3.dat ist the kernel.dat.
File dat2.dat ist the ramdisk.dat

So you could rename them and copy it to you’re tftp.
The menu should so look something like:

SAY 02 Acronis true Image 2010 Home
LABEL 02
kernel acronis/kernel.dat
append initrd=/acronis/ramdisk.dat vga=791 root=/dev/ram0 quiet

@stiger What’s dat10.dat and dat11.dat ? Those filenames don’t sound like a kernel and init to me. What is it you’re trying to boot through fog?

What George said. Also, new problem means new thread. I’m not going to work this new problem in this thread so please make another if you need help on that.

@redbob said in UEFI PXE boot from Windows 2003 DHCP:

it worked!

However as George said already, this is not a real solution. The network needs fixed.

@stiger What version of FOG?

@Tom-Elliott @eliaspereira Not only what Tom said, but looks like the path is more wrong than that. If you look in the kernel variables, you see this:

[Moderator Note] Edited the requested IP address -Geo
storage=192.168.1.150:/mnt/imagens/dev/

That’s surely wrong. On the FOG Server, the default images directory is just /images and not /mnt/imagens

@stiger We need to know all of the parameters you used to create the item, not just it’s title.

@eliaspereira Please update to 1.4.4 and see if the problem still exists. There are dozens upon dozens of bug fixes in every release, and you’re 4 releases behind. We don’t have the resources to support old versions.

@eliaspereira What version of FOG?

As well as: https://wiki.fogproject.org/wiki/index.php?title=Getting_FOG

@sunks if it happens again like this, come back and tell us, try to use this same thread.

@msi In other words, that node’s copy of the image was corrupt somehow so you deleted it, and replication re-replicated a good copy from the master node to the slave node.

@tim-reynolds said in Domain add error 2224:

“hostnamechanger unknown return code: 2224”

That’s not a fog client error, it’s a windows error (because the fog client often just passes any errors it hits along to you via the fog.log file). Knowing this, you can use Google to search for stuff like “Windows error 2224” And after having ran that search, you might find these things:

• https://msdn.microsoft.com/en-us/library/windows/desktop/aa370674(v=vs.85).aspx
• http://comphelp.org/guide/rename-computer-error-2224/

@msi What fixed it? Please provide details for the next person that comes to this thread for answers.

Each individual image can be set in Image Management. I forget where, but there is a place that is like hidden from view unless you enable a fog configuration setting I think.

Typical newbie mistake. I’ve done my best to spread this knowledge all over the wiki:
https://wiki.fogproject.org/wiki/index.php?title=Ubuntu_16.04_Server#Settings

set a username, recommended name is YOUR first name, or “admin”. Do not use “fog”!

And
https://wiki.fogproject.org/wiki/index.php?title=Password_Central#Local_.22fog.22_user

Please do not use the local “fog” user account on the server to do back-end work. Create another account and use that.

It’s other places too. I don’t know what it’s about but I think the force compels the human soul to set the local account name as fog

@susdtech said in New to Fog:

Do you need to pxe boot a desks top in order to capture or image a computer?

Yes. If that’s not possible for you, clonezilla would suite you better than FOG. FOG’s designed to remotely image thousands of systems and then configure all of those systems for you automatically. Clonezilla is doesn’t do that because it doesn’t scale, but Clonezilla is awesome at simply taking and putting images via USB.

Also, Is the client needed as well to complete this process?

No. But once you learn the power of the client, you’ll wonder how you managed to live without it.

I have tried installing the client on a Windows 10 VM and get the following error. “Unable to install CA certificate”
thanks for any help you can offer.

Try disabling antivirus. Also ensure you’re putting in the right fog IP address, and that the host is not pending in Host Management.

@obsidian That’s not the only one. Off the top of my head, I remember each storage node having one, and each image having one. There might be others too.

@sebastian-roth said in Windows 7 Image:

You’re saying Ghost can do BitLocked partitions in resizeable mode?

It can’t. Since Ghost is a file-level cloning solution (as opposed to an imaging solution), I question if it can handle bitlocker at all.

@obsidian I don’t remember, and don’t have a fog server at my current job. Just poke around until you find it? It’s a checkbox somewhere.