[quote=“ch3i, post: 44891, member: 2513”]I think : Thinkcenter M73 
Edit : The [B]M73z[/B] is in Working Devices of the wiki : [url]http://fogproject.org/wiki/index.php/WorkingDevices[/url][/quote]
Right, but his ipxe.efi isn’t present inside /tftpboot
EDIT: lol, the model name is in the thread title. Duh.
Just tested this and it appears to work:
[CODE]sudo wget https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/ipxe.efi -O /tftpboot/ipxe.efi[/CODE]
this might do it:
[CODE]sudo wget ‐‐continue ‐‐timestamping https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/ipxe.efi -O /tftpboot/ipxe.efi[/CODE]
Otherwise, manually download the ipxe.efi file and put it into the /tftpboot directory.
The file is here:
[url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/[/url]
[quote=“Junkhacker, post: 44883, member: 21583”]regarding the backups of config files, i thought i would share what i’ve started doing.
i create a local git repository on my desktop for each server
before editing a config file, i copy the file over to the git repo for that server so that i have the original version.
whenever i make a change, i commit the change to the config file in the git repo as well.
this gives me a complete log of all changes i make to the server’s configuration and i make notes in the commit logs about what i did and why.[/quote]
Could you share some resources about that? I’m absolutely a total noob with doing Repos… and that other stuff you just said…
Clearly something went wrong with some part of the download process.
Maybe cancel it and retry?
Please post your dhcpd.conf file here so we can take a look at it.
Also, look inside your /tftpboot directory and verify that the file is actually there.
Also, what is the model of the problem Lenovo?
SVN is a software package that allows you to ‘check out’ software (basically downloading a specific revision, or the latest of some software).
SVN in and of itself is not FOG, but a lot of FOG users use it.
FOG developmental versions are called “revisions” (at least in MY head).
Revisions are usually stable for the PRIMARY functions of FOG, being: IMAGE -> NAME -> JOIN TO DOMAIN using UNICAST and MULTICAST
Other features in FOG revisions (not directly related to the imaging process) are sometimes broken, Tom is pretty good about getting to them when someone asks about them. These other features usually do not impact imaging.
Additionally, if you encountered an issue, let us know about it here and someone is likely to fix it quickly, making a new “Revision” that you can download and install very quickly. Also, updating FOG from one revision to a newer one usually takes all of 34.8 seconds to accomplish (in other words, no answering questions, no additional configurations because it uses the settings you’ve already set).
However, with the current revisions, you’ll benefit from a plethora of bug fixes, a much wider range of supported host hardware, and new features!
On your FOG’s web GUI login page, you can check what version you’re running:
[IMG]http://s22.postimg.org/gpv52ymwx/Fog_SVN_version.png[/IMG]
The Dell Precision T3500 is listed in FOG’s working hardware list…
I think your problem is partitioning related.
Could you read through this and give it a go? [url]http://fogproject.org/forum/threads/quick-format-to-ntfs-with-fog-for-noobs.10349/[/url]
Also, if you find those instructions to be too confusing, you can optionally use a Windows XP disk JUST to delete all the partitions on the problem computer, and then remake 1 partition, and then format.
By default, when the WinXP disk finishes formatting, it begins copying files. That’s fine; when it starts copying files, just take the disk out and turn the computer off, then retry imaging with FOG.
Imaging to a blank hard drive is a known issue. FOG expects some sort of partition to be present.
As far as pressing ENTER to continue for each partition, I’ve never heard of that problem.
If you press ENTER when it asks, does it eventually complete?
I was looking at this thread: [url]http://fogproject.org/forum/threads/cant-mout-image-folder-and-images-folder.12150/#post-40215[/url]
and the “Press ENTER to continue” problem there sounds a lot like the issue you are having.
What OS are you trying to image? Windows 8 ? Windows 7 ? Vista? XP ?
You don’t have to use DomainName\Username for the username field (you used a forward slash, that isn’t right).
But, you do need to use a Domain account that has permissions to join systems to AD.
Also, when you install the FOG client on the host machine prior to uploading an image, you have to ‘tick’ the features that you want. I suggest ticking them all.
Another thing that could break it is typing in the wrong IP into the FOG client installation.
Also, if you’ve got really fast systems, you might want to set the FOG client service to delayed start. This will make waiting for domain joins 1 to 2 minutes, rather than like 10 seconds… but it works every time.
Also, you might wanna re-encrypt your password again and be very, very sure you don’t make a typo. You can make multiple encrypted strings by piping the output to different text files. ( you’d use the arrow character to pipe output ). If you get two encrypted strings that match, in a row, you’re probably not making any typos.
ALSO, inside of host management, on the left, you need to enable the “Join to AD” feature (that’s not what it’s exactly called, I can’t remember) for it to work at all on a particular host.
LATER, when you have FOG working right, and are adding massive amounts of hosts into FOG, you can lump them into a temp group and enable the AD join feature on all of them at once, along with other features.
Today at work, I noticed that my workstation supports UEFI and legacy.
I plan to turn UEFI on, and figure out the DHCP settings to make FOG work with Legacy BIOS and UEFI at the same time, diving out either undionly.kpxe or ipxe.efi based on the computer’s request.
Don’t know if I’ll figure it out, but there is a pretty good chance that I will.
For the record,
If it wasn’t for the developmental versions, FOG wouldn’t work in my environment at all.
And, from what I’ve seen, it’s really stable.
Tom primarily focuses on the imaging features in FOG (who would have guessed??) and makes sure that it works for all sorts of hardware. This is understandable, because he is only one man, and fog has a lot of razzle dazzle plugins and other features that aren’t specific to Imaging -> Naming -> Joining to domain
And, of course, all I do with fog is: Image -> Name -> Join to domain… and FOG is really good at that.
Or create a feature…
That might be easier than bug fixing if you’re new to it. It’s what I plan to do.
I just checked on my Optiplex 7010,
My particular BIOS does not allow Long-POST, or Through-POST.
I know older systems used to allow configuring fast POSTing and full POSTing…
Maybe that’s gone to the wayside???
Either way, you don’t know till you just get in there and look.
Powershell from a domain controller can immediately force computers to shutdown / restart / etc.
It’s incredibly powerful… let me dig up the script I use…
here:
[CODE]stop-computer -computername FirstCompName, SecondCompName -force
stop-computer -computername ThirdCompName -force[/CODE]
You can also call a powershell script to run with admin rights using a batch file, like this:
[CODE]PowerShell -NoProfile -ExecutionPolicy Bypass -Command “& {Start-Process PowerShell -ArgumentList ‘-NoProfile -ExecutionPolicy Bypass -File "“C:\Remote_Shutdown.ps1"”’ -Verb RunAs}”[/CODE]
Does the Optiplex 3020 have solid state drives?
And, out of curiosity, can you enable the long POST check on one? Like, a full memory count before booting… or something similar?
I read something the other day that claims this can help newer/faster systems to PXE boot right… Again, Just a curiosity.
I would suggest building a new FOG server, using FOG 1.2.0, or (what you probably need) the latest developmental revision. This will more than likely fix your problem.
You don’t need to dismantle you’re old server - just turn it off while you do this (and forever if it works.)
Go get one each of those three machine models you have, image them, and sit them next to your desk (clean).
Then work on building a new FOG server, get that working, and then upload your three images you have for your three models.
We’re here to help you at every bump and snag - but it should be really straight forward.
See here: [url]http://fogproject.org/wiki/index.php/FOGUserGuide#Installing_FOG[/url]
Do you know if you’re current .32 FOG server is using DNSmasq, ProxyDHCP, or is handling DHCP itself? Is it the only FOG server in your organization, or just a node among many?
IMO, it’s safer to wait until the computer is not in use…
Changing a computer name and forcing a reboot in the middle of someone getting work done will cause MUCH more than just I.T. problems…
I.T. maintenance should be transparent, even totally invisible to the end users… and should never prevent or disrupt productivity.
What version of FOG are you using? What revision?
Have you tried to delete that user, and recreate?
Have you tried different browsers?