If you have your dhcp setup correctly with the address of your fog server, all you had to do was burn [URL=‘http://boot.ipxe.org/ipxe.iso’][U][COLOR=#0066cc]http://boot.ipxe.org/ipxe.iso[/COLOR][/U][/URL]
Posts
-
RE: PXE boot iMacsposted in Linux Problems
-
RE: PXE boot iMacsposted in Linux Problems
[url]http://ipxe.org/download[/url]
If they have drives use the prebuilt ISO or make USB
-
RE: Silly beginners question - Fresh install of an OS from ISOposted in General
The windows 7 CD is nothing more than a boot disk and an image file. It restores the image file install.wim which is in the sources folder of the CD.
You could just upload a vanilla image of windows 7 to FOG and restore that.
-
RE: (1.1.1) Multicast Hang - Starting to restore image (-)posted in FOG Problems
check the log file /opt/fog/log/multicast.log
-
RE: How to Update AD Username and password for all hostsposted in FOG Problems
Simple,
create a group and add all hosts to that group, then modify ad setting for that group.
-
RE: Changing Name works, Joining AD is not but was prior to upgradeposted in FOG Problems
it’s probably case sensitive, modify the query with the correct case, check an existing host for the case your using
-
RE: Changing Name works, Joining AD is not but was prior to upgradeposted in FOG Problems
I use SQLyog community edition to make a connection to the database.
Recommend you make a backup first.
The SQL query you need to execute is:
update hosts set hostADUser=‘Administrator’ where hostADUser=‘roxborough\Administrator’; -
RE: Changing Name works, Joining AD is not but was prior to upgradeposted in FOG Problems
You could do an SQL query to the database directly and change only the ones that have the setting roxborough\Administrator
-
RE: Changing Name works, Joining AD is not but was prior to upgradeposted in FOG Problems
Your welcome Bill, If you have hundreds of hosts in your database with that setting, create a temporary group and mass change the AD setting.
-
RE: WOL and Task doesn't workposted in FOG Problems
remove the gateway 192.168.1.1, leave it blank.
-
RE: Changing Name works, Joining AD is not but was prior to upgradeposted in FOG Problems
Bill,
Looking through the posts again, you have probably changed the global AD settings to use [B]Domain Username: Administrator[/B] but you have not done it for that individual host in Host Management. Its is still probably using Domain\Administrator.
-
RE: Changing Name works, Joining AD is not but was prior to upgradeposted in FOG Problems
Before you change the account, If the host already exists in AD try deleting it, then restart fog service on client.
-
RE: WOL and Task doesn't workposted in FOG Problems
I just thought of something else. Have you got 2 gateways configured on the server, on both eth0 and eth1 because that would cause an issue.
-
RE: WOL and Task doesn't workposted in FOG Problems
Raffa,
The only thing I can suggest now is to try it with a server with a single card configured to use eth0.
-
RE: WOL and Task doesn't workposted in FOG Problems
In your pic your fog host is 192.168.1.2 but in your configuration its 192.168.1.1, is that an error in the pic or have you changed the static IP on the server.
-
RE: WOL and Task doesn't workposted in FOG Problems
Your pic just tells us that your using connection eth1, not that you have configured fog to use eth1 for WOL in the fog settings.
check /var/www/fog/commons/config.php or use the console
define(‘WOL_HOST’, “1.1.1.1”);
define(‘WOL_PATH’, ‘/fog/wol/wol.php’);
define(‘WOL_INTERFACE’, “eth0”); -
RE: WOL and Task doesn't workposted in FOG Problems
Put Wireshark on a client and start monitoring, send the packet from fog server to check if it receives it.