Welcome to the community forums for Theopenem. All responses are provided by other users that wish to help out. Theopenem will not respond to these posts. If you require more assistance than what the community can provide, we offer various paid support options.

  • Is there way I could setup TOEMS to utilize 2 separate LANs, but share the same image files?

    We have a Lab LAN and a Staff LAN that are not directly connected for obvious reasons, but I would like to have the ability to clone PCs from either network and share the image files so I don't have to store them on 2 seperate servers.

  • Can you put your Toems server on both networks with 2 nics?

  • This I can do, I would also want to have PXE booting for both using Proxy DHCP. We have been using Clonedeploy for quite sometime and I have not been able to figure out the finer details of how to make this work across both networks, so I am seeking advice before installing TOEMS and moving our operations to it.

  • This is a fairly complicated topic and seems worthy of a video tutorial. I'll create one in the next few days. I think it would be beneficial for others as well.

  • Awesome! I look forward to it, I'll keep an eye out for it.

  • I started looking into this to see if it was possible. It is possible to do this with a single server but only if you do usb boot. If you want to do tftp boot, you would need to create another com server on that other network. Everything would still function as a single system but you would need to have two servers, either physical or virtual. What type of video tutorial do you want, if either?

  • I was kind of thinking that might actually be the case, so my plan and this instance is to take one server as a hypervisor then I could set up the two or three servers I need on that one physical server.

    So I would say that demonstrating how to set up multiple servers and one Central storage location would be the focus of the tutorial.

  • This is great, I'm going to get started on this, thank you for doing that.

  • let me ask this, do you think I could have the setup like you explained, but instead of adding one of the Com servers to the other network, have a VM only network between them for their communications?

  • You would need a com server on the other network so the computers on that network could communicate with something. For all of the theopenem servers to communicate, a vm network is fine.

  • That's what I was thinking, the Com servers would need to be directly on the subnets they service, but communications between them didn't necessarily have to be on one of those subnets. I would think that should also keep the image file "sharing" from using the actual NIC, and just use the internal net to access that info.

  • It would be slightly more difficult to do it this way, you would need to do it through a FQDN with different DNS. For example when a com server is defined, the url is used for communication from both the clients and the server. If the com server is defined as, then the server will communicate with it across that network. If you use a FQDN then the server and client could reach that com server through different ip's.

  • so on the replication, does that truly mean it copies the image file to both servers or is it just updating that it is available? I would like to have the image files stored just once but available to both com servers for cloning on either subnet.

    If it is making multiple copies, would maybe a third server for SMB storage prevent that and accomplish one file for both?

  • It's actually copying the image to each com server. It's by design and can't be changed. It's done this way so the clients only need to communicate with the com server and nothing else.