Posts made by Troye Johnson

Troye Johnson

@george1421

here is a screen shot

0_1500307207023_85623c47-d101-40db-b601-d5f713387803-image.png

Troye Johnson

@george1421

But I don’t get this error in the vm when booting it goes straight to the fog menu.

Troye Johnson

@george1421

Ok so I started from scratch and got it to work in a vm using the steps from here “https://wiki.fogproject.org/wiki/index.php?title=Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE” Now while it worked in a vm when doing it from a workstation hp compaq elete 8300 ultra-slim desktop I get a “please enter tftp server:” error.

Troye Johnson

@george1421
Yes at lease until we get new computers in a year or two.

 dnsmasq -v
Dnsmasq version 2.48  Copyright (C) 2000-2009 Simon Kelley
Compile time options IPv6 GNU-getopt DBus no-I18N DHCP TFTP "--bind-interfaces with SO_BINDTODEVICE"

This software comes with ABSOLUTELY NO WARRANTY.
Dnsmasq is free software, and you are welcome to redistribute it
under the terms of the GNU General Public License, version 2 or 3.

Troye Johnson

@george1421
Here is the dnsmasq config file I was using.

# Sample configuration for dnsmasq to function as a proxyDHCP server,
# enabling LTSP clients to boot when an external, unmodifiable DHCP
# server is present.
# The main dnsmasq configuration is in /etc/dnsmasq.conf;
# the contents of this script are added to the main configuration.
# You may modify the file to suit your needs.

# Don't function as a DNS server:
port=0

# Log lots of extra information about DHCP transactions.
log-dhcp

# Dnsmasq can also function as a TFTP server. You may uninstall
# tftpd-hpa if you like, and uncomment the next line:
# enable-tftp

# Set the root directory for files available via FTP.
tftp-root=/tftpboot

# The boot filename.
dhcp-boot=pxelinux,,192.168.1.172

# rootpath option, for NFS
#dhcp-option=17,/images

# kill multicast
dhcp-option=vendor:PXEClient,6,2b

# Disable re-use of the DHCP servername and filename fields as extra
# option space. That's to avoid confusing some old or broken DHCP clients.
dhcp-no-override

# PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
pxe-prompt="Press F8 for boot menu", 3

# The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
# Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
# This option is first and will be the default if there is no input from the user.
pxe-service=X86PC, "Boot from fog", pxelinux

# A boot service type of 0 is special, and will abort the
# net boot procedure and continue booting from local media.
pxe-service=X86PC, "Boot from local hard disk", 0

# If an integer boot service type, rather than a basename is given, then the
# PXE client will search for a suitable boot service for that type on the
# network. This search may be done by multicast or broadcast, or direct to a
# server if its IP address is provided.
# pxe-service=x86PC, "Install windows from RIS server", 1

# This range(s) is for the public interface, where dnsmasq functions
# as a proxy DHCP server providing boot information but no IP leases.
# Any ip in the subnet will do, so you may just put your server NIC ip here.
# Since dnsmasq is not providing true DHCP services, you do not want it
# handing out IP addresses.  Just put your servers IP address for the interface
# that is connected to the network on which the FOG clients exist.
# If this setting is incorrect, the dnsmasq may not start, rendering
# your proxyDHCP ineffective.
dhcp-range=192.168.1.10,proxy,255.255.0.0

# This range(s) is for the private network on 2-NIC servers,
# where dnsmasq functions as a normal DHCP server, providing IP leases.
# dhcp-range=192.168.0.20,192.168.0.250,8h

# For static client IPs, and only for the private subnets,
# you may put entries like this:
# dhcp-host=00:20:e0:3b:13:af,10.160.31.111,client111,infinite

Troye Johnson

@george1421 said in hp8000-8300elite Issues.:

maintain the syslinux menu for some reason. You might be able to do this.
DEFAULT vesamenu.c32

hey, @george1421

