You may need a bios update, my windows 7 machines needed an update in order to turn on the functions for WOL with Windows 7.

I know you probably don’t need all of this but give your settings a review, this is a walkthrough I set up for some of the things we use in our corporation, like PXE boot and WOL.

[SIZE=3][FONT=Times New Roman]How to Enable Windows 7 WOL (Wake on Lan)[/FONT][/SIZE]
[B][SIZE=3][FONT=Times New Roman]WINDOWS 7[/FONT][/SIZE][/B]
[SIZE=3][FONT=Times New Roman]Right mouse click [U]My Computer[/U] and click on [U]Manage[/U], then [U]Device Manager[/U] in your left panel. Find [U]Network Adapters[/U] and expand it to reveal your Network Card, right mouse click your network card, and click [U]Properties[/U], then the [U]Advanced[/U] tab.[/FONT][/SIZE]

[SIZE=3][FONT=Times New Roman]Energy Efficient Ethernet - Enabled[/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman]Shutdown Wake On Lan – Enabled[/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman]Wake on Magic Packet – Enabled[/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman]Wake on Pattern Match – Enabled[/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman]WOL & Shutdown Link Speed 100 MBPS (Only if you have problems getting the computer to receive the packets)[/FONT][/SIZE]

[SIZE=3][FONT=Times New Roman]Now click on the [U]Power Management[/U] tab.[/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman]Check “Allow the computer to turn off this device to save power.”[/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman]Check “Allow this device to wake the computer.”[/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman]Not necessary but if problems persist, check “Only allow a magic packet to wake the computer.”[/FONT][/SIZE]

[SIZE=3][FONT=Times New Roman]Boot into computer bios[/FONT][/SIZE]

[B][SIZE=3][FONT=Times New Roman]BIOS[/FONT][/SIZE][/B]
[SIZE=3][FONT=Times New Roman]Click the [U]Advanced[/U] tab[/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman]Choose [U]Integrated Peripherals[/U] and press enter. [/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman]Lan Rom Option – Enabled[/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman]Press Escape[/FONT][/SIZE]

[SIZE=3][FONT=Times New Roman]Choose [U]Power Management[/U] and press enter. [/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman]EUP 2013 – Disabled[/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman]Power Loss – Last State[/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman]Press Escape[/FONT][/SIZE]

[SIZE=3][FONT=Times New Roman]Choose [U]Wake Up Event Setup[/U] and press enter.[/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman]Wake up by – BIOS[/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman]Resume from S3 by PCI/PCI-E Device – Enabled[/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman]If you are STILL unable to get magic packets to wake computer, log back into Windows 7, go to [U]Control Panel,[/U] click [U]Programs[/U], click on [U]Add or Remove Windows Components[/U], place a check next to [U]Simple [/U][U]TCP[/U][U]/IP[/U] allow to install and reboot.[/FONT][/SIZE]

How are your settings set up for your virtual machine? Were you able to get to web pages and ping hosts from the virtual machine?

You need an IP address before TFTP can do any good

I have only used pxelinux.0 in place of the file name, it should be all you need.

Take a look at your card settings for you VMWare machine, my bet is something isn’t jiving.

Fog will register the Host with the AD if you enable the ability.

Windows 7 joins to the domain without requiring netdom.

I image windows 7 pro 32 and 64 bit using sysprep. I do not use Fogprep, as it’s not required with Windows 7 and FOG 0.32.

These are the steps I used to get it working:

1. Run FOGCrypt on a windows machine to encrypt your password.
2. When you install the FOG client, make sure to enable the hostnamechanger portion
3. Enable the hostname changer portion on the FOG settings of the server.
4. Input the AD join information in the FOG settings. I use domain\username for the username. Password is the encrypted password from step 1. Domain is the FQDN of the domain, like my.domain.com
5. Make sure the hosts are setup to join AD in the Active Directory menu item on the hosts screen.

After you do this, image a client. It should boot to windows, rename, reboot, join domain, and reboot. I do not use FOG to put client into a specific OU, just the default Computers (which you can redirect I hear, but have no experience). After computers join the domain, I put the computers into specific OU’s and groups for policy and management.

