Hi,

i boot all my iso’s that way:

initrd http://${fog-ip}/iso/acronis2017.iso
chain memdisk iso raw ||
goto MENU
:easeuspms
initrd http://${fog-ip}/iso/easeuspms.iso
chain memdisk iso raw ||
goto MENU
:aomeipau
initrd http://${fog-ip}/iso/aomeipau.iso
chain memdisk iso raw ||
goto MENU
:veeam
initrd http://${fog-ip}/iso/veeam.iso
chain memdisk iso raw ||
goto MENU
:erd2005
initrd http://${fog-ip}/iso/erd2005.iso
chain memdisk iso raw ||
goto MENU
:dart7
initrd http://${fog-ip}/iso/dart7.iso
chain memdisk iso raw ||
goto MENU
:dart8
initrd http://${fog-ip}/iso/dart8.iso
chain memdisk iso raw ||
goto MENU
:dart81
initrd http://${fog-ip}/iso/dart81.iso
chain memdisk iso raw ||
goto MENU
:dart10
initrd http://${fog-ip}/iso/dart10.iso
chain memdisk iso raw ||
goto MENU
:dban
initrd http://${fog-ip}/iso/dban_2.3.0.iso
chain memdisk iso raw ||
goto MENU

Here is my complete menu: https://pastebin.com/zWBnT5c0

i know that problem and i solve it with:

shutdown -s -t 0 -f

please try this.
This can also happen with some sucky notebooks where you have only milliseconds to press the network boot button and accidentally press strg+alt+del in the wrong moment because the damn thing is booting the os again while you wanna image.

Also Windows 10 has an option where its not shutting down the way we may suggest, some kind of powersaving state.

https://answers.microsoft.com/en-us/windows/forum/windows_10-files/win-10-leaving-dirty-ntfs-partitions/8b9be760-7003-48de-97b2-06bdf497085c

This is for the unclean disk state the inode error seems to be a bad sector on your hdd or something like that. Try to run chkdsk or similar tools to check filesystem integrity and bad sectors.

@user4000 said in Authentication:

The IP is not the issue. I just changed the numbers for the post.

tell this when posting, what a trap

@george1421 said in UEFI Booting with Lenovo T470 NvMe drive:

If you capture a bios image it will only deploy to bios image configed systems. Same for uefi/gpt.

Deployment will work but booting the system will not
I always deploy UEFI Images to Virtual Box in legacy mode because Virtual Box cannot PXE Boot in UEFI Mode, so i Deploy in legacy shut the machine down, enable EFI and start the VM again.

@sam240 FOG does not convert between MBR and GPT you need to capture your image in the desired Partition Layout. If you have an image for MBR and one for GPT you have to choose the right image depending on the Mode you boot to pxe.

Hi,

i would recommend to create a new image (UEFI Mode), it’s not impossible to convert from MBR to GPT but the Partition Layout and Partition size is different to MBR.

http://www.thewindowsclub.com/convert-mbr-to-gpt-disk
https://www.howtogeek.com/193669/whats-the-difference-between-gpt-and-mbr-when-partitioning-a-drive/

I was at the same situation and i created both legacy and uefi image.

Regards X23

Hi,

is this a physical server (not a vm) why not cloning the complete harddrive from 1tb to 8tb? For me that sounds like the best solution. You can even do what @george1421 suggested also a nice solution

is it maybe important to have the correct date and time to install that cert?
Are these settings correct at the time of trying to install?

Maybe he can try to manually import that cert to certmgr? Is that possible?
Or is the cert just copied to the file system?

Regards X23

@george1421 can i have that image too please?

I deployed my UEFI Image in the last hours to 4 different UEFI Systems and it was working on all, i don’t know what happened in the last days when it was not working but it seems to be okay now… Strange!

I maybe should mention that i updated to 1.4.2 from 1.4.1 last night, but i don’t see any relation.

Regards X23

@sysadminatelier said in macOS update broke iPXE:

10.11

is this maybe related to your problem?
http://forum.ipxe.org/archive/index.php/thread-8296.html

Sorry one page 2 you are referencing to this thread, saw it to late sorry.

sysprep the machine before capture.

curious, when i deploy my image back to a vm office 365 activation and internet explorer is working fine. What could this be when this will not work on a physical machine? head scratching…

@sfayle

@sfayle look at my screenshot below

delete the image definition in the webif, i think the size is saved in the db?

@george1421 i know this, but you simply gain reimage rights with a single purchase of a VL copy. Then you are also allowed to reimage OEM (thats just a rights fact), what i think is that ms knows that a lot of people do reimaging with OEM so maybe they are evil like features to disable lockscreen in pro version (they disabled that with 1607, now with 1703 you can redisable lockscreen)

Since i do everything exactly with 1703 like with 1607 i think ms is seeding traps here.

I will figure this out, i create a new image and change nothing, then i run sysprep and i will see if ie is working or not. If so i can add office 365 to see how that performs.

Some other rumors could be “CopyProfile” in unattend.xml, i read some stuff where people say CopyProfile breaks sysprep:
https://www.reddit.com/r/sysadmin/comments/6796rt/windows_10_1703_sysprep_imaging_issues/

Regards X23

@Avaryan i dont talk about starting edge in local administrative account. After sysprepping you cannot start iexplore or activate office 365. ie doesnt show up but there is a process in taskmgr, the office activation window is left grey after 2 minutes it states that it cannot connect to the actication servers (thats not an online problem).

I know that some programs are not startable under local admin account but thats not the issue. FYI you can change this in the registry: https://www.linkedin.com/pulse/how-use-microsoft-edge-built-in-administrator-account-raza

Did this in the past to make edge default settings.

But like i said thats not the issue here.

Hi, i recreated my image, only installed all updates and added fog client and office 365.
After deployment and adding the machine to the domain i cannot start iexplore.exe or office 365 activation if i am not the domain administrator, every other user cannot use it.

I have the feeling MS is working against reimaging of OEM Version, else i cannot explain this problem.

Anyone with ideas?

Regards X23

@Tom-Elliott @Wayne-Workman @george1421 Hey dudes this random mac option for wlan was really enabled, since i didn’t knew it was existing i have to disable this by gpo, this user enabled it on it’s own, he thougth it would be a good idea, no it’s not for FOG Thank you Tom for giving the solving idea

Where is the option to mark as solved? Can’t find it.