@mimi1255 Make sure you run the sudo apt-get dist-upgrade command
You will also need to check/adjust so that the next LTS is downloaded, try this
Check the /etc/update-manager/release-upgrades file and change the line
Prompt=normal
to Prompt=LTS save and exit.
Run the do-release-upgrade command again.
This should upgrade you to 15.10 (depending on your choices in the release-upgrade file) which will allow you a direct upgrade path to 16.04.
@abos_systemax
Since you are trying to remove a key. You can use the command line to do so.
reg delete "HKCU\The\Registry\To\Delete" /f
OR if you have a .reg file open the file and put a - before the HKEY portion…
[-HKey_Current_User\The\Registry\To\Delete]
like so and do a reg import for that file.
I use a hidden flag.txt and a script that will look for the flag.txt file, if not found, it will run some scripts similar to what you have described and then the next time the user logs in, if the flag.txt is present (which it should be, the script copies the file to where it needs to be.) then the script won’t run again.
I do this in cases where I need to update the registry values for that user only one time. I.E. I set the taskbar, and Start menu to a specific layout. I don’t want to do this on every log in, and it requires registry edits. So I do it once per user when flag.txt isn’t present.
Another option would be to create the script, use a snap in as a deployment after imaging completes. I don’t know exactly what you are trying to accomplish, but I am certain it can be done.
Hope this helps!
@mimi1255
From command prompt
sudo apt-get update
sudo apt-get install update-manager-core
sudo apt-get upgrade
sudo apt-get dist-upgrade
sudo do-release-upgrade -d
If you don’t have much on the server, it might be faster to download 16.04 and install it to your machine.
I upgraded my 10.04 x32 all the way to 16.04 x64… I don’t recommend this, in the end due to all the errors, I just installed from scratch and imported my old images one at a time with a capture task from the new server.
@coop90 FOGPrep is not required anymore, that was something we did many many moons ago before we understood the sysprep process.
You’re welcome to try, but I HIGHLY doubt it will help in this situation.
It seems to me that the image is having trouble scaling to the proper disk size after imaging, particularly to smaller hard drives than the image was captured on.
You know what stinks?
Sneaking into a lab, leaving the lights off so no one will find you, booting up your client to image and MY LAND WHO SET THE BACKGROUND TO RETINA SEAR?
I have made a darker background that I wanted to share that may help with the sizzling retina, it’s a lot harder to find me when there isn’t a bright white screen in front of me 
Enjoy! (It’s nothing spectacular, but its something!)
You have one of two options, either
A.) Change the background by using the web gui. You still need to place the file in the {fogwebdir}/service/ipxe folder but you can name it whatever you like, just make the adjustment on the fog settings page under Fog Boot Settings for the FOG_IPXE_BG_FILE option.
B.) Upload this image to {fogwebdir}/service/ipxe and save it as bg.png (I used filezilla to place the image)
This will overwrite the old background file, I highly recommend backing up the previous bg.png JUST IN CASE!
These commands will need to be issued after every SVN or GIT pull. Keep the new background above in a safe place (/home/user/Pictures).
BACK UP
Ubuntu
sudo mv /var/www/fog/service/ipxe/bg.png /var/www/fog/service/ipxe/bg.png.old
CentOS
sudo mv /var/www/html/fog/service/ipxe/bg.png /var/www/html/fog/service/ipxe/bg.png.old
I will put up other commands later when I figure out where the bg is stored in other versions of Linux.
@mimi1255 It could be possible that the repos do not work for your
Ubuntu installation.
I do not see repositories listed for Vivid Vervet in the ppa list.
I see Xenial, Trusty, Precise, and Yakkety.
Are you opposed to upgrading to 16.04? I use 16.04 in my environment and haven’t run into issues yet (other than issues with my web filter).
@dloudon96 Are you talking about the windows set up screen? “starting services” That doesn’t sound like a FOG thing 
Try narrowing down the number of machines you are imaging at a time. If you only do 10 at a time, do they succeed?
Are all the computers in the same location?
@mimi1255 you will need to issue the following command
sudo apt-get install -y php
drop the 7.0 off the end.
I see the php7.0 repo in the list on his launchpad page, I am not exactly sure why you aren’t able to download that specific repo.
The command I gave you should install php7.1
From what I can tell, all php5.6, 7.0 and 7.1 are housed in the php ppa.
@plegrand Hey no problem!
Thanks for reporting the issues you find. It helps to make FOG better!
@plegrand Did the task start? If so this might be a minor issue, and I sure Tom will fix it 
I was hoping nothing was broken 
@plegrand looks like it listed the word “array” instead of the array of machines that are suppose to be there, if you go to the tasks page, do you see the task and your machine name?
@mimi1255 try sudo add-apt-repository ppa:ondrej/php
It states that you can only use the commands below, php is in the list but php7.0 is not.
@dloudon96 Did you change the setting on the fog server Storage Management page for the nodes?
then this causes the graph on the front page to display a higher number
Is this the answer to the question you were asking?
@mimi1255 Do you have any kind of filter device, or proxy settings?
Did the repository update succeed and only the php installation fails?
@plegrand Thank you for providing the solution that you have found, I am certain that someone else will benefit from this information!
Glad you got it all sorted!
@coop90 Hmm, seems to be something else then.
I appreciate you taking the time to work with us so that we could try to resolve your issues.
Please follow Tom’s instructions and see if that fixes your problems with this image.
I apologize for the problems you have had, but we will get to the bottom of it hopefully Tom already has
@maximillian Keep us posted, I am VERY interested to see your work/what you find!
Can you, for craps and giggles, grab a 250 gb HDD or smaller and deploy to it successfully?
I would be curious to see if capturing the image (before it boots) from that 250 gb HDD if it would also have the same issues you are experiencing above with the same 250 gb SSD when deployed again.
(I’m trying to find the fail point so we can work around it and resolve it)
I wonder if anyone else uses these SSDs… maybe one of them can weigh in.
I apologize for my lack of knowledge here, but we use the Samsung 850 Evo SSDs.
So we have determined that the issue is not the image itself as it will deploy to a standard hard drive without issues.
Is the SSD Smaller in size than the hard drive that the image was captured from?
@coop90 said in Inserting Extended partitions - failed:
thinking
It could always be possible, what make and model of SSD are you using?
If you use a HDD right now, does the image deploy correctly?