imunro01

I'd certainly agree with you on that - we use FOG on any machines we can.

Or how about a Knoppix live cd. That should let you mount the drive, and also have access to utilities and common network drivers.

It's all early days yet - just investigating it as a possibility

Hi Guys, We've recently signed up for a Google Apps educational account, and are trying to provision accounts via the directory sync tool. Now, sofar we've managed to get the accounts to create/delete/suspend, along with the users names on them, and all looks well. The problem we are having is that I can't get the passwords to sync from Active Directory to Google Apps. I know the Directory Sync mentions issues with the password attribute from AD being in the wrong format, and suggests using SSO. My knowledge if SSO is non-existent, so I'm struggling to get this last step sorted. If you've done this successfully, or have any guidance on it, please let me know before I do finally tear my hair out Cheers Iain

PING 224.0.0.1 (224.0.0.1) 56(84) bytes of data. 64 bytes from 192.168.3.100: icmp_seq=1 ttl=255 time=0.475 ms 64 bytes from 192.168.3.122: icmp_seq=1 ttl=255 time=0.677 ms (DUP!) 64 bytes from 192.168.3.126: icmp_seq=1 ttl=255 time=0.685 ms (DUP!) 64 bytes from 192.168.3.121: icmp_seq=1 ttl=255 time=0.691 ms (DUP!) 64 bytes from 192.168.3.124: icmp_seq=1 ttl=255 time=0.761 ms (DUP!) 64 bytes from 192.168.3.125: icmp_seq=1 ttl=255 time=0.772 ms (DUP!) 64 bytes from 192.168.3.123: icmp_seq=1 ttl=255 time=0.782 ms (DUP!) 64 bytes from 192.168.3.109: icmp_seq=1 ttl=64 time=1.07 ms (DUP!) 64 bytes from 192.168.3.113: icmp_seq=1 ttl=64 time=1.27 ms (DUP!) 64 bytes from 192.168.3.119: icmp_seq=1 ttl=64 time=1.57 ms (DUP!) 64 bytes from 192.168.3.4: icmp_seq=1 ttl=64 time=1.82 ms (DUP!) 64 bytes from 192.168.3.80: icmp_seq=1 ttl=64 time=2.12 ms (DUP!) 64 bytes from 192.168.3.14: icmp_seq=1 ttl=255 time=3.77 ms (DUP!) 64 bytes from 192.168.3.107: icmp_seq=1 ttl=64 time=4.77 ms (DUP!) 64 bytes from 192.168.3.22: icmp_seq=1 ttl=64 time=7.91 ms (DUP!) 64 bytes from 192.168.3.4: icmp_seq=2 ttl=64 time=0.229 ms --- 224.0.0.1 ping statistics --- 2 packets transmitted, 2 received, +14 duplicates, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 0.229/1.838/7.915/1.971 ms

I get 1 packet sent and 1 received. - strangely it's one of our photocopiers that has sent the reply PING 224.0.0.1 (224.0.0.1) 56(84) bytes of data. 64 bytes from 192.168.3.100: icmp_seq=1 ttl=255 time=0.308 ms --- 224.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.308/0.308/0.308/0.000 ms

Idx Device : Count Querier Group Users Timer Reporter 1 lo : 0 V3 010000E0 1 0:00000000 0 2 eth0 : 4 V2 FB0000E0 1 0:00000000 0 010000E0 1 0:00000000 0 Does that tell you much?

We have been successfully running a FOG server under Fedora 10, and finding it most useful to be able to multicast an image to a suite of PC's Recently, FOG has stopped multi-casting, although it will still work fine in uni-cast mode. We have made no changes to our netowrk infrastructure as far as I can see. Has anyone any sggestions as to why this has occured Cheers Iain