FOG Virtual Machine
-
I did miss a letter, my apologies. If it started the service there should be an output listing the pid hat it started with.
What version of Ubuntu are you running? And if you are doing re-installs of FOG why are you not using a more recent version??
-
The version of ubuntu, i don’t know (is there a way the cmd can tell me?)
I would like to know how to upgrade FOG within VM, but i can’t find a neat way to do it.
Updating on retry to [FONT=Consolas]ps ax|grep tftp[/FONT]
4490 ? Ss 0:00 in.tftpd -s /tftpboot
6105 tty1 R+ 0:00 grep tftp
This was the output, but from WS or W2012 server still no tftp cmd line response… Weird. -
[CODE]lsb_release -a
[/CODE]Will give you the OS version.
As for upgrading within the VM, why not use SVN?
-
[B]Thanks for that:) [/B],
version is
Ubuntu 8.04.3 LTS
I will look into your other option, but not at this moment, i need to relax. I’m coming back on this issue tomorrow -
Hi there, new day, fresh start, new problems to come…((-:
I looked at SVN, briefly, but when i get this VM running, or when i get the right hardware to install ubuntu and FOG, then there’s no need for this SVN. I guess at this point, i want to make this work, so stubborn as i am, i need this for my egoboost ((-:
No, i’m joking, but it is on my W2012 server at this time the simplest solution without compromising a lot on my server.
I’m still looking into former reactions, and trying the best i can do for now. -
I had done a few tweaks,
sudo /bin/sleep 30 && /etc/init.d/tftpd-hpa restart
DHCP option 66 10.1.0.21
DHCP option 67 pxelinux.0 or undionly.kpxe (which one do i really need here?)
and as stubborn Microsoft sometimes is, i deleted option 60 in DHCP (PXEClient) from both servers in scope and server options.
Now when i start my older laptop and go to boot from lan, i get FOG. So the next step is quick host configuration and that worked too.
Now i try to get an image from it, remotely… cross my fingers… -
No go this last option, deleting number 60. I can’t get into my domain because of a failing trust relationship. It is in Dutch so i can spill it here but that makes no sense if you don’t understand the language.
I’m putting thing back the way they were and retry to log in on the domain.
Btw. the task i gave FOG, upload a image, got on the laptop from which i just spoke a tftp timeout. it is still trying… and the home screen of the fog server says that there is no task, no activity…
I’ll be back later…And later it is, it seems that for no reason at all my old hp laptop decided to “I will not log in anymore” in windows domain. So, i have to reinstall the darn thing. Coming back on a later time.
-
You want undionly.kpxe in option 67.
Don’t you have a local account on any of your machines? You can log into the local admin account and disconnect/rejoin the domain instead of reinstalling windows.
-
Option 60 on your DHCP did not have anything to do with the domain loosing trust on your laptop. That was just a bad coincidence.
It sounds like you are getting pretty close to getting it working!
-
Hi, thanks for thinking along, but i had to reinstall that old HP laptop in order to get a fresh view. I changed the bootp option in undionly.kpxe and i think too that it was a coincident, shameless OS!!
Well, we have to work with it, and don’t tell me that i have to step away from Windows, because i don’t want to…it has it’s advantages too.
To the point: I am now so far that when i start a task in FOG to upload that HP image to the fog server, it wakes the laptop but there is no connecting to the fog server for uploading. It tries to connect, it does not get a ipadres and all, but by memory i thought there should be a client that i need to install, i can’t find it. Must have over looked it in the process. So i’m looking on the forum at this time to find that missing piece.
I still am puzzled why it does not connect to the DHCP from my windows server. I’m shutting down one of them now and see if that helps. -
The client is for things after imaging(Renaming, deploying snapins, etc).
As far as your problems now it looks like your client is not connecting to your DHCP server as that is where the IP comes from.