Topics created by Jonathan Cool

Hey !
I’m back … with some good news : it’s works !
After deployed the new 21h2 clean image, i can see the C:\Windows\DRV\x64 on the 640G2 !
Youpiiiiiiiiiiiiiii … but … the script fog.copydrivers can used .CAB with DELL or not ?
Because i tried to deploy my 21h2 clean image on a o7050 … and no DRV folder after deploy … maybe we need just use x64 folder for all machines instead of .CAB for DELL now ?

#!/bin/bash ceol=`tput el`; manu=`dmidecode -s system-manufacturer`; dots "Identifying hardware" case $manu in [Ll][Ee][Nn][Oo][Vv][Oo]) machine=$(dmidecode -s system-version) ;; *[Dd][Ee][Ll][Ll]*) machine=$(dmidecode -s system-product-name) ;; *I[Nn][Tt][Ee][Ll]*) # For the Intel NUC and intel mobo pick up the system type from the # baseboard product name machine=$(dmidecode -s baseboard-product-name) ;; *) # Technically, we can remove the Dell entry above as it is the same as this [default] machine=$(dmidecode -s system-product-name) ;; esac # if the machine isn't identified then no need to continue with this script, just return to caller if [[ -z $machine ]]; then echo "Unable to identify the hardware for manufacturer ${manu}"; debugPause; return; fi echo "${machine} Identified"; # Removes Spaces in machine name, works better with path definitions machine="${machine%"${machine##*[![:space:]]}"}"; # Jeffrey Boulais posted that the above code did not work for his install. He # supplied this code as an alternative. If you run in to a problem using my code # comment out my code and see if his code works better for your installation. The # only right way is the one that works. Thank you Jeff for your input. # machine="$(echo -e “${machine}” | tr -d ‘[:space:]’)" dots "Verifying we've found the OS disk" if [[ ! -d /ntfs/windows && ! -d /ntfs/Windows && ! -d /ntfs/WINDOWS ]]; then echo "! OS root Not found !"; debugPause return; fi echo "Found"; dots "Verifying target Arch" system64="/ntfs/Windows/SysWOW64/regedit.exe" [[ ! -f $system64 ]] && arch="x86" || arch="x64" echo "${arch} found"; debugPause # set osn path names based on the osid set in the FOG WebGui case $osid in 5) osn="Win7" ;; 6) osn="win8" ;; 7) osn="win8.1" ;; 9) osn="Win10" ;; esac dots "Preparing Drivers" clientdriverpath="/ntfs/Windows/DRV" # remotedriverpath="/images/Drivers/$machine/$osn/$arch" remotedriverpath="/images/Drivers/$osn/$machine/$arch" debugPause if [[ ! -d "${remotedriverpath}" ]]; then echo "failed"; echo " ! Driver package not found for $osn/${machine}/$arch ! "; debugPause; return; fi echo "Ready"; debugPause [[ ! -d $clientdriverpath ]] && mkdir -p "$clientdriverpath" >/dev/null 2>&1 echo -n "In Progress" rsync -aqz "$remotedriverpath" "$clientdriverpath" >/dev/null 2>&1 [[ ! $? -eq 0 ]] && handleError "Failed to download driver information for [$machine/$osn/$arch]" debugPause # the following code is only valid for Windows 7 operating systems since Windows 8 and beyond # relies on the unattend.xml section to locate OEM drivers. If you are no longer deploying Win7 # you may exclude this section. 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

@sebastian-roth Ok !
Many thank for your precisous time. I have learned many thinks with your answers !

Sorry, I’ll post a new topic.

After lots of trying I’ve been able to deploy printers. The main problem was the name of the printer, which is not clear what it should be.

I’ve put the details in a new topic: https://forums.fogproject.org/topic/14891/problems-deploying-printers

Thanks for your help!

Thank you to all for your answers.

I think, i will use the safe approach : i will clone my existing Golden Win 7 image in Virtual Box.
With the cloned image, i will install Ubuntu with Grub and upload the new “Golden Dualboot Win7/Ubuntu image”.

In my ref image, i do … nothing 'cause all conf", softs and scripts are run at the post-deployement …

I will try this approach and “i will be back” with the results.

Thank you for “the right way” 😉

This old topic is solved !
I was setup a new FOG stable server on a debian (on a new disk) and snapins works flawlessly.

Solved ! 😉

Hi,
Today is a good day !
i tried a new test : i used an other NAS (Seagate) and created a public share.
With the same windows 10 station, i can xcopy files as SYSTEM and the printer was correctly installed.

So, now, on the Syno NAS, i will tried to join our domain … i will be back 😉

@Quazz Thanks again for your work on this! I’ll add this soon but have one more question about it, see on github.

