Posts made by adukes40

@george1421 I’ll give it a try. Dont need a fancy report, just a listing would suffice, I was going g to cross reference it with inventory to see if it has been relied, or trashed. Thanks George

@george1421 that would be a good way. We can do similar reports with our other software, if fog could do that kind of reporting that would be a path I would attempt.

@Wayne-Workman I don’t foresee space being an issue at all, just more so OCD kicking in. Starting fresh on something, just want to keep it clean as possible.

I just had this issue as well. I migrated a DHCP scope from an old server to the current server. It now has two scopes. For what ever reason, the boot options disappeared from the original scope but stuck with the migrated scope. I added the options 66 and 67 back to the original scope, and it worked.

/shrug

General question of curiosity. As most of work in school districts, we all know machines come and go frequently.

My question is, how do you all keep the host inventory of the FOG server, cleaned up, so there aren’t just a bunch of non exisit hosts taking up space?

With over 3000 devices (that will be in FOG) I am just trying to get a feel on how to keep old machines that have been scraped, out of the inventory.

As talked about on the Hangout today, I mentioned that my snapins were not running. the client version I was running was 0.10.6, although I updated FOG to the latest release which included 0.11.2. I just did a test image to see what would happen. The host was imaged with 0.10.6 on the image, and the client updater turned on. During imaging it updated to 0.11.2, and ran the snapins.

During the Hangout, Wayne mentioned the importance of having the client updated to the latest, as Tom and Joe work closely together to have FOG and the client work together.

I just want to post that this indeed was the case, and my snapins are now working perfectly fine once the client version updated to the latest.

Thanks all

@Joe-Schmitt Luckily I haven’t rolled out yet, so I just turned off the auto update for the moment. Hoping that works.

@Joe-Schmitt I have mine set to install directory.

@Tom-Elliott its no big deal. once this summer is over, adding new hosts gets more rare. It was just this being our first roll out, there will be a lot of machies to touch. All good though, rather have FOG do what it needs correctly instead of me tearing it up.

@Tom-Elliott I am starting to lean towards FOG not liking my hosts import. It sees some hosts, not all and the same machine that the log was from, I removed from FOG and performed a full inventory, and imaged again. All is going through now. I guess we will just perform full registers on all hosts (thats what summer help is for)

I was getting ready to make a thread about this. Just started happening about a day ago. i have been looking for answers, and found a couple posts about it happening during a program install. Being this is happening during my image process I am leaning towards something in the new client as well. I only say that because I have 0.9.10 on my image, and sometime during the first reboot I notice it has version 11 and the message box pops up.

@Tom-Elliott Just set an image and came back to it in sleep mode. Checked machine and the snapins did not run. I found this in the log:

--------------------------------Authentication--------------------------------

6/21/2016 8:56 AM Client-Info Version: 0.9.12
6/21/2016 8:56 AM Middleware::Communication URL: http://10.103.72.49/fog/management/other/ssl/srvpublic.crt
6/21/2016 8:56 AM Middleware::Authentication ERROR: Could not get security token
6/21/2016 8:56 AM Middleware::Authentication ERROR: Could not find file ‘C:\Windows\system32\token.dat’.
6/21/2016 8:56 AM Data::RSA FOG Server CA cert found
6/21/2016 8:56 AM Data::RSA ERROR: Certificate validation failed
6/21/2016 8:56 AM Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. (NotTimeValid)
6/21/2016 8:56 AM Middleware::Authentication ERROR: Could not authenticate
6/21/2016 8:56 AM Middleware::Authentication ERROR: Certificate is not from FOG CA
6/21/2016 8:56 AM Service Sleeping for 120 seconds

@Tom-Elliott OK, looks like imaging is running now. And the other parts still look good.

@Tom-Elliott I was getting ready to say that there was an error Attempting to checkin during deployment. Updating now.

@Tom-Elliott Alright, my issues seems to be checking out now. All looks good so far. Thanks Tom!

@Tom-Elliott Lol. OK, updating again.

@adukes40 OK, the boot now goes through. However, the host screen now look different and there is a SQL error at the bottome of the page, can’t change location again. Here are some screenshots:

This is at the bottom of the above page:

SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘) ORDER BY LOWER(printers.pAlias) ASC’ at line 1 SQL: [103] SELECT pID FROM printers WHERE printers.pID NOT IN () ORDER BY LOWER(printers.pAlias) ASC Params: 0

And when changing the location I get this:

SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘) ORDER BY LOWER(modules.name) ASC’ at line 1 SQL: [89] SELECT * FROM modules WHERE modules.id IN () ORDER BY LOWER(modules.name) ASC Params: 0

@Tom-Elliott OK, updating now, be back in a few

@Tom-Elliott Ok, updated all nodes, the Location can be set now, but still getting the SQLSTATE[42000] chainload issue

@Tom-Elliott updating now. master almost done, then I will hit nodes. Let you know in a few