Thanks for your help guys…I think I was able to pinpoint it as being an issue with these being on a domain and the domain not recognizing the new name given from FOG.
I removed them from the domain, rebooted, and then added it back to the domain with the new name and now everything is working again.
So I was able to get it to change the computer name…but now the computer fails to shut down. I hit shutdown and explorer.exe closes, and the wallpaper is just stuck on the monitor.
I have just a few questions about the process for host names in FOG if anyone can help…
After I imaged all of our sites computers, I was told that I’d need to follow a different naming scheme than what was used. Is there a way for me to change the host name AFTER they’ve already been imaged? I tried just changing it in the FOG menu and saving, but that didn’t work…is there a wiki document that someone can point me to if it’s possible?
[quote=“Junkhacker, post: 35160, member: 21583”][URL='http://www.fogproject.org/wiki/index.php/Supported_Snapin’s_and_Command_Line_Switches’]http://www.fogproject.org/wiki/index.php/Supported_Snapin’s_and_Command_Line_Switches[/URL][/quote]
Thanks so much!
I have used FOG to deploy software installs using .msi or .exe files. I’m in an environment without WSUS or any other form of centralized management of our desktops, and I’m looking for ways that I can easily make changes to OS settings without having to individually do each machine.
[quote=“ianabc, post: 33372, member: 24548”]What do you see in the PXEboot process, can you see it getting a DHCP entry?[/quote]
Yeah, it gets to DHCP and sits for a few moments, then proceeds to Windows.
[quote=“ianabc, post: 33369, member: 24548”]Check the task list in fog to make sure that the task has actually be scheduled and is waiting.[/quote]
It is
I have a machine that has been inventoried and I literally just deployed an image to it via FOG. I installed some software and then ran sysprep again to upload my final image to our FOG server and now when I PXE boot, it just goes straight into Windows…does anyone have any ideas?
[quote=“Junkhacker, post: 32288, member: 21583”]no it is not. were those computers running over the weekend? fog does not send a wake up to computers to deploy snapins[/quote]
I’m fairly positive they are running, but all of these are overseas so I’m unable to verify firsthand (had to e-mail someone to check for me).
I’ve been monitoring them since about 3 hours ago and in that time it has completely another 10 machines.
Has anyone experienced this? I deployed snap-ins to roughly 230 machines on Thursday night and I’ve been checking the status of them throughout the weekend…It has been three full days, and there are still 65 in queue. Is this normal?
I have been getting conflicting opinions on this whenever I try to search for it on the web. I am going to be making a master image of one computer and then deploying it to roughly ~200 other systems. In my unattend.xml I have not set the option to skip rearm, because I need to make sure the image I deploy runs as OOBE for the new workstations.
If I make sure to create a pre-sysprep image and upload it to FOG, do I need to worry about setting my unattend.xml to skip rearm. I’m just trying to think in advance in case I ever need to do Windows updates on a massive scale, other software deployments, etc. - I can just install the master image on a machine, make the changes or updates I need, and then re-deploy it without ever having to worry about my sysprep count ever going over 3?
I should note the reason I would need to do it this way is because we don’t have any other sort of software deployment options at this location using AD or something like that. In the past I have been doing software installs using psexec, but I know this wouldn’t be ideal for some software packages.
Thank you, I was able to get it. TFTP is not enabled by default in Windows 7. We aren’t using our Fog server for DHCP, so I just had to enable tftp and it worked.
I’m having problems adding several workstations to my Fog server. They are all in the same subnet as my server and I have several other workstations that are up and running. I have added them as hosts with their MAC addresses. However when I PXE boot, I see DHCP reaching out for a response, and then it just boots to Windows and never shows me the FOG menu.
Is it because I have already added them as hosts? I thought that the quick registration and inventory was still required? I tested sending a snap-in to see if they were up and running, but it just stays stuck in the queue - while I can send snap ins to the other computers.
[quote=“need2, post: 30946, member: 21891”]Are these systems part of any kind of Domain?[/quote]
They are
Edit: At least I’m 99% sure they are. I should mention that I just started this job and I’m not really the guy who is in charge of any of our sysadmin type stuff.
I need to deploy the FOG client service to several hundred machines to an offshore location, and I have this guide:
[url]http://www.bauer-power.net/2011/09/how-to-deploy-fog-service-client-from.html#.U6Q2TvldVqV[/url]
My only problem is that the machines will not have access to a file share and will not be part of an OU (though they will be Windows systems). Do I have any alternatives?