Topics created by Scott Adams

@george1421 I just verified, that line is indeed in my fog.conf file. If you look through the code that is posted on that particular thread, the change has already been made in the code that is posted. But, I did open the file on my server just to verify. Like i said, it is correct.

@Scott-Adams said in Computers not joining domain after password change:

I had thought about that as a work around, didn’t think that would be the actual solution though. Thanks @Wayne-Workman

@Scott-Adams You’d need to post the fog.log from a problematic host.

I’ve wanted to give FOG classes for years. But it’d take more than just you signing up for them (paying in advance too, I shall not be blown off).

@Scott-Adams It’s a DB-only setting, it’s not anywhere else. So no worries.

Remoted in, found the svn directory was in a very strange state and not actually updating anything during an svn up.

Removed the conflicting repo, use git and installed that way, All is working properly now (reporting wise at least).

@Tom-Elliott TIL xcopy has internal error codes, that’s very useful.

@Tom-Elliott

--------------------------------PrinterManager-------------------------------- 5/19/2016 10:24 AM Client-Info Client Version: 0.10.6
5/19/2016 10:24 AM Client-Info Client OS: Windows
5/19/2016 10:24 AM Client-Info Server Version: 7717
5/19/2016 10:24 AM Middleware::Response Success
5/19/2016 10:24 AM Service ERROR: Unable to run module
5/19/2016 10:24 AM Service ERROR: Object reference not set to an instance of an object.

@Tom-Elliott After the update (SVN 7695), that error is gone and I can make changes again.

Thanks!

@Scott-Adams

We are requesting that all community members who have Surface Pros to please do a packet capture, to capture the DHCP conversation the client sends out at boot time via the ethernet dock, and upload the capture here. The intent is to gather more information about the Surface Pro, so fog can better support network booting it.

Thanks,
Wayne

@Scott-B None of that stuff is in the globalSettings table. Look for yourself and see what I’m talking about. select settingDesc from globalSettings;

A cool little way I track what is going on for the clients when that is happening (That @Tom Elliott showed me )

Open powershell and type: get-content -wait C:\fog.log (or wherever you have the log stored.)

this will let you see what it is doing while it is doing it. Depending on the error it can lead you in the right direction.

Thanks Tom and everyone! The update has resolved the error with my kernel download. Not sure what got flubbed up to begin with, but resolved.

CPU seems to be looking more normal as well, after deleting all the hosts and re-adding as they check in.

Can be marked as solved.

@Scott-Adams Latest trunk version is around 65xx. Maybe this has been addressed already? As hostname changes happen through the client I suppose it would be interesting to know which client version you use right now and which you have used back then?

@Scott-Adams And there is another thread where we got past the “No Network Interface Found” issue I think. Try adding has_usb_nic=1 the host’s kernel parameter (host settings)! But it depends on the USB NIC used. We have pretty much every USB NIC driver included in the kernel but I guess there are devices out there for which the kernel does not have a driver (yet). Just give it a try and let us know.

And please see exactly which USB NIC you have. Read through this interesting discussion on Surface 3. The first couple if posts (page 3) we talk a lot about the two different MS surface adapters and the NIC chip they have.

As well make sure to update to the very latest trunk version. There have been a lot of fixes!!

Edit: Re-reading the surface3 posts I remembered that we needed to add the PCI IDs for the MS USB NICs to the kernel. As far as I know those should work if you upgrade to the latest trunk!

Thanks for all your help. I hope so as well.

@Wayne-Workman

I did. Created a backup user to avoid this in the future. Thanks everyone for your help! I am up and running again.

@Scott-Adams Yup.

It’s called a “raw” image type. But, I’d really recommend against that… really strongly… using a raw image type is 99% of the time not necessary and also ridiculous.

When you come into the FOG world, you need to re-learn how you think of imaging.

Glad you got it working! and, that info is good to know.

I am going to have to set FOG up at our central location for something like 27 buildings soon… glad to know what to use now!

At the moment, I’m sort of the lone ranger using FOG in just one building, and everyone is envious of my 4 minute image deployment time, with auto naming and auto joining to domain… and web functionality. And, the people at Acronis screwed up when my manager called them up with a list of basic questions about their network solution… and nobody he got on the phone with could give direct answers… so they missed out on something like a $50,000 sale lol. My manager wants to move forward with FOG now. 🙂

@Wayne-Workman
That did Wayne, thanks again for the help. Updating passwords between storage node in gui, and .fogsettings, so they match, was the final answer.