svnserve does have a web interface. here. The error message that’s generated when I try to access fog is as follows:
[Tue Oct 04 17:18:23.485189 2016] [dav:error] [pid 16632] [client 192.168.10.28:58477] Could not open the requested SVN filesystem [500, #2]
Not too long ago I successfully set up a FOG server on a Linux VM, was able to image a few machines as well, haven’t yet had to use them as they are for DR purposes mostly. More recently I had been approached by one of our software guys who was looking to get a SVN repository server set up on the machine as well. I installed and configured svnserve, but now when I try to access the FOG management page it loads the directory as an un-formated svn repository, here. Insight anyone? Tried reinstalling FOG using the settings specified in my previously working copy. No dice. Just a hunch but my first inclination is settings in apache2, I don’t really know where to start looking though.
@george1421 I did briefly, but it doesn’t appear that Veeam Endpoint would be compatible. Target requirements.
@george1421 I’ve looked into clonezilla, but some of these machines have very limited hardware, no USB, no available IDE, etc. But they all have network cards. This is why FOG seemed like a viable solution. As far as DR goes, I have a separate solution, NTBackup to FTP via .bat and Scheduled Tasks, that runs more regularly but I’m only backing up our board programs that we run in the software on our pick-and-place machines.
I’ll check out Veeam though for DR and its compatibility with XP, as the NTBackup to FTP I set up is a fairly new system that I’m not completely satisfied with.
@Wayne-Workman Thanks
I figured everything would be fine. Just figured I’d ask a crowd with more experience. I’ve attached a link to the datasheet for the motherboard, not really sure how (un)common it is. DATASHEET.
What is different about the RC8 version? Is the setup just the same? I was just going to move the virtual machine I’ve created and installed FOG with to our server. But if it’s really worth it, I’ll just start from square one with RC8.
Not so experienced FOG user here, just looking for an honest answer to a simple question.
I am contemplating implementing a regular imaging of 3 machines (using FOG) that are used for UI purposes on a few robots used for the manufacturing of circuit boards. These machines run XP and a software developed by the robot manufacturer, custom BIOS (that supports booting via LAN), run on 386’s I believe. We bought the robots second hand and have no install CDs for the software or any drivers associated with the software/hardware :S
Currently, I use another imaging software that runs within XP and takes live images (shadow). I’ve run into issues on one of the machines where it locks up partially through the imaging process, which overwrites my last image taken and I am left with an unusable file… forced to revert to an ancient image taken of the drive that is kept in dry storage.
I’m looking for an imaging solution that will regularly take images of the HDs connected to our robots, along with a few other machines on our subnet for production machines. Recently I set up FOG on a virtual machine and was able to take/deploy images from/to other virtual machines and it seems to be working correctly. Being that these machines have and are connected to uncommon hardware, (and some things I’ve read about FOG in regards to drivers installation issues) I’m a little weary to make it live on our production subnet.
Is this a safe and reasonable use for FOG? Should I be worried about any hardware or driver issues? Is the best option to just take an image, deploy to a spare HD and test it?