@tesparza Yeah, todays log is full of “No need to sync …” messages. Seems all fine.

The replication process does check file size and checksum of the files on master node and each storage node. In case they don’t match the replication deletes the file on the storage node and resyncs that file over. So in general there shouldn’t be a case where replication is “stuck” with one file not in sync even if it was broken half way.

@btoffolon You might want to search the forums for dc7800 to find many posts on this hardware. Here is one post that might help your: https://forums.fogproject.org/post/137220

When I first encountered DC7800 problems I rolled the kernel way back to one even older than 4.15.2 […]
With 4.15.2 I have been able to image, capture, etc etc all different kinds of laptops and workstations via legacy and UEFI PXE boot without any problems.

Old hardware, old kernel…

@sebastian-roth said in Lenovo T15 Gen2 Slow Imaging:

@jconway1006 We have reports with Lenovo T14 Gen2 being slow as well: https://forums.fogproject.org/topic/15433/lenovo-t14-gen-2 - see @saad-naeem’s post in this topic for a possible solution.

Yeah I ended up reading that post after I posted mine. Same exact issues. Tried some of the suggestions in there (upgrade BIOS) and all that stuff with no success. I’m making due right now with a little work around. Its just a pain when ya have more than a few laptops to setup.

@bruce-stewart said in 21H1 imaging issue-variables do not populate:

My variables don’t seem to get populated.

Well that’s pretty normal when you don’t use bash command export to make those available globally.

@WillingMost7 Usually the fog-client software does autoupdate but due to the certificate issue it won’t. You’ll need to deploy the 0.12.0 fog-client using other methods like GPO or so.

@jyost Search the forums for snapin order. You’ll find several threads. Here’s one that probably will help:
https://forums.fogproject.org/topic/12784/snapin-order

@stu There’s a wiki article all about passwords: https://wiki.fogproject.org/wiki/index.php?title=Password_Central

Though, if you cannot log in via terminal or SSH, you might could try a Linux password reset boot utility. Use your favorite search engine to search for reset Linux password. Highly advise to backup / create snapshot before trying anything you find.

Disregard - problem has been solved. I renamed a .msi setup file but forgot to edit the filename in the snapin configuration.

@brmitmhart @Wayne-Workman Just want to add a little warning here. FOG does not support downgrading as of now. Depending on the versions it might work but could also break things.

I don’t have enough time to look into this the next few weeks. Maybe @Tom-Elliott can?

@george1421 said in Storage nodes or Master nodes?:

Storage nodes can only send images via unicast images.

What’s the technical reason for this? Just wondering. Like, why can’t it be done? Or, has it simply not been implemented?

@sebastian-roth I found the machine in hosts and approved it and now it worked out thanks

@gn_ro Hi and thanks,

You have solve my problem, disk was already in thick mode but i change the NIC and capture going to the end.

So thanks again, have a good day.

@tom-elliott yes, Zm9nOnBhc3N3b3Jk (default fog:password), as you can see on screenshot. I’m also create new user, enable API for him and get same result.

And same result with curl:

[root@ ~]# curl -H 'fog-api-token: <token>' -u fog:password -X GET http://<fog-ip>/fog/system/status [root@ ~]# curl -H 'fog-api-token: <token>' -H 'Authorization: Basic Zm9nOnBhc3N3b3Jk' -X GET http://<fog-ip>/fog/system/status [root@ ~]# curl -H 'fog-api-token: <token>' -H 'fog-user-token: <token>' -X GET http://<fog-ip>/fog/system/status **success**

Only auth with two tokens work fine.

Hi Sebastian,

I want to say thank you for all your assistance. You changes hit the nail right on the head. Thank you very much.

Kind regards
Duane

@nasmod OK we have a bit of confusion in your post. We actually have 2 linux machines in this picture. The first is the FOG server.
The second is FOS Linux running on the target computer. The target computer gets its network settings from YOUR network not the FOG server. So its IP address is assigned by the DHCP server. Now if FOG is your dhcp server for this target computer we can talk. If its your enterprise dhcp server doing this then you need to talk to your enterprise group.

The order the dns entries are added are also part of the dhcp server settings. FOS Linux is only adding them in the order they are defined in your dhcp server.

I don’t want you to think I’m saying its not a FOG issue as a matter of deflection, but in this case your infrastructure is telling the FOS Linux about the network, not the fog server.

You made reference to the resolv.conf file, that is on the FOG server. Changing that order or name servers will only impact the ability for the FOG server to look up and ping the target computers, when referenced by name. It will not have an impact on the target computer at all.

@brakcounty said in Imaging from large drive to small drive:

I am assuming that this would have to be done for each image.

Correct.

my dir listing works but when i click the kickstart file, it doesnt ask me to download it, where as it should instead of just viewing me the contents of it

is it ok to add this line in my httpd.conf as i know @george1421 advised against it

<Directory /var/www/html/listing>
Options +Indexes
</Directory>

@Patrix While you might have the same issue it could be a totally different problem as well. We just don’t know enough of you specs to tell yet.

So if you want help I ask you to open your very own topic and post all the information of you setup:

FOG version Init version Linux OS and version of your FOG server OS installed on the host you want to capture/deploy contents of d1.minimum.partitions of the particular image you want to deploy to a smaller size disk

@george1421 Thank you for the clarification. This is duly noted. Appreciate the help, you saved my ass today basically.

@mperriello ok so you are using the post init script to update the unattend.xml file with the system name? I’m trying to understand where its falling down. In the link I provided you there should be a section of the code that calls.

${postdownpath}fog.updateunattend

That line is commented out in the tutorial. Remove the hashtag from in front of that line and it should update your unattend.xml file. You may need to update the code if your unattend.xml file is not found in the standard location.