I only did it this way because it was the only way I was able to get it to work. I have tried various different methods to get it to work without the syslinux menu but for some reason all of the other methods have failed me. I have dnsmasq installed on the fog server and we are also dealing with crossing subnets all of our servers are on the .1 subnet while all of the workstations are on the .11 subnet. I have no issues when imaging with my current setup but it does involve me replacing the ipxe.krn everytime I upgrade the fog server to the latest one from the ipxe.iso.

Troye Johnson

@Quazz

drwxr-xr-x   6 fog  root 4.0K Jul 11 15:26 .
dr-xr-xr-x. 26 root root 4.0K Jul 11 15:11 ..
drwxr-xr-x   2 fog  root 4.0K Oct 20  2016 10secdelay
-rw-r-xr-x   1 fog  root  868 Jun 20 16:07 boot.txt
-rw-r-xr-x   1 fog  root  428 Jun 20 16:07 default.ipxe
drwxr-xr-x   2 fog  root 4.0K Aug  1  2016 i386-7156-efi
drwxr-xr-x   2 fog  root 4.0K Aug  1  2016 i386-efi
-rw-r-xr-x   1 fog  root 195K Jun 20 16:07 intel7156.efi
-rw-r-xr-x   1 fog  root 222K Jun 20 16:07 intel.efi
-rw-r-xr-x   1 fog  root  94K Jun 20 16:07 intel.kkpxe
-rw-r-xr-x   1 fog  root  94K Jun 20 16:07 intel.kpxe
-rw-r-xr-x   1 fog  root  94K Jun 20 16:07 intel.pxe
lrwxrwxrwx   1 root root   18 Jul 11 12:03 ipxe.0 -> /tftpboot/ipxe.efi
-rw-r-xr-x   1 fog  root 921K Jun 20 16:07 ipxe7156.efi
-rw-r-xr-x   1 fog  root 971K Jun 20 16:07 ipxe.efi
-rw-r-xr-x   1 fog  root 848K Jun 20 16:07 ipxe.iso
-rw-r-xr-x   1 fog  root 341K Jun 20 16:07 ipxe.kkpxe
-rw-r-xr-x   1 fog  root 341K Jun 20 16:07 ipxe.kpxe
-rw-r--r--   1 root root 316K Jul 28  2016 ipxe.krn
-rw-r-xr-x   1 fog  root 340K Jun 20 16:07 ipxe.krn.latest
-rw-r-xr-x   1 fog  root 334K Nov  8  2016 ipxe.krnold
-rw-r-xr-x   1 fog  root 334K Aug  1  2016 ipxe.krn.old
-rw-r-xr-x   1 fog  root 337K Mar 15 17:04 ipxe.krn.older
-rw-r-xr-x   1 fog  root 334K Nov 15  2016 ipxe.krn.org
-rw-r-xr-x   1 fog  root 341K Jun 20 16:07 ipxe.pxe
-rw-r-xr-x   1 fog  root 121K Jun 20 16:07 ldlinux.c32
-rw-r-xr-x   1 fog  root 184K Jun 20 16:07 libcom32.c32
-rw-r-xr-x   1 fog  root  26K Jun 20 16:07 libutil.c32
-rw-r-xr-x   1 fog  root  26K Jun 20 16:07 memdisk
-rw-r-xr-x   1 fog  root  29K Jun 20 16:07 menu.c32
lrwxrwxrwx   1 fog  root   14 Aug  1  2016 pxelinux.0 -> pxelinux.0.old
-rw-r-xr-x   1 fog  root  43K Jun 20 16:07 pxelinux.0.old
drwxr-xr-x   2 fog  root 4.0K Aug  1  2016 pxelinux.cfg
-rw-r-xr-x   1 fog  root 195K Jun 20 16:07 realtek7156.efi
-rw-r-xr-x   1 fog  root 221K Jun 20 16:07 realtek.efi
-rw-r-xr-x   1 fog  root  95K Jun 20 16:07 realtek.kkpxe
-rw-r-xr-x   1 fog  root  95K Jun 20 16:07 realtek.kpxe
-rw-r-xr-x   1 fog  root  95K Jun 20 16:07 realtek.pxe
-rw-r-xr-x   1 fog  root 194K Jun 20 16:07 snp7156.efi
-rw-r-xr-x   1 fog  root 220K Jun 20 16:07 snp.efi
-rw-r-xr-x   1 fog  root 194K Jun 20 16:07 snponly7156.efi
-rw-r-xr-x   1 fog  root 221K Jun 20 16:07 snponly.efi
lrwxrwxrwx   1 root root   23 Jul 11 12:03 undionly.0 -> /tftpboot/undionly.kpxe
-rw-r-xr-x   1 fog  root  94K Jun 20 16:07 undionly.kkpxe
-rw-r-xr-x   1 fog  root  94K Jun 20 16:07 undionly.kpxe
-rw-r-xr-x   1 fog  root  94K Jun 20 16:07 undionly.pxe
-rw-r-xr-x   1 fog  root  30K Jun 20 16:07 vesamenu.c32

