Since you’re very new to FOG server I feel the need to ask if you’ve been able to make images for windows 7 or 8?
Are you just new to FOG or are you new to imaging entirely?
Depending on what customizations you want to make, making an image for any version of windows isn’t all that different really.
What is your end goal here?
Although I imagine you figured this out by now, I also wanted to do this and found this post. I figured this is as good a spot as any to post it.
I’ve noticed that the service works better when it’s installed on each computer after imaging rather than trying to include it as part of an image.
So the idea of this script is to download the latest version and install it silently right after imaging, so I would suggest adding it as a snapin that you put on all clients. The only change you should need to make is changing the fogip variable to your fog server ip.
@ECHO off
set fogip=192.168.100.100
echo "downloading latest client..."
powershell -Command "wget http://%fogip%/fog.client/download.php?newclient -OutFile C:\FOGService.msi;"
echo "installing client..."
msiexec /i C:\FOGService.msi /quiet WEBADDRESS=%fogip%
echo "starting service..."
net start FOGService
echo "Done!"
exit
@Toby777 I think it might still work on larger drives and you can manually expand the partition. That’s pretty good for RAW from what I’ve seen. Trouble with RAW is that it does every sector of the drive no matter how much space is taken up. Before multiple and extended linux partitions became supported I only used it for very specialized images for computers that were always the same size hard drive.
@anthonyglamis said:
I created those images in the previous fog version so is this a bug or am I not capturing the image correctly?
Also I deleted those images (Dell3450, LenovoE430) however they are still on my linux box, can I get those back into the fog server?
If they are still in the /images folder then yes. If they are in a different machine, still yes, just transfer the files to the new fog server /images folder.
Just make new images in the fog gui with the same settings and point them to the file names and they should work. Does that make sense?
@vbelous said:
i’m taking for a previous user
I’m not sure what you mean by that
And since you have 7 and 8 images, are you running into some sort of trouble with uploading a windows 10 image or are you just worried that there’s no option to say an image is windows 10 in the older versions of fog. Setting it to windows 7 or 8 doesn’t change anything in the imaging process that I am aware of, it’s more for inventory and organization of the database as I understand it. Granted Windows 10 is an option in the latest trunks, so it doesn’t really matter.
Have you tried uploading a windows 10 image to your working image configurations for 7 and 8 and run into trouble?
Just trying to help you better here.
@Jbob oh sorry, that was kind of vague.
It starts and all that but it doesn’t seem to do anything when I set the client to a task on the server.
This could be just me and I need to test more though.
In the storage management of the fog gui is everything set correctly? IP address, interface, user/password and all that?
on the server what does your /etc/exports look like?
cat /etc/exports
What does fog say about your hard drive in the gui?
https://{fogip}/fog/management/index.php?node=hwinfo&id=1
I’ve seen mine mess up before and one of those configurations was just messed up. Maybe your ip isn’t static and it changed on you?
Other times a quick restart of apache refreshed and fixed the issue
sudo service apache2 restart
or
sudo /etc/init.d/apache2 restart
Or just a good old fashioned restart of the whole server can fix it to if it’s an odd bug in your server.
Though it’s most likely a simple configuration issue in the ui based on when this has happened to me a few times and since your nfs server is probably working since you were able to upload an image.
How big does the gui say your image is? You will need to enable “FOG_FTP_IMAGE_SIZE” under “General Settings” in the FOG Configuration then go to image management and list all images.
Hopefully one of those ideas helps.
@MRCUR The IE stuff in appdata is where the shortcut files that are pinned to taskbar go, but to get it to work fully you need the ntuser.dat files. The script I posted copies that file from your customized profile into the default profile but only that file. Give my batch script a try. If you’re using sysprep, some customizations might disappear so you could run the script before sysprep then put the resulting C:\Users\Default in a network share somewhere then copy it back over after sysprep or after imaging.
Does that help at all?
Isn’t this functionality also available in the GreenFog settings?
I’ve looked at them but never tried playing with them.
So you can do these things in the gui with much ease. I’m guessing you’re trying to write a script of some sort to automate it further?
If you run a debug session then you can run any of those commands on the computer you’re imaging with things like fog.wipe and fog.download.
Since the actions you make in the gui are essentially doing things in the database, I suppose that it would be possible to manually edit the database with a script to queue the actions you want on the computers you want. But I don’t know the database well enough to help much more than point you in that direction.
What exactly are you trying to do though? You can set up cron style jobs in the gui if you are trying to just have wipes and restores done regularly, you could set that up in the gui without custom code. Just select cron style deployment when you queue a job in the gui.
Hopefully that’s helpful in some way.
@mrdally204 I usually set the owner and group of images to fog
sudo chown -R fog.fog /images
And I set the permissions to 775
sudo chmod -R 775 /images
Whether or not that’s the best security practice is arguable, and since your permissions are already 777 the owner being root probably doesn’t matter. But changing the owner might be worth a shot.
@MRCUR I see what you’re saying. It would be less work to not have to manually pin some icons to the taskbar and then run the script.
Granted I have my default base image with my default profile on a esxi vm, so for me it is pretty easy to do. I suppose it could be possible to edit the ntuser.dat file manually to add in shortcuts. I’ll look into that, because it would certainly be easier.
Also, this might still be a thing
https://wiki.fogproject.org/wiki/index.php/Auto_driver_Install
@Wayne-Workman I see that now, You posted while I was writing my post so I didn’t see that. I got distracted whilst writing it.
@MRCUR Well I think it is possible to edit it directly, but it is not easy.
Let’s say you run my script and have a working default profile and you saved the folder somewhere.
Now let’s copy the whole profile folder to the local computer, in the C:\ root for example(just to be safe not editing the original right away)
Now open up regedit.exe as an administrator and highlight ‘HKEY_USERS’
File → Load Hive
Open up
“C:\Default\NTUSER.DAT”
name the hive test, or something like that.
You can now edit the default profile registry .dat settings to your heart’s content. Problem is, it’s the registry…
So the second half of task bar pins is in that hive under
HKEY_USERS\test\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Taskband
But that key is all binary and Dwords.
Granted, you could just customize some pins on any user and export that key from
HKEY_USERS\userSID\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Taskband
And then import or copy paste the values into the hive you’re editing and that would work.
Then just highlight the test hive and do file→unload hive and all the settings should be saved in the .dat file.
I saw some vbs scripts in various forums that claimed to automate the pinning but I didn’t try any of them. But I’ll post some links in case they help you do it the way you want to.
Here’s where I came up with most of this
http://smallbusiness.chron.com/modify-ntuserdat-56096.html - editing ntuser.dat
https://social.technet.microsoft.com/Forums/windows/en-US/73eb1c0a-fc78-4ae7-ba6d-356d9a9a5328/solved-how-to-pin-to-start-menutask-bar-for-default-user?forum=w7itproinstall - possible script solution
http://blogs.technet.com/b/deploymentguys/archive/2008/06/06/useful-script-number-5-adjusting-the-default-user-registry-hive.aspx - editing ntuser.dat some more
http://blogs.technet.com/b/deploymentguys/archive/2009/04/08/pin-items-to-the-start-menu-or-windows-7-taskbar-via-script.aspx - other script possibility
Hope that helps in some way. Sorry that I didn’t find an easy answer for you.
@wayne-workman
Fun fact, you can add the old default windows photo viewer to LTSB or the normal windows 10.
You just need to enable it in the registry. This is the contents of the reg file to do that
Thanks Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Applications\photoviewer.dll]
[HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell]
[HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\open]
"MuiVerb"="@photoviewer.dll,-3043"
[HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\open\command]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\
6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\
00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\
25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\
00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\
6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\
00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\
5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\
00,31,00,00,00
[HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\open\DropTarget]
"Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}"
[HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\print]
[HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\print\command]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\
6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\
00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\
25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\
00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\
6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\
00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\
5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\
00,31,00,00,00
[HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\print\DropTarget]
"Clsid"="{60fd46de-f830-4894-a628-6fa81bc0190d}"
Save all that as a .reg file to add the windows 7/8 style photo viewer to windows 10
@Wayne-Workman I just noticed that I missed this post, it was when I was on vacation. This hasn’t actually been a problem on this new network as much. If it happens to me again I’ll come back here or make a new post with the fog.log on anything having trouble.
@Tom-Elliott is on top of this problem
Check out this forum post https://forums.fogproject.org/topic/6315/hp-z640-nvme-pci-e-drive/37
I’m posting my results of testing on the /dev/nvme0n1 type drives with his current inits found here
32 bit Init: https://mastacontrola.com/init_32.xz
64 bit Init: https://mastacontrola.com/init.xz
To use them do the following
cd /var/www/fog/service/ipxe
sudo mv init.xz init.bck
sudo mv init_32.xz init_32.bck
wget https://mastacontrola.com/init.xz --no-check-certificate && wget https://mastacontrola.com/init_32.xz --no-check-certificate
sudo chmod -R 775 ./
Granted by the time dell gets you a replacement it might already be tested enough and the fix will just be in the latest trunk. But that’s what to do in case anyone else is looking.
@anthonyglamis Nope. The installer will auto download the latest client to your server and you don’t need to maually update your hosts with the new client. I think it’s supposed to update itself even, if I remember right