Updated, [B]same[/B] error, [B]same[/B] spot. I’m just selecting the “Verify Client Compatibility” menu option from FOG iPXe menu.
HOWEVER, I tried PXE booting another PC (Optiplex 745) and selecting the “Client Compatibility” menu option to verify and it continues correctly. I suspect it must be something with Optiplex GX520 which is the one giving me the error I showed before.
FOG 1.1.0
OS Ubuntu 12.04 LTS
I’m trying to image (previously worked with FOG 0.32) a Dell Optiplex GX520
I updgraded from FOG 0.32 as soon as 1.0.1 was out, imaged many computers with 1.0.1.
Now moved to FOG 1.1.0, and having this issue.
Is this related to this error I’m having?
[IMG]http://i57.tinypic.com/ot2r88.jpg[/IMG]
Also, I try to update the Kernel thru the FOG 1.1.0 interface, it downloads then stays at this screen indefinetely…
[IMG]http://i61.tinypic.com/1rvvid.jpg[/IMG]
Capone does not work with the “old” images? I know the new 1.0.1 can read PartImage images, but so does Capone?
I tried deploying some images with it, and it did NOT recognize the images as being partclone images and did not deploy with Capone, had to do the whole “inventory and register” then in FOG deploy to the registered host - and it worked perfectly.
However if I try to do the same (deploy images using Capone), it identifies the host correctly but as soon as it gets to the imaging part, an error shows up that the image is not recognized as a partclone image.
Re-uploading the image so that it gets saved in the new image format maybe?
Do we lose Reports when we update to 1.0.1?
I updated and now I can’t run any of the Reports. What should I do?
After some more testing, I found out the REG line, after /d instead of:
[FONT=Consolas]“cmd /c rd /s /q %SystemDrive%\Drivers”[/FONT]
SHOULD be:
[FONT=Consolas]“cmd /c “”“rd /s /q %SystemDrive%\Drivers””"[/FONT]
[FONT=Consolas](Yes 3 quotes to escape a single quote). That works magic! [/FONT][FONT=Consolas] [/FONT]
small correction:
on:
[FONT=Consolas][CODE]ECHO reg add HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce /v CMD0 /t REG_SZ /d “rd /s /q %SystemDrive%\Drivers” >> %SystemDrive%\Drivers\RemoveD.cmd[/CODE][/FONT]
[FONT=Consolas]should be: [/FONT]
[FONT=Consolas][CODE]ECHO reg add HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce /v CMD0 /t REG_SZ /d “cmd /c rd /s /q %SystemDrive%\Drivers” >> %SystemDrive%\Drivers\RemoveD.cmd[/CODE][/FONT]
After a few trial runs, here is what I did:
Modify the sysprep.inf file (with setupmgr.exe) so that:
1 - Completely Unattended = NO
2 - Additional commands = startup.cmd (Add this command, this will create a CMDLINES.TXT file under \sysprep\i386$oem$
include in [I][B]\sysprep\i386$oem$[/B][/I] as [I][B]startup.cmd[/B][/I]:
[B]cd %SystemDrive%\Drivers\SAD[/B]
[B]call DP_Install_Tool.cmd[/B]
in [I][B]\Drivers\SAD[/B][/I], edit [B][I]DP_Install_Tool.CMD[/I][/B]:
just after these lines:
[B]popd[/B]
[B]endlocal[/B]
include:
[CODE]ECHO @ECHO OFF > %SystemDrive%\Drivers\RemoveD.cmd
ECHO reg add HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce /v CMD0 /t REG_SZ /d “rd /s /q %SystemDrive%\Drivers” >> %SystemDrive%\Drivers\RemoveD.cmd
ECHO rd /s/q %SystemDrive%\D >> %SystemDrive%\Drivers\RemoveD.cmd
ECHO DEL /F /S /Q /A “%SystemDrive%\Drivers\SAD” >> %SystemDrive%\Drivers\RemoveD.cmd
ECHO rd /s/q %SystemDrive%\Drivers\SAD >> %SystemDrive%\Drivers\RemoveD.cmd
ECHO EXIT >> %SystemDrive%\Drivers\RemoveD.cmd
shutdown -r -c “Drivers Installed! Machine will now restart…”
call C:\Drivers\RemoveD.cmd
NET START “Fog Service”
[/CODE]
The RunOnce key added will delete the \Drivers\SAD directory on next reboot, since RemoveD.cmd can’t do it after erasing itself. But since the FOG service is restarted just after RemoveD.cmd, the FOG service will restart the computer (to rename it).
Tried many times and works like a charm!
Hope it helps!
My AD level is 2008. I’m using Windows 2008 R2 Enterprise.
FOG adds computers to the domain without a hitch (Windows 7 or XP computers), but if I rename it (thru FOG browser interface), FOG Service in the computer renames the computer but will NOT rejoin the computer to the domain. I guess when the computer is already part of a domain, it should un-join the computer, then re-join.
I have tried renaming directly under Windows, and I always have to unjoin then rejoin to be able to change the computer name correctly on AD. I guess its a limitation imposed by Windows AD.
I believe there is a way within the DPinstall script to create the necessary RemoveD.cmd for the cleanup.
I will try including these lines just before the final shutdown (where FOG service is restarted):
[CODE]ECHO @ECHO OFF > %SystemDrive%\Drivers\RemoveD.cmd
ECHO rd /s/q %SystemDrive%\D >> %SystemDrive%\Drivers\RemoveD.cmd
ECHO DEL /F /S /Q /A “%SystemDrive%\Drivers\SAD2-111118” >> %SystemDrive%\Drivers\RemoveD.cmd
ECHO rd /s/q %SystemDrive%\Drivers\SAD2-111118 >> %SystemDrive%\Drivers\RemoveD.cmd
ECHO EXIT >> %SystemDrive%\Drivers\RemoveD.cmd[/CODE]
I changed 
to [FONT=Consolas]%SystemDrive% to make it more compatible with different boot configurations. [/FONT]
Never had a problem imaging Dell 7010 / 710 or 790. After preparing the “master” and uploading the image to FOG (using single NTFS, resizable for XP and multiple, non-resizable for Windows 7), I always schedule a “Quick Wipe” to the computers to be imaged, followed by a “Deploy”. So far I’ve imaged 20+ 7010 without a hitch.
Maybe the “Quick Wipe” just sets the partition to be compatible with FOG? I don’t know, but never had any problems. Been using the 3.3.3 and 3.6.9 kernels, and did not find any issues.
This would be a GREAT feature to have!
Is this in a wish / to-do list?
I am having the same problem, I am running the FOG server under Hyper-V on Windows 2008R2 datacenter. Could the virtualized network adapter (legacy network) on Hyper-V cause this?
It does not work either manually or thru the menu. I have used a WOL utility from the same subnet and it works. FOG does not seem to be sending any WOL packet.