@wayne-workman said in Where can i get the new 1.53 install with the fixed Binaries from:
Just noticing here, @developers @moderators @testers is it normal for the message to be
bzImage412? I’m refering to the screen-shot the guy posted a few posts below.
I do not get the “412” at the end of bzImage to answer your question.
@tom-elliott We were seeing this same “issue” last week on 1.5.3 prior to the host registration fix. I have re-installed to fix the aforementioned registration issue, but I am getting pressured as to why the MBR/GPT erasure takes so long by the techs now. Is this part of this new feature you mentioned earlier? I myself will test tomorrow to get an exact time it takes, but I wanted to let you know that this may be wider spread than initially thought.
Hey @george1421
Thanks for the reply and I apologize for the delay in my response. I am now 100% sure that there is little to no danger in having this open in my situation. Our images are free of any sensitive info and all licensing is done through KMS, so no possibility of stealing software activation codes either. I’m glad the project developers have NFS v4 on the feature radar for possible distant releases. Thank you for the thorough explanation and putting into terms someone like me can understand. Keep up the good work guys.
I tried manually adding the host through the web interface and was able to get to deploy image. However, it hung on “Erasing MBR/GPT”.
@tom-elliott Full Reg is throwing a “No Viable MAC found” (not the exact error) after registration for me on 1.5.3. I just updated this morning and the problem started then. I can try to get the exact error if needed, but I am doing this on an integrated NIC for an Optiplex 790, a model we’ve successfully imaged many times before. Thanks in advance for your help
Hi All,
It has been a while since I have posted as FOG is working beautifully for us at the moment. I have actually been able to look at some proactive things like security on our infrastructure. This brings me to the point of this post.
As a disclaimer, I am far from a security guru. In fact, I’m quite new to it. I am using a penetration testing solution to try to start figuring some of this stuff out. During my testing on the FOG server here, a few things popped up as critical/high level warnings. I was spooked at first but then I noticed that anything that was flagged had to do with the /images NFS Share.
The first flag was for “NFS Exported Share Information Disclosure”, basically saying that the /images share could be mounted by scanning the host. I figure this is like this so any host can pull from this share during capture/deployment. If this is the case, I am fine with it. If I screwed something up a while back with permissions and left a gaping hole in the security of this server, I’d like to find the best practice for setting permissions for this share. Ideally it would be moderately secure but (very importantly) still be able to image indiscriminately throughout our network. I can provide more info if needed, but I appreciate any input.
The second flag is also related to the /images NFS Share. This one also points to a permissions issue. “The NFS share is user mountable”
I appreciate the help guys and keep up the good work!
@wayne-workman said in Surface pro 4 gets stuck on init.xz (still):
@fry_p What caused it to be unable to image a Surface Pro 4? Has it ever worked at your location? When did it last work? What’s changed since then?
Hey guys. I realize more info is needed. However we don’t have another surface to test with. I can tell you it has been a while since we have done a pro 4. We did do a pro 3 with the same conditions without issue last week. It has worked at our location before albeit very sporadically with no rhyme or reason it seems. I’d say it has been months since the last pro 4, so I have updated FOG since then. I’m sorry I don’t have more info. If we get another pro 4 any time soon and if I am back to work, we will test. I suppose we can file this away for now. Right now, we only get 4’s for warranty replacements as the new Surface Pro is out so they are few and far between.
I am out of the office on medical leave, but my colleague messaged me that he is unable to deploy to a surface pro 4 once again. It goes through the fog boot menu just fine, but hangs on init.xz. He has tried updating to the latest RC 13 with all of the latest ipxe files. I remember there were issues with the ipxe files and pro 4’s but he told me that the latest were supposed to fix this as mentioned in another post here.
He ended up building from scratch on the Surface due to time constraints and I am not there to actively troubleshoot it unfortunately. Just wanted to let you guys know.
I have to say, FOG has been quite solid lately. I’ve been on RC10 working since it came out and I haven’t found any bugs in my environment. Keep fighting the good fight developers. I live vicariously through you guys since I don’t have one iota of programming skill!
@sebastian-roth Sorry to double post, but this is getting bizarre. You can fork this into windows issues or delete the thread for being off topic. I just want to pick your brains on this. Thinking this issue was related to LTSB, I downloaded and installed Windows 10 Education version 1709 on the test VM and joined it to the domain. I then applied GPO’s from 4 different servers. 3 Physical Server 2012 R2 servers and the original problem Server 2012 R2 VM Server.
What I found was the same inconsistency after rebooting the Win 10 Edu Test VM. I am getting the same Event 513. See below:
I am 100% sure the naming is right because I can manually add the same printer using the \FernwayAD\FerLib path. All printers that fail to add have the Event 513. I am also going to post this on other forums.
@sebastian-roth Thanks for the info. We just ran into the same issue with FOG as we did with Windows! 
I tested more printers and logins to try to make it not work. It was solid until I rebooted. Just like with Windows GPO printers, they pulled a Houdini and were gone after the reboot. I waited and they still never appeared. I looked in event viewer and found This error, identical to what I was getting with GPO printer adding. I should have snapped a screen, but I blew away the VM to try something else. Here is a link to the Technet on the error I am getting: https://technet.microsoft.com/en-us/library/dd380098(v=ws.10).aspx
The reason I blew it away is I suspect it may have something to do with LTSB. I am installing full Windows 10 Education on the VM now.
I know this is more of a windows problem now, but I wanted to put it out there. I will report back.
@sebastian-roth Thanks! It did eventually install while I was away from my desk. So I’d say it was a success.
What is the status of managing printers on FOG? By that I mean would it be wise to move away from Windows Print Management to Fog Print Management? Is this feature antiquated and going to be killed off? Only asking because I legit never paid attention to this feature.
As a bit of background on this, we are having a heck of a time with Group policy consistently adding printers with Windows 10. As a result,. I was given the green light to try FOG’s printer add capability 
I am running Working branch “version 69” and 0.11.12 client
I am testing it on a VM Windows 10 LTSB. I have one shared printer I want to test with. The printer is HS214Copier and the VM is “TVM” Here is what I’m getting.
------------------------------------------------------------------------------
--------------------------------PrinterManager--------------------------------
------------------------------------------------------------------------------
10/23/2017 7:37 AM Client-Info Client Version: 0.11.12
10/23/2017 7:37 AM Client-Info Client OS: Windows
10/23/2017 7:37 AM Client-Info Server Version: 69
10/23/2017 7:37 AM Middleware::Response Success
10/23/2017 7:37 AM PrinterManager PrintUI return code = 0
10/23/2017 7:37 AM PrinterManager PrintUI return code = 0
10/23/2017 7:37 AM PrinterManager PrintUI return code = 0
10/23/2017 7:37 AM PrinterManager Adding printers
10/23/2017 7:37 AM Printer Adding: \\printerad\HS214Copier
10/23/2017 7:37 AM PrinterManager PrintUI return code = 0
10/23/2017 7:37 AM PrinterManager Invoking add \\printerad\HS214Copier for all users
10/23/2017 7:37 AM PrinterManager PrintUI has not finished in a timely fashion, abandoning process
10/23/2017 7:37 AM PrinterManager Restarting spooler
-------------------------------------------------------@sebastian-roth I should have checked that before updating My bad, is there a way to look at the previous git pulls? I was on RC-9, but had not updated for quite a period of time until now.
@tom-elliott I pulled the latest working and it got past that point to partclone. I’m not sure what fixes were implemented, but they seemed to have worked. If you need any additional info that I can provide in order to pinpoint this issue, please let me know.
@tom-elliott It is a WD2500BEKT 250 GB Notebook Drive. It is a standard MBR format and I don’t know how to identify if this is Advanced format. I included the model just in case you can glean that info from it.
@sebastian-roth I will try some of the things in the thread tomorrow, but it looks like the final result was having to re-create the image from scratch? I am also sysprepping the same as the other thread and I encounter 0 errors when it does the OOBE stuff coming out of sysprep after the task fails to upload.
FOG 1.5.0 RC-9
Client: 0.11.12
Please see the below picture. Trying to capture a Windows 10 LTSB image from a HP EliteBook 8460p. Debug capture fails at this point. Already ran chkdsk and sfc on it.
@sebastian-roth I’d love to do more tests, but unfortunately I don’t have an available surface. My apologies. If I get one I’ll let you know.
@avaryan I have never tried anything but the Microsoft Dongle. It may certainly be worth a try.