This was the result

Troye Johnson

Ok sorry guys just got back from an unexpected vacation and now I am back to trying to get this working as it should.

Troye Johnson

@george1421 & @Tom-Elliott

I have tried to change both of those boot files to undionly with symlink and it will not get past the tftpboot screen. It keeps saying the file cannot be found. My dnsmasq Version is “Dnsmasq version 2.48” and when I do a yum upgrade and update it says everything is up to date and I cannot seem to find instructions on installing 2.76 on centos 6.5. I could be over looking it. The only method I have been able to get working to get computers imaged is using the pxelinux.0 file with pxelinux.cfg

DEFAULT vesamenu.c32
LABEL fog
	MENU DEFAULT
	kernel ipxe.krn dhcp && chain http://${next-server}/fog/service/ipxe/boot.php?mac=${net0/mac}
PROMPT 0
TIMEOUT 01```

Troye Johnson

I just updated My tag line been a while since I posted.

@quinniedid I will give that a try, I think I tried it before but it wont hurt to try it again.

@george1421 I am using pxelinux.0 since it has been the only method that worked with these machines currently. I am using dnsmasq here is a copy of the config that has worked so far.

# Sample configuration for dnsmasq to function as a proxyDHCP server,
# enabling LTSP clients to boot when an external, unmodifiable DHCP
# server is present.
# The main dnsmasq configuration is in /etc/dnsmasq.conf;
# the contents of this script are added to the main configuration.
# You may modify the file to suit your needs.

# Don't function as a DNS server:
port=0

# Log lots of extra information about DHCP transactions.
log-dhcp

# Dnsmasq can also function as a TFTP server. You may uninstall
# tftpd-hpa if you like, and uncomment the next line:
# enable-tftp

# Set the root directory for files available via FTP.
tftp-root=/tftpboot

# The boot filename.
dhcp-boot=pxelinux,,192.168.1.172

# rootpath option, for NFS
#dhcp-option=17,/images

# kill multicast
dhcp-option=vendor:PXEClient,6,2b

# Disable re-use of the DHCP servername and filename fields as extra
# option space. That's to avoid confusing some old or broken DHCP clients.
dhcp-no-override

# PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
pxe-prompt="Press F8 for boot menu", 3

# The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
# Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
# This option is first and will be the default if there is no input from the user.
pxe-service=X86PC, "Boot from fog", pxelinux

# A boot service type of 0 is special, and will abort the
# net boot procedure and continue booting from local media.
pxe-service=X86PC, "Boot from local hard disk", 0

# If an integer boot service type, rather than a basename is given, then the
# PXE client will search for a suitable boot service for that type on the
# network. This search may be done by multicast or broadcast, or direct to a
# server if its IP address is provided.
# pxe-service=x86PC, "Install windows from RIS server", 1

# This range(s) is for the public interface, where dnsmasq functions
# as a proxy DHCP server providing boot information but no IP leases.
# Any ip in the subnet will do, so you may just put your server NIC ip here.
# Since dnsmasq is not providing true DHCP services, you do not want it
# handing out IP addresses.  Just put your servers IP address for the interface
# that is connected to the network on which the FOG clients exist.
# If this setting is incorrect, the dnsmasq may not start, rendering
# your proxyDHCP ineffective.
dhcp-range=192.168.1.10,proxy,255.255.0.0

Troye Johnson

Re: Fog .032 and HP8000 elite

Just want to think anyone who is able to help in advance.

I am still having the issue where I need to replace the ipxe.krn file in the /tftpboot folder. if I do not replace the file I get the following error.

When I replace the file I loose the ability to customize the menu.

Troye Johnson

@bmorris Happy to help.

Troye Johnson

@bmorris No problem just let me know if you have anymore questions I am happy to help.

Troye Johnson

For the licensing aspect you can create different power-shell scripts for each of your techs so that you can keep an audit of who ran what when applications are being deployed. This way not only will you stay in compliance with the eula but you also have an audit if something happens.

Troye Johnson

@bmorris Yes no need to change the fog user on the service.

Troye Johnson

@bmorris Please remember to add this registry setting based on PDQ recommendations

Additionally, you’ll need to add an entry into the registry on the PDQ Deploy machine in order to tell the background service to use TCP/IP:

Location: HKLM\Software\Admin Arsenal\PDQ Deploy\
Type: DWORD Name: ServicePort Value: <port number>

The value needs to be a port number that is allowed within your network.

or find it here https://www.adminarsenal.com/webcast-bonus-content/

Troye Johnson

@bmorris Yes I we created a domain user added that users under the “pdq deploy> Preferences>Credentials” to allow it access to deploy apps and then added those credentials into the PDQdeploy script by powershell. Here is my script I encrypted the password for best practices.


<#
.SYNOPSIS
Start a PDQ Deploy Deployment on a target machine

.DESCRIPTION
Trigger a PDQ Deploy deployment to start locally or on a remote machine with PDQ Deploy installed

.EXAMPLE
Start-Deployment -PackageName "Example Package" -Targets "Wolverine"

.EXAMPLE
Start-Deployment -ScheduleName "Example Schedule" -Targets "Wolverine"

.EXAMPLE
Start-Deployment -ScheduleID 123 -Targets "Wolverine"

.PARAMETER DeployComputerName
The machine with PDQ Deploy installed. This defaults to the local machine

.PARAMETER PackageName
The names of packages on DeployMachine that you wish to use

.PARAMETER ScheduleName
The names of schedules on DeployMachine that you wish to use

.PARAMETER ScheduleID
The schedule IDs on DeployMachine that you wish to use

.PARAMETER Targets
A list of targets that you wish to deploy a package or schedule to. Leave blank if you wish to target the local machine.
#>
[cmdletbinding(
    SupportsShouldProcess = $True
)]
Param(

    [String]$DeployComputerName = $env:COMPUTERNAME,

    [Parameter(ParameterSetName = "Package")]
    [string]$PackageName,

    [Parameter(ParameterSetName = "Package")]
    [String[]]$Targets = $env:COMPUTERNAME,

    [Parameter(ParameterSetName = "Schedule")]
    [string]$ScheduleName,

    [Parameter(ParameterSetName = "ScheduleID")]
    [Int]$ScheduleID

)

Process {
    
    # Add parameters to a hashtable to easily push into invoke-command as an argument
    $MyParameters = @{
        DeployComputerName = $DeployComputerName
        PackageName        = $PackageName
        Targets            = $Targets
        ScheduleName       = $ScheduleName
        ScheduleID         = $ScheduleID
        DeploymentType     = $PSCmdlet.ParameterSetName
    }
	#OS Check
	
	$PSScriptRoot = Split-Path -Parent -Path $MyInvocation.MyCommand.Definition
	
	#Credentials

$User = "domain\user"
$PasswordFile = "$PSScriptRoot\Password.txt"
$KeyFile = "$PSScriptRoot\AES.key"
$key = Get-Content $KeyFile
$MyCredential = New-Object -TypeName System.Management.Automation.PSCredential `
 -ArgumentList $User, (Get-Content $PasswordFile | ConvertTo-SecureString -Key $key)

    # This outputs a powershell.log to the root directory of the target machine
    $MyParameters | Out-String | Out-File C:\powershell.log

    # Testing to see if PSRemoting is enabled
    If (Test-WSMan -ComputerName $DeployComputerName) {
            
        Write-Verbose "Test-WSMan test passed on $DeployComputerName"

        # Added -Whatif capability to script
        If ( $PSCmdlet.ShouldProcess($DeployComputerName, "Starting deployment with the following parameters:`n $($MyParameters | Out-String)") ) {
            
            # Connect to Deploy machine and attempts to start a deployment
            Invoke-Command -ComputerName $DeployComputerName -credential $MyCredential -ArgumentList ($MyParameters) -ScriptBlock {
                Param ($MyParameters)

                # This outputs a powershell.log to the root directory of the deploy machine
                $MyParameters | Out-String | Out-File C:\powershell.log

                # Build command string based on deployment type
                Switch ($MyParameters.DeploymentType) {

                    "Package" {

                        $PDQDeployCommand = "pdqdeploy deploy -package ""$($MyParameters.PackageName)"" -targets $($MyParameters.Targets)"
                    
                    }
        
                    "Schedule" {
                    
                        $DB = "$env:ProgramData\Admin Arsenal\PDQ Deploy\Database.db"
                        $SQL = "SELECT ScheduleID FROM Schedules WHERE Name = '$($MyParameters.ScheduleName)' COLLATE NOCASE;"
                        $ScheduleID = $SQL | sqlite3.exe $db
                        $PDQDeployCommand = "pdqdeploy StartSchedule -ScheduleId $ScheduleID"
                    
                    }

                    "ScheduleID" {
                    
                        $PDQDeployCommand = "pdqdeploy StartSchedule -ScheduleId $($MyParameters.ScheduleID)"
                    
                    }
                }                    

                # Append the actual command that will be run to powershell.log
                "Invoke-command: $PDQDeployCommand" | Out-File C:\powershell.log -Append

                # Create and invoke scriptblock
                $PDQDeployCommand = [ScriptBlock]::Create($PDQDeployCommand)
                $PDQDeployCommand.Invoke()

            } 
        }
    }
}