from chad on

[url]http://fogproject.org/forum/threads/adding-imaged-host-to-domain-and-renaming.4313/[/url]

Make sure the user that you use has delegated control to join/delete computers on the domain. Hopefully your not using the Domain Admin account. We use Domain\user for the username too or else there is an error.

There are AD settings in the Other Information -> Fog Settings page. There is a setting on the same page to globally enable the host name changer service globally, but it is a duplicate of the FOG Configuration -> Host Name Changer option. In the FOGClient config on the host, you can also enable/disable the host name changer service.

One thing to remember is that if you want to boot via WOL you need to shut the computer down by the OS, or a WOL Manager.

Thru extensive research, my colleges and I have noted that our problems with WOL not functioning out of any product (we use a product called DeepFreeze that locks our computers in a “frozen” state and changes do not stick, with it I am able to reboot my machines, shut them down and start them again in the morning.) the problems came back to the end user using the power button to physically turn the machine off. The OS can not tell the BIOS to keep the card active, if the OS doesn’t know it’s going down.

Just something to keep in mind while you are troubleshooting.

At least this is true to all 19 different models of computers across my scope. My units all use some variation of RealTek networking cards, and I am not sure if this has something to do with it.

I too am hoping for a better way to manage WOL thru FOG.

Awesome, glad you got it going!

That is the server edition not the desktop edition, which is what I previously posted. Yes you will need to do it via the command line.

try this

sudo vi /etc/network/interfaces

For the primary interface, which is usually eth0, you will see these lines:

auto eth0
iface eth0 inet dhcp

edit it to something similar to this

auto eth0
iface eth0 inet static
address 192.168.1.100
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1

save and exit.

sudo vi /etc/resolv.conf

On the line ‘name server xxx.xxx.xxx.xxx’ replace the x with the IP of your name server. (You can do ifconfig /all to find out what they are) save and exit.

You need to also remove the dhcp client for this to stick

sudo apt-get remove dhcp-client

now restart networking

sudo /etc/init.d/networking restart

after you log in are you presented with a graphical interface or are you presented with a command line?

I’m going to assume this is a desktop install and not the LTS install.

Click the “Dash Home” icon, in the text box at the top type “Network” and select the first icon in the list displayed as “Network”. Select Wired and click Options. Select the “IPV4 Settings” tab and change the method from Automatic to Manual, Add, and supply the server with a proper IP address and information. Click Save. Your connection will reconnect.

what linux version did you use to install fog with?

Man you are a scripting machine thanks for sharing these with us!

[quote=“IT @ CC, post: 12221, member: 252”]We installed our Fog Service on the image.[/quote]

Thanks for letting me know this works I was kind of sweating it and up in the air about installing it before or after imaging.

Sorry I never got around to looking at my Virtual box I’ve spent all week in the attic running networking cable!!! did you get this resolved? I can try to get a look at the box Monday.

Windows 7 is supported by Fog, there is even a FogPrep included if you visit [url]http://serveripaddress/client[/url] download and run.

Not wanting to complete the upload process could be a number of problems, do you have other hardware available, are you able to fog and upload them?

How do you have your image registered on your Image Management section? Did you set the partition type to “Multi Disk - All partitions (no resize)”? Try this. Others have had success by choosing “Vista” as the OS type as well.

Sounds like a VB problem, and you shouldn’t do Virtual images for pushing from Virtual Box, at least form what I am told.

We use VMWare for our virtual images, I was told that it works better (?) I don’t know if there is any truth to this I am still very new to VMWare, but I have been scolded by many for using VirtualBox. I was told that with VMWare you can inject drivers and then sysprep so it can grab drivers during set up. I have my images made but I’ve not pushed them to FOG yet or to any physical box to try it out.

[B]HOWEVER,[/B] I have used VirtualBox to get my feet wet with sysprep and uploading to FOG and I have had success. The problem you might be running into is using the RAW format to upload to. I ALWAYS set my images to a Multi Partition. Try going to Image Management and changing the disk type to “Multi Partition - All Disks (Non Resizable)” and see if you are able to get past it PXE boot.

If not change it back, no harm no foul.

