Best posts made by Quazz

@Satheesh Well, it doesn’t really work like that. It will only attempt to start its task at the designated time. It won’t block you from accessing the menu until that point in time, so people can use their computers normally in the mean time.

@Rich-C Assuming you have a good copy of your images and your database you can basically reinstall your OS, install FOG, put the images back, then restore the database and everything is the way it should be.

From what I understand you want to change the IP of the server?

If so: https://wiki.fogproject.org/wiki/index.php/Change_FOG_Server_IP_Address

I’d just like to mention that if you clean install the latest W10 iso, this shouldn’t happen (unless you incorrectly remove certain apps)

There are no scheduled release dates. FOG is entirely worked in free time of the developers, so it would be impossible to schedule any target dates, realistically.

That being said 1.3 is on RC11 right now, so you can perhaps draw some conclusions from that.

Soon TM

I believe the error codes are general windows error codes (correct me if I’m wrong)

In which case it’s

ERROR_TOO_MANY_OPEN_FILES
4 (0x4)
The system cannot open the file.

https://msdn.microsoft.com/en-us/library/windows/desktop/ms681382(v=vs.85).aspx

Which of course isn’t particularly helpful on its own.

@VincentJ From what I’ve read this compression algorithm is targetted specifically at modern CPUs, leveragering their instructions sets, which older CPUs will lack.

Meaning that tests will be needed on older hardware, as there will be people using it for quite some time. If there’s a huge time penalty there, it will still be a no go for a lot of people.

You can clean install Windows 10 and enter the Windows 8 key for upgrade.

I don’t know if the boot file accepts “param wipe 1” as a legitimate parameter.

Easiest solution would be to use the advanced login menu and put it as an item there.

Does the boot option give the option to enter credentials?

Any error messages when you try the boot option?

@Scott-Adams

xcopy /e “\\x.x.x.x\WES_Apps\Technology\Beyond Question\Beyond Question” “C:\%programpath%\Beyond Question”

should be

xcopy /e "\\x.x.x.x\WES_Apps\Technology\Beyond Question\Beyond Question" "%programpath%\Beyond Question"

Since %programpath% will include the drive letter already as inherited from %programfiles(x86)%

Please test the batch file manually to confirm.

#Edited to add backticks so we can properly see the command.

You could also simply edit the registry before capture of course.

But if you have, say an SSD, I don’t particularily recommend leaving it in IDE mode.

@Wayne-Workman said in Windows 10 Anniversary Edition - Not changing hostname.:

The legacy client for Win10 isn’t supported - per @Joe-Schmitt - a senior developer. You’ll need to move to FOG Trunk.

To add to this, imaging is also poorly supported for Windows 10 in FOG 1.2, but fully supported in Trunk version.

Note that you have to update both your FOG Server, any Storage Nodes and install the new FOG Clients.

@JJ-Fullmer You need to keep advanced login menu on advanced login only and then enable login for advanced menu under the ipxe boot menu options I believe.

I think that’s the issue, it’s using an SSD with eMMC memory.

Might have to call in the devs on this one perhaps.

You can try fixparts /dev/mmcblk0 though

For future reference, all devices are listed in /dev, so regardless of your devices name it will be there.

Technically you can probably capture and deploy it in a non-resizable fashion (it will be slow since it will do a RAW capture), though I’m not sure if this will work reliably with such a filesystem.

It’s closed source and only available on enterprise, so I don’t expect any open source solutions to arrive any time soon.

Might be possible that there’s a firmware update for the DVD drive. Could resolve the issue, of course you need to be running some kind of windows to run it…

@JJ-Fullmer

:urls
set msdart-url http://192.168.1.155/2-MSDART
:MENU
menu
colour --rgb 0xff0000 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap -- -------------------------------------
item fog.local Boot from hard disk
item msdart6x86 Microsoft DaRT for Windows Vista 32bit
item msdart6x64 Microsoft DaRT for Windows Vista 64bit
item msdart7x86 Microsoft DaRT for Windows 7 32bit
item msdart7x64 Microsoft DaRT for Windows 7 64bit
item msdart81x86 Microsoft DaRT for Windows 8.1 32bit
item msdart81x64 Microsoft DaRT for Windows 8.1 64bit
item fog.return Return to previous menu
choose --default fog.local --timeout 5000000 target && goto ${target}
:fog.local
sanboot --no-describe --drive 0x80 || goto MENU
:msdart6x86
initrd ${msdart-url}/MSDaRT60x86.iso
chain memdisk iso raw
:msdart6x64
initrd ${msdart-url}/MSDaRT60x64.iso
chain memdisk iso raw
:msdart7x86
initrd ${msdart-url}/MSDaRT70x86.iso
chain memdisk iso raw
:msdart7x64
initrd ${msdart-url}/MSDaRT70x64.iso
chain memdisk iso raw
:msdart81x86
initrd ${msdart-url}/MSDaRT8.1x86.iso
chain memdisk iso raw
:msdart81x64
initrd ${msdart-url}/MSDaRT8.1x64.iso
chain memdisk iso raw
:fog.return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} ||
prompt
goto MENU

@Sandi-Trogdon Those will match the mac addresses of the hosts you took the image of. All the data will be inside those folders. It’s the job of FTP to move that data to the correct spot under /images , so it’s time for you to troubleshoot FTP.

You can probably script some stuff together and schedule a new capture task using the API https://news.fogproject.org/simplified-api-documentation/

I’m not sure how compatible the newer iPXE binaries are with 1.2

Fairly certain it should work, though.

Try using ipxe.kpxe as bootfile instead of undionly.kpxe