Im not sure if it works with server mode of PDQ deploy that was just released yet though I have not tested it. If you get a chance to please let me know.

Troye Johnson

Good news this morning I rebooted the server gave it another try and it all worked.

Troye Johnson

@Bob-Henderson

Its ok Bob, but yes the pdq script it self does dump a script when it runs. The script it self can be run outside of the fog snapin feature flawlessly. by me logging into a machine locally not on the domain and running the script. the problem is the fog is not running the script and I cannot find logs to tell me why its not running correctly.

If it helps here is the script.

<#
.SYNOPSIS
Start a PDQ Deploy Deployment on a target machine

.DESCRIPTION
Trigger a PDQ Deploy deployment to start locally or on a remote machine with PDQ Deploy installed

.EXAMPLE
Start-Deployment -PackageName "Example Package" -Targets "Wolverine"

.EXAMPLE
Start-Deployment -ScheduleName "Example Schedule" -Targets "Wolverine"

.EXAMPLE
Start-Deployment -ScheduleID 123 -Targets "Wolverine"

.PARAMETER DeployComputerName
The machine with PDQ Deploy installed. This defaults to the local machine

.PARAMETER PackageName
The names of packages on DeployMachine that you wish to use

.PARAMETER ScheduleName
The names of schedules on DeployMachine that you wish to use