I will look into my VirtualBox settings and see what I have set up. Good Luck in the mean time!

Please post it, it would be beneficial to all!

1.) It’s like you told me, i had choosen Single Partition instead of Multipartition but why is there this resize Problem?

[B]I’m not exactly sure why there is a resize problem. I’m not exactly sure what the “resize” option even does. All the images I have worked with so far have had multiple partitions, thus makes them non resizable?[/B]

[B]Anyway. It won’t cause problems as long as you start with your least ammount of space drive say something 80Gb and you want to put your image on a 100GB drive, you will still have all open space. However you can not use a larger drive and go to a smaller drive. This is true with Clonezilla aswell.[/B]

2.) Is this a behaviour of partimage?

[B]The resizing? Or having to choose multipartition? If it’s the later, it is because your MBR is technically stored on “another partition” that is hidden. If you use a program like Partition Magic you can see all the partitions.[/B]

[B]As far as the resizing goes, I only know that when I use a resizable option, I get errors.[/B]

3.) If i choose Multipartition will the image blow up?
[B] Lol, no. Even if there is only a single partition, Multipartition is a good idea in case there is a hidden partition.[/B]

4.) Means will it also save null data?

[B]You mean like over write empty space? No, it will still have your free space, it will only occupy the space that has data written to it.[/B]

Anyway null data should be hardly compressible but i need to understand how exactly that works.

5.) It’s unlikely that a computer get a smaller hdd then before but lets say it’s a bigger hdd what about the additional hdd space will it be allocated or leaving blank?

[B]It will allocate the space to the partition, but it will leave the space blank for you you write to. There will be no problems when upgrading to a larger drive only when downgrading to a smaller drive.[/B]

6.) When last it’s the same like the MBR thing in Single Partition mode, rework have to be done to blow up the partition size i hope increasing will work automatically?

[B]Increasing a hard drive size will be automatic, it will read the drive and give you the free space.[/B]

7.) What about changing a hdd against a ssd this is a case a storage medium went smaller, what would you do here? Making a single partition image, restore, fix mbr?

[B] This is something I honestly don’t know. We don’t work with SSD but I imagine it would be similar. If you are familiar with a process using another imaging solution to “fix” going from a larger drive to smaller (when you are not using the max capacity of the smaller drive) I would attempt it here. Not in your working environment but maybe as a test to see how it turns out. If you find a way that works please share with us all :)[/B]

Hope this helps, I answered these questions to the best of my ability. If someone knows more about the subject hopefully they will chime in

If you select “Multi Partition - All Disks (Not Resizable)” or “Multi Partition - Single Disk (Not Resizable)” under image management it will copy the MBR and all partitions.

I’m sure it is possible to write fixMBR as a snapin, but I have no experience with snapins at the moment.
Yes running the fixMBR on each machine would be taxing.

Just edit your images to reflect the changes and push your upload again, this should correct the issue and any units imaged in the future should not need to be “fixed”.

I can not promise that downgrading will solve your NAS issues. I recommend downgrading to 10.04 if you do not like to restart the TFTP-HDA service after each reboot. The command can be scripted and I am waiting for a reply to see if we have a resolve for this.

All functionality of FOG is available with newer revisions of Ubuntu, but starting after 10.04 Grub was changed and a few other things causing TFTP-HDA to start before the machine has the opportunity to get and IP address, and this causes your TFTP-HDA to be unreachable until you restart the service. I hope I’ve made this as clear as possible.

Any NAS problems, I would start by first making sure that the users have the proper permissions to the space you are trying to save to.

Awesome I’m glad you got it!

What was the resolve? It’s nice to let others know how you solved your problem if/when they use the search feature!

Go to the Storage Management section. list all storage nodes and select the one the one that is being used (in my case it was the ‘default member’).

Check the username and password there and make sure there is a corresponding user account on the fog server with the right access priviliges on the images folder shown in fog managment.

In my case it was set to username ‘fog’ with a very long password. I don’t know how this ended up as ‘fog’ instead of ‘fogstorage’ but it appeared to have been configured with some randomly generated password.

[url]http://fogproject.org/forum/threads/ftp-connection-to-storage-server-has-failed.556/[/url]