Posts made by VincentJ

The BTSync is also still quite popular for seeding the latest updates.
Main Fog BTSync - BAU3NUY3XTKVMHHEZO6C7OH55AN2PCGJV
Fog Kernels - B7AGQ6JVIP4MF5LCRL3XURQBYC53UIS25

both are read only secrets and get updates as soon as theyre put in

VMware tools maybe. or use thin provisioning

looks more like a VMware/Linux issue than a FOG specific issue.

why do you need reservations? if your fog is an isolated network the address shouldn’t matter

iirc you could setup a NAS as a storage node without fog installed on it.

I would like to see a plugin for FreeNAS…

there are plenty of other programs to do this (silent application installs while pc is in use). I don’t use snapins in fog.

So many ways to make things faster… disk/cache/storage nodes/switches/NICs.

I try to keep my image size down by using other tools that install some applications after imaging (if they’re needed on that machine)

the upside being that the machine can be in use while the applications silently install.

Would be nice to see if someone is using 10GbE or SSD or both.

Possibly also the new features involving clients seeding data to other clients in the latest SVN might make things a ton faster.

on machines with 10/100 I would expect 500MB/minute. On my gig machines I can push 5+GB per minute to a few at a time… but if I pile on more it can throw in the towel and really drag the speed down.

Also consider checking the disk IO statistics on your drives… HDDs aren’t good at random IO, and if you have enough sequential transfers at once, it becomes random.

Not exactly solving the problem of the slow speed, but could you do twice as many with an extra storage node?

I’ve found with multiple clients there is a point at which the slowdown really does ramp up. would be interesting if someone had FOG on SSD and could see if the same thing occurred.

‘crash’ meaning what? the switches stop working?

my school FOG stays in the server room, since we’re gigabit all the way around the buildings throwing an image across doesn’t hurt anything.

could it be your fog has a DHCP server and when you plug it in your normal DHCP server isn’t giving out the addresses anymore and things like DNS etc get misconfigured?

if your not imaging why use fog?

there are other solutions around that do unattended installs using installation media.

or install the client and use an unattend.xml for sysprep.

get the PCs to sysprep with a common name and then have the client change it to the proper name and join the AD.

there was talk of including key functions in fog, but yet again. OEM licenses don’t have reimaging rights. that’s why you need a VL license to get the reimaging rights.

I would say having to go to a PC is something to avoid, and that is certainly possible. it just depends what budget is available and how much your company values time.

you want to image them or use the native windows unattended install?

Microsoft licensing is usually a pain. I would suggest you read the imaging rights pdf from Microsoft and use a volume license key to image many PCs with the same key…

An OEM key is unique for each individual PC, not every brand/model of PC.

Also if you own a single Volume License to get reimaging rights, you get media direct from Microsoft so you skip all the junk the OEMs install.

if you are using a standardised image, have a read

[url]http://www.microsoft.com/licensing/about-licensing/briefs/reimaging.aspx[/url]

it just depends how you set things up…

if you have one image per PC and you are using FOG as a backup solution, it’s different than a standard image.

it might be worth buying one volume license so you can reimage with a standard image, if you pay for tech people as it may end up saving you time/money in the long run.

Are you thinking this could replace multicast? (which has had a ton of problems)
Or possibly become the main method of distributing images?

Can the clients peer the parts of the image they have already in chunks or does it need the whole image to download to become a peer?

Is there a configurable time after the image finishes downloading on that machine that the client reboots to allow getting into the new OS, so people could have 5 minutes peering to speed up others and then reboot?

Is there a tracker/torrent file that could be added to other torrent clients? easy setup storage node…

is this the server distributing it to clients primarily or do the clients play a big part in distributing to each other now?

if you want the latest updates you could use SVN or BTSync

BTSync Secret - BAU3NUY3XTKVMHHEZO6C7OH55AN2PCGJV

It may not be specifically named 1.3 but it does have lots of changes happening every day.
Additionally with BTSync you get changes sent to you almost immediately and it even shows which files were changed.

performance can depend on a great many things.

I run fog in a VM, and I can throw data out at speeds where I can image a PCs in 10-15 mins. multiple at a time.

the client gets the workstation to join.

I wouldn’t bother with a dedicated network… are you imaging that often or your network so slow that imaging would hurt it?

much more bother having to pickup a PC and take it to the other network.

I’ve got 150+ machines and not had problems relating to the network. just some really brand new machines not liking booting anything except windows 8…

there is a thread in the hardware section on which hardware works…

I have had machines that worked even on 0.32 that had UEFI. try and find out.