@Tom-Elliott Perhaps @StefanTS does not want to set this testing software as the default item for all the systems in his environment? Perhaps he only wants to set it for a specific group of computers. That’s what I was asking.
@Toby777 I’m guessing that the images you want across groups (Melborne and Sydney as of right now?) are setup to be a part of the groups, for example an image named win7 is setup to be in both groups? The only change that I can think of is I made what I am calling the “primary group”. The idea of this is to help ensure the images are replicated and done so properly. Without a primary group both side could potentially wreak havoc on trying to replicate the data. Think of the issue like this:
Melborne win7 image is freshly updated and you want the image replicate to the Sydney group. Sydney’s image replicator is in such a way that the replicator service runs before the Melborne replication service. Because Melbornes image is different, the Sydney image starts replicating it’s version of the image file which would delete the current one you uploaded. Now your fresh image is no longer proper. This is easily fixed by simply making one group the “main” group. Yes it does mean if you have Sydney as the primary but want/need Melborne as the primary due to the update that you would need to change what the primary group is.
Sorry about the long winded post but I felt giving all the info I can think about for it, it’s make a bit more sense.
Report bugs, request features, or get the latest progress.
@ITSolutions The Task Manager shows the task as queued. I think the MAC is correct, because if I reboot the machine manually it images as normal.
This morning, I migrated from Fedora 21 server to Fedora 23 server.
I moved over the public & private SSL certificates and CA in /opt/fog to the new server. I moved over the images. The new server uses the same IP as the old one - but has a different name. The Legacy clients in the environment were installed using the IP. I’ve created a DNS A record for the server’s name along with a corresponding PTR record. I exported/imported the hosts and images also, not the entire DB - I didn’t want to bring over all the old data.
Just me and another guy uses our building’s FOG Server, and the other guy didn’t change the MAC. FOG is sort-of my baby in my building.
I’m still mostly using the Legacy Client because I felt the new client was not ready when I was making all of the images I needed - that was in May & June this year. I know it’s come a long way and is pretty solid, and I do want to move to the new client but I don’t have a strong reason to do it. I only need three things from the client on Windows - rebooting, naming, and domain joining. The Legacy Client does those three things fine on Windows Vista through Windows 8.1. If the @Developers chose to discontinue support for the Legacy Client, naturally I’d move to the new one. But you understand how it’s not pressing to me? Testing is going on in my building and I will not do any software deployments during this time. For my particular situation and needs - I think it is best to move to the new client via imaging instead of all at once.