Reinstall Sims with Solus3

[dan400007]

Ok, heres a question. How do you reinstall Sims.NET Workstation on the Sims Server?

 

Since installing the latest update Sims.NET will crash before getting to the logon screen, all the clients are ok it's just the server which has failed to update correctly.

 

Generally for a workstation we'll just remove the Solus3 client, rename the folder in program files, reinstall Solus3 agent and its sorted. Since this is the Sims and Solus3 server it won't allow us to remove the Solus3 agent - so how do I reinstall Sims Workstation on the server?

 

Why isn't there an option in Solus 3 to tell the client, 'Uninstall and Reinstall Sims.Net'!?!

[3s-gtech]

You can copy and paste a working SIMS.net directory over that one as an easy fix. Agreed though, that getting it to reinstall via SOLUS3 is a swine.

[MrMat]

Pretty much the same as you do for the workstations but instead of removing the agent, just remove the server from the list of Workstation Target Definitions within Solus3. So remove Server from Workstations, rename the SIMS.net folder then re-add the Server as a Workstation. This should do the trick. If it doesn't start automatically, click Get Target Version from Agents screen. If still not picking it up, restart the S3 service on the server. Bish Bash Bosh - job done. Edited January 24, 2014 by MrMat

[Rawns]

Pretty much the same as you do for the workstations but instead of removing the agent, just remove the server from the list of Workstation Target Definitions within Solus3. So remove Server from Workstations, rename the SIMS.net folder then re-add the Server as a Workstation. This should do the trick. If it doesn't start automatically, click Get Target Version from Agents screen. If still not picking it up, restart the S3 service on the server. Bish Bash Bosh - job done.

 

You don't even have to go that far.

 

Simply rename the C:\Program Files\SIMS\SIMS .net folder to C:\Program Files\SIMS\SIMS .net.OLD or something like that, then do a re-deploy of the SIMS Client to the server using the last Successful/Partially Successful deployment. Simples.

Edited January 24, 2014 by Rawns

[MrMat]

You don't even have to go that far.

 

Simply rename the C:\Program Files\SIMS\SIMS .net folder to C:\Program Files\SIMS\SIMS .net.OLD or something like that, then do a re-deploy of the SIMS Client to the server using the last Successful/Partially Successful deployment. Simples.

Aha smarty pants!!! The problem with that for us is we generally deploy to about 10 schools at a time so it's a right pain to access the re-deployment screen as it takes forever to load!

[Rawns]

Aha smarty pants!!! The problem with that for us is we generally deploy to about 10 schools at a time so it's a right pain to access the re-deployment screen as it takes forever to load!

 

Ahhh, you running a Cetrally LA managed SOLUS3 environment?

 

All our schools have their own S3 environments.

[MrMat]

Ahhh, you running a Cetrally LA managed SOLUS3 environment?

 

All our schools have their own S3 environments.

 

Yep! Sometimes it proves useful having it this way, other times I regret it and wish we had set it up differently i.e. separate S3 environments. At the moment it's useful as we are currently in the process of re-imaging all our SIMS machines to Windows 7 so having a central S3 server where I can remove and re-add machines to S3 for all schools is very useful (saves me from having to hop from server to server). Upgrade time however is a very different story...

 

Realistically if we were to go back and do it all again, I would probably opt for separate S3 environments but hey, you live and you learn!