Topics created by Arsenal101

Just Kidding :))))) I just added the other architectures under the helpful little NOTE: and it works just great! I Skim too much and don’t read enough. You guys are great.

@Quazz said in Where are the logs!?!?!:

From what I can tell, this answer file has some issues, but I’m far from an expert on them.

I’m not an expert either. I thought these files were being generated by some helper program that you can run to set everything the way you want? Please do not tell me everyone has to manually make these things.

So I am not really sure what I did, it was some combination of commands but it let me install it just fine… I’ll take it.

This can be marked as solved I guess!

@MRCUR said in FOG Services Crashes - subsequently doesn't join domain:

@Joe-Schmitt Do you have the new client that I can test Joe?

This issue was fixed in 0.11.3.

Current Client version is 0.11.4, and 0.11.5 will probably be released sometime in the following week (August 2016).

That’s pretty slick… fog service updated itself before I could even get into the host that had it installed!

That seems to have worked!

@Arsenal101 To ensure all goes smoothly on the next upgrade, edit the /opt/fog/.fogsettings file.

Look at the snmysqluser= snmysqlpass= and snmysqlhost fields and make sure they’re set properly.

In your case:

snmysqluser='root' snmysqlpass='' snmysqlhost='IP/Hostname of FOG here'

While I still stand by what I’ve already said - just try multicast and see if it works - for same images at once. Stick computers into a group, and initiate multicast from the group.

Look at the path in the error, ...URL /fog//service... It has two slashes back to back. That’s probably the issue.

What OS are you using? What’s your web-root setting for this storage node set to?

I think I solved it! We do currently have a .32 server in place as it has good images on it and I didn’t want to completely drop it and lose those unitil i knew that I had the New 1.1.2 server 100%. I was able to deploy fine with the .32 server but not the 1.1.2 but it looks like the problem was the NIC driver. installed the updated driver and all is well in the world of imaging, for me atleast. Ill just inject the new driver into the windows driver store so i don’t have to install it on all the machines after the imaging process

Sounds like a “firmware” issue in the NIC that the “latest” driver fixed.

Well that’s weird… I don’t have a .fogsettings file, none the less I changed the fog account password and now my images are being replicated successfully. Thanks again for your help!

You probably had a 1st rev of fog_1.1.2.tar.gz. There was a bug in the user login stuff which I was able to correct and retag and push as the 1.1.2. Thanks for reporting back.

Megabyte, go ahead and start your own thread and post your question including what version of windows and FOG you are using. I’ll be happy to help you get it working with AD if I can.

you do not need to specify the Reseal in your xml file as that’s what the switches do - by having this in your unattend file it conflicts with the switches you pass to sysprep. just remove this section all together from your unattend file and it should stop the issue.