[sims] SOLUS 3.7

[zag]

Installed in about an hour. Seems to work OK but still very slow to navigate.

 

The user interface is much nicer now, although still very hard to find out how to add a workstation.

 

Got no idea why Sims Discover has a different install procedure either.

 

And the Available Updates view is still as complicated as ever, although I think this may be more to do with all the re-releases that are ready to be deployed.

 

Also there is still the problem where I have to enter the username/password each time I add a new workstation.

Edited July 8, 2014 by zag

[localzuk]

Also there is still the problem where I have to enter the username/password each time I add a new workstation.

 

I'm struggling to see this as a problem to be honest. The reason for it is if you have machines which are on different networks which have different credentials needed to install as far as I can tell. Is typing a username/password in that much of a chore?

[MrMat]

I'm struggling to see this as a problem to be honest. The reason for it is if you have machines which are on different networks which have different credentials needed to install as far as I can tell. Is typing a username/password in that much of a chore?

 

I have to agree. I'm constantly adding workstations, it's not a big deal.

[zag]

I'm struggling to see this as a problem to be honest. The reason for it is if you have machines which are on different networks which have different credentials needed to install as far as I can tell. Is typing a username/password in that much of a chore?

 

I've typed the same password in over 100 times now so yes its a problem for me. Why can't it have a "save user/pass" checkbox?

[Sheridan]

Actually mine seems to be working now, after a long wait of seemingly no activity! I've had good results with Solus on the 3.5/3.6 releases so I didn't want it broken!

[matt40k]

I've typed the same password in over 100 times now so yes its a problem for me. Why can't it have a "save user/pass" checkbox?

 

Eh? You know you can deploy to batches right? Also you could script the agent install then you just need to add them to channels to get SIMS so you don't need to enter a user\pass (I believe)

[zag]

Eh? You know you can deploy to batches right? Also you could script the agent install then you just need to add them to channels to get SIMS so you don't need to enter a user\pass (I believe)

 

Everytime I add a teacher computer to the network I have to go through the same process of adding it to Solus. We add 1 or 2 machines to the network each week.

 

Each time I have to type in that user/pass combination and there doesn't seem to be any way round it.

[matt40k]

We add 1 or 2 machines to the network each week.

 

What, do you HDD fail that often? Pretty sure if I had to replace\rebuilt\deploy that frequently I'd scripted it.

[zag]

What, do you HDD fail that often? Pretty sure if I had to replace\rebuilt\deploy that frequently I'd scripted it.

 

No these are new machines that we are rolling out to staff.

 

I have to enter the password every single time which is crazy annoying.

[localzuk]

No these are new machines that we are rolling out to staff.

 

I have to enter the password every single time which is crazy annoying.

 

You are deploying machines individually? Why not get the machines all working, then batch deploy SIMS to them? I can't match up deploying 100 computers with deploying SIMS 100 times.

[Sheridan]

I deploy individual machines occasionally, but would batch a few together normally.

[Cache]

To be honest, if your manually joining machines to the domain every other day, I would export the Agent Installer from Solus3, stick it on a memory pen and then when you join the PC, after a reboot logon and manually run the installer. You would then just need to go into the Solus3 console and then add it to the correct targets using the Agent target rather then browsing to the OU and pushing it out.

 

