@Tom-Elliott I hope I didn’t come off as rude earlier, certainly wasn’t trying to be. Here are the settings under my tftp server settings.
FOG_TFTP_PXE_KERNEL_DIR /var/www/html/fog/service/ipxe/
FOG_TFTP_PXE_KERNEL bzImage
FOG_KERNEL_RAMDISK_SIZE 127000
FOG_PXE_BOOT_IMAGE init.xz
FOG_PXE_IMAGE_DNSADDRESS 127.0.0.1
FOG_TFTP_PXE_KERNEL_32 bzImage32
FOG_PXE_BOOT_IMAGE_32 init_32.xz
Ok, I will admit that it has been a while since I have uploaded a linux image to fog as we are primarly windows at our school. I thought that all I had to do was configure my machine the way I wanted it and then upload it, no sysprep like in windows. Well I did that my current ubuntu image that I am working on and when I pushed out the image to another computer, that computer has the same name as my upload machine. Not sure if it is something that I did while setting up the original machine or not. I joined my domain using pbis and got it updated then uploaded the machine. Do I just need to change the name of the local machine after I deploy the image?
@Tom-Elliott No Tom, that is not it. I did follow the instructions and changed my dhcp server to the correct setting. Some of my hosts that i created a couple of years ago still had the old kitchen sink kernel and when I went to push out an image to one of them it wouldn’t go until I deleted the host and re-registered it. That’s when I got to thinking about the old format for for where the directory stored the kernel. I originally had the kitchen sink kernel and a lot of my computers wouldn’t run on that kernel so I had to updated it periodically. For my server, a lot of the older hosts have the kernel tied to the old kernel in the host menu.
is there a way that I can change that for all of my old hosts at once or do I have to change that for each host? 1600+ hosts and I’d rather not have to do it manually if I don’t have to.
@Wayne-Workman Ok, I think that I might know what it was. In my host settings from my old images, the kernel was at fog/kernel/bzImage; I think that now it is just bzImage.
@Wayne-Workman When you say to re-run the installer, are you talking about the fog installer or something else?
I am trying to upload a new ubuntu 14.04 image to my fog server that I recently upgraded to 1.2.0. When it goes to network boot, it gets to /fog/kernel/bzImage… No such file or directory…could not boot. What do I need to modify to get this working right?
@Wayne-Workman Ok when I try to upload a new image, I go to preform full registration and it goes to a black screen with a blinking cursor. Also when I am on the host management page, I can only access the delete link from the host menu. I can’t search for a specific host, it just comes up with a “searching error, please try again”, so I have to list all host and find it there. I tried to upload another image to a currently registered host and I had to hit the upload arrow in the host search screen. After booting to network it would boot to ipxe and acted like it was connecting then loop back to the computers boot menu. Any ideas.
@Wayne-Workman One other thing, I know in version .32 when you had to chose the operating system for the image we had to chose xp for any windows 7 system. Has this issue been corrected in the latest version?
@Wayne-Workman Ok it is now back to working just like it should. Thanks Wayne
@Wayne-Workman I uninstalled mysql and reinstalled it like you originally said. Now when i try to reinstall fog it gets to the checking package php5-mysql…failed
Ran “sudo service mysql stop” then ran “sudo service mysql start” and still the same page
Ok I did press enter and finished in the terminal and went to try logging back into fog and still get the “Database schema installer/updater” page
I just upgraded my fog version from .32 to 1.2.0 and I got to the point where I needed to update my database schema so when I went to the link in the terminal and pressed the link to update I received the error that the install/update failed with lots of errors. What can I do from here? I did not back up my database…yes I know stupid on me. Am I just going to have to do a full reinstall of fog and start over on everything?
I’m trying to upload a mint 17 image to fog .32 and using the bzImage32 kernel. The file system setuple should be good because I did it the same as an older x64 image using ext3. It goes to start the upload, but when it goes to the screen where you see the percentage bar going across, it just stays at 0 and moves to next partition. Any ideas?
Ok, well after setting up the computer back up, all is well and working like it is supposed to.
[quote=“Lee Rowlett, post: 31748, member: 28”]you don’t actually have to specify unattend:unattend.xml if it’s in the default location i.e. C:\Windows\System32\sysprep\unattend.xml
how many times has this machine been sysprepped? check /panther folder also. have you always had <ProductKey>xxx-xx etc in ur unattend.xml if so that would cause it to fail - try this: remove ur unattend file from sysprep folder, open sysprep.exe leave as is and click ok, when/if machine reboots goes to oobe and asks u for pc name press ctrl, alt F3. let me know the outcome btw just to check it is win7pro x64 on the machine isn’t it?[/quote]
I haven’t actually been able to sysprep it at all. As far as the product key xxxx-xx, I just removed the actual key and put xxxx in its place to post on here. What I was describing earlier is what was happening when did try to go to audit mode…it just wasn’t working properly. I just reinstalled the win 7 pro x64 and hit ctrl shit f3 and now it is working properly. I’ll get back to it on Monday when I come back to work. Heading home now. Will let y’all know how it goes.
[quote=“braindead, post: 31747, member: 24282”]
Yes, an OEM key can only be on one computer, but this is regards to the OEM keys that are printed on the machines, or come with an OEM version of Windows.
What I’m referring to when I say ‘generic OEM key’ is a key that is only used on machines that have preinstalled licenses in the BIOS. For example, on these Lenovos I’m working on, there’s a line in the main section of the BIOS called “preinstalled OS license”. Microsoft has what keys called “Windows 7 Professional OEM:SLP” (System Locked Pre-Installation Key); i.e., the key is used in conjunction with Windows disks/ISOs that are used by OEM manufacturers that rely on the BIOS to activate the key. Volume installation images will not work this key, and neither will individual CD installs, be it OEM or retail disks.
These keys are specifically for manufactured machines.
That’s the way the crazy license world of Microsoft and these keys was explained to me. You’ll need to get that key from your vendor, then you can put that in your unattend file and as long as the machines are manufactured OEM machines with preinstalled keys, all will be well.[/quote]
Ok, well I just put the install/repair disk that came with one of the laptops in one and I deleted all the partitions and am reinstalling windows. I just hope that it will sysprep properly this time around and be ok. Did you take a look at my unattend file and does that look good to you? I used a keyfinder and was able to obtain the key that way, I Xed out where I have the product key currently in the .xml file. Tom was saying to not have a product key field at all, so which is the way to go here?