I should say this is giving extra information on paat’s post - I am having the same issue
Chris Shipley
@Chris Shipley
I run a small IT Services provider firm based in CT, USA
Best posts made by Chris Shipley
-
RE: Installation ERROR: Fresh Install with current git trunk version.
-
RE: Installation ERROR: Fresh Install with current git trunk version.
Tom poked around on my setup and found an error to push out - stay tuned for his update.
-
RE: ...boot.php... Permission denied
@Sebastian-Roth I had the same symptoms that @jasonm had. I tried the resolution you put on May 6, 2020 and that worked to resolve my permission denied issue.
Latest posts made by Chris Shipley
-
RE: ...boot.php... Permission denied
@Sebastian-Roth I had the same symptoms that @jasonm had. I tried the resolution you put on May 6, 2020 and that worked to resolve my permission denied issue.
-
RE: Start Menu after Sysprep - non-Fog issue
@x23piracy that did the trick for me, now i just need to read up on where to put that handy CMD file you wrote. thanks so much.
For those that are doing that post deployment where a user already logged in, had to reboot in safe mode, delete the files, remove the profile from profilelist in registry, change the folder name in c:\users\USERNAME to c:\users\USERNAME.BAK, reboot, and then the user logged in again and it was good.
-
RE: Start Menu after Sysprep - non-Fog issue
@Sebastian-Roth I appreciate that, and I did try to search the forums but didn’t turn up a result. Perhaps my search was too narrow.
@x23piracy Thank you, I’ll give this a go. It is the first time I tried copyprofile, i thought for sure it would, i don’t know, copy all the windows start menu, default file associations, shortcuts on the desktop … I may just avoid this in the future. I’m using 1803, and will report back after I give that a go and create a new user profile.
-
Start Menu after Sysprep - non-Fog issue
This was the most appropriate forum I could find to post about this issue. I’m having trouble with an image I created and post sysprep, “search” from the Start Menu isn’t working correctly. It just gives me dots that move across the top of the search (see screenshot below). Can anyone offer some insight on this for me, or a better forum to ask about imaging windows with sysprep in general? This is a Windows 10 1803 image. There used to be a Windows 10 Start Menu Troubleshooter from Microsoft, but it appears they’ve removed that and suggest you “Reset your PC” - I’d rather not do that just now.
Happy to hear any and all suggestions. So far I’ve tried:
- SFC /scannow
- Reinstalling all Win10 apps (including Cortana and Start Menu)
- Rebuilding the search index
I have -NOT- tried:
- Reset My PC - this would be very painful for us right now
-
RE: Latest dev update, postdownload driver script broken
thanks. I emptied the drivers folder and it went through - perhaps the extra script information will assist me to find out why it failed when i had drivers in it. let’s mark this resolved.
-
RE: Latest dev update, postdownload driver script broken
this system downloaded drivers fine before the update, same system. and yes, using the driver injection.
For user names, I tried the UI user not the linux fog user. I’m not positive what password it uses. Here is the fog.drivers script:#!/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 system64="/ntfs/Windows/SysWOW64/regedit.exe" # sloppy detect if 64bit or not [[ ! -f $system64 ]] && setarch="x86" || setarch="x64" ############################################# #this is not section necessary needed, it's just to make the path "human readable" #rather than using osid for filepath 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! clientdriverpath="/ntfs/Windows/DRV" remotedriverpath="/images/Drivers/$osn/$machine" [[ ! -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: #/images/Drivers/Win7/Latitude E5410/x86 rsync -aqz "$remotedriverpath" "$clientdriverpath" >/dev/null 2>&1 [[ ! $? -eq 0 ]] && handleError "Failed to download driver information" #if you wanted to use driver.cab use this line below. #i.e. /images/Drivers/Win7/Latitude E5410/E5410-Win7-A07-KTT4G.CAB #cabextract -d "$clientdriverpath" "$remotedriverpath/*.CAB" >/dev/null 2>&1 #if you wanted to mix both cab and extracted use these: #rsync -aqz --exclude='*.CAB' "$remotedriverpath" "$clientdriverpath" >/dev/null 2>&1 #[[ ! $? -eq 0 ]] && handleError "Failed to sync cab and non-cab drivers" #cabextract -d "$clientdriverpath" "$remotedriverpath/*.CAB" >/dev/null 2>&1 #[[ ! $? -eq 0 ]] && handleError "Failed to extract cab files" #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;%SystemRoot%\DRV"; 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 :-)"
-
Latest dev update, postdownload driver script broken
Server
- FOG Version: 1.4.0-RC-9.3
- OS: Centos CentOS Release 6.8
Client
- Service Version: what came with 1.4.0-RC-9.3
- OS: Windows 10
Description
Prior to the latest update, drivers were downloading great. Now they are not, however. Please see attached screenshot for the error message. It’s not very detailed. I tried to ftp://foghost/images but it came up with an authentication screen: neither the CentOS root or fog user has access to it - not sure if that’s normal.
-
RE: Git pull failed
Which, after running the install script again, worked fine. Thanks, @Tom-Elliott
-
RE: Git pull failed
Here are the results of that:
[] cd /root/fogproject [] git reset --hard HEAD is now at ded2598 Use predefined set of cores - 1 for zstd reasonings. Use PIGZ to decompress gzip compressed images rather than relying on seemingly faulty zstd decompression of gzip. [] git checkout master Branch master set up to track remote branch master from origin. Switched to a new branch 'master' [] git pull Already up-to-date. [] git checkout dev-branch Switched to branch 'dev-branch' [] git pull Already up-to-date.