Best posts made by fry_p

Hi @GFm
I had the same issue in the past. The reason this is happening is that the newer revisions of the FOG client are much more efficient than the legacy client. It is basically kicking in too early. The way to fix this is to disable the service before you sysprep it pre-capture (best practice for the FOG Client). You then use the setupcomplete.cmd method shown in this Wiki Article:

https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

You are basically telling it to re-enable and start the FOG service after sysprep is finished.

Installing as we speak. Well done! Though I recently joined the active community for this project, I’ve been using FOG since the 0.29 days and am amazed to see where the project is now. It’s come a long way to say the least. You take tools like this for granted when you are forced to do it the old fashioned way. I (briefly) worked IT at a factory that refused to implement any imaging solution. Each PC was built from OEM Windows from scratch. It sucked.

I’m glad to be back using my favorite open source project out there. Though most things we use at my job are proprietary, the support for FOG far surpasses any paid software. I can literally post on the forums and hear from a moderator, developer, or the legendary Tom Elliott himself within the hour. Even early in the morning!

I’m already thinking in the future, but I must ask, will the trunk style of updating disappear once the final revision of 1.3 is out? It would be bittersweet to lose that. On one hand you have the obligatory bugs that come with any testing, but being on the cutting edge of a growing project is actually pretty cool.

But I digress, keep up the good work guys and kudos for the dedication to the project. I look forward to the 1.3 release party

@Wayne-Workman I figured it out! I’m actually kinda proud of this one. Please see below for all of my Windows Server 2012 configs

Please let me know if you need anything else for this. It did indeed work. Thank you so much!

Congratulations everyone! I’m actually going to miss trunk/svn/RC’s in a weird way lol.

@Quazz I just tried both arguments on a surface pro 4. As long as you put

usbcore.old_scheme_first=1

before

has_usb_nic=1

separated by a space like you said, it works with no errors.

@Sebastian-Roth said in Stuck at Task Management Page "Unable to start task. Unable to upload file":

Not because it’s screwed but because more often than not you can learn something by re-doing things.

Amen to that. I learned Linux basics and the finer capabilities of FOG from rebuilding from scratch. Most people who use FOG seem to inherit an old installation from the last regime, myself included. I tried to fix what was there but it was poorly set up and unstable. It took some convincing and getting my hands dirty but I am on Trunk and loving it.

@george1421 I took a complete 180 on the methodology on this problem with the help of my co-worker who is better with Powershell than I am. Below is the sanitized version of our simple script to check Domain PC’s for the FOG Client:

ForEach ($Computer in (Get-ADComputer -Filter * -SearchBase "OU=Sample,DC=yourdomain,DC=com")) {
$ComputerName = $Computer.Name
If (Test-Connection $ComputerName -Count 1 -Quiet) {
    $FogService = Get-Service -Name FogService -ComputerName $ComputerName -ErrorAction SilentlyContinue
        If ($FogService) { Write-Output "FOG is running on $ComputerName" | Out-File C:\Scripts\FOG.csv -Append}
        Else {Write-Output "FOG is not running on $ComputerName" | Out-File C:\Scripts\FOG.csv -Append }}
Else {Write-Output "$ComputerName is Offline" | Out-File C:\Scripts\FOG.csv -Append}
}

It isn’t the prettiest, but it is versatile in the way that you can really sub the FOGService with any other service name to check if said service is installed and running. I have a initial CSV for the online PC’s that had a broken or not installed FOG Client and set a GPO Startup script to remove any old service, install the new service, and finally start the service. Below is a sanitized batch file for that:

msiexec /q /x C:\LegacyClientInstaller\FOG Service Installer.msi"
msiexec /i "C:\NewClientInstaller" /quiet USETRAY="0" HTTPS="0" WEBADDRESS="YourFOGAddress" WEBROOT="/fog" ROOTLOG="1"
net start FOGService

Hope this may help someone someday!

I just recently used FOG to create a surface pro 4 image. My workaround was to use a port replicator/hub to have both an external USB keyboard and Ethernet adapter plugged into the surface. It seemed to recognize both. It isn’t a permanent solution but It is how I did it.

So, this is really dumb on my part… It was our web filter blocking the calls out to pushbullet. It now displays the email and name in the table and the GUI after I whitelisted it. I will double check that notifications are working tomorrow, but this is looking like a whoopsie on my part. Most likely solved.

@ITSolutions I suppose my method is a band-aid fix of sorts. At my place of work, we are moving to standardize the models of PC’s we are putting in. By the time next school year starts, we will have about 75% of all of the PC’s in the network be Dell Optiplex 5040’s. Ultimately, we are going the model-specific route of images since we only have a handful of models we use. I agree with what you are saying though.

@Mark-krikunov said in Host Status is Unknow:

@Tom-Elliott I am aware of that, but it something just annoyed and drilled my eyes every time i looked at host list, so i just wanted that to be fixed. And i just made some holes in firewall so just waiting for some results to pop on screen.

The hosts status is not perfect. But I want to mirror Tom’s comments by saying that the few developers that work on FOG focus currently on the fundamentals of imaging. I love these other features (and their quirks) but please understand that with the developers doing this on their own time, they must triage priorities.

@robza and @Wayne-Workman, just thinking out here. So we know the script runs flawlessly manually. Sorry if this is a silly question, but which user do you run it as? I believe the snapins run as SYSTEM (i think, correct me if I’m wrong). Could this have anything to do with the discrepancy we are seeing?

@Wayne-Workman That seems to have done it. Thanks! Is there anything I can do to prevent this crap data, or reduce it?

Ah thank you! Also, yes I realize I am on the bleeding edge of FOG and I do expect bugs. Been on Trunk for 2 weeks, flawless so far.

Thanks!

@Tom-Elliott I am actually using a script that checks for the latest and installs. To my knowledge, this is the latest. Please see below for my script:

echo *MYPASSWORD* | sudo -S apt-get update -y
sudo -S apt-get upgrade -y


sudo cp /opt/fog/service/etc/config.php /home/fogadmin/fogInstalls # config file
sudo cp /etc/exports /home/fogadmin/fogInstalls/exports # Exports file
sudo cp /var/www/html/fog/service/ipxe/bzImage /home/fogadmin/fogInstalls # 64 bit kernel
sudo cp /var/www/html/fog/service/ipxe/bzImage32 /home/fogadmin/fogInstalls # 32 bit kernel
sudo cp /var/www/html/fog/service/ipxe/bg.png /home/fogadmin/fogInstalls # custom background
mysqldump -u root --all-databases --events > all-Databases-backup.sql # database backup

cd /home/fogadmin/fogInstalls
time_stamp=$(date +%Y_%m_%d_%H_%M_%S)
mkdir ${time_stamp}
cd ${time_stamp}


sudo svn checkout https://svn.code.sf.net/p/freeghost/code/trunk
sudo chown -R fog /home/fogadmin/fogInstalls
sudo chgrp -R fog /home/fogadmin/fogInstalls
sudo chmod -R 777 /home/fogadmin/fogInstalls

cd ${PWD}/trunk/bin
sudo yes | ${PWD}/installfog.sh
wget -O - --post-data=“confirm=yes” “http://${FOGWEBIP}/commons/schemaupdater/index.php” 2>/dev/null


#sudo rm /opt/fog/service/etc/config.php
#sudo cp /home/fog/fogInstalls/config.php /opt/fog/service/etc
#sudo rm /home/fog/fogInstalls/bzImage && sudo rm /home/fog/fogInstalls/bzImage32
#sudo cp /home/fog/fogInstalls/bzImage /var/www/html/fog/service/ipxe
#sudo cp /home/fog/fogInstalls/bzImage32 /var/www/html/fog/service/ipxe
#sudo cp /home/fog/fogInstalls/bg.png /var/www/html/fog/service/ipxe
#sudo cp /tftpboot/undionly.kpxe /tftpboot/undionly.kpxe.original && mv /tftpboot/undionly.kpxe /tftpboot/undionly.0
#sudo cp /tftpboot/undionly.0 /var/www/html/fog/service/ipxe/undionly.0

sudo chown -R fog /var/www/html/fog
sudo chgrp -R fog /var/www/html/fog
sudo chmod -R 775 /var/www/html/fog
sudo chown -R fog /images
sudo chgrp -R fog /images
sudo chmod -R 775 /images



sudo /etc/init.d/apache2 restart
sudo service mysql restart
sudo service tftpd-hpa restart

Please let me know if you see anything wrong with it.

I’d also be interested in buying one

@Tom-Elliott No worries! I was just making sure I didn’t do anything to mess it up. No harm done, just got a mild teasing from my boss! ;D

@Wayne-Workman said in New FOG Testing dashboard. Feedback?:

I’ve shut down the old tests, and switched the new tests to use fogtesting.theworkmans.us

Well done man! I’m going to miss the successful patch streaks just because that was fun to look at. I understand why its gone though. I am probably due for an update to 1.5.5 from 1.5.4 and this is a great resource.

@adukes40 said in Issues with FOG Client Pre-Sysprep (Or maybe it's me):

@Wayne-Workman batting .1000 so far lol. maybe a trip to the casino is in order

I wish I had such luck about a week and a half ago. Since the newest client is so much more efficient, there is a great chance it will screw up sysprep. I got lucky on only one PC out of 26 before I made the change in the SetupComplete.cmd. That was a bad day lol.

Edit: I should mention after the changes, I’ve not had a single issue.

@george1421 I will look tomorrow as I am off today. I know it is in the 1000’s. I like your layout there though. This seems quite doable.