Posts made by dpotesta50

Is there a way to turn a FOG image in a recovery thumb drive I can send to outer offices when they have a hard drive crash?

@george1421 Pffft…i’m there with ya brother.

@george1421 said in Errors Before Image:

@dpotesta50 Ok so then the firmware doesn’t address the issue. Then do what Tom recommended. In the host management page for that computer, there is a field called kernel parameters. Place noapci in that field, save and then pxe boot that computer again.

But again, these are just warning message and do not, will not impact imaging.

No Kernel parameters. I see Kernel Arguments and Host Kernel under NEW HOSTS

@george1421 BIOS updated. Same errors.

@tom-elliott said in Errors Before Image:

@dpotesta50 as they appear to be acpi errors I might suggest turning it off for that machine with the appropriate kernel arts? I think it’s just noapci

Do I literally just type “noapci” from a command window?

@george1421 Hey George
I’ll check to see if there is a BIOS update for the hardware. I have no idea how to do a kernal update.

BzImage Verision: 4.13.4

Hey All
I’ve been getting these lines of errors before the image starts to pull for a couple of weeks now. The image loads perfectly fine, but I’d like to know what changed for these errors to appear.

@sudburr No clue how to do that.

@wayne-workman That’s actually a friggin’ genius idea. Too bad I didn’t do that at first. There’s no way I’m rebuilding this thing again. I needed outside help getting FOG configured.

@wayne-workman Yeah I played around with that a bit but couldn’t figure it out.

Now that my FOG image server is up and running I want to create a full backup image of the drive. Can anybody recommend something easy and possibly free?

Running the Fog 1.5 on top of Ubuntu 16.04. Everything was working perfectly fine but today I can’t get a laptop to PXE boot to the server anymore. Says NO DHCP or proxyDHCP offers were received. This was literally working perfectly fine on Friday. No changes were made, now it’s not working.
What do I check?

@george1421 My reference image is NOT 1709 and once attached to the domain that update has been blocked by our WUS. Too many problems with it.

@george1421 Looking back at that post. The three scripts you have there literally just need to be copy and pasted into a file and placed into the appropriate sections? No customizing needs to be done to them?

I’m looking at those instructions cross-eyed. I’m not certain if have the ability/knowledge to do that.

@george1421 Luckily the image boots just fine. What’s missing are things like network drivers, bluetooth and proper audio.

Fog server up and running. Fresh Windows 10 Pro image uploaded. Pulled the image down to a machine different from the one the image was built on.
Missing drivers.
I’m assuming snap-ins would be the best way to do this and I understand the basic concepts of scripting .exe silent installs. But I don’t want/need these drivers to load on EVERY model we image. Just this one particular model. How do I do that?

nevermind

I’ve created several “test” images and never had to deal with this section. Today when I go to create my new host it’s telling me the PRIMARY MAC section is required. I’ve made my image on a 2n1 DELL with no ethernet so I"m using a USB-Ethernet adapter. Is this issue (never was in the past) and if so how do I resolve?