Just a quick note to let everyone know that we've received a few reports about our management console not installing on a Windows Server 2003 computer if Service Pack 2 has been installed. There is no true interoperability issue, it just appears that we don't properly detect a supported SP level so the installation of the management console fails.
To work around this, be sure that the management console is installed prior to installing Windows Server 2003 SP2. Currently there are no other workarounds but we're continually investigating potential solutions, and this will also be resolved with the upcoming Service Pack 1 release for SoftGrid 4.1 which is due sometime in the first half of this year.
We apologize for the inconvenience and will post further information here once known.
- The SoftGrid Team
From my experience, the console breaks after applying SP2 - even if you installed it fine with SP1 applied !
You can get around this problem by dropping the one row out of the Condition table in "SoftGrid Virtual Application Server.msi" (using Orca or similar)
Download Orca, edit the SoftGrid Virtual Application Server MSI with Orca and go to the condition table. Change the line for the Release_SoftGrid_Management_Console condition from:
Not ((VersionNT = 501 And ServicePackLevel = 2) Or (VersionNT = 502 And ServicePackLevel = 1))
Not ((VersionNT = 501 And ServicePackLevel = 2) Or (VersionNT = 502 And ServicePackLevel >= 1))
I ran into this exact problem on a new Server 2003 installation with SP2 installed prior to installing the SoftGrid virtual Application Server. The management consol wouldn't install, and the option to install it wasn't even available performing a custom install. My solution was to repackage the management console only using conventional repackaging methods on a XP Professional machine and then install my package on the Windows 2003 server. Works exactly like it's supposed to now.
I ran into an issue tonight when I was trying to build a Softgrid demo. I loaded up a VM Workstation