@george1421 Ok, I’ll work on getting them automated. One more question. So the file you’re referring to called sysprepper.cmd is what you built to copy the files? Or can I look it up online to create that file? Where in the task sequence do I put it in to copy those files? Can you send a screen shot for example? I’m assuming copying the custom unattended.xml file replaces the one MDT uses during deployment?

@george1421

I think they’re mostly coming from the ini files. I would need to check.
If worse comes to worse, I can boot the vm, add in the third party apps and when I’m done with everything, just run light touch to sysprep it, correct? Also if I go that route, where should I configure the unattended file? From the unattended tab in MDT? Or directly on the vm like c:\windows\panther for example? I think the unattended file I got confused with last year on where to edit and think that’s another reason why my drivers didn’t transfer over.

@george1421 Ok, my bad, I meant reference WIMs. But for example, how do you handle in house apps to install and configure automatically? We have a few apps that’s in house and we need to configure the settings after install, 1 app we need to configure to point to the G drive to a server for example and our old way we used the USB and bring down the image with Acronis, which I don’t want to do anymore, know what I mean?

@george1421 ok, I get it now. I’ll play around with it this weekend. And thanks to you, I have a better grasp with MDT 2013 update 2. Do you do what most do like have 2 WIMS? Example, one will be a reference image with like antivirus, office 2013, VNC with up to date windows updates and the other WIM will be a little fatter with other company in house apps that are a little harder to auto install?

@MotD Hey there Motd. So I took a break off of this for a while due to being busy with work projects.
So when you added your drivers onto the fog server for Lenovo, the product name worked compared to for example Lenovo ThinkPad T570?

Hello, all,

I’ve been a member for about 2 years now I think and can’t thank you all enough with tutorials I’ve seen
on the site. Ok, so here’s my dilemma. I took a break from all of this because I got swapped with my current position (like desktop support for example). I understand how MDT 2013 works now and all, but has anyone come across after finishing a Windows 10 reference image the administrator account doesn’t have rights to the windows store?

Is there a script to allow the account not do so? I was trying to see maybe I can create another account during the MDT to log in after deployment? haven’t found anything on line as yet to add to the MDT task.

Also has anyone used Fog to deploy to different Lenovo ThinkPad models? example, X1 Carbons, T560, T570 & T580? I know there were codes written up for specifically Dell, but just need more steps on preparing for Lenovo laptops. I want to go with the MDT route instead of using audit mode, feel like MDT is the way to go with the unattend.xml, etc…

thank you again.

@george1421

Ok, thanks for the explaination George, appreciate your help.

@george1421

George, ok, thanks for explaining that to me. Now I understand why I saw _x86_64 and I changed the
folder in the osn back to x64. I guess where I’m lost is for example, I installed the Lenovo sccm drivers for a T570 laptop, right? then in each folder, I took any inf’s I can find and put it in the x64 folder. The structure I followed on your other pages and in the file is /images/Drivers/ThinkPad T570 W10DG/Windows 7/x64.

I did Windows 7 because when I ran the fog debug, it came out osname=Windows 7. Now my question is in the fog.drivers script for example, do I change osn to osname=Windows 7? I know I tried that yesterday and it didn’t work.
When I changed the folder back to x64, during driver deployment, it goes quickly and says done instead of failed, which is good, but the drivers never make it to the T570…

Not sure what I’m doing wrong.

@george1421 @Quazz

Thank you both. George, I know you said you’re still working on the driver injection-2017, but I’m testing it out right now as I’m trying to understand more about Linux commands to put under my belt, you know. Quazz/George,
in the fog.copydrivers, I put in where it says && arch= and arch= I put x64 and removed where it had 86.

@george1421 [0_1512049987850_fog sample.pdf](Uploading 100%)

I did a command in the Fog OS called uname -m which gave me the architecture of x86_64. Now I thought
under the architecture on the fog server, I’d call the folder _x86_64 instead of x64. Is that not correct? I was fighting with this yesterday, but working at it now, will post once I have an update. Please tell me if I have this correct, attached the pic.

@george1421

Hey George, hope all is good. So I’ve taken a break from this as I got busy with my job, so I’m almost there with this.
I copied and pasted the fog driver script and also ran a debug to confirm on the Lenovo laptop, it’s dmidecode -s system-version. Now my question is that for example, the version name for the machine is Lenovo T570 W10DG ( a zero by the way, not an o) how am I supposed to load the drivers? I have the structure as /images/Drivers/$machine/$osn/$arch, so /images/Drivers/Lenovo T570 W10DG/win7/x64 and I downloaded the drivers for sccm for example and let them in their folder structure, ex; network, display, etc… with all the files in it.

