allanlinwood

Hi Guys I have installed this software previously without too many issues in the past, but this year no matter where I install it (window xp, 7, etc) it keeps forcing a restart every half an hour or so. The event logs say the MsiInstaller initiated the restart to complete the installation of 'ESM'. I have made sure all permissions are correct in the registry, the install folder and the network share. Both components have been installed from downloads and not the auto, but this seems to make no difference. Currently we have the ESM Server and Administrator installed on one PC with the required share on the network server. Has anyone else come across this issue? Their tech support didn't have any clues.. Cheers.

Hi Guys..For anyone having this issue: I had this exact same problem today. I could not get it to work at all using Chrome and IE11 and would have the same ftp error as you had, however, Firefox works fine and downloads the file.

OK thanks very much guys for your input. I think that pretty much concludes this now How do you close a thread

OK I think that pretty much sums up my thoughts already. We do have quite a lot of older software lurking around the network and with a new campus to build we are starting new hardware, but with some old titles. It will be a case of suck it and see I think. Thanks already for those who have responded.

This may seem a bit simplistic; but I assume you have an image of these laptops? Have you tried a fresh image to save time figuring out all the other possibilities. If you are still having problems after that, then you know you have a hardware issue.

Hi I wanted to find the general consensus on what people are currently rolling out in regards to using 32bit or 64bit versions on their desktops and any issues they have found. Obviously I am aware of the memory gain advantage of 64 bit versions, but more specifically any day to day working issues or any reasons to stick with 32bit. Look forward to your thoughts. Update: *** THanks everyone for your input. I think I have made my decision now. ***

I also fell foul of this issue, like you I was curious how Windows 8 would run on one of these, then found that Windows 8 does some kind of check and in doing so destroys any chances of having it run properly again. There is a around it but it is not a permenant fix: When the fizzbook starts, press delete as though you were going into the BIOS It will then display the familiar message you have got "Sorry, the computer boot certificate.." Press Ctrl + INS Then you should have a menu to choose to get into the BIOS setup. Change the system to date to the year 2000. Now you can boot into your O/S Unfortunately as soon as you change your system date to 2013, you have the same problem again! Until there is a way around it I personally think Microsoft are liable for essentially bricking a lot of older motherboards, I have seen many people have the same problem online as this. No warning at all is given by MS about this before you attempt to install Win8!

I also fell foul of this issue, like you I was curious how Windows 8 would run on one of these, then found that Windows 8 does some kind of check and in doing so destroys any chances of having it run properly again. There is a around it but it is not a permenant fix: When the fizzbook starts, press delete as though you were going into the BIOS It will then display the familiar message you have got "Sorry, the computer boot certificate.." Press Ctrl + INS Then you should have a menu to choose to get into the BIOS setup. Change the system to date to the year 2000. Now you can boot into your O/S Unfortunately as soon as you change your system date to 2013, you have the same problem again! Until there is a way around it I personally think Microsoft are liable for essentially bricking a lot of older motherboards, I have seen many people have the same problem online as this. No warning at all is given by MS about this before you attempt to install Win8!