@george1421 As always, thanks for the quick reply. Another reason i don’t want to use a storage node with location plugin, is that I then have to register my host first, before i can deploy an image. Unless this is incorrect?
Posts made by Baessens
-
RE: Multiple master nodes syncing images
-
Multiple master nodes syncing images
I have two standalone fog nodes, each on a different site. I want to automatically sync images from node A to B. What is the best way to do this? Do i need the location plugin for this?
I understand I have to export/import the Images list.
I will only be creating images on node A.The reason i’m not using a storage node, is cause I want to be able to use fast deploy from both nodes.
EDIT: i don’t want to have to register my hosts
Thanks in advance !
-
RE: FOG capture to iso bootable media
@george1421 Ah, i see. I was doing it with rsync in a cron job at the moment. I’ll try out your suggestion. Thanks for the info.
-
RE: FOG capture to iso bootable media
@george1421 Oh, so FOG will automatically replicate between fog standalone servers as well? i don’t need to do it manually?
-
RE: FOG capture to iso bootable media
@george1421 Thanks for your reply. i’ll look into a clonezilla and/or a mobile Fog server.
Although people have recommended me to use a standalone fog server for each location and sync the images manual(with rsync,…). As i can’t “fast deploy” with a storage node without registering the devices.
-
FOG capture to iso bootable media
Hi everyone
I was wondering if there was a way to turn an image i capturedwith FOG into an ISO or something. To create a bootable usb-stick from later?
I want this because not all my sites have a server.
Thanks in advance
-
RE: Can't deploy after migrating
@Baessens Maybe i need to change the UID of my FOG installation? ?
Edit: changed the UDPCAST INTERFACE to eth0, still same problem.Also, Is this wrong?
ict@fogserver:/images$ ls dev postdownloadscripts Priminfowin10pro lost+found postinitscripts priminfowin10pronewofficekey ict@fogserver:/images$ cd dev ict@fogserver:/images/dev$ ls dev postdownloadscripts
EDIT: re-running the installer seemed to fix the issue.
-
RE: Can't deploy after migrating
@Quazz
I think it’s quick deploy, i just boot a PC to network, login on the FOG server and chose ‘deploy image’.
Also my fog server doesn’t have DHCP server, we use a windows DHCP. -
Can't deploy after migrating
I migrated a FOG server(physical) to another FOG server(VM).
I used the following tutorial: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG
I migrated the DB aswell. However the new fog server has a larger disk then the first one.
At first the dashboard showed me the older disk size en usage (in the pie chart).
Now i fixed that by changed the IP adres. (still had the old one)The problem i’m now having is that when i try to deploy one of those images, i get the error invalid mac adres when checking mounted file system… (see picture below)
Few things i tried then:
- Changed the interface name to ‘eth0’ it was something else on the old server. (on the fog webportal under settings)
- Changed NFS ETH MONITOR to ‘eth0’ as well
- UDPCAST INTERFACE to eth0
Any ideas here?
Thanks in advance
EDIT: re-running the installer seemed to fix the issue.
-
RE: Change the default /images location
@george1421 I didn’t know that storage nodes were deploy only. Thank for the info.
-
RE: Change the default /images location
@george1421 Thanks for the quick reply. This helped me out, thank you !
So you wouldn’t recommend me setting up a Fog storage node? -
Change the default /images location
Hi people
I installed my FOG server in a VM on a 60GB SSD disk, that i made.
Now i would like to add a secondary Disk of about 300-500GB HDD to that same ubuntu instance to store the images.Is there a way i can change the /image folder to that second disk?
Or should i not bother and install a second FOG server just as a storage node?
Thanks in advance
-
RE: win 10 deployment / disk size auto-adjusting / recovery mode
I captured a new image of one of the physical machines (not VM). This is a resizable image.
I CAN deploy this image to the other machines without the recovery screen error…This machine has been setup by one of my colleagues using windows media creation tool.
It’s also a Win 10 pro 64 bit.
The Disk management looks a little different tho; (name of OEM partition)Seems like something must be wrong with the VM i set up ?
Thanks
-
RE: win 10 deployment / disk size auto-adjusting / recovery mode
Make sure you disable fast boot and shutdown the machine using shutdown -s -t 0 -f in Windows command line.
I used the shutdown command. I’ll try disabling fast boot and reimaging.Is it possible you’re deploying an MBR (legacy/old BIOS) (assuming, based on your partitions) to a system that’s trying to boot in GPT (new/UEFI) mode?
It’s possible the VM i made uses MBR. But i’ve enabled Legacy boot on the BIOS and disabled secure boot. Also with the other image(not resizable) i made i have no problems deploying.Does d1.mbr exist in your image folder?
Yes, it does.The thing i don’t understand is how i don’t have any problems deploying the other image i made. Which is Not Resizable. I’m deploying on the exact same machine.
I do have the option legacy boot enabled in the BIOS, and secure boot disabled. I’ve tried using uefi boot but that doesn’t work at all.
Maybe i have to add some kind of option or parameter in the host options on the FOG UI?
-
RE: win 10 deployment / disk size auto-adjusting / recovery mode
@Quazz
I do not use any unattend.xml file.
All I do is install from a win 10 pro 64 bit iso, on my hyper-v which is Windows server 2016.Version: Windows 10 Professional, version 1803 (june 2018) - Dutch
I manually go through the installation process, install office and some other small things (with Ninite); and capture the machine with FOG.
I do add a legacy network card to be able to boot from network on hyperv. and i use generation 1 as my VM type.If i do not chose for the resizable disk, it deploys just fine.
Thanks for all of the help already!
-
RE: win 10 deployment / disk size auto-adjusting / recovery mode
@Sebastian-Roth Thanks for the reply.
d1.fixed_size_partitions:
This is an empty file.
d1.partitions:
d1.minimum.partitions:
Disk management of the machine i captured;
-
RE: win 10 deployment / disk size auto-adjusting / recovery mode
@Quazz Yes i recaptured the image. It does deploy quite a bit faster now. The part where it erases MBT/GPT tables goes a lot faster now. Thanks for that. But for some reason the device still reboots onto the error recovery screen with the same error.
-
RE: win 10 deployment / disk size auto-adjusting / recovery mode
@Quazz I ran the commands; The deploy seemed succesfull, but the device still rebooted to the error recovery screen…
-
RE: win 10 deployment / disk size auto-adjusting / recovery mode
@Quazz Thank you for the quick reply. The language installed is Dutch.
I tried deploying to two different devices both from HP. There is an Recovery OEM partition. -
win 10 deployment / disk size auto-adjusting / recovery mode
Hi everyone
New FOG user here…
Scenario:
I have a Hyper-v environment. I made two VM’s to deploy to our workstations.
They are both 64 bit windows 10 Pro’s, Generation 1.
installed language: Dutch.I did not do any sysprepping.
I imaged them both to my FOG server (Version 1.5.4)
One uses a Multiple Partition Image - Single Disk (Not Resizable), which deploys just fine. Only problem i have is that it does not adjust the partition of the drive automatically. So i would have to manually expand it…
On the second image i chose Single Disk - Resizable thinking this would auto adjust the partition. But when i try to deploy this one of our pc’s, it just boots into recovery mode…Giving me error 0x0000225.
Now, i’m not sure if this is a windows problem or something in FOG.
(edit ->)
tried this after suggestion from comments:wget https://fogproject.org/kernels/bzImage -O /var/www/html/fog/service/ipxe/bzImage wget https://fogproject.org/kernels/bzImage32 -O /var/www/html/fog/service/ipxe/bzImage32 wget https://fogproject.org/inits/init.xz -O /var/www/html/fog/service/ipxe/init.xz wget https://fogproject.org/inits/init_32.xz -O /var/www/html/fog/service/ipxe/init_32.xz
This did help increase the speed of deployment, but the device still booted to the recovery screen…
Any help would be appreciated.