Failed SOLUS2 Workstation upgrade after a SOLUS3 deployment?
As advised by Capita at a SOLUS3 training day, we are rolling out SOLUS3 to schools in order to install Discover. We've done this in 14 schools now, and last night we released the SIMS Autumn upgrade to three trial schools via SOLUS2 which we are still using for SIMS and FMS upgrades. One of these schools has had SOLUS3 installed and Discover deployed successfully. In this school, the Summer upgrade installed successfully on all but three workstations and the SIMS server (which failed to upgraded the SIMS client to the Autumn release when it was ran). Strangely, the server and these three devices are machines that all have the SOLUS3 Agent installed, and have had Discover deployed to them. We've compared the SIMS.INI, S: drive mappings etc to workstations that have upgraded successfully and there is no difference between them, but for some reason, SIMSLoad.exe does not pick up and apply the SIMS upgrades! These machines upgraded with no issues when the Summer upgrade was released, and it's too much of a coincidence to be only SOLUS3 machines that are not automatically upgrading any more when they have been fine previously before SOLUS3 was present on them. Has anyone else come across this or have any idea of what's going on?
We're planning on rolling out the Autumn upgrade to al of our sites on Monday, and this has made us a bit cautious about releasing it to the otherschols that have SOLUS3 installed. :(