Good day,
issue is solved; line 060 was being used by WDS server, which is inactive for some time and we do not use it anyway. It was agreed to disable this line and so FOG server is already running smoothly - 40 GB test image deployed on testing PC within 3 minutes. AWESOME! Plus I’ve managed to integrate few utilities such as Clonezilla, Clonezilla Server Edition (or DRBL live), System Rescue CD, PMagic, GParted and AVG Rescue CD.
Will come back with other questions; thanks so far!
Organization Name: The Institute of Technology and Business in České Budějovice
Web: www.vstecb.cz
Location: České Budějovice, Czech Republic
Approximate Number of systems: ~400 and growing
How long: Implemented in May 2017
Can be listed on the Wiki.
FOG servers: 1 dedicated server
Additional Storage Nodes: None
Previous Imaging Solution Used: Ghost Solution Suite 2.0
Uses FOG Client: YES
Got only Czech logo, hope you don’t mind.
Thank you, I will look over them; now I need to get some more work done, or my boss will chew me out for chatting 
Best regards,
M. M.
I already thought about it, but it seems too early for our school environment, since we’re mostly running on W7; so for now I am too lazy about it. In the future, I might get sick of USB sticks, so I might do it, though installing one PC once in while, sysprep it and then make usable image for deployment won’t kill me.
Btw, got a question about this tutorial.
In part 1, to create somewhere on server/workstation/etc. network share, which will hold installation DVD contents. Does it have to be on this network share? Can’t we move this folder onto FOG server somewhere between other ISOs? Or this kind of setup has issues?
Hi,
I just used this tutorial and I must say it was very usefull - managed to install W7 on Toshiba Portege Z30 only via FOG W7 installation from this tutorial. So in regard of taking the time to even create such an usefull tutorial, you have my “Thank you very much!” .
However I found an error; in part 4, configuration in FOG you have this:
Parameters:
initrd initrd http://<ip_addr_fog_server>/fog/iso/winpe_amd64.iso
chain memdisk iso raw
Using these parameters will end up in error “Memdisk: bootstrap too large to load”
I have edited parameters like this:
initrd http://<ip_addr_fog_server>/fog/iso/winpe_amd64.iso
chain memdisk iso raw
And now everything works flawlessly!
Maybe this will help to someone else as well.
Best regards,
Michal Milsimr
Organization Name: The Institute of Technology and Business in České Budějovice
Web: www.vstecb.cz
Location: České Budějovice, Czech Republic
Approximate Number of systems: ~400 and growing
How long: Implemented in May 2017
Can be listed on the Wiki.
FOG servers: 1 dedicated server
Additional Storage Nodes: None
Previous Imaging Solution Used: Ghost Solution Suite 2.0
Uses FOG Client: YES
Got only Czech logo, hope you don’t mind.
Oh, btw, I’ve read this https://wiki.fogproject.org/wiki/index.php?title=Windows_Storage_Node - just wondering, if there is workaround, which would not require to install FTP server at target machine (vserver5) and so on.
Good day everyone,
recently I was looking for a ways to hook up FOG image repository into Windows server shared folder.
I’ve managed to mount //vserver5/install/IMAGEs to /mnt/images (by editing /etc/fstab) and in FOG Storage Node settings I’ve managed (somehow) to add new Storage Node. The web GUI shows correct information about new storage node (disk usage), but that seems to be all - when I try to capture new image using new Storage Node, I am getting error “Permission denied” (unable to mount /mnt/images/dev).
Is there easy workaround? Or do I have to set permissions for //vserver5/install/IMAGEs on Windows Server 2012 R2 to Everyone / Anonymous? Or am I to take completely different approach to this problem?
Thank you for advice.
@Wayne-Workman Thank you, that’s exactly what I needed! Problem solved.
Good day,
I’ve come to you with probably the last problem I have till succesful FOG deployment a integration in our university network.
Everything seems to run just fine, will need to only increase the size of /images repository from current 70 GB to 1 TB. But my boss requested, if it is possible, to password protect entry into FOG menu and it’s utilities, so that we - IT, with proper password knowledge - can use FOG to our hearts content, but to keep everyone else outside, so that especially smart-ass students won’t be able to do any kind of unwanted damage (like erasing whole drive through GParted). Sure, I’ve read something, but I am not really sure how to approach this.
Also I would like it so that automated / scheduled operations won’t be affected by this password protection, and - if possible - I would like some easy way to this off.
Any ideas where / how to start?
Have found quite similiar topic here: https://forums.fogproject.org/topic/8780/want-to-skip-booting-press-escape-to-access-the-menu/20 but it is not exactly what I want…
Idea is; iPXE boot => login / password request => FOG Menu.
Thank you!
Good day,
issue is solved; line 060 was being used by WDS server, which is inactive for some time and we do not use it anyway. It was agreed to disable this line and so FOG server is already running smoothly - 40 GB test image deployed on testing PC within 3 minutes. AWESOME! Plus I’ve managed to integrate few utilities such as Clonezilla, Clonezilla Server Edition (or DRBL live), System Rescue CD, PMagic, GParted and AVG Rescue CD.
Will come back with other questions; thanks so far!
@george1421 Thank you. I will get to it a little bit later, once the usually heavy “morning traffic” calms down. Before that however, I have one - probably little bit silly - question; path for the saved output log of tcpdump will be shown in console, or is there a specific path to it? And in case of the latter option, where would I find it?
Thank you.