• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. JJ Fullmer
    3. Best
    • Profile
    • Following 5
    • Followers 4
    • Topics 55
    • Posts 945
    • Best 253
    • Controversial 0
    • Groups 3

    Best posts made by JJ Fullmer

    • Creating a csv host import from a network scan

      Run the following code in powershell (after editing it with your network’s subnets) to create a csv that will import all hosts on your network.

      # examples, just gotta put subnets minus the final .x in a string array
      # Could also be params if this was a function
      $subnets = @("192.168.1", "192.168.2", "10.2.114", "192.168.0"); 
      $subnets | ForEach-Object { # loop through each subnet
      	for ($i=0; $i -lt 255; $i++) { # loop through 0 to 255 of the subnet
      		$hn = nslookup "$_.$i"; # run nslookup on the current ip in the loop
      		if ($hn[3] -ne $null -AND $hn[3] -ne "") { # does the ip have a dns entry
      			$hostN = $hn[3].Replace("Name:","").Trim(); # parse the nslookup output into a fqdn host name
      			$mac = getMac /S $hostN; # does the hostname have a mac addr. Can also add /U and /P for user and password if not running from a administrative account
      			if ($mac -ne $null) { # was there a mac for the host?
      				$macAddr = $mac[3].Split(' ')[0]; # use the first found mac address and parse it
      				"$hostN,$macAddr" | Out-File C:\hosts.csv -Append -Encoding UTF8; # add the hostname,macaddress to the csv
      			}
      		}
      	}
      }
      
      posted in Tutorials
      JJ FullmerJ
      JJ Fullmer
    • RE: Can't Edit Exisiting Snapins or Create New ones

      @Arrowhead-IT Scratch that, it totally worked after a restart. So if you go breaking your permissions just run the script posted and restart and violia!

      posted in Bug Reports
      JJ FullmerJ
      JJ Fullmer
    • RE: New Inits

      Everything is working for me now! hooray for the new inits!

      posted in General
      JJ FullmerJ
      JJ Fullmer
    • RE: Cortana/Windows Search breaks in default profile

      @Lee-Rowlett I think you are somewhat correct there. In all my testing I found that it relates to when a user first logs in it installs all the metro apps for that user including cortana. And when you do a profile copy in the system advanced settings control panel it ends up copying some of those installed apps to the default profile which causes the installation of metro apps on a new profile to fail, but there’s no error because the installs think they succeed since the files are already there.
      At least I think that has some to do with it. My new script system seems to work flawlessly and it is much easier than my old way of having to change the registry everytime and such.

      I would still test your theory for you, just for funzies, but I don’t actually use an unattend.xml. I don’t like sysprep. It breaks my default profile sometimes, and I’ve seen it break other things and it forces you to go back to oobe which messes with my computer naming system. I’ve kinda found it to not be necessary. Yes it resets some security id’s for activation this and that but if you are using windows enterprise volume licensing, that doesn’t cause any problems. In windows 7 I figured out the registry key to change and then just re-inputting the windows key and reactivating gave it a new sid. Windows 8 and 10 just work without issue without doing that. As for drivers, I make my images on a vm so they’re already hardware independent and I use the terminal tool devcon (included in the windows wdk 8.1, I just copy the devcon.exe over to my image vm after installing the wdk on my workstation) to uninstall all the devices in the device manager before rebooting with devcon -r remove *
      It goes through the uninstalling of devices much much faster than sysprep does too.

      So thank you sir for your help, but I think I got it figured out.

      posted in Windows Problems
      JJ FullmerJ
      JJ Fullmer
    • Powershell API Module

      I created a powershell module for using the Fog API

      https://www.powershellgallery.com/packages/FogApi

      Install instructions are found at that link.

      You can also use powershellget https://www.powershellgallery.com/packages/PowerShellGet the command Install-Module -Name FogApi;*

      Importing that module will help you to set up a quick and easy and crossplatform way to manage fog from a powershell prompt.

      It is structured based on the api documentation found here https://news.fogproject.org/simplified-api-documentation/
      It even autocompletes the parameter options based on that documentation.

      So if you read that documentation and see that you can get an ‘object’ you can then take that to the command by saying Get-FogObject -type object -CoreObject objecttype that object type validates/autocompletes to the list of available core objects found in the documentation.

      If you install the module and run help Invoke-FogApi it will display a bit more verbose help and documentation on how it all works.

      There are a few main functions to use that all make calling the Invoke-FogApi function a bit easier with autocompletion fun times

      • For GET api calls : Get-FogObject
      • For POST api calls : New-FogObject
      • For PUT api calls : Update-FogObject
      • For DELETE api calls : Remove-FogObject

      Each of these return powershell objects. If you’re unfamiliar with powershell and powershell objects, then this is a good way to learn.
      They make it so you can take information and easily find and manipulate their properties.
      i.e. if you did a $hosts = Get-FogObject - type Object -CoreObject host $hosts would contain 2 properties, a count of returned objects and an array of all your fog hosts, each with all the information fog has on them. So lets say you want to see all your hosts that have a intel cpu, you can search all the hosts for where the inventory’s cpu manufacturer has ‘intel’ in its value. $intelPCs = $hosts.hosts | ? { $_.inventory.cpuman -match 'intel' } Then maybe you just want the hostids, names, and mac addresses. $intelPCList = $intelPCs | Select-Object id,name,primac; $intelPCList;

      PS Objects can also easily be turned into json by piping them into a ConvertTo-Json command. Meaning that you can just change the values of an object’s properties, such as a host’s name, image, etc. And then convert that to json to use as the jsondata in any other command.

      I also included a Install-FogService function in the module for good measure that downloads the latest version of the client msi installer from your server and then silently installs it. In theory, you could use Invoke-Command to run that command on remote computers (though you would also have to import the module on each computer).

      There is a settings.json file that the module pulls from to get your api keys and servername. It needs to be set manually, but automatically opens in an appropriate editor for your OS if it finds that the settings are still set to default. The default settings are explanations of where to find the values on your server.

      Help Info from function code Will be updated overtime, putting here as it is the help info uri listed in module manifest
      Invoke-FogApi

      <#
              .SYNOPSIS
                 a cmdlet function for making fogAPI calls via powershell
              
              .DESCRIPTION
                  Takes a few parameters with some pulled from settings.json and others are put in from the wrapper cmdlets
                  Makes a call to the api of a fog server and returns the results of the call
                  The returned value is an object that can then be easily filtered, processed,
                   and otherwise manipulated in poweshell.
                  The defaults for each setting explain how to find or a description of the property needed.
                  fogApiToken = "fog API token found at https://fog-server/fog/management/index.php?node=about&sub=settings under API System";
                  fogUserToken = "your fog user api token found in the user settings https://fog-server/fog/management/index.php?node=user&sub=list select your api enabled used and view the api tab";
                  fogServer = "your fog server hostname or ip address to be used for created the url used in api calls default is fog-server or fogServer";
                          
              .PARAMETER serverSettings
                  this variable pulls the values from settings.json and assigns the values to 
                  the associated params. The defaults explain how to get the needed settings
                  fogApiToken = "fog API token found at https://fog-server/fog/management/index.php?node=about&sub=settings under API System";
                  fogUserToken = "your fog user api token found in the user settings https://fog-server/fog/management/index.php?node=user&sub=list select your api enabled used and view the api tab";
                  fogServer = "your fog server hostname or ip address to be used for created the url used in api calls default is fog-server or fogServer";
      
              .PARAMETER fogApiToken
                  a string of your fogApiToken gotten from the fog web ui. 
                  this value is pulled from the settings.json file
              
              .PARAMETER fogUserToken
                 a string of your fog user token gotten from the fog web ui in the user section.
                 this value is pulled from the settings.json file
              
              .PARAMETER fogServer
                  The hostname or ip address of your fogserver, 
                  defaults to the default name fog-server
                  this value is pulled from the settings.json file
              
              .PARAMETER uriPath
                  Put in the path of the apicall that would follow http://fog-server/fog/
                  i.e. 'host/1234' would access the host with an id of 1234
                  This is filled by the wrapper commands using parameter validation to 
                  help ensure using the proper object names for the url 
                  
              .PARAMETER Method
                Defaults to 'Get' can also be Post, put, or delete, this param is handled better
                by the wrapper functions
                get is Get-fogObject
                post is New-fogObject
                delete is Remove-fogObject
                put is Update-fogObject
              
              .PARAMETER jsonData
                  The jsondata string for including data in the body of a request
              
              .EXAMPLE
                  #if you had the api tokens set as default values and wanted to get all hosts and info you could run this, assuming your fogserver is accessible on http://fog-server
                  Invoke-FogApi;
      
              .Example
                  #if your fogserver was named rawr and you wanted to put rename host 123 to meow
                  Invoke-FogApi -fogServer "rawr" -uriPath "host/123" -Method "Put" -jsonData "{ `"name`": meow }";
      
              .Link
                  https://news.fogproject.org/simplified-api-documentation/
              
              .NOTES
                  The online version of this help takes you to the fog project api help page
                  
          #>
      
      posted in Tutorials api api help powershell task management fogapi-psmodule
      JJ FullmerJ
      JJ Fullmer
    • RE: executing batch file from snapin

      I would suggest using the full path of the file in your batch script instead of changing the directory.
      And when I say full path, I mean the true full path, not the mounted S:\ drive.
      Even if S:\ is being mounted by active directory or is a mapped drive as part of your image, I would still suggest using the full network/unc path.
      I would also suggest mounting it with net use and a username and password. This will ensure the system account that the Fog Service uses has access to the files you want
      I would also add some logging and other error preventions.

      i.e. if S:\ was mapped to \FileServer\Share …

      @ECHO off
      
      echo. Create variables to make scripting easier
      set sharePath=\\FileServer\Share\Pat
      
      echo. Mount S drive path, replace username and password with share credentials. 
      echo. If share is public omit the /USER parameter and everything after it
      
      
      net use %sharePath% /USER:username password
      
      echo. make sure destination exists, create it if it doesn't
      if not exist C:\temp mkdir C:\temp
      
      echo. copy each file, add /Y to overwrite without any prompt
      echo. copying tdpunt...
      copy /Y %sharePath%\tdpunt.bat C:\temp\ > C:\temp\tdpunt-bat-Copy.log
      echo. copying tundpt.exe...
      copy /Y %sharePath%\tundpt.exe C:\temp\ > C:\temp\tundpt-exe-Copy.log
      
      echo. Done!
      
      exit
      
      

      Use that and then see if the .log files show up after deploying the snapin.

      Also, in the web gui snapin config, you should take out the /qn that does nothing.
      The snapin arguments section is for custom arguments that you have in your script. Your script doesn’t do anything with the /qn and it could cause issues. The /c parameter is passed to the cmd.exe command which tells cmd.exe to open a prompt, run the command, and then close.
      If you had a line in your script like this

      if "%1" == "/qn" (
          echo. hey look a parameter, lets do something since it's there!
      )
      

      then the /qn would have a point.

      Hope that helps a bit.

      Thanks,
      -JJ

      posted in General
      JJ FullmerJ
      JJ Fullmer
    • RE: Powershell API Module

      New Module Version Published

      Just wanted to let people know that there’s a new version of the API yay!
      It’s been published to the psgallery here https://www.powershellgallery.com/packages/FogApi/1903.0.0.22 and it is awaiting a pull request to show up in the fog community scripts git.
      It has new functions to help do some common tasks, particularly with snapins. Here’s a list of the current functions.

      Add-FogSnapins
      Set-FogObject
      Get-FogAssociatedSnapins
      Get-FogGroup
      Get-FogHost
      Get-FogHosts
      Get-FogInventory
      Get-FogLog
      Get-FogObject
      Get-FogServerSettings
      Get-FogSnapins
      Install-FogService
      Invoke-FogApi
      New-FogObject
      Remove-FogObject
      Remove-UsbMac
      Set-FogInventory
      Set-FogServerSettings
      Set-FogSnapins
      Start-FogSnapins
      Update-FogObject
      
      posted in Tutorials
      JJ FullmerJ
      JJ Fullmer
    • Automating Git Updates for FOG

      In the past I made a script for automating svn updates. Since sourceforge has been making a habit of crashing lately, I decided to start using the git repo instead and adjusted my script to work with git.
      I figured others might benefit from it so why not share…

      #!/bin/bash
      clear
      # -------------------------------------------
      # Fog Git Updater
      # -------------------------------------------
      # -------------------------------------------
      # Script Purpose
      # -------------------------------------------
      # This script is designed to run an automated update of the latest FOG Git dev build and it's cron friendly
      # -------------------------------------------
      # -------------------------------------------
      # Some prereqs for this script
      # -------------------------------------------
      # 1. Already have an existing working install/configuration of FOG 1.0 or later
      #
      # 2. Have git installed and setup. You can do that by doing....
      # 	sudo apt-get install git
      #  	mkdir /home/fog/fogInstalls/git
      #	git clone https://github.com/FOGProject/fogproject.git /home/fog/fogInstalls/git
      #
      # 3. A script to echo the encrypted version of your sudo password, create one with this function
      #	just put in your password into the following in place of your_super_secret_password (leave the quotes)
      #	and then uncomment and copy paste the function into a terminal and then run it with just the name of the function pw
      	# pw(){
      	# 	touch /home/fog/fogInstalls/.~
      	# 	ossl=`echo "your_super_secret_password" | openssl enc -des -a -e -pass pass:PASSWORD`
      	# 	echo 'echo "$(echo '$ossl' | openssl enc -des -a -d -pass pass:PASSWORD)"' >> /home/fog/fogInstalls/.~
      	# 	sudo chown fog.root /home/fog/fogInstalls/.~
      	# 	sudo chmod 700 /home/fog/fogInstalls/.~ 
      	# }
      # -------------------------------------------
      # -------------------------------------------
      # Variables
      # -------------------------------------------
      # -------------------------------------------
      echo "Creating Script variables..."
      fogInstalls='/home/fog/fogInstalls'
      gitPath="$fogInstalls/git"
      backup="$fogInstalls/backups"
      pw=`sh $fogInstalls/.~` 
      # -------------------------------------------
      # -------------------------------------------
      # Functions
      # -------------------------------------------
      # -------------------------------------------
      perms(){
      	sudo chmod -R 775 $1
      	sudo chown -R fog.fog $1
      }
      
      srvUpdate(){
      	# Enter sudo mode aand do some quick server maintenance update fun times
      	# First, enter sudo mode by echoing the output of decrypting your encrypted password and pipe that into an apt-get update
      	#	Don't worry, it doesn't output the password into the terminal
      	#	Now that the password is in once the terminal will keep it stored for the next bunch of sudo commands
      	echo "Running Sever updates!..."
      	echo $pw | sudo -S apt-get update -y
      	sudo apt-get upgrade -y # install any upgrades you just downloaded
      }
      
      backupConfig(){
      	# Backup custom config and other files
      	# Copy the latest versions of any files you've changed that will be overwritten by the update and backup the database just in case.
      	# For example you may want to back up...
      	# Config.php
      	# 	To be on the safe side your config file in the /opt folder that has may have a corrected webroot for ubuntu 14.04 and may have stored encrypted credentials (i.e mysql)
      	# 		I think that the installer uses this file and keeps it anyway, but I like to be careful
      	# Exports file
      	#	Because this runs the installer with a yes pipe, it ends up telling it that the image path is "y",
      	# 		simply backing up and restoring your current one avoids the issue of fog not finding your precious images. 
      	# Custom pxe boot background
      	# 	If you have a custom background for the pxe menu, the bg.png file
      	# Mysql database dump
      	#	It would be rather troublesome if something went horribly wrong in the update and your database goes kaboom, it's unlikely but backups are a good thing 
      	# Just a note, It's a good policy to also have backups of these outside of your server, which you could add to this script with an scp command or something like that
      	# -------------------------------------------
      	echo "make sure backup dir exists..."
      	if [ ! -d $backup ]; then
      		mkdir $backup
      	fi
      	echo "Dumping the database..."
      	mysqldump -u root --all-databases --events > $backup/DatabaseBeforeLastUpdate.sql #backup database
      	echo "Backing up config and custom files..."
      	echo "config.php..."
      	sudo cp /opt/fog/service/etc/config.php $backup/config.php
      	echo "fog settings..."
      	sudo cp /opt/fog/.fogsettings $backup/.fogsettings
      	echo "nfs exports..."
      	sudo cp /etc/exports $backup/exports
      	echo "custom pxe background..."
      	sudo cp /var/www/html/fog/service/ipxe/bg.png $backup/bg.png 
      }
      
      gitP(){
              perms $gitPath
      	echo "git pull...."
      	cd $gitPath
      	git pull
      }
      
      updateFOG(){
      	echo "running FOG installer..."
      	cd $gitPath/bin
      	sudo bash installfog.sh -Y
      }
      
      restoreConfig(){
      	# Restore backed up files
      	# Restore the backed up files to their proper places and make sure they're formatted correct too.
      	echo "restoring custom pxe background..."
      	sudo cp $backup/bg.png /var/www/html/fog/service/ipxe # Restore Custom Background 
      	# I found that I needed to do this in some configurations, but it may no longer be neccesarry...
      	echo "Creating undionly for iPxe boot in ipxe folder, just in case..." 
      	sudo cp /tftpboot/undionly.kpxe /tftpboot/undionly.0 # backup original then rename undionly 
      	sudo cp /tftpboot/undionly.0 /var/www/html/fog/service/ipxe/undionly.0
      	sudo cp /var/www/html/fog/service/ipxe/undionly.0 /var/www/html/fog/service/ipxe/undionly.kpxe
      }
      
      fixPerms(){
      	echo "Changing Permissions of webroot..."
      	perms '/var/www/html/fog'
      	echo "Changing permissions of images...."
      	perms '/images'
      	echo "Changing permissions of tftpboot...."
      	perms '/tftpboot'
      }
      
      # -------------------------------------------
      # -------------------------------------------
      # Run the script
      # -------------------------------------------
      # -------------------------------------------
      srvUpdate
      backupConfig
      gitP
      updateFOG
      restoreConfig
      fixPerms
      echo "Done!"
      
      posted in General
      JJ FullmerJ
      JJ Fullmer
    • RE: Active directory Join issue

      @anthonyglamis Fogcrypt is essentially obsolete, yes. You can still put the fogcrypt output into the legacy input but I find the new auto-encrypt to work better. But yes I’m pretty sure that the fogcrypt tool is still there

      I hadn’t noticed that the hashes were different before, so I checked mine and they are different. I haven’t had any problems though, so I would say it shouldn’t be an issue.

      posted in Windows Problems
      JJ FullmerJ
      JJ Fullmer
    • RE: HP Z640 - NVME PCI-E Drive

      I just finished working with @Tom-Elliott we got it working. It was a simple fix.
      It’s in the latest fog update now. So nvme drives work with fog 100% now right out of the box. Awesome like a possum!

      posted in Hardware Compatibility
      JJ FullmerJ
      JJ Fullmer
    • RE: Installation woes: dhcp...Failed!

      @kbramhall said:

      @Tom-Elliott I attempted to go through the installer and saying no to DHCP and DNS but if failed to install tftp-server this time. Attached is the foginstall.log file.0_1450298881023_foginstall.log

      I took a look at the install log and noticed this bit

      ../lib/redhat/functions.sh: line 1: n#: command not found
      

      I’ve seen that before. You need to both make sure that you’re running as the root user and make sure you’re running the install script from the bin folder.
      i.e. cd into where you downloaded/untarred the fog installer and then

      cd bin
      ./installfog.sh
      

      I figured out when making the automated update scripts that you can’t run it with the full path like
      /home/fog/installFoder/bin/installfog.sh
      because it use the trailing … to get to some included scripts. So you have to start the script from its happy home.

      Also, what happens when you try to install the packages that failed manually?
      I would try them one at a time. It looks like these ones…

      yum install tftp-server
      yum install xinetd
      yum install vsftpd
      yum install gcc
      yum install gcc-c++
      yum install lftp
      

      And I just had another thought, are you sure the firewall is completely disabled? I just remembered a recent experience where a fresh install cent OS wouldn’t do internet things until I flushed the iptables.
      Which if memory serves is

      iptables -F
      or
      iptables -f
      

      Hopefully something there helps

      posted in FOG Problems
      JJ FullmerJ
      JJ Fullmer
    • RE: Active directory Join issue

      @anthonyglamis @Wayne-Workman speaks the truth.
      I would just add that there is a setting called FOG_FTP_IMAGE_SIZE in fog configuration → Fog Settings → General Settings
      that you can enable. The size that says 0.0 is likely image size on client. If you enable FOG_FTP_IMAGE_SIZE then you will also see the compressed image size on the FOG server which I think will automatically update, but it might also need to be deployed first.

      I just like being able to see both sizes.

      posted in Windows Problems
      JJ FullmerJ
      JJ Fullmer
    • RE: Installation woes: dhcp...Failed!

      @kbramhall said:

      @Arrowhead-IT As we’re troubleshooting I’m thinking it is definitely something with our internal networking configuration. The DNS servers we are using include google’s 4.2.2.2 and an internal DNS server.

      Isn’t google dns server 8.8.8.8 and 8.8.4.4 ?
      And if you’re using public dns’s maybe try opendns and see if that makes a difference
      208.67.220.220 and 208.67.222.222

      When you say internal network config, do you mean at the network infrastructure level or with the FOG server OS?
      If you think its the local network, do you have any other cent OS boxes, and if so are they able to install the packages?

      @kbramhall said:

      @Tom-Elliott Hey Tom, we are not dead set to use 1.2.0 we just figured we’d download the latest from the FOG project website 🙂

      Welcome to Fog, where if Tom were to release every stable release of the development branch it would be worse than Ccleaner updates.
      1.2.0 was the last time something was labeled stable. I use the trunk in production and rarely have any issues, and you get new features all the time! And if there ever is a problem it’s fixed in a snap. Only issue with your configuration and the trunk is that you wouldn’t have internet, so you wouldn’t be able to install and updates. Which overall would be fine, I’m one of the crazies on the bit torrent sync to the source files because I can’t wait the 20 seconds it takes Tom to hit the commit button.

      Anyway to install the trunk you’ll need git, svn, or btsync. Git is probably the easiest, svn is on sourceforge.net and they’ve gone down like 5 times in the last 3 months. There’s instructions on the wiki here https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

      posted in FOG Problems
      JJ FullmerJ
      JJ Fullmer
    • RE: 1.3.0

      1.3.0 is really the trunk/“beta” version currently. It isn’t quite yet to release. Granted if every stable trunk was released as a final version, we would be at FOG 5782.2.0 by now.
      @Tom-Elliott has been working on gpt partitions recently trying to get it perfect. Give the trunk a go

      https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

      posted in FOG Problems
      JJ FullmerJ
      JJ Fullmer
    • RE: snappin doesn't work

      @lebrun78
      So looking at how you map the drive, I think that may be where the problem lies. With Powershell scripts mounting a drive defaults to stay in the scope of the script running it. So in other words it won’t persist once the script ends.
      My recommendation is you change it up a little bit by using the New-PSDrive method with a few specific arguments.

      Anyway…
      Instead of doing this

      if (!(Test-Path -Path p:)){
          $net = new-object -ComObject WScript.Network
          $net.MapNetworkDrive("p:", $serveur, $false, $credential.GetNetworkCredential().UserName,$credential.GetNetworkCredential().password)
      }
      

      Try this

      if (!(Test-Path -Path p:)){
          New-PSDrive -Name "P:" -Scope Global -PSProvider FileSystem -Persist -Root $serveur -Credential $credential;
      #The -Persist switch and setting the scope to Global ensure that your drive is mounted outside of the script. 
      #This also lets you use your PowerShell Credential object without converting it to plain text when its used in the command (Which is what .GetNetworkCredential().password does
      }
      

      Then at the end of the script you do this to remove the PSDrive

      Remove-PSDrive -Force -Scope Global -Name "P:"; 
      

      One other thing you may need to do is enablelinkedconnections. It’s a registry key at
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system\enablelinkedconnections

      If you create and set that key as a REG_DWORD with Value data 0x1 (1) it will make it so you can see all mounted drives from an admin prompt. By default, drives mounted by a user in standard mode won’t show up if you run get-psdrive in an admin prompt and vice versa. Setting that reg key makes it so they can see one another which will ensure the system account that runs the fog service will be able to access the mounted drive. This security “feature” of the drives not being visible to elevated/non-elevated is a part of windows UAC.

      You can create this key with powershell like so

      $regKey = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system\enablelinkedconnections";
      if (!(Test-Path $regKey) {
          New-Item -Path $regKey -Force
      }
      New-ItemProperty -Path $regKey -Name "enableLinkedConnections" -Value "1" -PropertyType DWORD -Force;
      

      Also, a side note, you can pipe the secure pw to a file stored on the local machine to make it so you don’t have to create the secure string and have any sort of password in plain text. Just make sure that it can only be read by the System and admin accounts. i.e. add a hidden folder to the fog service called keys, or secure, or even just ~, and lock it down to only allow admin access. Then as part of your image you can store secure pw files for mounting drives with powershell without needing to put your password in plain text in a file anywhere. You just do the key the same way since its needed for decryption, and you just put the path to the password file. And you have to be an admin to run the secure string commands and an admin to access the pw file and the cert file, so there’s not really a risk of a non admin being able to see the decrypted password. Just a thought that might help simplify writing scripts. Personally I made a module for mounting shares with powershell I use in my install scripts.
      The contents of the password file would look like what you are putting into your $pwd string variable, so you could essentially copy and paste that into a text file.
      Or run $pwd | ConvertFrom-SecureString -key $tab_key | Out-File "C:\Program Files (x86)\Fog\secure" You could put the pw file anywhere you want really.

      One other note that might be causing problems is that you should try not using $pwd as a custom variable because it is already a alias system variable for the Get-Location command. So it’s possible, although maybe not super likely, that the $pwd variable could be reset to your working directory. So maybe try changing that to $pw instead.

      Hopefully that’s all some helpful information.

      posted in FOG Problems
      JJ FullmerJ
      JJ Fullmer
    • RE: HP Z640 - NVME PCI-E Drive

      It was getting a different device name /dev/nvme0n1 to be exact
      I was able to get it to run hardware inventory,
      just had to manually add it to the hosts in the fog web console and set the primary hard disk to that.
      I found that information with the fog compatibility menu option under partition information.
      It worked for running the hardware inventory but it is not working for imaging the computer unfortunately.

      posted in Hardware Compatibility
      JJ FullmerJ
      JJ Fullmer
    • RE: Can't Edit Exisiting Snapins or Create New ones

      I found a script to restore permissions here
      http://serverfault.com/questions/221447/how-to-repair-restore-ubuntu-10-04-after-sudo-chmod-777

      #!/bin/bash
      # Restores file permissions for all files on a debian system for which .deb
      # packages exist. 
      #
      # Author: Larry Kagan <me at larrykagan dot com>
      # Since 2007-02-20
      
      ARCHIVE_DIR=/var/cache/apt/archives/
      PACKAGES=`ls $ARCHIVE_DIR`
      cd /
      
      function changePerms() {
          CHOWN="/bin/chown"
          CHMOD="/bin/chmod"
          PERMS=`echo $1 | sed -e 's/--x/1/g' -e 's/-w-/2/g' -e 's/-wx/3/g' -e 's/r--/4/g'  -e 's/r-x/5/g' -e 's/rw-/6/g' -e 's/rwx/7/g' -e 's/---/0/g'`
          PERMS=`echo ${PERMS:1}`
          OWN=`echo $2 | /usr/bin/tr '/' '.'`
          PATHNAME=$3
          PATHNAME=`echo ${PATHNAME:1}`
      
      #    echo -e "CHMOD: $CHMOD $PERMS $PATHNAME"    
      
      #    result=`$CHOWN $OWN $PATHNAME`
      #    if [ $? -ne 0 ]; then
      #   echo -e $result
      #        exit 123;
      #    fi
      
          echo -e "CHOWN: $CHMOD $PERMS $PATHNAME"
          result=`$CHMOD $PERMS $PATHNAME`
          if [ $? -ne 0 ]; then
          echo -e $result
          fi
      }
      
      for PACKAGE in $PACKAGES;
      do
          if [ -d $PACKAGE ]; then
          continue;
          fi
          echo -e "Getting information for $PACKAGE\n"
          FILES=`/usr/bin/dpkg -c "${ARCHIVE_DIR}${PACKAGE}"`
      
          for FILE in "$FILES";
          do
              #FILE_DETAILS=`echo "$FILE" | awk '{print $1"\t"$2"\t"$6}'`
          echo "$FILE" | awk '{print $1"\t"$2"\t"$6}' | while read line;
              do
                  changePerms $line
              done
              #changePerms $FILE_DETAILS
          done
      done```
      
      It's running right now, hopefully that does the trick.
      posted in Bug Reports
      JJ FullmerJ
      JJ Fullmer
    • RE: Client boot to HD goes to memtest.

      I had this problem too, upgrading to the latest trunk/svn solved it for me. This happened to me last week, so whatever svn version was valid at the start of last Tuesday was having that problem for me, but it went away after an update and restart of the server.

      posted in FOG Problems
      JJ FullmerJ
      JJ Fullmer
    • RE: HP Z640 - NVME PCI-E Drive

      @Sebastian-Roth on it

      posted in Hardware Compatibility
      JJ FullmerJ
      JJ Fullmer
    • RE: Can't Edit Exisiting Snapins or Create New ones

      @Arrowhead-IT Well it was worth a shot but it didn’t do the trick, maybe restarting would work, I’m backing up before I try that though.

      posted in Bug Reports
      JJ FullmerJ
      JJ Fullmer
    • 1 / 1