This
echo "System breakpoint";
debugPause;
rsync -azP "$remotedriverpath" "$clientdriverpath"
[[ ! $? -eq 0 ]] && handleError "Failed to download driver information for [$machine/$osn/$arch]"
echo "End driver copy";
debugPause;```
or This
echo "System breakpoint";
debugPause;
rsync -azP "$remotedriverpath" "$clientdriverpath"
echo "End driver copy";
debugPause;
So worked with George yesterday on this. Here is what we know and where we left of.
Ran Debug
Broke out of script after Driver Copy
Checked the HD and the x64 folder was there and in it the test .txt file
Then sysprep
Folder is gone after sysprep
So it might be an issue with unattended file. I did not make it it was from our last image which was Win 10 EDU 1609. I am going to upload a blank image with no unattended file and see if the file sticks.
#!/bin/sh
## This file serves as a starting point to call your custom postimaging scripts.
## <SCRIPTNAME> should be changed to the script you're planning to use.
## Syntax of post download scripts are
#. ${postdownpath}<SCRIPTNAME>
echo "starting postdownload";
. /usr/share/fog/lib/funcs.sh
[[ -z $postdownpath ]] && postdownpath="/images/postdownloadscripts/"
case $osid in
5|6|7|9)
clear
[[ ! -d /ntfs ]] && mkdir -p /ntfs
getHardDisk
if [[ -z $hd ]]; then
handleError "Could not find hdd to use"
fi
getPartitions $hd
for part in $parts; do
umount /ntfs >/dev/null 2>&1
fsTypeSetting "$part"
echo "$part"
case $fstype in
ntfs)
dots "Testing partition $part"
ntfs-3g -o force,rw $part /ntfs
ntfsstatus="$?"
if [[ ! $ntfsstatus -eq 0 ]]; then
echo "Skipped"
continue
fi
if [[ ! -d /ntfs/windows && ! -d /ntfs/Windows && ! -d /ntfs/WINDOWS ]]; then
echo "Not found"
umount /ntfs >/dev/null 2>&1
continue
fi
echo "Success"
break
;;
*)
echo " * Partition $part not NTFS filesystem"
;;
esac
done
if [[ ! $ntfsstatus -eq 0 ]]; then
echo "Failed"
debugPause
handleError "Failed to mount $part ($0)\n Args: $*"
fi
echo "Done, fixing to load the drivers"
debugPause
# . ${postdownpath}fog.log
. ${postdownpath}fog.drivers
# . ${postdownpath}fog.ad
umount /ntfs
;;
*)
echo "Non-Windows Deployment"
debugPause
return
;;
esac
I am not seeing any difference between my win7 and win10 setup so it leads me to believe it’s the script.
FOG 1.4.4
Ubuntu 16.04
Here is my fog.drivers
I had @george5848 and Tom work on this in the past. Works great for Windows 7 x86 or x64. Now tried to do the same for Windows 10 1709 EDU but it is not dropping the driver folder onto the disk. Ran Debug and it looks like it found the folder so I am not seeing why it’s not copying down.
I know Optiplex 580 is old but just using it as a test. There is just a .txt file in its driver folder. Also tested this on our main desktop that we have HP Compaq Elite 8300 same issue.
#!/bin/bash
ceol=`tput el`;
manu=`dmidecode -s system-manufacturer`;
case $manu in
[Ll][Ee][Nn][Oo][Vv][Oo])
machine=$(dmidecode -s system-version)
;;
*[Dd][Ee][Ll][Ll]*)
machine=$(dmidecode -s system-product-name) #pruduct is typo, just realized sorry :(
;;
*)
machine=$(dmidecode -s system-product-name) # Technically, we can remove the dell one as it's the "default"
;;
esac
[[ -z $machine ]] && return #assuming you want it to break if it is not lenovo or dell?
machine="${machine%"${machine##*[![:space:]]}"}" #Removes Trailing Spaces
echo "Debug found ${machine}";
#############################################
# Quick hack to find out if the installed OS image is a x86 or x64
system64="/ntfs/Windows/SysWOW64/regedit.exe" # sloppy detect if 64bit or not
[[ ! -f $system64 ]] && arch="x86" || arch="x64"
echo "${arch} was detected";
#############################################
#this section has been updated to bring the osn names in line
# with how the Dell CABs are defined
case $osid in
5) osn="win7" ;;
6) osn="win8" ;;
7) osn="win8.1" ;;
9) osn="win10" ;;
esac
#############################################
dots "Preparing Drivers"
# below creates local folder on imaged pc
# this can be anywhere you want just remember
# to make sure it matches throughout! (case IS important here)
clientdriverpath="/ntfs/Windows/inf/Drivers"
remotedriverpath="/images/drivers/$machine/$osn/$arch"
echo "setting client path";
[[ ! -d $clientdriverpath ]] && mkdir -p "$clientdriverpath" >/dev/null 2>&1
echo -n "In Progress"
#there's 3 ways you could handle this,
#driver cab file, extracted driver files or both
#so on the server put extracted driver files to match below folder tree
#i.e. Model Latitude E5410, Windows 7 x86 image would be:
#/fog/Drivers/Latitude E5410/win7/x86
echo "System breakpoint";
debugPause;
rsync -aqz "$remotedriverpath" "$clientdriverpath" >/dev/null 2>&1
[[ ! $? -eq 0 ]] && handleError "Failed to download driver information for [$machine/$osn/$arch]"
echo "End driver copy";
debugPause;
#this next bit adds driver location on pc to devicepath in registry (so sysprep uses it to reference)
# remember to make devicepath= match the path you've used locally
#also do not remove %SystemRoot%\inf
#and to add more locations just use ; in between each location
regfile="/ntfs/Windows/System32/config/SOFTWARE"
key="\Microsoft\Windows\CurrentVersion\DevicePath"
devpath="%SystemRoot%\inf;";
reged -e "$regfile" &>/dev/null <<EOFREG
ed $key
$devpath
q
y
EOFREG
echo -e "\b\b\b\b\b\b\b\b\b\b\b${ceol}Done"; # this just removes "In Progress and replaces it with done :-)"
Unable to use search function on the forums. See screenshot of error.
@Tom-Elliott Seen that you have been at 1.5 RC 9 now for 30 days now would you say this is close to a stable release? We have been holding off on any upgrades but need some fixes.
@Tom-Elliott No I think it’s been link this for a long time. But now that we got the driver postscript working, it can’t find the folder when the model name is “OptiPlex 740 Enhanced Invalid entry length (0). DMI table is broken! Stop.” when it really needs “OptiPlex 740 Enhanced”
Invalid entry length (0). DMI table is broken! Stop.
Getting hosts that have this in the inventory. Was testing out postscripts and auto download drivers and found a host that I could not get its inventory to read. Deleted the host re inventory. Ran mysql maintenance.
How do I repair this table? I see about 211 hosts with this in their inventory.
mysqlcheck
DELETE FROM `hosts` WHERE `hostID` = '0';
DELETE FROM `hostMAC` WHERE hmID = '0' OR `hmHostID` = '0';
DELETE FROM `groupMembers` WHERE `gmID` = '0' OR `gmHostID` = '0' OR `gmGroupID` = '0';
DELETE FROM `snapinGroupAssoc` WHERE `sgaID` = '0' OR `sgaSnapinID` = '0' OR `sgaStorageGroupID` = '0';
DELETE from `snapinAssoc` WHERE `saID` = '0' OR `saHostID` = '0' OR `saSnapinID` = '0';
DELETE FROM `hosts` WHERE `hostID` NOT IN (SELECT `hmHostID` FROM `hostMAC` WHERE `hmPrimary` = '1');
DELETE FROM `hosts` WHERE `hostID` NOT IN (SELECT `hmHostID` FROM `hostMAC`);
DELETE FROM `hostMAC` WHERE `hmhostID` NOT IN (SELECT `hostID` FROM `hosts`);
DELETE FROM `snapinAssoc` WHERE `saHostID` NOT IN (SELECT `hostID` FROM `hosts`);
DELETE FROM `groupMembers` WHERE `gmHostID` NOT IN (SELECT `hostID` FROM `hosts`);
DELETE FROM `tasks` WHERE `taskStateID` IN ("1","2","3");
DELETE FROM `snapinTasks` WHERE `stState` in ("1","2","3");
@george1421 I copied what your pasted and changed the permissions. Maybe it was the permissions to fog:root that did it?
@george1421 This now works. I will now work on putting drivers in the folders and testing it out. SO EXCITED to start working on a Golden image.
Thanks @Tom-Elliott now comes the real dumb question. How do you run that? Like what program do I use to run the API commands?
So I want to know if it’s possible to take a list of hostnames and add them to a group. We went through a laptop swap and we need to reimage the ones that were returned but I do not want to add 100 hosts to a group 1 by 1 just to assign image snapins and OU info. Is fog at a point that this can be done easier?
Setting up Postdownload scripts to put drivers on universal image. Worked with @george1421 but got stuck when the script would not run. I was not able to update FOG as we were in a huge deployment that is over with and I want to take a wack at this again.
How do I test to see the Postscript run? Here are the scripts
fog.postdownload
#!/bin/sh
## This file serves as a starting point to call your custom postimaging scripts.
## <SCRIPTNAME> should be changed to the script you're planning to use.
## Syntax of post download scripts are
#. ${postdownpath}<SCRIPTNAME>
echo "starting postdownload";
. /usr/share/fog/lib/funcs.sh
[[ -z $postdownpath ]] && postdownpath="/images/postdownloadscripts/"
case $osid in
5|6|7|9)
clear
[[ ! -d /ntfs ]] && mkdir -p /ntfs
getHardDisk
if [[ -z $hd ]]; then
handleError "Could not find hdd to use"
fi
getPartitions $hd
for part in $parts; do
umount /ntfs >/dev/null 2>&1
fsTypeSetting "$part"
echo "$part"
case $fstype in
ntfs)
dots "Testing partition $part"
ntfs-3g -o force,rw $part /ntfs
ntfsstatus="$?"
if [[ ! $ntfsstatus -eq 0 ]]; then
echo "Skipped"
continue
fi
if [[ ! -d /ntfs/windows && ! -d /ntfs/Windows && ! -d /ntfs/WINDOWS ]]; then
echo "Not found"
umount /ntfs >/dev/null 2>&1
continue
fi
echo "Success"
break
;;
*)
echo " * Partition $part not NTFS filesystem"
;;
esac
done
if [[ ! $ntfsstatus -eq 0 ]]; then
echo "Failed"
debugPause
handleError "Failed to mount $part ($0)\n Args: $*"
fi
echo "Done"
debugPause
# . ${postdownpath}fog.log
. ${postdownpath}fog.drivers
# . ${postdownpath}fog.ad
umount /ntfs
;;
*)
echo "Non-Windows Deployment"
debugPause
return
;;
esac
fog.drivers
#!/bin/bash
ceol=`tput el`;
manu=`dmidecode -s system-manufacturer`;
case $manu in
[Ll][Ee][Nn][Oo][Vv][Oo])
machine=$(dmidecode -s system-version)
;;
*[Dd][Ee][Ll][Ll]*)
machine=$(dmidecode -s system-product-name) #pruduct is typo, just realized sorry :(
;;
*)
machine=$(dmidecode -s system-product-name) # Technically, we can remove the dell one as it's the "default"
;;
esac
[[ -z $machine ]] && return #assuming you want it to break if it is not lenovo or dell?
machine="${machine%"${machine##*[![:space:]]}"}" #Removes Trailing Spaces
#############################################
# Quick hack to find out if the installed OS image is a x86 or x64
system64="/ntfs/Windows/SysWOW64/regedit.exe" # sloppy detect if 64bit or not
[[ ! -f $system64 ]] && arch="x86" || arch="x64"
#############################################
#this section has been updated to bring the osn names in line
# with how the Dell CABs are defined
case $osid in
5) osn="win7" ;;
6) osn="win8" ;;
7) osn="win8.1" ;;
9) osn="win10" ;;
esac
#############################################
dots "Preparing Drivers"
# below creates local folder on imaged pc
# this can be anywhere you want just remember
# to make sure it matches throughout! (case IS important here)
clientdriverpath="/ntfs/Windows/DRV"
remotedriverpath="/images/drivers/$machine/$osn/$arch"
[[ ! -d $clientdriverpath ]] && mkdir -p "$clientdriverpath" >/dev/null 2>&1
echo -n "In Progress"
#there's 3 ways you could handle this,
#driver cab file, extracted driver files or both
#so on the server put extracted driver files to match below folder tree
#i.e. Model Latitude E5410, Windows 7 x86 image would be:
#/fog/Drivers/Latitude E5410/win7/x86
echo "System breakpoint";
debugPause;
rsync -aqz "$remotedriverpath" "$clientdriverpath" >/dev/null 2>&1
[[ ! $? -eq 0 ]] && handleError "Failed to download driver information for [$machine/$osn/$arch]"
echo "End driver copy";
debugPause;
#this next bit adds driver location on pc to devicepath in registry (so sysprep uses it to reference)
# remember to make devicepath= match the path you've used locally
#also do not remove %SystemRoot%\inf
#and to add more locations just use ; in between each location
regfile="/ntfs/Windows/System32/config/SOFTWARE"
key="\Microsoft\Windows\CurrentVersion\DevicePath"
devpath="%SystemRoot%\DRV;%SystemRoot%\inf;";
reged -e "$regfile" &>/dev/null <<EOFREG
ed $key
$devpath
q
y
EOFREG
echo -e "\b\b\b\b\b\b\b\b\b\b\b${ceol}Done"; # this just removes "In Progress and replaces it with done :-)"
What did your Powershell command look like? I would like to see that example. I am most familiar with it and the one main thing I need to work on is a for each from a csv file with all of our old junked computers and laptops returned from lease. We no longer need them in fog.
The repair worked Thank you all. But what about those other Apache errors? Should we be concerned or how can we fix those?
Thank you. We will give this a shot in the am. What about those PHP warnings? How can we fix those?