Posts made by d4rk3

Don’t use FogPrep it’s only needed for XP images…

Turn legacy booting off. Then set the bootfile to any .efi file and try again.

Go to https://rom-o-matic.eu

Click the drop down and choose
UNDI only (.kpxe)

Paste this script into the script box:

#!ipxe

dhcp
cpuid --ext 29 && set arch x86_64 || set arch i386
params
param mac0 ${net0/mac}
param arch ${arch}
param product ${product}
param manufacturer ${product}
param ipxever ${version}
param filename ${filename}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain http://10.50.0.48/fog/service/ipxe/boot.php##params

Click Proceed, save the new undionly.kpxe, transfer it to your FOG server’s /tftpboot and give it another whirl.

@Tom-Elliott I am aware. This is fixed too, btw

@Sebastian-Roth The AD issue is fixed. The snapin issue is fixed. I’ll report back soon about the rest.

-Deleting a host removes it from the host list but manually browsing to its old URL (http://xxxx/fog/management/index.php?node=host&sub=edit&id=152) and the host remains with blank information. Browsing to its old URL for deletion does not remove it either.

-Unable to set BIOS/EFI exit types on new hosts. Any options set for either do not stick after updating the host with the desired options.

-Random hosts do not have button to reset encryption data anymore.

-When deploying two snapins to a host only one deployed successfully.

-Hosts join AD before hostname changes instead of after the hostname changes like they normally do.

I’ve already upgraded all of my clients, I was just genuinely curious to know if any easier methods existed

@Wayne-Workman Other than waiting for v0.9.6/re-imaging are there any easy ways to accomplish this on a large amount of hosts?

1. Open a command prompt as Administrator.
2. Type wmic and hit enter.
3. /node:“Computer-01”,“Computer-02”,“Computer-03” /user:domain\user /password:password product where name=“FOG Service” call uninstall /nointeractive
4. From there you can deploy the new client

@Wayne-Workman Even if the web interface isn’t used by anyone the load will always be high.

However, out of the ~1000 clients I have approximately 900 have the new client installed.

Maybe this issue is related to these newest revisions with regard to communication with the new client (v0.95).

I know for certain it started somewhere between r4960 and r4982.

I am also experiencing this. This includes random revisions ranging from r4982 - r5080.

@Wayne-Workman Yep, the sky’s the limit as far as drivers go Customize your little heart out lol…

@mcgonigiggle I don’t have any right now, but I know a guy…

Just download 7zip and then right click any Dell driver .exe file and extract

@mcgonigiggle The manufacturer’s site, silly

If you’re only using those two Dell models just grab the drivers for both, extract them to your folder, run the reg add command and you’re done.

I should mention that the Dell .exe driver packages will not work as-is. Make sure you extract them first.

This is the driver folder structure I use for all of my images:

AHCI
Audio
Chipset
LAN
Video
WiFi

@mcgonigiggle It is really that simple enjoy the many hours you’ll save with this trick ;D

(This works on Vista/7/8/8.1/10 and Server 2008 R2/2012/2012 R2)

All you need to do for drivers in images is this:

1. Put all desired drivers in a folder. I use “C:\Drivers”.

2. Run this in an elevated command prompt (if you want to use a different directory simply replace the bolded C:\Drivers with your driver directory):

reg add “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion” /v “DevicePath” /t “REG_SZ” /d “%SystemRoot%\inf;C:\Drivers” /f

3. Profit???

Good news, Single Disk (Resizable) uploads and deploys normally.

The problem was with my automated .xml I use with WDS. I had to manually set the partition types/sizes in the .xml and apparently FOG didn’t like something I had set.

Anyway, I turned off the automated setting, re-deployed to my image station, wiped out all partitions and let Windows automatically create the partitions. Once that was done I re-uploaded without issue. Then I deployed without issue

After this deploys I’m gonna try the newer init_32.xz, I have a feeling it will be fine now

@Tom-Elliott Will do…I was shocked that I was able to upload the image but had issues deploying it. When the init_32.xz from SVN 3504 worked I was even more baffled.

Now all we need is a Secure Boot signed set of iPXE .efi bootfiles!