Best way to utilize FOG_1.5.0 on LAN



  • I have just upgraded my FOG server within the business to 1.5.0 and now the WIKI is quite out of date. Could anyone please link me to videos / guides on how to do the following:

    • Sysprep / Fogprep machines (Need fogprep.exe)

    • PC renaming to TAG number upon imaging

    • Joining Domain and going into correct container.

    • Adding drivers for different dell machines from 1 master image.

    • creating base image and inserting extra software.

    Thanks in advance


  • Moderator

    @callumhird said in Best way to utilize FOG_1.5.0 on LAN:

    so we can install all the required software from our file servers

    I would challenge you, that you don’t “need” to connect to the domain to map a drive to your file server to install software. If there are applications that require AD credentials to install, then those should be installed post imaging via a snapin or some other software deployment tool like PDQ Deploy.

    The only software that I “must” install after imaging is our antivirus software because that application creates a unique GUID when its installed to identify the machine to the AV console. its not possible to clone a system after AV is installed because of this. But most all other applications can be installed before imaging without AD rights.



  • @george1421

    We add them to the domain so we can install all the required software from our file servers, then usually drop of the domain, logon as local admin and remove all domain accounts.

    If there is a better practice to follow when using FOG i am happy to change my procedures, my manager wants it to be used how you guys see fit.


  • Moderator

    @callumhird said in Best way to utilize FOG_1.5.0 on LAN:

    Can anyone attach a unattend.xml they have that works perfect that i can tweak?

    Here is a good place to start if you need a generic unattend.xml file: http://windowsafg.no-ip.org/


  • Moderator

    @callumhird said in Best way to utilize FOG_1.5.0 on LAN:

    this required us to drop PCs off the domain when “taking” an image

    This makes me think you are doing something different than traditional MS style imaging. Its best practices to never connect your reference image to AD before sysprepping and image capture. What is your logic to connect to AD during reference/golden image build up?

    In my comapny’s case we use MDT to build the reference image so its consistent each time we recreate the reference image. There is no need to connect the reference image to AD for anything during its build out. Actually by not connecting to AD it avoids any GPO policies from being applied and breaking imaging.



  • Can anyone attach a unattend.xml they have that works perfect that i can tweak?



  • We used to use another product for capturing images and deploying, this required us to drop PCs off the domain when “taking” an image.

    Do i need to do the same process with FOG and drop the PC off the domain and logon with the local admin account for running sysprep


  • Moderator

    @callumhird boy you have quite a wish list. Lets see if we can address them in order. Based on your questions I’m suspecting you are coming from a pretty old version of fog (i.e. 0.3x)??

    1. FOG no longer needs FOGprep. Just use your normal sysprep command and have sysprep power off the computer to ensure the disk is closed properly. If you just use shutdown partclone will complain that the disk was not shutdown properly and refuse to upload.
    2. This one is a little complicated. (this part may be a bit off-loint) The older versions of fog allowed you to have custom naming rules when you picked quick registration. That code has been removed since FOG 1.1.0. If you go through manual registration you can enter the asset tag there. What we have for our system naming is a LUM code and then the dell asset tag. When we do registration we will key in the LUM code and then use a usb bar code reader to “zap” the barcode on the dell computer’s chassis. This keeps us from having a type-o when entering the system name into FOG. Now once that is done, you can have FOG set the target computer system name. This is done with the FOG client. So the fog client service will need to be installed in your golden image if you plan on using some of the advanced fog features.
    3. The FOG client can join the computer to AD using the OU you define in the webgui. In my case we have a complex OU arrangement so the OU is calculated during imaging based on the hardware type (desktop/laptop/tablet), site code, and image name being deployed. This calculated value is then updated in the unatend.xml file dynamically during imaging using a FOG post install script.
    4. Use a FOG post install script I have a tutorial on how to do this. I will link it in a few minutes. [edit] Well it looks like the tutorial is all done except for the finishing: https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed
    5. The creating a base image is outside of the scope of FOG. It is up to the IT admin on the best way to setup the golden image for their company. In my case I use MDT to build a consistent golden/reference image every time. Then I capture and deploy with FOG.

 

518
Online

41.9k
Users

12.5k
Topics

117.7k
Posts