What are your thoughts on https://forums.fogproject.org/topic/12428/win7x64-golden-image-partitions-problems-again/29 as an alternative system, by the way?

Good you reminded me on this! I moved the issue from repo fogproject to fos#18 where it belongs now that we have those things separated a while ago. Please let’s try to collect information and ideas there.

@Jonathan-Cool Nice you got it working! We’ll add Quazz pull request anyway for the time being. Should be in there in the next couple of days. I’ll mark this solved now.

After reflexion, i wiil use the postinit script … Why ? Because if i receive a new model with the VBoxMouse.sys conflit driver, i will need to search again the culprit file into the Driver Pack … and waste many times …

So, in the fog.bonus, i added this :

# suppression du fichier VBoxMouse.sys ... eviter conflit et BSOD avec les Optiplex5050 durant SYSPREP (au 2nd reboot, durant verif perf. videos) rm /ntfs/Windows/System32/drivers/VBoxMouse.sys echo "Suppression du fichier VBoxMouse.sys pour eviter BSOD durant SYSPREP (au 2nd reboot) ... Done !";

I also added this in the SetupComplete.cmd :

rem uninstall VirutalBox Guest Additions : eviter les BSOD comme VBoxMouse.sys sur machine cible "C:\Program Files\Oracle\VirtualBox Guest Additions\uninst.exe" /S

I retried a download task on the Optiplex 5050 … and no BSOD 🙂

So … just many thanks again George for your help ! Knowledge growth up !

PS : how can pass the subject to “Solved” ?!

@jonathan-cool said in FOG PXE Configuration : the hide menu option / no menu option:

my collegues want to display the 3sec menu boot FOG on

Just use hide-menu. You have to enter valid credentials to show the menu if hide-menu is enabled. No credentials, no menu.

Marked this solved as the initial issue can be circumnavigated and we have a github issue open on that topic.

Hi,
Thank for answers …

@george1421 :
I’m not sure if i really understood your things …

You said :
you may need to use persistent groups to set some default actions
Can you write an example ?

You will have the most flexibility if you use the post install scripts to connect to AD
I use post install scripts to connect my AD with the desktop computer. But, for theses laptops, i don’t need to connect to AD …

I think, i’m not really need to alter the unattend.xml because i use a specific unattend file for theses laptops.

You can only install “things” that windows will find during installation : yes, i understood this part 🙂

I use my specific unattend file to create my user Utilisateur. But i can’t personnalize this user with unattend …

@Seb-B : i will try your way 🙂

I will be back !

My bad …
After many waste of time to find the culprit, i finally found it … : me !
Why ?
Because i realized many many MANY tests (upload task, download task) to create my best-dream-universal-win7x64-image …

So … i simply forgot to disable FOG service BEFORE ran sysprep on the Golden Image … (did it in the small test image)

Now, the Sysprep works fine …

But now, i know all sysprep logs … :

cbs.log setup.etl session.xml setupact.log in Windows folder setupact.log in Windows\Panther folder setupact.log in Windows\Panther\unattendGC folder setupapt.dev in Windows\inf setupapt.offline in Windows\inf setuperr in Windows\Panther …

Shame on me !

@Jonathan-Cool Use this: http://windowsafg.no-ip.org/

Many thanks for your reply.
I think, for the beginning, i will try the Quazz’s advice.

I will post my experience in this topic later …

@Jbob Thank you for your reply.
There is any solution to say to FOG : “i want manage the printers of this computer but, please, don’t delete the PDFCreator printer”.

@Sebastian-Roth Interesting … Maybe i can try to do not include the PDFCreator Printer in the image and add it (by snapins) on computers after the deploy task … but what is the result about the default Printer ? Need to be NOT the PDFCreator printer

Or maybe i just install all printers on the master, delete the printers by the Windows Printers Menu (except PDFCreator), upload the master.
On the clients, i just check “add printers” (instead of “add and delete”) in the FOG printers management ?

@Tom Elliott : Many thanks for your answer.
Now, i will use my brain and think if multicast is really necessary …
In french, a proveb say : “Le mieux est l’ennemi du bien”.

In few days, i will discuss with my collegue of the situation and we will choose a good decision about that.

PS : Learn guitar is hard but it’s a very cool hobbie 🙂

Because it has no idea where to look for the file?

The “This is not partclone image” error, so far as i know, only shows up on downloads, not uploads. are you sure you pressed the right button?
You said you deleted the OEM partition. Is there a blank space were it was, or did you expand another partition into that space?

Hi.
I found a temporary solution : after the upload, i connect to the NAS by FTP and move the files into …/fogimages/dev/@MAC to …/fogimages/“folder named in FOG interface”.
After that, the download task works on an other computer but only for Mint Linux OS … (other distrib’ not tested yet). With Windows 7 image, i have an error message …
Maybe i need to create a new topic about this new issue ?