My assumption was that fog will look throughout the subfolders under x64 for the correct drivers, or am I wrong? I then decided to take all of the inf drivers from the subfolder an past them in the x64 folder, but I still couldn’t get the drivers to install. Please look at the fog.driver file:

#!/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”

if [ -d $remotedriverpath ]; then

[[ ! -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

rsync -aqz “$remotedriverpath” “$clientdriverpath” >/dev/null 2>&1
[[ ! $? -eq 0 ]] && handleError “Failed to download driver information for [$machine/$osn/$arch]”

#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 :-)”

fi

@george1421 George, 2 more questions as I’m starting to get the hang of MDT 2013 and fog. How do I put in the task to change the registry to put c:\drivers for where Fog will drop the drivers for the Lenovo machines? And the other thing that’s giving me an issue, where else in the fog.drivers script do I edit c:\drivers?

Other than that, I’m feeling confident I’ll be able to deploy our fleet.

@Jamaal said in FOG Post install script for Win Driver injection:

@george1421 George, I think I got the name correct for the Lenovo, getting further than before. I remember I had the name structure as ThinkPad T560 under the drivers folder, but getting stuck at Preparing Drivers… in progress. In the task menu on the web, it only shows like 1% and not moving. Any idea on why that’s happening?

I think I see what is the issue. Just that the screen moves too fast and said no such file or directory and it reboots.

@george1421 George, I think I got the name correct for the Lenovo, getting further than before. I remember I had the name structure as ThinkPad T560 under the drivers folder, but getting stuck at Preparing Drivers… in progress. In the task menu on the web, it only shows like 1% and not moving. Any idea on why that’s happening?

@george1421 Ok, I’ll try that tomorrow when I go back to work. Thanks for the info, but can you tell me about the joining of the domain? or maybe it’s best if I use a script to just join it?

Hello, George,

1st off, thanks for all of your documentation on this. I’m getting further than before in my deployment.
I’m however stuck on a few things, so I’ll provide as much info as you need.
Fog server running on Ubuntu 16.04 server
Fog server version: 1.3.0-RC-10.

So here are the machines and other things we have in our environment:
laptops: Lenovo ThinkPad T540p, ThinkPad T560, Lenovo ThinkPad T530, and other lower models.
Desktops: Lenovo ThinkCentre M800

I used MDT 2013 Update 2 as you were saying about MDT and I took an image on our VMware and deployed the image on a ThinkPad T560 from the fog server I have on our VMware. On my fog server, there is already an image folder, so I created under there drivers/ThinkPad T560/win7/x64. 0_1482360759122_Lenovo.docx

Now do I need to create another subfolder under the root like images 2 or something like that? Sorry, I’m a Windows guy and still getting used to Linux. I also replaced the fog.postdownload with what you have in this forum and ran that chmod command and looked like it took it.

When I deploy the image to the T560, it 1st gave me an error with the fog.driver script from in the forum that failed to load the driver, had it just Thinkpad T560, had to do ThinkPad T560, then it would get stuck on in process during the driver loading and when it was preparing it for the first time, I would get errors during syspre that it had errors, forgot the exact error, so I would restart it and get an error windows rebooted and reinstalling Windows during the sysprep.

Can you tell me what I’m doing wrong? also I’m unable to join the machine to my test domain. I did the hostnamechanger and did the encrypt, but still won’t join my test domain, the account is not a domain admin, but I gave it delegate to the test OU I created. Does it need the hostnamechanger for 1.3.0? I verified the options in AD on the console are checked off.

Look at the Word attachment I’ve attached.

I just don’t want to screw up anything on the network because of my experimenting.

Hello,

I’m new to Fog and the whole Linux thing. I have a desktop that has Unbutu desktop at my job with the fog server installed. When I try to boot up a test Lenovo T420 in PXE mode, it failes. Now I have both the desktop and laptop in the same switch, but I think I didnt configure something correctly during the setup.

we have existing DHCP and DNS servers on our LAN and I don’t want to screw up anything. I looked at guides on Fog’s website, but too many conflicting ways of doing things.

Can someone please give some advice on how to setup the fog server? I got a static IP from the networking team since I requested it. Any help would be appreicated.