• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Raj G
    R
    • Profile
    • Following 0
    • Followers 1
    • Topics 2
    • Posts 7
    • Best 0
    • Controversial 0
    • Groups 0

    Raj G

    @Raj G

    0
    Reputation
    532
    Profile views
    7
    Posts
    1
    Followers
    0
    Following
    Joined Last Online

    Raj G Unfollow Follow

    Latest posts made by Raj G

    • AD Join Issue Using Script and Answer File
      Server
      • FOG Version: 1.3.0-RC-8
      • OS: CentOS (don’t remember what version)
      Client
      • Service Version: v0.11.5
      • OS: Windows 10
      Description

      So I am using the following script post download for builds for one of my clients:

      #!/bin/bash
      hostadpwd="ADPASSHERE"; #only downside to this method- this is the plain ad password
      unattend="/ntfs/Windows/Panther/unattend.xml";
      [[ ! -f $unattend ]] && return
      dots "Preparing Sysprep File"
      rm -f /ntfs/Windows/System32/sysprep/unattend.xml >/dev/null 2>&1
      if [[ ! $? -eq 0 ]]; then
          echo "Failed"
          debugPause
          handleError "Failed to remove original unattend file"
      fi
      echo "Done"
      debugPause
      dots "Writing Computer Name"
      sed -i "/ComputerName/s/*/$hostname/g" $unattend >/dev/null 2>&1
      if [[ ! $? -eq 0 ]]; then
          echo "Failed"
          debugPause
          handleError "Failed to update originating unattend file"
      fi
      echo "Done"
      echo "ComputerName set to $hostname"
      debugPause
      [[ -z $addomain ]] && return
      dots "Set PC to join the domain"
      sed -i "/<JoinWorkgroup>/d" $unattend >/dev/null 2>&1
      if [[ ! $? -eq 0 ]]; then
          echo "Failed"
          debugPause
          handleError "Failed to remove the Workgroup setter"
      fi
      sed -i \
          -e "s|<Password></Password>|<Password>${hostadpwd}</Password>|g" \
          -e "s|<Username></Username>|<Username>${addomain}\\\\${aduser}</Username>|g" \
          -e "s|<MachineObjectOU></MachineObjectOU>|<MachineObjectOU>${adou}</MachineObjectOU>|g" \
          -e "s|<JoinDomain></JoinDomain>|<JoinDomain>${addomain}</JoinDomain>|g" $unattend >/dev/null 2>&1
      if [[ ! $? -eq 0 ]]; then
          echo "Failed"
          debugPause
          handleError "Failed to update user, pass, ou, and domain setter"
      fi
      echo "Done"
      debugPause
      

      So one question with this: where I have the AD password listed, would that have to be the domain Administrator account’s password or the password for any account that has admin rights (e.g. the main support account that I use).

      I also remember reading as follows from one of the tutorials that my Answer file (unattend.xml) needed to include the following:

      <JoinWorkgroup>Workgroup</JoinWorkgroup>
      <Credentials>
      <Password></Password>
      <Username></Username>
      </Credentials>
      <JoinDomain></JoinDomain>
      <MachineObjectOU></MachineObjectOU>
      

      Silly question, but under what section in the Answer File would I need to put that?

      Thanks!

      posted in Windows Problems
      R
      Raj G
    • RE: Printer Setup Using FOG

      @Joe-Schmitt said in Printer Setup Using FOG:

      @Raj-G the printer tool can be downloaded form here: https://github.com/FOGProject/fog-client/releases/tag/0.11.9

      Sounds good; is there any documentation on that (in terms of what server version should be used, simple setup, etc.)? I don’t remember seeing anything on the Wiki.

      Thanks.

      posted in Tutorials
      R
      Raj G
    • RE: Printer Setup Using FOG

      @Wayne-Workman said in Printer Setup Using FOG:

      I’ve used FOG with the FOG Client to deploy over 90 printers to 2,000 clients. My recommendation is to absolutely under no circumstance deploy a printer via fog without verifying first that it works. I’ve gone down that road before, it wasn’t fun. Do not let technicians in your organization just do as they please - this is an area that can be screwed up and difficult to recover from.

      Setup your printers in FOG - use the FOG Printer Helper program to assist you with figuring out the parameters.

      Typically, you would manually install the printer first. Run the FOG Printer Helper program, get the correct parameters it requires, and test deploying the printer via fog to ONE system. If necessary, make available any needed drivers from an anonymous read share.

      There’s a lot that goes into FOG Printers - but it can be done, I’ve done it before, several have done it, and you can too.

      Hey Wayne,

      The FOG Printer Helper program is on the FOG Server (the management dashboard) I assume? From what I’ve seen on the FOG Wiki, the printer setup info seems outdated, but might be similar to what’s in place now?

      Like you said, I certainly don’t want to mess this up especially if it breaks during testing.

      Thanks!

      posted in Tutorials
      R
      Raj G
    • Printer Setup Using FOG

      Hi all,

      I was looking to see if anybody has recently setup printers with FOG. Part of me was thinking that we might as well just use scripts to install said printer drivers, but that would involve replication to each model type in the field for our clients.

      Essentially, what is the best practice to deploying and managing printers in FOG, or is best to let Windows handle that portion?

      Thanks!

      posted in Tutorials
      R
      Raj G
    • RE: Utilizing Postscripts (Rename, JoinDomain, Drivers, Snapins)

      @Lee-Rowlett
      Silly question on the FOG client, but I gather you’re referring to the web client on the FOG server we’re using correct? The FOG Service on the host PC would pull from the information/data we have on the FOG server for printers, snap-ins, etc. correct?

      Thanks!

      posted in Tutorials
      R
      Raj G
    • RE: Utilizing Postscripts (Rename, JoinDomain, Drivers, Snapins)

      Hi all,

      New user here, working with my team head to get a FOG server setup; all these scripts have been super useful for drivers and such. Just need to SysPrep our image and we’re good to go. That being said, I have a question about the Snap-Ins script here.

      We have just about the same software setup for most of the users for a client we service; however, we have about half our users who have a full Office 365 (Office 2016 install) and the others don’t, while we have a hodgepodge of users that use some specific apps for their work (scattered between folks who use Office 2016 and not).

      Do I simply put in the installation executables in the SnapinData/Map Files folders or does this script for Snap-Ins need to change? I’m not great at scripting at all, but I wondering what would need to change in this script.

      Script from @Lee-Rowlett as follows:

      #!/bin/sh
       
      snpchk=`wget -O - --post-data="mac=${mac}" "http://${web}service/snapcheck.php" 2>/dev/null` #checks for snapintask
      if [ "$snpchk" == "1" ]; then
          setupcmd="/ntfs/Windows/Setup/Scripts/SetupComplete.cmd";
          mkdir /ntfs/Windows/Setup/Scripts
          #this line below pulls my latest build script from server
          cp /fog/CompleteBuild/CompleteBuild.exe /ntfs/Windows/Setup/Scripts/CompleteBuild.exe  &>/dev/null
          #copies lastest setupcomplete.cmd from server
          #which only actually contains one line to execute
          #C:\Windows\Setup\Scripts\CompleteBuild.exe
          cp /fog/CompleteBuild/SetupComplete.cmd $setupcmd #above script
          sloc="/ntfs/Windows/Setup/Scripts/Node.txt"; # this is just so my above script
          #knows which node to use to run software from (if needed) left in to give you
          #guys ideas....
          echo "$storageip" >> "$sloc"; # writes node ip to the text file
          #next line gets snapin name
          snapname=`wget -O - --post-data="mac=${mac}&getSnapnames=1" "http://${web}service/snapcheck.php" 2>/dev/null`
          #next gets snapin argument/switch
          snaparg=`wget -O - --post-data="mac=${mac}&getSnapargs=1" "http://${web}service/snapcheck.php" 2>/dev/null`
          #this next line adds the switch to the setupcomplete.cmd
          # so if switch was /DefaultBuild .cmd line would now look like:
          #C:\Windows\Setup\Scripts\CompleteBuild.exe /DefaultBuild
          #if switch empty just nothing gets added
          sed -i -e "s|$| ${snaparg}|g" $setupcmd
       
          #this is self explanatory - some of our builds rely on 24GB of map files
          #rather than adding them to the "general" image
          #as it's the select few machines
          #i get fog to add it for me after imaging
          #so if they ever change, just update on server, job done.
          if [ "$snapname" == "MAP Build" -o "$snapname" == "Example Build" -o "$snapname" == "Test Build" ]; then
              dots "Downloading Map Files";
              echo "In Progress";
              rsync -a --info=progress2 "/fog/SnapinData/Map Files" /ntfs
              echo " * Downloading Map Files Completed.";
          fi
      else
          echo "No Snapin Task Found - Snapin Setup Skipped";
      fi```
      posted in Tutorials
      R
      Raj G