Posts made by RobTitian16

@theWizard I can confirm my location was also left blank for the system I was trying to image with Tom earlier. Perhaps this is the culprit?

@Tom-Elliott This FOG server only has the default storage node, and the web gui does say it’s there. When browsing to /images/ I can also see it listed (can provide screenshots of anything if it helps).

@Tom-Elliott Still the same, unfortunately, even after going through the steps suggested.

@JJ-Fullmer When does RC22 go live? I’m currently running into this issue as well.
I tried updating but I’m still on RC21 and I attempted to use the files mentioned in the link to no avail.

@Wayne-Workman Just one final thing on this: would the replicated images on the US server show that they’ve been updated at all?
For example, if I’ve updated an image here in the UK, then see the replication has finished comparing and matching the files, should it say anything when looking at the image in the web gui (i.e. last updated) on the US server? Or do you just purely go by the replication log?

@george1421 Very interesting - thanks for posting! It definitely helps to see it like that.

@Wayne-Workman Thanks for explaining
Everything seems to be working as expected now so hopefully I’ll be seeing the new image on the US server shortly

@Tom-Elliott Indeed, that all does make sense. Many thanks for your help! I can see the replication is going across perfectly fine.
One thing to note: I had to use the local account and the password for the ftp access, instead of the username and password listed in /opt/fog/.fogsettings (which is what it says in step 12 of https://wiki.fogproject.org/wiki/index.php?title=Managing_FOG#Storage_Management).

@Tom-Elliott Ahh okay, thanks. I’ve changed it to the master node now for that group, so I shall wait and see what happens in that case.

@Tom-Elliott Yes, on the UK server the images I want to replicate belong to the primary storage group called UK, and a secondary storage group called US.
The US server is listed as a storage node on the UK server, although I’ve just noticed it isn’t listed as a master node. The UK server is in its own storage group, as is the US server, so I assume all I need to do is enable the US server as a master node and it should then work?
P.S. sorry if it seems like a dumb question… I just don’t want replication to occur the wrong way/have the images wiped.

@george1421 The US server is a full FOG server, but it’s listed as a storage node on the UK server. The only storage nodes on the US server are its own.

@Wayne-Workman Thanks for this, Wayne. Is it normal to see:

[11-01-16 9:14:18 am] | Image name: Win7Clientx86
[11-01-16 9:14:18 am] * Found Image to transfer to 1 node(s)

On both the master node in the UK and the US storage node? I can’t see any received data on the US FOG server, so I’m concerned that the replication is not working correctly.

@Tom-Elliott Nice - thanks!

@Wayne-Workman Perfect - thanks for this!

Server

• FOG Version: 1.3.0-RC-16 (5983)
• OS: Ubuntu 14.04

Description

Hi all,
I’m currently having an issue where my settings aren’t showing up after being imported.
To give you some background, I copied my UK FOG installation to an external hard drive, sent it to our US site, and have configured it as a storage node for our main UK FOG server. During the time it was in the post, I configured snap-ins, AD settings, etc. on the UK server and now want to export them and import them into the US server. When I do so, however, it says there are no results found when trying to view all snap-ins, despite the import page saying:

I’ve checked on here already and can see it seems to be a common issue at the moment. I’ve updated to the latest version of FOG on both servers with still no joy. Have I missed a step somewhere?

@Tom-Elliott Ah that makes sense. Thanks for clarifying!

Thanks, Wayne. I’ll test this out shortly and report back my findings

@Wayne-Workman Just an update on this: I tried running the script again after adding an image (the FOG web gui said it was image 31), but the script didn’t appear to run at all - there was no output as before. As a workaround, I had to set the image ID manually, but is this a known issue with the script?

@Tom-Elliott Yeah, I thought it would come down to naming the snapins appropriately. In our case, I think most like to know what they’re signing up for. As such, I’ll just create a document for them to follow and then answer any questions that do come up from it.

Thanks for the help and assistance!