.PARAMETER ScheduleID
The schedule IDs on DeployMachine that you wish to use

.PARAMETER Targets
A list of targets that you wish to deploy a package or schedule to. Leave blank if you wish to target the local machine.
#>
[cmdletbinding(
    SupportsShouldProcess = $True
)]
Param(

    [String]$DeployComputerName = $env:COMPUTERNAME,

    [Parameter(ParameterSetName = "Package")]
    [string]$PackageName,

    [Parameter(ParameterSetName = "Package")]
    [String[]]$Targets = $env:COMPUTERNAME,

    [Parameter(ParameterSetName = "Schedule")]
    [string]$ScheduleName,

    [Parameter(ParameterSetName = "ScheduleID")]
    [Int]$ScheduleID

)

Process {
    
    # Add parameters to a hashtable to easily push into invoke-command as an argument
    $MyParameters = @{
        DeployComputerName = $DeployComputerName
        PackageName        = $PackageName
        Targets            = $Targets
        ScheduleName       = $ScheduleName
        ScheduleID         = $ScheduleID
        DeploymentType     = $PSCmdlet.ParameterSetName
    }
	#OS Check
	
	$PSScriptRoot = Split-Path -Parent -Path $MyInvocation.MyCommand.Definition
	
	#Credentials

$User = "pdqtest"
$PasswordFile = "$PSScriptRoot\Password.txt"
$KeyFile = "$PSScriptRoot\AES.key"
$key = Get-Content $KeyFile
$MyCredential = New-Object -TypeName System.Management.Automation.PSCredential `
 -ArgumentList $User, (Get-Content $PasswordFile | ConvertTo-SecureString -Key $key)

    # This outputs a powershell.log to the root directory of the target machine
    $MyParameters | Out-String | Out-File C:\powershell.log

    # Testing to see if PSRemoting is enabled
    If (Test-WSMan -ComputerName $DeployComputerName) {
            
        Write-Verbose "Test-WSMan test passed on $DeployComputerName"

        # Added -Whatif capability to script
        If ( $PSCmdlet.ShouldProcess($DeployComputerName, "Starting deployment with the following parameters:`n $($MyParameters | Out-String)") ) {
            
            # Connect to Deploy machine and attempts to start a deployment
            Invoke-Command -ComputerName $DeployComputerName -credential $MyCredential -ArgumentList ($MyParameters) -ScriptBlock {
                Param ($MyParameters)

                # This outputs a powershell.log to the root directory of the deploy machine
                $MyParameters | Out-String | Out-File C:\powershell.log

                # Build command string based on deployment type
                Switch ($MyParameters.DeploymentType) {

                    "Package" {

                        $PDQDeployCommand = "pdqdeploy deploy -package ""$($MyParameters.PackageName)"" -targets $($MyParameters.Targets)"
                    
                    }
        
                    "Schedule" {
                    
                        $DB = "$env:ProgramData\Admin Arsenal\PDQ Deploy\Database.db"
                        $SQL = "SELECT ScheduleID FROM Schedules WHERE Name = '$($MyParameters.ScheduleName)' COLLATE NOCASE;"
                        $ScheduleID = $SQL | sqlite3.exe $db
                        $PDQDeployCommand = "pdqdeploy StartSchedule -ScheduleId $ScheduleID"
                    
                    }

                    "ScheduleID" {
                    
                        $PDQDeployCommand = "pdqdeploy StartSchedule -ScheduleId $($MyParameters.ScheduleID)"
                    
                    }
                }                    

                # Append the actual command that will be run to powershell.log
                "Invoke-command: $PDQDeployCommand" | Out-File C:\powershell.log -Append

                # Create and invoke scriptblock
                $PDQDeployCommand = [ScriptBlock]::Create($PDQDeployCommand)
                $PDQDeployCommand.Invoke()

            } 
        }
    }
}
}

While it may say the script successfully it didn’t actually run.

Troye Johnson

@Joe-Schmitt

Something strange is definitely going on I tried to send the same snapin to another computer and it changed my snapin here are the logs

The highlighted lines

was not how it was before. the thing is this time I actually was able to see the Zip file download and extract and attempt to run on the machine.