Thanks Wayne for taking time to reply.
I will review your suggestions. I’m not really committed to Ubuntu so perhaps changing to OS is worth a look.
Thanks Wayne for taking time to reply.
I will review your suggestions. I’m not really committed to Ubuntu so perhaps changing to OS is worth a look.
I have been running my FOG server, version 1.2.0, on Ubuntu 10.04 for some time. I would like to upgrade Ubuntu to a newer version. Can anyone offer suggestions and caveats regarding problems I will encounter? How much reconfiguration/reinstallation will be necessary?
Thanks for your assistance.
Where do I do that? Can I do it in the FOG GUI or from a command prompt?
OK, so if I want to image only the E: drive how do I do it?
I thought about the one-drive-at-a-time idea but it is clunky. This is just one PC, I have only a few that are dual boot, all the others have only one OS/drive to image. I was hoping to use the same imaging configuration. It would be really cool if there was the ability to select only one drive to image from within FOG.
Yes, I did try that. I selected the OS as Windows 7, there is no provision to choose two OSs. It did not work. I can’t recall the exact error message but the PC kept rebooting trying to run the task.
I have a dual boot Windows PC with XP and 7. XP is on the drive and Win 7 is in the E: drive. Ideally I would like to image both drives; multiple disks seemed like the correct option but that does not work as expected. I can’t figure out how to do that.
Alternatively, I would like to image just the E: drive. Is there a way to select which drive is imaged?
If a user is logged on to a client machine the only way I can schedule a FOG upload is to send a shutdown/restart command to the client machine via the Linux scheduler.
Thanks for the information. What “time limits” are you referring to?
The Intel NIC driver bug had me stumped for a bit.
I am very close to having this all work the way I envision.
If only I could get all users to log out at the end of the day.
SO, is there a way to restart a client if a user is logged on from FOG?
I still don’t know why the FOG services stopped…
I did find that the Intel driver installed on the clients did not actually support WOL even though there were check boxes to enable it.
I haven’t fully sorted out the Auto Log Out.
I scheduled a few upload tasks overnight. They did not run.
When I look at the fogscheduler.log I see that the last entry was yesterday morning. I did not stop the services.
[COLOR=#008080]Edit: I did check and none of the FOG services was running.[/COLOR]
How do I troubleshoot this?
Also, does the Windows client have to be at the login screen for the task to run? What if a user is logged in or the machine is locked ?
[COLOR=#008080]Edit: I found that the Auto Log Out module was disabled. I’ll test again tonight. Does the global setting override the setting on the client? The clients were installed with Auto Log Out selected.[/COLOR]
OK.
The only thing I saw that looked different was this:
If I search for wol.php I find it in two locations.
/var/www/fog/wol
/home/pmusfog/desktop/fog_1.2.0/packages/web/wol
The path in FOG Configuration->FOG Settings->General Settings->FOG_WOL_PATH = /fog/wol/wol.php.
Tom said that it was correct though.
When I schedule an upload task does FOG automatically send the packet or do I have to enable that somewhere?
I believe this option is to wake at a user specified time.
I think the important option is Wake on LAN from S5 <Power On>