Posts made by Lee Rowlett

you need to setup a ICMP Rule (Solution 2) - [url]http://www.sysprobs.com/enable-ping-reply-windows-7[/url]

turn off FOGImageReplicator Service manually (/etc/init.d/FOGImageReplicator stop)
and then set a crontab to run the command to enable it at 6pm and then use crontab again to turn it off at 6am…

sudo -s
crontab -e
add this at the bottom of the file:
0 18 * * * /etc/init.d/FOGImageReplicator start
0 6 * * * /etc/init.d/FOGImageReplicator stop

Hi PatinMT,

FOGServer does but if you set it up as a Node it will not unless you modify the installer for node installation. Might be worth doing so if you have future setups?

Well done in solving your own issue and posting the solution.

Hi Pat,

yes the files are based around on the 0.31 code, i haven’t yet changed it to 0.32 because there were so many changes being made, it seemed sensible to wait for 0.33 to be released and i will then re-code the location patch etc for 0.33.

@Syluspilot

DNS A record would only work if each site had it’s own local DNS wouldn’t it? however atleast 75% of our sites use the DNS from our main office (or atleast the DNS records are replicated). but i do like the concept of your approach

try to unmount and remount the pxelinux.cfg share

umount /tftpboot/pxelinux.cfg
mount /tftpboot/pxelinux.cfg

the roaming issue has never been a problem of ours because we use FOG purely for image deployment. Software rollouts, Windows Updates, Printers etc is handled by other products, so unless the machine needs to be re-imaged this issue doesn’t crop up an we are in the habbit of confirming location before kicking off the image.

oh and image replication is set only to run between 6pm - 6am snapin changes are set to sync every hour, the first sync is quite heavy, but that’s done on the “Build Area” when the storage node is being setup and the FOG Server pushes our a script that looks for the installers which are copied from the relevant node just after the image is deployed before it boots up to sysprep. so the installers are running locally to the machines also.

Option 3 is how i have our infastructure setup. we have 55 sites, alot of those are branch sites and only have VPN links, We have the FOG Server on a VM on our server scope, a Master Node in the “Build Area”, which has it’s own 1GB switch/scope so uploading and downloading images,snapins etc is quick, and another Master Node at our failover site and rsync and crontab syncs down the changes to the relevant sites, dependant how they’re routed (Main Office - Branch Site). Works extremely quick, Build Area Gets 4-5GB/Min Deployment and the others are 1.4-1.5GB/Min… All data is transferring on site, Images, snap-ins, tftpboot etc… the only traffic going across the VPN is reporting to and from to the FOG Server to kick off the image etc…

See tutorial [url]http://fogproject.org/forum/threads/requested-multi-site-location-patch-requested.410/[/url]

[SIZE=3][B]Please be aware this is patched for 0.31[/B][/SIZE]

i would like to see maybe a progress bar or be able to send detail to the gui like what stage of the script it is installing if it is a multiple software install script… I.e Installing Adobe… Then Installing Java etc. etc…

Hi karlfp,

i’ve only just come across this post, sorry otherwise i would of transferred some instructions on the location patch. the only thing is, this is going to need completely re-writing to work with 0.33 but i was just waiting for blackout to get 0.33 released and then post the patch to correspond but looking at the changes it may even be easier than actually patching the core files.

This will be the problem then mate, I’m pretty sure WinWaitActive only works when there is an active session as it’s interactive.

oh, sorry didn’t realise you were controlling the script with WinWaitActive… do you see the install start at all? where is the msi located?

Hi bigjohn322,

your problem maybe due to the fact the autoit script is exiting before the msi completes but because the autoit script is “complete” by running the msi close and send the exit code to FOG. try ShellExecuteWait, this will wait for the msi to complete and then close the autoit script. if not try to run the msi using runwait.

Hope this help