@Wayne-Workman

The devs are still busy folks…

From the RC4 change log

Fix multicast issues for the fog service. Fix multicast not closing on task cancellation from active tasks page (hosts are being untasked but session still exists.)

From the RC3 change log
88197b5 Update Version to 1.3.0-RC-3
f31b852 Merge branch ‘working-RC-3’ into dev-branch
3fd5ff3 (origin/working-RC-3, working-RC-3) Enable snapin location altering or not via locations.
58709a1 Update iPXE files to latest pull.
b1f9240 Add back the 7156 efi files for ensuring surface pro’s can still boot.
a9652be More accurately display multicast and don’t create a tasking, but do report why the tasking couldn’t be created.
99ef87a Make sure only multicast sessions that have a defined session client count are able to be used for multicast session joining.
627348c Use the fullPath variable for the multicast task.
363ef28 Ensure multicast continues even if the file cannot be found. Otherwise it will fail for that node and nothing after that point will run properly.
3cf50e3 Properly link progress row with it’s task.
67d5ebe Fix issue with multicast sessions being cleaned before they’re even booted.
2b692a7 Fix issue with printer memberships
289524f Fix getting the snapin job variable as there was a typo.
98921af Add expand-child element to the progress row.
ed70684 Make sure version is incremented
3eae96c Remove accesscontrol plugin
8327f66 Make fog configuration use ajax for kernel versions.
a8acad2 Address issue with nodes blocking load of the page.
3f38ef8 Make sure suf variable in javascript returns if suf is null
5158f67 Fix upload last time not setting.
f2d8d72 Fix split call.

For those of you that may have tried this with CentOS 7, re-pull and it’ll work now.

This works with:

Debian Ubuntu Fedora CentOS

Confirmed and fixed. Will be available for rc 3

@Tom-Elliott

No problem!! 🙂

@george1421 I’ll try with the Quick Image first and if it does not work I’ll look with this methode more deeply.

@Wayne-Workman I keep these solutions in mind if Quick Image is not for me.

@Tom-Elliott Ok, I will upgrade the server to try this.

Thank you all for you replies ! 🙂

@ITSolutions @Tom-Elliot

Thanks for that info. I’ve been a few revisions behind in my prod and nonprod servers. Just got around to doing that today at the recommendation of Tom.

@george1421 said in Master -Master Replication:

Right now FOG doesn’t have a real good way to limit what techs can do at each location. For example we would only want IT techs at site A to be able to image machines at site A and not site B. As well as the other way around. If you had FOG setup to automatically PXE boot into FOG, techs at site A could accidentally reimage a machine at site B.

Sounds like a great opportunity to solve a problem, to me. I could write a PHP service that would just undo any tasking that a tech does at a wrong site. In fact - I can write a stand-beside fog thingy that will let you assign locations to fog users. It can be a non-required extra field in the users table, and won’t affect FOG functionality.

At work, we don’t have problems with bandwidth between sites. It’s 1Gbps throughout 23 buildings separated by miles each. But we do have a potential problem with is techs doing things they shouldn’t be doing.

Update please. I fixed this already. I’m adding more implicit text as well, but i noticed and corrected this.

@george1421 I was simplying using mount -t nfs, no other modifiers, so yeah, specifying the protocol is probably what does it.

Still much to learn about Linux and such, heh.

@dolf Sounds really strange to me! I’d suggest doing the reverse test. Pop that HDD back into the other PC and see what WOL is doing?!?

If the CloneZilla image is not compressed, it will not have the .gz extention (easy to check for), and the last command becomes:

cat /home/user/czimg/sda2.ntfs-ptcl-img.* | pigz -stdout > /images/fogimg/d1p2.img

If CloneZilla was invoked using dd, we can concatenate and pipe to partclone:

cat /home/user/czimg/sda2.ntfs-dd-img.* | partclone.$fstype -fsck-src-part -c -s - -O - | pigz -c > /images/fogimg/d1p2.img

etc… There might be a few more cases to consider.

Thanks! I’ll take a look see. 🙂 I found the Wiki on Hooks. I’ve worked with PHP before in the past but it’s been many many versions ago.

@Joe-Gill How is it better to do it manually, when powershell can do the same identical thing but faster and in mass and without visiting each computer? It’s simple:
Remove-Computer -UnjoinDomaincredential Domain01\Admin01 -PassThru -Verbose -Restart
https://technet.microsoft.com/en-us/library/hh849816.aspx

Only thing to remember is to definitely delete the snapin after you’re done with it, because it’s associated it’ll run every time you image - which would cause problems.

@Joe-Gill said in SOPHOS Cloud - Duplicate Names:

@george1421 Thank you!!

My google-fu is strong today.

I did not see that there was a dedicated tasks section. I’m still learning to find my way around the web GUI. The issue has been resolved, thank you!

@Tom-Elliott Oh well now I just feel silly! Oh Well, all is a good learning curve, and a good introduction. It helped me understand what was going on behind the very well laid out GUI! Im very impressed with this product and cant believe its Open Source. I am going to make a business case to the FD for some sort of donation. I work for a charity, so who knows how well that will go??

Nonetheless, it was all very interesting!

@george1421 Alright, so here’s what I’m going to do.

I’ve got an old PFsense box that I set up to handle DHCP, and it can hand the clients off to FOG. This will happen on a separate subnet on the FOG servers second NIC. I’ll still be hooked up to the core network via the first NIC for easy access and management to the box.

This way I can have my unmanaged switch, and be open to multicasting.

Now that it is an option, it kind of goes back to my original question; if I’m going to image via multicast, my understanding is that it takes some setup, with making the group and registering hosts. I won’t be able to use quick image for this will I?

Thanks for all of the useful replies! We’ll use one of these iterations for our inventory when we start deployment in the next week or two.

Cheers,

Joe

@adukes40 You can only limit the number going at once for unicast as @Quazz said, not the bandwidth. The bit rate is a throttle for multicast. The replication rate is a throttle for replication.

Multicast only works from master nodes. Enable broadcast forwarding on your router and it’ll start working at other sites. You have to enable the same thing for WOL to work at other sites I believe, there’s a plugin to assist with WOL.

yeh svn info worked.

im on 5721

Many thanks