Just an update.
I grabbed the latest fogservice client 0.12.0 off github. Set defender to remove quarantines over the next day with a GPO and added it to the exclusion list. Wrote a shutdown script to reinstall the MSI if the fogservice is missing.
Wrote a conspiracy rant to my team about MS having hurt feelings because we don’t use intune or SCCM. Thousands of different apps and the one app they false flag on us JUST HAPPENS TO BE part of our imaging system. Yeah, ok, MS, sure mm hmm… yep.
Hello,
My fog client (version 0.11.17) on windows machines was detected as Program:Win32/Uwasson.A!ml with windows defender. This is a false positive with the latest definition update.
Windows defender has quarantined every fog client windows service on my network currently so I get to spend today figuring out how to reverse that for more than a few machines. I guess I’ll start with domain GPOs and see if I can set a do not quarantine list for now but I’ll probably have to reinstall fog everywhere and that means my images all have post install steps now unless I script something or rebuild them.
Any advice?
I keep getting this memdisk error when I try to load a win7pe SE iso. The ISO is about 200mb and the vm has 4gb of memory available.
[IMG]http://i.imgur.com/cvZri.png[/IMG]
Ive tried keeppxe, raw, and rebuilding the ISO in several different ways. I tried a clean slate rebuild even but I can’t quite figure out if I’m troubleshooting the ISO or memdisk.
Does anyone have any guides for just simply installing XP over PXE? Or can XP installed in the normal fashion without loading the entire ISO into memory when pxe booting? I googled around but I can’t find exactly what I’m after in this situation. This would be handy for when my images aren’t working correctly or when working on low memory systems.
Thanks! I’ll try this and report back with my findings.
I work in a computer shop and we get many different variations of machines. I have found all of the sysprepping resources I would need to make things work on these machines but I’m concerned about the licensing.
I planned to create a few master images and activate them after windows is installed. I usually call in all the OEM keys anyway after installing by hand. Microsofts article states that sysprepping an OEM is unsupported but that doesn’t mean impossible.
So my question is, if I use an OEM winxp SP3 or a retail SP3 to do my initial master image, will I be able to activate it properly afterwards or will sysprepping this convert my licensing to corp somehow hoping for a VLK key?
I noticed some people leave a series of X’s where the VLK key would go. Does this tell sysprep that we won’t be providing a key at that moment or does it error out at that point? You can imagine the envy I have for techs that get to work with the same hardware all day long. 
I did some sysprepping a very long time ago and remember having it not work properly with OEM keys but I’m not sure if that was a funny disc I was using from the start or if it has to do with the sysprep itself.
Thank you for the links, I haven’t seen these yet. I do have quite a few different images and tools working on my server right now. I wasn’t sure if adding bootable media for fog to the wiki was frowned upon because there is such a lack of articles geared towards them at the moment.
I have some time off this Canadian long weekend and I have lots of experience in wiki writing. I’ll create a page for all of the bootable media that I have gotten to work using different methods I have found around the web.
I tried the new TRK but it didn’t work either using the ISO method in this thread.
I’m trying to get HDAT working using your method but it tries to fall back to the cdrom drive. I have seen other people have had HDAT2 in their PXE menus around the web but it has some sort of weird extention with a .imz I think.
Do you have any sage wisdom on how i could get HDAT working in my install?
[url]http://clonezilla.org/livepxe.php[/url]
This is a guide on how to get clonezilla working under PXE properly. I have noticed that majority of the PXE tutorials I found are geared toward DRBL which seems to use different paths and favor different memory management?
Can someone break this guide down or any other DRBL guide on what needs to change for fog. I understand how to boot most ISO’s but some of them are simply too large and would rather use the PXE alternatives if they are available.
I got it working! thanks
the solution was right on the front page of the fog website for servers running debian
Thanks for the input, the file does exist in /tftpboot and the web console looks like this.
Hello I’m setting up fog for our tiny computer store and I have done quite a bit of research but I can’t shake this issue out with my own troubleshooting.
I setup the server with debian squeeze CLI, no GUI, setup mysql and edited the two config files with the root user/password properly. I can access the fog control panel and create the database. No real issues there.
I setup the ddwrt with the suggested line in the wiki to send clients looking for pxe to my server address.
The server IP is 192.168.0.155
I can’t get to the fog menu because it can’t locate the pxelinux.0 file. I loaded up a gpxe boot cd hoping for more info and thankfully was shown a bit more. It seems that the client is looking for the file at the following:
tftp://192.168.0.155/pxelinux.0
I may have the tftp:// part wrong as I’m working from memory but I believe that was the beginning of the address. It doesn’t seem to be finding the file or perhaps there is not enough permission for the file. I’ll take that as good news though that the ddwrt is sending my client to the right place and that there may be a path I need to change in one of the configuration files or perhaps a file permission.
The fog server is not handling DHCP at all. I just want to make that clear. My testbed just consists of a router hooked up to my pxe server and a test machine on the bench right now. I can’t put this live on our own network or the internet until I can make sure it works well and lock down some other potential security issues on the server being that it is a fresh install.
I searched the forums but was unable to find a string that brought my issue forward. I may just be tired though, actually caused me a bit of grief on valentines day here as I put a little too much extra time in at the shop trying to get it going before I left heheh.