@george1421 the amount of machines vary based on what classrooms are not in use, so it’ll range from 2-300 machines based on how large the classroom’s break is.
Posts made by zacadams
-
RE: Multi-cast with Location plugin enabled
-
RE: Multi-cast with Location plugin enabled
@tom-elliott beautiful I’m glad to see I was on the right track there, we currently use Ghost and are trying to move to Fog so if this does work I will be happy to see Ghost gone.
-
RE: Multi-cast with Location plugin enabled
@wayne-workman I’ll give this a try today and see what I can find, thank you.
-
RE: Multi-cast with Location plugin enabled
@tom-elliott I know it’s really weird man hahaha, it is currently showing that both are master nodes at the moment. So our setup is a campus with multiple buildings with many hosts in each building. Our current setup uses Ghost servers in each building (I guess the equivalent would be individual fog servers instead) installed on a physical machines in closets that then multicast to the respective hosts in the building. Our network admins will only let us use multicast when imaging to machines in the building so my plan was to use location as a way to represent these buildings and using their existing ghost boxes as fog storage nodes and multicasting from those nodes. I hope that makes sense, do you think my theory is possible with FOG in this setup?
-
RE: Multi-cast with Location plugin enabled
@tom-elliott I have the remote fog storage node set as the selected node for my remote location and for testing purposes have just set that storage node as a master node as well as my default master node. So for my defaultStorage group I have 2 master nodes, I am trying to now do the multicast on my remote host tied to my remote node. The session appears to start with the remote node now but is not starting the imaging process.
-
RE: Multi-cast with Location plugin enabled
@george1421 would I be able to set my remote storage node as a master node and then have multicast session run from it?
-
RE: Multi-cast with Location plugin enabled
No, the master and storage node are in different locations.
-
Multi-cast with Location plugin enabled
I have been testing out the location plugin with my current fog setup of 1 master node and 1 remote fog storage node. During a multicast session I noticed my host machine, which is set to use the remote fog storage node, was showing that the storage location was the IP of my master node. The host will grab from the remote fog storage node during unicast session so my question is does the location plugin support multicast sessions?
-
RE: Error when creating snap-in pack to storage group
@Wayne-Workman I apologize I meant to say storage group, I figure ‘“default” storage group’ leaves enough context clues for the reader to infer that a “storage account” is a storage group.
@Sebastian-Roth thank you for the speedy response as well!
The solution to the issue was that I had to create a separate storage node to correlate to the storage group being created, and then setting the storage node to the corresponding storage group. The purpose for this was to better organize snap-ins to certain “task groups” like what is present in Norton Ghost, I hope that this helps.
-
Error when creating snap-in pack to storage group
I keep getting the error:
Type: 2, File: /var/www/fog/lib/fog/fogftp.class.php, Line: 217, Message: ftp_connect(): php_network_getaddresses: getaddrinfo failed: Name or service not known, Host: , Username:
when attempting to create a snap-in linked to my new storage account named “Activation”, but the snap-in will save to the “default” storage group. Any ideas on what I’m doing wrong?
-
RE: Sending client machine files using Snap-Ins
@joe-schmitt Thank you for the quick response, I will start experimenting with Snap-In packs
-
RE: Sending client machine files using Snap-Ins
@george1421 Thank you for the response this looks like it should work. The other issue with our system is our batch or machines are not allowed on the domain so all work must be done locally.
-
Sending client machine files using Snap-Ins
My organization is transferring from an old instance of Norton Ghost to FOG, and are currently in the process of porting old Ghost “Tasks” to FOG Snap-Ins. A lot of our “Tasks” simply transfer a individual file from the Ghost instance to a specific directory on the client machine. When looking into Snap-Ins I do not see a transfer file option and upon attempting to send a file, the file is deleted after the script has completed. Is there a preferred method for doing this using the Snap-Ins or a setting/checkbox I am missing?