Enable FOG Rename after Driver Install



  • I ahve an automated process for installing drivers on my computers after an image. But FOg rename/join domain reboots the computer part way through the driver install process.

    Is there a way to only start FOG rename after the first reboot or delay it a set amount?


  • Testers

    I am doing the same thing. I actually have modified the SAD2 script to determine the make and model of the machine and use custom driver packs for each machine. I am finishing up the script and testing it on a few more of our models. When I get it complete I can post, along with a howto on the way I have it set up and running. I found that you do not need to have the machine logged into run it, I have it so that in case it reboots during the middle it will even resume the install so that you make sure all the drives get installed.



  • I am creating a SAD pack from http://driverpacks.net/ and then calling it in a script on first login. Sysprep does one automated login for me.



  • @TJ333, post: 12747, member: 793 said:

    That did it. I tried using sc config “Fog service” start= auto before but I added it to the run in GUI section of sysprep to try and get it to run. That does not work. What does work is creating a separate batch file to enable FOG and have sysprep call the batch file.

    Thank you for the help.

    Can you please let me know how you are automating the driver install?



  • That did it. I tried using sc config “Fog service” start= auto before but I added it to the run in GUI section of sysprep to try and get it to run. That does not work. What does work is creating a separate batch file to enable FOG and have sysprep call the batch file.

    Thank you for the help.


  • Testers

    Actually update to my last post that may be a better solution for you is this:

    1. on your image set the Fog service as disabled
    2. In your script at the very end add these 2 lines:
      sc config “Fog service” start= auto
      net start "Fog service"
      This will keep the service from starting at all until the script is done and set it to auto start from then on

  • Testers

    Is the driver script coming from the FOG server as a snap in or is it called as a first run command through sysprep? If it is the later then it should be the first thing command that you use in the script. I personally call my script from FOG as a snap in and it doesn’t deploy until after the machine is already named and joined to our domain.



  • net stop “Fog service” is how I am entering the command because that is what works on the command line. Unfortunately despite trying to put it in both sysprep and the driver script in different places it does not seem to be effective in stopping FOG service before it starts renaming.


  • Testers

    If you are using a script for driver installs you can add “net stop Fog service” to the beginning of it and then “net start Fog service” at the end.


Log in to reply
 

324
Online

38729
Users

10555
Topics

99938
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.