Either that, or spend a bit of time looking more into developing a script to deploy it using Group Policy (or read up on Capita's notes at the back of the Install or System Admin guide).

[synaesthesia]

Well,

 

We updated it the other day.

 

Logged first support case today, and I'm wondering whether to log a second case about fact Sims discover hasn't deployed to workstation after adding target 3 hours ago.

 

The UI is kinda different - whilst there's some improvements, some parts look to be more confusing so far (Given being used to the old system)

 

Has anyone else upgraded so far?

 

To start with, "moo!"

One of my schools upgraded without a hitch. The other just fails on the database. Not sure about that bug mentioned here as I upgraded SQL identically on both systems :/

[ianriley1986]

I had issues on some and some worked fine. Basically the ones that had issues just seemed to freeze on the install, Check in add/remove programs to see what parts of SOLUS weren't upgraded. To fix mine I done the following:-

 

* Took a backup of database

* Manually uninstalled SOLUS 3 database

* Manually run the SOLUS 3 database upgrade entering server details etc (it will tell you the database already exists so will just upgrade exisiting)

* Manually run the SOLUS 3 deployment server UI

 

Once I done this, SOLUS was fine.

 

NOTE: I had to get the install files sent from Capita to do the above.

Edited July 11, 2014 by ianriley1986

[Sheridan]

Mine seems to be working now - and has deployed a few clients ok since initial problems.

 

The gui is a bit different and the way you deploy an agent is different. One annoyance is when browsing AD for clients you have to specify the domain every time, but thats a minor niggle.

[zag]

Mine seems to be working now - and has deployed a few clients ok since initial problems.

 

The gui is a bit different and the way you deploy an agent is different. One annoyance is when browsing AD for clients you have to specify the domain every time, but thats a minor niggle.

 

What is the exact process of deploying and agent and upgrading Sims?

 

I've been going to Environment >> targets >> then auto detect >> Yes to the popup >> Active Directory

 

But no idea if thats the correct way or not. It doesnt seem to install Sims if I do that, we have to copy the Sims directory manually to program files.

[MrMat]

That should work but if it's not then the Auto Detect isn't doing what it's meant to by the sounds of things.

 

Try this:

 

Environment >> Targets >> Clients >> Add >> (Make sure SIMS is ticked, not SD) Choose Clients >> Select OU in AD and click 'Select' >> Find the machine on the list, use column filters if required OR if you know the full machine name/IP address enter it manually into the boxes at the bottom >> Selected workstations will move to right side of the screen >> OK >> Enter username and password etc

 

Job done!

[Sheridan]

What is the exact process of deploying and agent and upgrading Sims?

 

I've been going to Environment >> targets >> then auto detect >> Yes to the popup >> Active Directory

 

But no idea if thats the correct way or not. It doesnt seem to install Sims if I do that, we have to copy the Sims directory manually to program files.

 

As MrMat says - but I've been using the manual Add method more often to specify small numbers of new target computers.

[Simcfc73]

Well that was a bad idea.. deploying Summer and Solus at the same time.

 

The deployment history is still awful

[zag]

Thanks, yes it seems to install Sims using the manual method fine.

 

Not sure what the "Automatic" method actually does...

[synaesthesia]

Well,

 

 

Trying to deploy 3.7 out to my main site today. Won't let me because it's withdrawn one of the updates! (3.7.161.0) - the .Net framework bit is marked withdrawn!

 

EDIT: It's now available but won't download. Argh, the competency!

 

 

Another Edit: Now it's going. .NET Framework appeared as a separate download (dated June??) and now we're cooking on gas - until it fails and rolls back! Hope that doesn't happen, it's bad enough on a 15 station primary!

Edited July 14, 2014 by synaesthesia

[zag]

It took ours about 2hrs to upgrade so be patient

[MrMat]

Scheduled Summer V2 to install to a total of 14 schools, which equates to 304 client machines, over the weekend.

 

Came in this morning expecting the usual barrage of calls but to my surprise (and delight) so far I've had 1 call. 1 call!! Of the 304 clients, only 3 failed.

 

So far, very pleased with Solus 3.7!

[Hulbert99]

Mine failed due to Tolerance not met for Solus 3 Database, so it did the .net 4.5 and the Solus 3 agent and then rolled the whole lot back.

 

This just happened to ours! What was your solution?

[DevilsAdvocate]

I had the same problem as above. There were some registry entries still pointing to SIMS2008 after our 2012 migration. Did a search in the registry for SIMS2008 and changed them to SIMS2012 instead and the install went fine after.