Topics created by vince.villarreal

@vince-villarreal Two other points.

You can build a usb boot drive with iPXE, but again that still relies on dhcp having the right settings to instruct ipxe on how to find the fog server.

You can also build a FOS usb boot disk, that will boot you right into FOS bypassing PXE altogether. But there are some caveats with this approach. If you can overlook the caveats and just want to capture and deploy (no multicast, no direct imaging from iPXE menus, etc) it will work for you.

One last comment, fog doesn’t like it when/if you change the IP address of the fog server once the FOG management console is installed. There are work arounds, but its best to have it at its assigned (forever) address when you install FOG.

@vince-villarreal Possibly someone capture an image over the original one. Run ls -al /images/<imagename> (put in the name of your image instead of <imagename>) to see the date of the files. Does that make sense to you?

Other than that could it be you are trying to deploy this image to a computer with a smaller disk?

Prompt time is the checkin time for the client. Anything below 60 seconds is invalid, and we won’t allow the client to go below that point. (Using Default = 60s)

Error code 2691 = The machine is already joined to the domain.

So this is likely true. When creating the master image, I would highly suggest disabling the “Join Domain” feature of the host. (Host Page->Edit relevant Host->Active Directory->Uncheck Join Domain) then disjoin that machine from the domain manually. Then capture your image. If you’re sysprepping your images, it’s also recommended to disable the fogservice from starting on the machine, and having a setupcomplete.cmd script that re-enables the service once sysprep process is complete.

@vince-villarreal If your image contains the FOG Client, which is sounds like it does, simply disable the service, disjoin the domain, capture the image. In terms of SYSPREP, you would have your setupcomplete.cmd set to enable the fog service as the last thing it does. Then you can start the service or restart the machine.

So basic steps:

Create your layout of software/OS, etc… If machine is to be constant master image maker machine, don’t allow it to join the domain (can be setup in the GUI under Hosts->Edit->Active directory->Join Domain) Install FOG Client.
# If sysprepping Disable fog client service. Sysprep Machine. Fully shutdown machine.
# End sysprep steps Capture image.

@george1421 Here is a post and a thread (with developer supplied code) that will hot patch the registration file. This thread was actually someone wanting to create a custom registration process.
https://forums.fogproject.org/topic/9754/custom-full-host-registration-for-1-3-4/45

@vince-villarreal this is the purpose of the persistent groups plugin. When a host is added, the new host will get whatever the template host has defined. This, to my knowledge, only happens when a new host is added. If you add a host to the group, then later edit the host itself, it should retain the new changes regardless of the template, until you remove and readd the host to the group.

you can solve this post. rewording this in a new post.

@vince-villarreal Yep. This can be automated with group policy though. When a box joins your domain automatically via the FOG Client, you can have group policy turn on TPM. I suppose TPM would need turned off somehow via postinit scripts.

@vince-villarreal Wiki is back up again.

What goes wrong with your storage node?

What are you trying to accomplish? Deploy from different storage nodes in different locations? (read up on location plugin if you haven’t already)

OU Drop Down option is kind of confusing to setup, but it does work.

Each OU is separated with a |

The “default” OU is marked with a ; at the end.

What this means is:

OU1|OU2;|OU3|OU4

Will create a dropdown of:
OU1
OU2
OU3
OU4
with OU2 being the default selected one.

Hopefully this helps.

Mind you all this is is a dropdown, you still have to make the choices and update the hosts/groups in question for this to apply.

@tom-elliott dumb question found how to enable plugins.

@vince-villarreal Try to add a group and see what the ID is.

@wayne-workman I want to reclassify the last point you made so hopefully easier reading.

A Storage Node Definition can only belong to one group. However, if you create a second storage node using the same information as a peer siting node, except changing the name of the node, it can belong to another group. The code has been adjusted to read all nodes.

I know this may seem arbitrary in explanation but it more directly points out that a node definition can only be in one group.

@vince-villarreal that’s the hope and those lines are added specifically so you can track the status more appropriately.

@tom-elliott That’s also at the very-tip-top of the ftp troubleshooting article, too. Saying that the problem is usually credentials, so go look at that first.

Also, this is the only FAQ that I could find (that I didn’t even know existed until now): https://wiki.fogproject.org/wiki/index.php?title=FAQ but there is no mention of FTP in there. I think that page should just be deleted since this information is covered in other places.

@vince-villarreal I have same issue and I have been going through all threads regarding this particular issue. I have exactly the same issue and I feel it’s definitely going through a replication loop. I’ve been monitoring the replication log for past couple days and seems like the replication is stuck on one storage node. Keeps deleting the d1p2.img file and begins synching only to come back to the same file and replicate to same node again.

I should also mention I have reinstalled fog from scratch configured all nodes so initial replication of an uploaded image worked fine. It was indeed after an updated image upload when replication loop began.

@vince-villarreal what feature are you referring to? An image will deploy to a machine based on the storage nodes within a storage group. Assuming both storage nodes are in the same group, it uses a rudimentary load based system to determine which node to deploy the image from.

What version of fog are you using?

Cool, I waited about an hour now and data has been transferring to the images folder.

Looks like it is working! I have another question, but will post it as a new topic

@george1421 Eh, saying ‘try’ sounds less like orders. I’m a boss of nobody but myself.