Sage 100

I'd post this under urgent, but since it's been going on since this morning...SMI, Sage 100 Advanced 4.50.2 Want to install SMI on a server 2008 R2 with Excel 2010 (32 bit). The reason being this is the system they've setup for my remoting purposes. Started the SMI install and the first issue was that .NET Framework 3.5 SP 2 was not installed. Actually .NET Framework 3.5 was not installed at all, so installed that and the SP. (Framework 4 was already installed) Next, said the MS SQL CE 3.5 SP 2 was not installed, again SQL CE wasn't there at all, installed it, and installed SQL CE SP2. The SP2 install warns that both the x64 and x86 should be installed. So I installed them both. Started the SMI install again...same issue SQL CE...checked under installed programs, only the x64 was showing. Uninstalled it, reinstalled it, then installed the x86. Okay, now both show in installed programs. Stared the SMI install again...this is getting ridiculous, same message. Checked the SQL CE SP2, ran the repair on the x86. I've looked for anything related to these error in Sage KB (which said if .net framework wasn't installed it would install it, ha-ha), Alchemex site, joined the Alchemex group and checked and I don't find either of these issues. More significantly, I can't seem to find anywhere that SMI lists what must be installed prior to installing SMI. Now perhaps I'm the issue wanting to run this on 2008 R2...

While I gave up (temporarily) on trying to get SMI installed, I did run across an issue at clients's where their workstation would lock up, then reboot for no apparent reason at odd hours. Checked task scheduler, av updates etc. to see if there was something that ran and required a reboot, didn't find anything in particular. Then checked the Windows Update history and found that a .Net Framework update had repeatedly failed to install. In researching that I ran across a MS KB article from May 2012 about corrupted .Net installations. Here's the link http://support.microsoft.com/kb/976982. Ran method 2 and resolved the mystery reboot on the workstation. I'll run throught this too at the SMI problem site and see if it helps.