• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Liam Sullivan
    3. Posts
    • Profile
    • Following 0
    • Followers 0
    • Topics 5
    • Posts 24
    • Best 1
    • Controversial 0
    • Groups 0

    Posts made by Liam Sullivan

    • RE: Adding Needed Repository............. Failed!

      Hey,

      Okay so I’m updating this so that any other users hitting this problem under these circumstances can hopefully get to a resolution.

      So it turns out that the problem is my self signed certificate. So I added the cert to the ca-certificate store and included it as trusted. This had no effect. SVN and Git methods were still rejected. In fact SVN just hangs. So tried SVN with --non-interactive --trust-server-cert options and it still refused to connect.

      In the end I worked round Git by running the following command to configure it to basically not verify SSL certs:

      git config --global http.sslVerify false

      This actually worked in that it allowed me to clone the Git repo. Success, or so I thought 😕

      I ran the install from the cloned repo and hit a different error:

      • Adding needed repository…/lib/common/functions.sh: line 456: /var/log/fog_error_5937.log: No such file or directory
        …/lib/common/functions.sh: line 457: /var/log/fog_error_5937.log: No such file or directory
        …/lib/common/functions.sh: line 458: /var/log/fog_error_5937.log: No such file or directory
        …/lib/common/functions.sh: line 460: /var/log/fog_error_5937.log: No such file or directory
        …/lib/common/functions.sh: line 461: /var/log/fog_error_5937.log: No such file or directory
        …/lib/common/functions.sh: line 462: /var/log/fog_error_5937.log: No such file or directory
        …/lib/common/functions.sh: line 463: /var/log/fog_error_5937.log: No such file or directory
        …/lib/common/functions.sh: line 464: /var/log/fog_error_5937.log: No such file or directory
        Failed!

      So any ideas on this one?

      Cheers!

      Sully

      PS: Thanks for all your efforts so far with this one Tom. Well beyond the call of duty mate. Nice one.

      posted in Linux Problems
      Liam SullivanL
      Liam Sullivan
    • Adding Needed Repository............. Failed!

      Hi Guys,

      I know this has come up before and I have trawled the forum and the internet in general looking for answers before I took to posting this issue again so apologies if this a bit like a broken record. Unfortunately none of the proposed solutions have resolved the issue.

      Heres the thing, I am trying to install FOG 1.3.0 SVN trunk onto my Ubuntu 14.04.2 server so that I can test it with Windows 10 deployments ready for this years refresh. I am hitting the error at the beginning of the install of FOG that states - Adding Needed Repository… Failed!

      The server is a clean Ubuntu 14.04.2 install running as a VM on VMware. It has already been operating as a web server so has Apache and MySQL already setup on it. Not sure if this is the issue? I have installed python-software-properties and software-properties-common. I am not behind a proxy. I used the wget method to retrieve the trunk as I was getting issues with SVN due to a self signed certificate on my firewall.

      Anyone got any ideas?

      Much appreciated 🙂

      Sully

      posted in Linux Problems
      Liam SullivanL
      Liam Sullivan
    • RE: TFTP & PXE from Windows

      Why don’t you save yourself a headache and just set FOG up the way it was intended then pass the DHCP option settings to whoever does have access to the DHCP server to configure. (Assuming you’re using a third party DHCP server from your original post) That way you wont have to faff on with this and you can have a fab fog server running peachy like 🙂

      posted in Windows Problems
      Liam SullivanL
      Liam Sullivan
    • RE: How to Setup Ubuntu Server/FOG 1.2.0/Create Univeral Windows 7 Image using Sysprep - Step-by-Step

      Sorry about the links, I’ve fixed all these in the tutorial now. Only took me 4 months to get round to it lol 🙂

      posted in Tutorials
      Liam SullivanL
      Liam Sullivan
    • RE: How to Setup Ubuntu Server/FOG 1.2.0/Create Univeral Windows 7 Image using Sysprep - Step-by-Step

      Hi
      You are quite correct I did gloss over that a bit, sorry. Basically, I saved the unattend.xml file on to a shared drive/folder on my network. You just install windows as you normally do either with a disc or mounted ISO in a VM. I would always use a VM btw unless there really is a reason not to. Snapshots are the key 🙂 Now, because your VM/machine will also be on your network in order to pull an image from it, you just access the shared drive where you saved the unattend.xml file from the VM and drag into the \System32\SysPrep folder as described in the walkthrough. Thats all it is, no need to modify any ISO’s.

      Good call on the WAIK tip, something else to note with that is that I found it wouldn’t let me create a 32 bit answer file on a 64 bit machine and vice versa either. Gotta love Microsoft.

      Good Luck 🙂

      posted in Tutorials
      Liam SullivanL
      Liam Sullivan
    • RE: How to Setup Ubuntu Server/FOG 1.2.0/Create Univeral Windows 7 Image using Sysprep - Step-by-Step

      I used Oracle virtualbox. Free and works perfectly every time

      posted in Tutorials
      Liam SullivanL
      Liam Sullivan
    • RE: Cant Find PXE and TFTP

      If your settings are correct as per Toms suggestion you could try restarting tftpd on the fog server. I’ve found that sometimes cures it. But only if you dhcp configuration is correct first.

      posted in FOG Problems
      Liam SullivanL
      Liam Sullivan
    • RE: Is FOG now happy with windows 8?

      Hi Paul

      Check the changelog on the WIKI - [url]http://www.fogproject.org/wiki/index.php/Main_Page[/url]

      Windows 8 support since FOG 1.0.0

      Hope this helps

      posted in General
      Liam SullivanL
      Liam Sullivan
    • RE: Is FOG for me?

      [quote=“prince xyryl, post: 34283, member: 25316”]And i can deploy the image in multiple destination pc all at once right?

      I have server2008r2 domain, pfsense router firewall, win7 and win8 on i3 and athlon, xp on pentium4 celeron[/quote]

      Yes you can run multiple tasks and deploy different image types simultaneously. You will need to build a different image for each OS of course but you can set up your machine groups in FOG and then push each image out to each group. Make sure when you set FOG up that you don’t allow it to be used as a DHCP server and that your DCHP options 66 and 67 on your Windows DHCP server are set correctly or iPXE wont boot. This is all covered in the guide I linked earlier 🙂

      posted in General
      Liam SullivanL
      Liam Sullivan
    • RE: Is FOG for me?

      Hi

      You already mentioned that you use VAMT for licensing, so depending on whether you use KMS or MAK keys for your install you will still use VAMT. Just supply either your KMS or MAK key in the unattend.xml file you’ll create while building your image and then once the machines are imaged you will licence them. KMS machines should in most cases check in with the KMS server that VAMT is running on and then license themselves, if your using MAK keys then you may need to use VAMT to perform an online validation en-masse. Depends on your setup, but due to the volume of PC’s we have here I use KMS. Simplifies everything a bit 🙂

      Hope this helps

      Cheers

      posted in General
      Liam SullivanL
      Liam Sullivan
    • RE: Is FOG for me?

      Hi Prince

      All of the above can be done with FOG. A full guide on how to do all of this can be found [URL=‘http://fogproject.org/forum/threads/how-to-setup-ubuntu-server-fog-1-2-0-create-univeral-windows-7-image-using-sysprep-step-by-step.11245/’]here[/URL].

      [QUOTE]1. Can I deploy WindowsXP/7/8 image to a different hardware? (DualCore PC to i3 PC)[/QUOTE]

      Yes you can create hardware independent images that can be deployed across different machines. The guide shows how to do this with Windows 7 however it can be done with XP and 8 as well.

      [QUOTE]2. Can I deploy a WindowsImage with custom applications installed ? like Install Windows* OS* then install applications I need like MSOffice and AdobeProducts then make Clone/Image of it and deploy to other hardware/PC.[/QUOTE]

      Yes you can add any applications you need into the image as you build it. A point to note is that I’ve found its best to create a “bare bones image”, i.e. Windows OS, all updates, MS Office, Adobe, Java, Flash etc. Then for additional applications I use the Snapins section of FOG. This is because I’ve found that when using Sysprep to create hardware independent images, some applications add registry keys that screw up the Sysprep process and then your images when deployed wind up booting in a loop. This is a Microsoft issue not a FOG issue. So far I’ve found it happens mostly with antivirus software but its likely not limited to just these.

      I am a little curious as to why the mixed OS environment, We have around 600 workstations on site ranging from brand new PC’s to those that are around 5-6 years old and I use only one hardware independent Windows 7 image for all of them with all of my apps installed.

      posted in General
      Liam SullivanL
      Liam Sullivan
    • RE: How to Setup Ubuntu Server/FOG 1.2.0/Create Univeral Windows 7 Image using Sysprep - Step-by-Step

      Cheers Junkhacker. Was bound to miss something. 🙂 Will edit to reflect.

      posted in Tutorials
      Liam SullivanL
      Liam Sullivan
    • RE: How to Setup Ubuntu Server/FOG 1.2.0/Create Univeral Windows 7 Image using Sysprep - Step-by-Step

      [B]Uploading your reference image to FOG[/B]

      1. After sysprep completes it will shut down your VM or workstation.

      2. On another machine, open your Fog Management Console [url]http://FogServer/Fog/Management[/url]

      3. Clicks Image Management -> New Image
        • Name the image something meaningful, enter a description if you desire and for Windows 7 make sure to set Image Type -> Multiple Partition Image – Single Disk (Not Resizable)
        i. This is why you need to use a smaller partition and we set the System Disk – Extend feature in
        the unattend.xml file.
        • Save your changes.

      4. Power the sysprep computer on and enter the BIOS screen. Ensure that the computer is set to PXE boot and that FOG’s PXE functionality is working on your network.

      5. When the computer reaches the FOG PXE boot menu, select Registration and Inventory and register the host. It helps to name it something that reminds you of its purpose. I usually do Win7x64Sysprep or the like.

      6. As you enter the options, make sure to select your new Host Image from the options and you can set the HOST OS.

      7. After the host registers shut the computer down.

      8. Now back in the web management interface; click Host Management -> List all Hosts – Select your imaging host. (Win7x64Sysprep)

      9. Click Update to save your changes.

      10. Click Basic Tasks (on the left) -> Upload

      11. Select Shutdown after Task Completion, if you need any scheduling you can enter that, and click Upload Image.

      12. Start up your VM or workstation you sysprepped. As it starts the PXE boot it will detect a waiting task from FOG
        and begin the image upload process.

      13. Once completed let the workstation power off and congrats! You’ve just created a universal Windows 7 image
        with easy deployment through FOG!!

      I hope I haven’t missed anything, I have attached this guide as a PDF in the original post that may be a bit easier to read! Good luck all 🙂

      posted in Tutorials
      Liam SullivanL
      Liam Sullivan
    • RE: How to Setup Ubuntu Server/FOG 1.2.0/Create Univeral Windows 7 Image using Sysprep - Step-by-Step

      [B]WORKSTATION IMAGE CREATION[/B]
      The installation of FOG only helps if you have an image to deploy. I’m going to focus first on the unattend.xml sysprep file, then we’ll quickly go through image creation and installation/configuration of the FOG client on the workstation.

      1. First download the Windows Automated Installation Kit (WAIK) for Windows 7 – [URL=‘http://www.microsoft.com/en-us/download/details.aspx?id=5753’]Here[/URL]
      2. Download and install the Windows 7 ISO image from the Volume Licensing Center
      3. Using a zip tool (I like 7-zip) extract the ISO to a folder.
      4. Open the Windows System Image Manager (the WAIK executable for our next step)
        • In the Bottom Left frame right click Select a Windows image or catalog file.
        • Browse to the extracted Windows 7 folder \Sources\install.wim and click Open.
        • Now we need to configure these unattended installation configuration. The settings are similar for an
        x86 installation but I’m going to be focusing on the 64 bit configuration in this guide.
        • Under Windows Image expand the section Components.
        i. Scroll down to amd64_Microsoft-Windows-Security-SPP_ (NOT the UX!!)
      5. Right Click -> Add to Pass 3 Generalize
      6. You’ll now see it appear under Components -> Pass 3 Generalize in the Answer File
        Frame.
      7. Select it, and in the right frame Microsoft-Windows-Security-SPP set SKIPREARM to 0
        ii. On the left frame scroll down to amd64_Microsoft-Windows-Deployment_neutral
      8. Right Click -> Add to Pass 4 Specialize
        a. Expand amd64_Microsoft-Windows-Deployment_neutral
        b. Right Click -> Extend OS Partition -> Add to Pass 4 Specialize
        c. Select in the middle frame d. In the right frame set
        i. Extend -> True
        e. Back in the left frame Expand -> RunSychronous
        f. Right Click -> RunSynchronousCommand -> Add to Pass 4 Specialize
        g. Select in the middle frame, and in the right i. Action -> AddListItem
        ii. Order -> 1
        iii. Path -> net user administrator /active:yes
        iv. Windows 7 natively disables the local admin account, we want to make
        sure it’s turned back on.
        iii. On the left frame scroll down to amd64_Microsoft-Windows-Shell-Setup_Neutral
      9. Right Click -> Add to Pass 4 Specialize
        a. Select and add the following settings to the right frame b. ComputerName -> *
        c. CopyProfile -> True
        d. ProductKey -> If you use a KMS server you can enter the generic KMS client key for your copy of windows. Otherwise enter your Volume Activation License key.
        e. ShowWindowsLive -> False

      f. TimeZone -> your current time zone. NOTE the documentation isn’t clear on how to enter these. You need to fully write it out e.g. Eastern Standard Time
      iv. In the left frame scroll down to amd64_Microsoft-Windows-International-Core_neutral

      1. Right Click -> Add to Pass 7 oobeSystem
      2. Select in the middle frame
      3. In the right frame.
        a. InputLocale -> en-US
        b. SystemLocale -> en-US
        c. UILanguage -> en-US
        d. UserLocale -> en-US
        v. In the left frame scroll down to amd64_Microsoft-Windows-Shell-Setup_Neutral
      4. Right Click -> Add to Pass 7 oobeSystem
        a. DisableAutoDaylightTimeSet -> False
        b. DoNotCleanTaskBar -> True
      5. Expand amd64_Microsoft-Windows-Shell-Setup_Neutral
        a. Right Click -> OOBE -> Add to Pass 7 oobeSystem
        i. HideEULAPage -> True
        ii. NetworkLocation -> Work
        iii. ProtectYourPC -> 1
        b. Expand -> UserAccounts
        i. Right Click -> AdministratorPassword -> Add to Pass 7 oobeSystem
      6. Set Value – to your desired local administrator account password.
        ii. Right Click -> Local Accounts -> Add to Pass 7 oobeSystem
        iii. Right Click -> Local Accounts in middle frame iv. Insert New Local Account
      7. Action -> AddListItem
      8. Description -> LocalAdministrator
      9. DisplayName -> Administrator
      10. Group -> Administrators
      11. Name -> Administrator
        v. Set password to match previous administrator password.
        vi. It seems odd to add this twice, but otherwise after sysprep it will still prompt for an initial local account name. It may be possible to remove the OOBE section, but I haven’t experimented with it.
        vi. You can also configure Taskbar and Start Menu settings to apply to all users. [URL=‘http://blogs.technet.com/b/askcore/archive/2010/03/16/how-to-customize-the-windows-7-start-menu-and-taskbar-using-unattend-xml.aspx’]Technet Article[/URL]
        • Save this file as unattend.xml
      12. Now for the easier part – Creating the windows install.
        • I like configuring my Windows 7 client images by installing them in a VM. This gains me the advantage of taking a snapshot prior to the sysprep. That way I can occasionally do windows update, add new software etc. then sysprep and recapture the image instead of starting over. I also recommend setting the hard drive or partition size at 20-25GB depending on how much you need to install. The reason for this is that the image can then be cloned to anything with a hard drive over that size, instead of needing to match the original drive size.
        • Either mount your ISO image or insert the CD into your test computer.

      i. After installing Windows, when you reach the Windows Welcome Screen and it asks you to create a username press [B]SHIFT-CTRL-F3[/B]

      1. This will enter Windows Audit mode, this mode is meant for image configuration prior
        to deployment and greatly simplifies the sysprep process.
        ii. One you’re at the desktop proceed with installing any necessary software, Windows Updates etc. This will really depend on your personal workstation needs for labs, offices and the like. My software image is pretty sparse as I use SCCM to auto-install most of my lab apps.
        [B]iii. For best results DO NOT ADD THIS COMPUTER TO YOUR DOMAIN!![/B]
        [B]1. OPTIONAL[/B]
        a. I configure my major system options through Group Policy, but you may want to set things such as System restore settings, Power Options, defrag, disk cleanup options etc.
        [B]iv. FOG Client Installation[/B]
      2. On your build system open your web browser and navigate to the FOG interface
        a. Download the FOG Client Service b. Extract the file and run Setup.exe c. On the Configuration page
        i. Enter the host name of the FOG Server. (you can use IP, but depending on firewalls and routing non-domain computers may have issues communicating which will disable the auto-domain join feature)
        ii. You can leave all other options selected as once the client service connects to the server it will copy the configured FOG options.

      [B]v. DRIVERPACKS!!![/B]

      1. This will be the greatest thing you ever use. Windows 7 has a number of built-in drivers and auto-detects a ton of hardware, but it can always be improved.
      2. So what we want to do is look at the DriverPacks repository - [URL=‘http://driverpacks.net/driverpacks/latest’]here[/URL]
      3. Find the version of Windows you are working with from the list.
      4. Not all of these files are needed, for most peripheral hardware (Touchpads, webcams etc.) the built-in windows drivers will function fine. What we need is the main system drivers crucial to booting the machine and getting network connectivity.
      5. I download Audio, Chipset, Graphics A, B, Mobile; LAN, Mass Storage and WLAN.
      6. Extract these files into C:\Windows\inf\DriverPacks
      7. There are other ways to install drivers but I found for adding 3-4GB to your image but gaining universal hardware functionality this is the easiest.

      [B]vi. Preparing to Sysprep[/B]

      1. **If using a VM as suggested, I HIGHLY recommend taking a snapshot before starting this process. If something is misconfigured you can easily revert back and fix it or use the snapshot to update software before refreshing your image file. **
      2. Browse to C:\Windows\System32\sysprep
      3. Copy your unattend.xml file to this location.
      4. Open a command prompt in administrative mode and browse to
        C:\Windows\System32\sysprep
      5. When you are absolutely ready to create your initial image, enter the following command
      6. sysprep /oobe /generalize /unattend:c:\windows\system32\sysprep\unattend.xml
        a. I’ll breakdown what this does as you may find you want to play with other
        settings.
        b. OOBE – configures Windows Welcome Mode, we’ve passed the initial user
        configuration to re-enable the admin account which is all this is used for
        c. Generalize – This resets the Security ID of the computer, removes all restore points and event logs and passes the initial hardware configuration and services startup to make the image hardware independent.
        d. Unattend – Just the command to reference our unattend.xml file for
        predetermined options.
      7. OPTIONAL
        a. You may find it useful to include a script for other functions post setup. If so create the directory C:\Windows\Setup\Scripts. At this location make a file SetupComplete.cmd
        b. The passwords are encrypted, but you may want to delete the unattend.xml after the workstation is fully setup or reference Microsoft Office’s license key service to automatically register itself.
      posted in Tutorials
      Liam SullivanL
      Liam Sullivan
    • RE: How to Setup Ubuntu Server/FOG 1.2.0/Create Univeral Windows 7 Image using Sysprep - Step-by-Step

      [B]INSTALLING FOG SOFTWARE:[/B]

      The installation of FOG is fairly straightforward, once installed the bulk of configuration is handled from the Web GUI through your browser. There are a couple of further tweaks that can be done from the system side but they are optional depending on your environment.

      1. Enter the following at your Ubuntu command line.
        • cd /opt
        • sudo wget [url]https://sourceforge.net/projects/freeghost/files/latest/download?source=[/url]
        • sudo tar –xvzf fog_1.20.tar.gz
        • cd fog_1.2.0/
        • cd bin
        • sudo ./installfog.sh
      2. Follow the steps in the FOG installer wizard
        • Choose Option 2 (Ubuntu)
        • Choose N (normal)
        • Press enter to leave IP address default
        • Press enter to leave gateway default
        • Press enter to leave DNS default
        • Choose NO when asked to change default NIC
        • If you already have DHCP configured, press NO to disable FOG DHCP
        • Press Enter to acknowledge MySQL warning
        • Set a password for MySQL when requested if you want (I left mine blank)
        • Be awesome and send a notification to the FOG community!
      3. FOG is now installed, we just want to check some of the MySQL settings real quick. wizard (skip this step if you left the password blank)
        • sudo vi /var/www/fog/lib/fog/Config.class.php
        • Set MYSQL_PASSWORD to the password you configured in the FOG
        • Confirm MYSQL_USERNAME is set to root account
        • sudo vi /var/www/fog/lib/fog/Config.class.php
        • Set MYSQL_PASSWORD to the password configured in the FOG wizard
      4. Congrats! FOG is fully installed!!

      [B]PREPARING FOG FOR USE[/B]
      There are still a few steps remaining before we can start to focus on image development and deployment. Some of these will require modifications of FOG which can now be done through the web interface, others will require changes on your existing DHCP and DNS server.

      [B]14. OPTIONAL this step is not necessary but is HIGHLY recommended.[/B]
      • On your DNS server open DNS MANAGEMENT
      • Go to FORWARD LOOKUP ZONES
      • Right click Your Domain example.org
      • Select NEW HOST (A or AAAA)……
      • Enter a name (fogserver works well)
      • Enter the IP address you configured earlier
      • Press Add Host
      15. Next go to your DHCP Server
      • Open DHCP Management
      • Expand IPV4
      • Right Click Server Options and select Configure Options
      i. Scroll to option 66 and give the hostname you just set in DNS
      ii. Scroll to option 67 and give the value undionly.kpxe
      • Apply settings and close
      16. Back on your workstation open [url]http://fogserver/fog/management[/url]
      • (if you used another hostname enter that)
      17. Login to FOG, the default credentials are fog/password
      [B]18. FOG CONFIGURATION OPTIONAL[/B]
      • USER MANAGEMENT
      i. HIGHLY RECOMMENDED – Change the fog username/password from default.
      ii. Optionally create a new user account for your helpdesk person to register and image computers.
      This will leave the primary admin account for your usage.
      • SERVICE CONFIGURATION
      i. There are many options here that the FOG client application can be used for. Most of the
      functions are pretty straight forward but I’ll explain configurations on any that need it.
      ii. Auto Log Out

      1. The FOG client will auto-logout computers. This can be accomplished more granularly through Group Policy deploying scheduled tasks to certain computers (e.g. student computer labs). Not recommended though as forced logout can create data loss issues.
        iii. Client Updater

      2. If you update the FOG client on the server, it will automatically update the client services installed on any workstations. Make sure to enable this!
        iv. Directory Cleaner

      3. This can be useful for cleaning out temp directories and other file locations on logoff. If you’re using Deep Freeze or something similar already, you probably don’t need it. Windows 7 can schedule this with tasks or some Group Policy settings.
        v. Display Manager

      4. This could be useful to force default screen size on a computer lab. But again, Windows
        7 will automatically fit the optimal screen resolution and changes can be blocked through Group Policy.
        vi. Green FOG

      5. A useful feature for auto-shutdown for power savings. Again, more granular controls and easier configuration uses group policy and scheduled task deployments.
        vii. Hostname Changer

      6. One of my favorite features. After the imaging process FOG will automatically join the computer to the domain and set its domain name to the unique client name you configured on the imaging and inventory screen off the PXE boot.
        viii. Host Registration

      7. The FOG client can be deployed to existing computer systems but I haven’t found this to be needed in my environment. Basically it would feed back all the MSinfo data to FOG to create the client hardware asset and inventory list.
        ix. Printer Manager

      8. Automate deployment of printers to machines. Again I much prefer the interface and options Group Policy/Preferences affords for printer deployment.
        x. Snapin Client

      9. FOG can be used to auto-deploy certain software packages. (Flash, Java, PDF Readers etc).
        xi. Task Reboot

      10. This is useful for hands-off imaging as you can schedule a deployment and the running computer will restart automatically when it detects the waiting job.
        xii. User Cleanup

      11. Removes stale user accounts. Again, Windows 7 can handle this functionality through group policy settings.
        xiii. User Tracker

      12. Logs local user login/logoff. If your local administrative accounts are secure there’s
        really no need to log this.

      [B]• FOG OTHER INFORMATION OPTIONAL[/B]
      i. Other Information provides a range of settings to further enhance FOG functionality. ii. VERSION INFO

      1. Displays current version, if it doesn’t say up to date just follow the instructions to
        update FOG.

      2. LICENSE
        a. Standard GPL license

      3. KERNEL UPDATES
        This part can be quite useful. I’ve had issues with certain computer models not responding well to some of the PXE boot images, to remedy this you may be able to download a new kernel.

      4. PXE BOOT MENU
        It’s possible to add a wide variety of options to the FOG PXE boot, including emergency boot CDs, system hardware test tools etc., but that is more in-depth then this guide will get.

      5. CLIENT UPDATER
        a. This is where you can update the FOG Client software installer.

      6. MAC ADDRESS LISTING
        a. Here you can delete or update the MAC address database. Addresses are used for easier manufacturer identification.

      [B]7. FOG Settings IMPORTANT[/B]
      8. Most of these are auto-populated and the usage of the setting is viewed by hovering the
      ? icon. My main focus is proper configuration of the auto-domain join settings. a. FOG_AD_DEFAULT_DOMAINNAME
      i. Set to your domain name (example.org)
      b. FOG_AD_DEFAULT_OU
      i. Must be entered as proper LDAP syntax. (OU=Computers,DC=example,DC=org)
      This can be also left blank for default
      c. FOG_AD_DEFAULT_USER
      i. This should be created as a service account. Must be delegated rights to create new computer accounts in whatever computer OU you are using, although if the password is secure you could give it Domain Admin rights, but that’s not optimal. (FOG-JOIN) (Note: You no longer need to precede the username with the domain as in previous versions of Fog)
      d. FOG-AD_DEFAULT_PASSWORD
      i. The FOGCRYPT tool is used to encrypt the password to make it secure.
      Follow the steps below to use it.

      1. Click on the FOGClient/FOGPrep link in the footer of the FOG GUI in the web browser and download FOGCrypt to your computer. (I put it on the root of 😄 for ease)
      2. Extract the Archive
      3. Go to Start, Run and type cmd and hit the Enter key.
      4. To get to the 😄 type cd c:\
      5. cd FOGCrypt
      6. FOGCrypt.exe your password >encrypted-password.txt (This is the FOG Domain Join password you set in your directory service)
      7. Open the file you created encrypted-password.txt with any text editor like notepad and the encrypted password can be copied into FOG via the FOG web interface.
      8. The rest of the options on the page are for diagnostics and referring back to the FOG
        information pages and as such are not under the scope of this tutorial.

      Congratulations! FOG is FULLY configured!

      posted in Tutorials
      Liam SullivanL
      Liam Sullivan
    • How to Setup Ubuntu Server/FOG 1.2.0/Create Univeral Windows 7 Image using Sysprep - Step-by-Step

      [B]EDIT[/B] - [I]Because I was bone idle when I put this on here I omitted the links from the text, I did include them in the downloaded version though, however because a few people have been asking about the links. I have now fixed them in this tutorial! Sorry about that :)[/I]

      This guide has been pieced together from a multitude of sources across the internet then adjusted to be in-line hopefully with the current FOG version of 1.2.0. I can’t take credit for the information in here, people who have struggled before me have provided all this information to help. As I have worked on my initial implementation of the FOG environment I found the resources and write-ups from the various groups extremely valuable. While much of this information exists already, it was spread across a number of sources and required numerous cross references to make my installation function to the level it has. I have tested my universal image across numerous PC’s and laptops of differing makes and model and so far it has worked flawlessly every time.

      This is a write-up to provide guidance on the installation of an Ubuntu Server OS, the FOG (Free Open-Source Ghost) imaging software, configuring FOG, then creating and deploying hardware independent images.

      This tutorial is divided into the following sections
      [LIST]
      []· Installing Ubuntu Server
      [
      ]· Configuring and Updating Ubuntu Server
      []· Installing FOG Software
      [
      ]· Configuring your FOG Installation
      []· Workstation Universal Image Creation
      [
      ]· Uploading Your Reference Image to FOG
      [/LIST]
      I’d like to give a nod to the Ubuntu Forums, the FOG Project community, the DriverPacks.net Team and the Spiceworks Community.
      [LIST]
      []· FogProject
      [
      ]· Ubuntu Forums
      []· Spiceworks Community
      [
      ]· Driverpacks
      [/LIST]
      What I’ve hoped to accomplish is provide a one-stop resource for FOG installation guidance as well as a number of tweaks I’ve made to increase efficiency. I can’t guarantee that every option I’ve used will be the best option for your environment, so I highly encourage a test environment that allows you to make any necessary tweaks before a full roll out. If you notice any errors in the document or have suggestions for improvement, please feel free to correct me/comment.

      [B]INSTALLING UBUNTU SERVER:[/B]
      [LIST=1]
      []Go to [URL=‘http://www.ubuntu.com’]http://ubuntu.com[/URL] . Click Download -> Ubuntu Server and for best results pick the LTS distribution. If you’d prefer a GUI you can utilize the desktop system, but I’m breaking down line by line commands for the server CLI so it won’t be necessary. (I used 10.04 LTS but that’s due to my server hardware more than anything. That said FOG has installed and worked flawlessly on this release)
      [
      ]Preferably create a VM, otherwise this can be installed on physical hardware.
      [/LIST]
      [LIST]
      []Minimum of 512MB of RAM, usage is low on the server OS.
      [
      ]Minimum 1 NIC, preferably Gigabit connectivity.
      []If using VLANS, be sure to set the VM in a network that can both route and broadcast to necessary client machines.
      [/LIST]
      [LIST]
      [
      ][B]NOTE[/B] To utilise FOG across subnets/VLANS you must insure that IGMP Multicast is enabled across your switches!!
      [/LIST]
      3. Leave the Ubuntu install settings at defaults, when it asks you to add packages select none. We’re looking for a JEOS installation (Just Enough Operating System) the less extraneous software this box runs the better.
      4. When it prompts you to create the user account, set it to whatever you want. I used FogUser. Realise that Linux logons are case sensitive for username and MAKE SURE TO WRITE DOWN YOUR CONFIGURED USER INFORMATION!!!
      5. Now wait for the server to reboot.

      Congratulations! You’ve now installed Ubuntu! We’ll step through configuring the server OS for usage and making sure all necessary packages and updates are installed.

      [B]CONFIGURING AND UPDATING UBUNTU SERVER:[/B]

      1. Logon with the credentials you configured.
      2. First we want to set the IP of the server so that it doesn’t require DHCP and that DNS is properly configured.
        • Type sudo vi /etc/network/interfaces
        • Press Insert and navigate through the file with the arrow keys.
        i. Using your environments IP schema configure it per my example. Italics are lines that need to be added. [I]NOTE Included IPs are examples only and will vary for your deployment![/I]

      [FONT=Courier New]1.#The loopback network interface[/FONT]
      [FONT=Courier New]2.auto lo[/FONT]
      [FONT=Courier New]3.iface lo inet loopback[/FONT]
      [FONT=Courier New]4.[/FONT]
      [FONT=Courier New]5.#The primary network interface[/FONT]
      [FONT=Courier New]6.auto eth0[/FONT]
      [FONT=Courier New]7.iface eth0 inet [B][I]static### Set to static IP[/I][/B][/FONT]
      [B][I][FONT=Courier New]8.address 192.168.1.5[/FONT][/I][/B]
      [B][I][FONT=Courier New]9.netmask 255.255.255.0[/FONT][/I][/B]
      [B][I][FONT=Courier New]10.gateway 192.168.1.1[/FONT][/I][/B]
      [B][I][FONT=Courier New]11.network 192.168.1.0[/FONT][/I][/B]
      [B][I][FONT=Courier New]12.broadcast 192.168.1.255[/FONT][/I][/B]
      [B][I][FONT=Courier New]13.dns-domain example.org ## Your internalDomain Name[/FONT][/I][/B]
      [B][I][FONT=Courier New]14.dns-search example.org[/FONT][/I][/B]
      [B][I][FONT=Courier New]15.dns-nameservers 192.168.5.3 192.168.5.4## enter your DNS server[/FONT][/I][/B]
      [CENTER][B][I][U][FONT=Courier New]addressesseparatedbya space[/FONT][/U][/I][/B][/CENTER]

      • Also, if you are using a proxy that requires authentication you will need to allow open access for the FOG server. Depending on your configuration it may be difficult getting Ubuntu to authenticate properly.
      8. At the command line type the following commands.
      • sudo apt-get update
      • sudo apt-get upgrade
      • This will find any necessary updates and upgrade any packages that need it
      9. Restart the server if necessary. (sudo shutdown –r now)
      10. Now that networking and server updates are taken care of, we are ready to begin installing the FOG software.

      [url=“/_imported_xf_attachments/1/1211_Implementing_FOG_with_Universal_Windows_7.pdf?:”]Implementing_FOG_with_Universal_Windows_7.pdf[/url]

      posted in Tutorials
      Liam SullivanL
      Liam Sullivan
    • RE: Creating tasks is very slow.

      Hey

      Just to rule out the obvious, I assume that your referring the the amount of time its taking the requests to be handled between the browser and your fog server. Maybe a server restart as point 1 might be in order if you haven’t already done it. Requests to the webserver might just be lagging and maybe a restart would clear that. (I know it sounds a lot like the old adage, turn it off and on again lol, but sometimes the simplest solutions are often the correct ones.)

      Hope this helps

      Cheers

      posted in FOG Problems
      Liam SullivanL
      Liam Sullivan
    • Multicast on Fog 1.1.2 running incredibly slowly

      Hi Guys

      Having spent most of yesterday scouring the web, the wiki and the forum for some help with this and not finding anything specific, thought I’d post the question and see if anyone has the solution. I set two labs imaging yesterday through Fog on a multicast task (around 64 machines), the task runs perfectly, all the PC’s pick up the job and wait until they are all at the same point as they are supposed to. The task kicks off and then settles at around 8-10 MB/min which is phenomenally slow. I can run one machine on unicast and will get speeds of around 2GB/min so I’m baffled as to reason for this. I am aware that there are a number of factors involved in getting good speeds on multicast, i.e. quality gig switches, good cabling, decent server, etc etc, however both the server and the labs are running through HP gigabit switches, all the PC’s in this case are HP DC7900 desktops (not new I know but not ancient). The server also not new but powerful enough I would have thought to cope (HP Proliant ML370 G4) 6Gb RAM, 2x Dual Core Intel Xeon Processors, gigabit PCI-X network adaptor etc.

      I know that multicasting is traditionally a touch slower than unicast anyway although I’m sure it shouldn’t be this slow? We have moved to Fog from Symantec Ghost as I cannot abide Ghost and it is pricey as hell and nowhere near as good as Fog in just about every way imaginable, however, multicast imaging these same machines on Ghost gives me speeds of around 1.7 GB/min. Seems odd that Fog won’t do the same on the same hardware.

      Have I missed a setting somewhere? Any help greatly received 🙂

      Cheers

      posted in FOG Problems
      Liam SullivanL
      Liam Sullivan
    • RE: Intermittent Sanboot Hanging

      Not yet, thanks for the reply, I will have a go with that when I get back to the office tomorrow and see if it cures it.

      posted in FOG Problems
      Liam SullivanL
      Liam Sullivan
    • Intermittent Sanboot Hanging

      Hi

      Not sure if this going to be a Fog or Linux issue but I have just a couple of PC’s out of 700 or so that hang with the message, Sanboot device 8x80. If i switch the PXE setting in Fog to Exit, these two PC’s work but I manage to kill a couple of labs (about 70 PCs) which then hang at boot time. Its an odd one. Apart from this fog works perfectly in every other way. We have multiple PC makes on site including varying models within each in this case these are both Fujitsu Esprimo E3521 machines. That said, I have around 60 other identical Fujitsu’s who don’t suffer this problem. Any ideas on how I can work around it?

      I am running Fog 1.1.2 on Ubuntu 10.04 running on a HP Proliant ML370 G4 Server. (Old server repurposed for Fog hence the older version of Ubuntu, however, Fog runs great on it 🙂

      Regards

      Liam

      posted in FOG Problems
      Liam SullivanL
      Liam Sullivan
    • 1 / 1