Topics created by JYost

@Mightmar Ahh , so you’ve hit a problem we see occasionally.

SNP SNPonly files, are effectively using the onboard information to drive network connectivity in the PXE environment. ipxe.efi attempts to match the device to a specific driver (usually for better performance/speed/accuracy of information)

As you might imagine, if the driver isn’t matched or not fully fleshed out, the NIC may not operate or hand off accordingly.

I think you’re right that updating the information wouldn’t have necessarily been required, but also probably wouldn’t hurt anything either (or at least shouldn’t.)

@Sebastian-Roth
Thank you Sebastian, I will give that a try. Thanks again for the excellent support! You can close this ticket.

@george1421

I just tried another capture after changing the FOG client on the image to point to our FOG server in Germany. This time there was a normal 1 minute pause during the resizing process then Partclone G-zip started and imaged without problems. All seems normal again…gremlins have been eradicated. You can mark this as solved.

Just heard back from our Cali, Columbia office. All is well, device imaged fine with no errors. Thanks again for the awesome support!

@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

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

@jyost Use that value set as password=... in /opt/fog/.fogsettings to (re)set the fogproject account password.

Well, sync’ing everything up a second time worked like a charm. Thank you for your help Sebastian!!

@jyost said in Old MAC's retained after being changed in web interface:

FOG 1.58

We don’t have a team of developers to backport fixes so this needs to be verified an issue in the latest dev-branch version. We won’t be able to help you with a fix for 1.5.8.

With that said we can still see if this is really a bug or just a missunderstanding. From what I remember when you change a MAC address it will add the old one as a secondary MAC to that Host. And I think there was a bug in 1.5.8 web UI that did not show the secondary MACs (were somehow hidden). Please see if that’s the case.

@jyost said in Roughly half of reimaged devices do not run first run scripts in autounattend.xml after imaging.:

If the renaming/domain join occurs AFTER the final restart I will need to run a powershell script to install our AntiVirus software and also add a domain user account to the Remote Desktop Users group –

You might want to consider deploying this action with a snapin. Snapins will run after all of the other imaging actions are complete.

We will be building a new VM with Ubuntu 20.x…it won’t be an in-place upgrade. I will post any issues we run into…fingers crossed.

I need to update the storage nodes, how are they updated? the Web Master updated it and it worked correctly

@JYost are you registering all of the hosts? How are you setting the preferred names? The way I did it was I set names as I registered, and then did an image deploy right there during registration from FOG’s boot menu, typically. I don’t know how much experience you have with FOG but Tom is right, naming and domain joining should work 100% of the time. If it’s not, something isn’t right and we need those logs to help.

@JYost Oh well, I was too quick looking at this without noticing the first part of it being really old. Next try:

6/5/2020 2:42:30 PM HostnameChanger Checking Hostname 6/5/2020 2:42:30 PM HostnameChanger Renaming host to HE-L002107 6/5/2020 2:42:30 PM HostnameChanger Joining domain 6/5/2020 2:42:35 PM HostnameChanger Success, code = 0 6/5/2020 2:42:35 PM Power Creating shutdown command in 60 seconds

Looks pretty good to me so far. And from then on the rest of the log shows:

6/5/2020 2:46:22 PM HostnameChanger Checking Hostname 6/5/2020 2:46:22 PM HostnameChanger Hostname is correct 6/5/2020 2:46:22 PM HostnameChanger Attempting to join domain 6/5/2020 2:46:22 PM HostnameChanger Host already joined to target domain

So I can only guess on what you mean by “not entirely sure what the error messages should be telling me”. Guess you mean these log entries:

6/5/2020 2:38 PM Client-Info Version: 0.11.15 6/5/2020 2:38 PM Client-Info OS: Windows 6/5/2020 2:38 PM Middleware::Authentication Waiting for authentication timeout to pass 6/5/2020 2:40 PM Middleware::Communication Download: http://10.6.190.155/fog/management/other/ssl/srvpublic.crt 6/5/2020 2:40 PM Data::RSA FOG Server CA cert found 6/5/2020 2:40 PM Data::RSA ERROR: Certificate validation failed 6/5/2020 2:40 PM Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: The signature of the certificate cannot be verified. (NotSignatureValid) 6/5/2020 2:40 PM Middleware::Authentication ERROR: Could not authenticate 6/5/2020 2:40 PM Middleware::Authentication ERROR: Certificate is not from FOG CA

The fog-client installed on this machine was pinned to a FOG server different to the one it is talking to right now. I suppose you switched your certificates or FOG server some time between installing this fog-client (0.11.15) and letting it talk to it now. Good news is that the fog-client figured there is an update (version 0.11.19 in the logs from then on), installed that and re-pinned to the current FOG server which essentially fixed the problem.

which brings to mind another question…why are there still fog.log entries from back in March and then appended with the log entries from Friday?

This means the fog-client on this machine (or your master??) has been running in March or the date/time of this machine was way off.

@JYost What you see when you first click hosts is the search view. Typing in the menu bar search field you should see results below.

To change this you go to FOG Configuration -> FOG Settings -> FOG View Settings and change setting VIEW DEFAULT SCREEN from SEARCH to LIST. Don’t forget to click Update to save the change.

@JYost Yeah, truly a bug. Fixed in latest dev-branch. Change will be in the next release.