Posts made by Lethal Kebab

I think your fog “server” is on it’s last legs… If you catch my meaning.

Are we talking faster imaging times here?

[quote=“TJ333, post: 12747, member: 793”][FONT=book antiqua][SIZE=3]That did it. I tried using sc config “Fog service” start= auto before but I added it to the run in GUI section of sysprep to try and get it to run. That does not work. What does work is creating a separate batch file to enable FOG and have sysprep call the batch file. [/SIZE][/FONT]

[FONT=book antiqua][SIZE=3]Thank you for the help.[/SIZE][/FONT][/quote]

Can you please let me know how you are automating the driver install?

[quote=“jose Santana, post: 12996, member: 7634”]this may seem like a dumb question but I’m new and willing,to learn. I’m fairly new to Linux and mostly do hardware. is the ip address that we just assign to address(192.168.3.3) , is that any class c ip address that we just give it? netmask seem to always remain the same as (255.255.255.0). IM sorry just a noobie willing to learn. hopefully other can relate to this discussion who have similiar issue.[/quote]

The IP address you give the server is up to you so long as it’s an address that fits on your network and is accessible across your network and make sense for you.

For instance, if all your servers are on 192.168.3.xxx vlan then you would put your fog server on that same vlan just for administration sake, as sometimes only server vlans are tagged across a network and traverse vlans to supply a service to the client computers on other vlans.

There is no hard and fast rule, however assigning an arbitrary address could have unforeseen consequences if your switching or networking environment changes.

Sandi, I think that means that their task has been created by the auto-reg process. Did you associate an image to the auto-reg process? Then send it another image task?

[quote=“chad-bisd, post: 12991, member: 18”]You’ll have to figure out the Wake-On-LAN issues. You have to have a compute capable of doing it. Not all are. Check the bios for enabling wake-on-lan. Even then, wake-on-lan only works if you do a soft shutdown of the computer. If you hold the power button down or unplug the power, most systems will not wake.[/quote]

That is correct. WOL only seems to work if the computers were shutdown via windows shutdown process.

Is it on the same vlan?

If not, the vlan that fog is on might need to be tagged in your switches to allow access across other vlans.

Bump

Austin

The only time I see issues in my fog server is when it’s getting thrashed by 10 or more active tasks at once. However pxe boot still happens but VERY slowly.

What type of computer do you have fog installed on? And what message do you get when pxe fails to load?

Hi Guys

Just a quick not to see if anyone can assist…

Every time I try to pull up an image of windows 7 on a single partition, it gets detected as raw, and FUBAR’s my image and I have to re-install windows.

mind you … this is the first time I try single partition resizable, I have always done multiple partitions etc… but im trying to form better imaging habits and heading closer to generic windows 7 images deployable on any type of hardware.

anyone ever encounter this? what did you do to solve it?

Thanks!

Kamran just out of interest, can you resolve “fogserver” from any location? or only by IP address?

Hey Trevelyan

Multicasting works as fast as the slowest link in the chain.
Imagine my disappointment when we just finished rolling out a brand new network infrastructure using HP 5406zl Switches with 10gb fibre connections between locations, only to find that a multicast of 30 computers resulted in a 500MiB/min speed in a room directly connected to the core switch!!!.

I tracked it down to one computer on a dodgy patch in the wall and presto!!! 4.01GiB / Min

So a few things to check.

1. Does your switch support IGMP Snooping (if not, then the slow down can be from flooding the VLAN with traffic to every nic connected to it and awaiting the packet drop)

2. Do you suspect any of the PC’s you are imaging to has a dodgy connection or NIC?

there is no reason why multicast should not work as fast as unicast all things being equal.

The best way to get fog project churning out updates and bug fixes and new versions is if we contribute to replacing the developers 9 - 5 income and pay them to develop FOG as a full time, mortgage paying, car buying, life living job.

other than that… as a community we should be grateful that we even have 0.32…

I have just started receiving the above issue. My Multicast reaches about 50% at 4.01GiB/Min then hangs completely. I see a message in the multicast log saing:

Bad command 0300
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=106672

then

Dropping client #0 because of timeout
Disconnecting #0 (192.168.3.85)
Dropping client #1 because of timeout
Disconnecting #1 (192.168.3.170)

gzip: stdout: Broken pipe
Udp-sender 2007-12-28
UDP sender for (stdin) at 192.168.4.2 on eth0
Broadcasting control to 224.0.0.1

We recently upgraded all our switches to HP ProCurve 5406zl and I think this error has something to do with IGMP Snooping, not fog…

Multicast log shows:
–mcast-data-address 239.168.4.2

anyone else had any experience with this problem?

An essential feature, not sure if its possible, is to provide more information on imaging progress in real time. If its even possible, a replicated screen of what the host looks like.

Currently, im getting plenty of exercise walking from one building to another to check on the progress of my multicasts and unicast jobs.

Id like to see real time stats on the job. ie:
Multicast Task - 3 out of 10 joined
Max Wait counter: 4m32s remaining until auto start
link speed: xxGiB/Minute
Tx: 0.00Gb

etc etc…

did it get the DHCP and connect to fog?
also, do the tasks still show up as pending tasks in the task manager?

take a look at /tftpboot/pxelinux.cfg folder, do those mac address’ have files that start with 01-<mac address> ??

This might sound silly, however, i think fog needs a windows client that can be installed on the admins computer and used to control fog.

i know there is a web ui and that is cross platform etc, but there needs to be more information added to the ui and it needs to look the part.

ok… i agree with all those changes / requests… however i think 9 is currently possible. I believe you would need to modify the init.gz to include what you want done… so for example, i use debug-deploy to change the MTU size to 9198 to take advantage of jumbo frames then launch fog from the command line to start the image.

I am seriously considering modifying the init.gz to make this happen from the standard fog process of deployment.

from a programming point of view, I think it is possible to give it steps to do, you would just end up with a heavily customised fog installation which would be useless if you went to upgrade to support new hardware / software…

YuYo

if you include tight or tiger VNC in your images, you can modify your PHP code (i do this on the host search and display section) to include a link to popup a new window with address “<computername>:5800” this loads the tight vnc client and you have just RDP’ed to the host.

google javascript code to open new window and modify the php to make it work.

I have created the same thing, except via snapin on the client computer. Its a simple VBS file that reads the registry.
I have also included a windows update management capability in 0.32. steps generally are:

1. Add required table to database ie: software inventory table (relevant fields)
2. make change to php code to display option to show inventory (i do this on the same page that displays host information)
3. create VBS to import registry values for software installed.
4. Schedule a snap in task to refresh the list every day.

with windows updates its pretty much the same process, however there is more modification of the base php code to allow for update authorisation etc.

happy to post up the VBS files that i have used and screen shots.

but i agree, it must be made native in next version of fog.

perhaps Fog can start downloading windows updates and assisting with their deployment natively like a local repo.