synaesthesia Posted September 8, 2015 Posted September 8, 2015 Machines that have been rebuilt with the same name and on solus 3. What a pain in the ****! ARGH! If it wasn't for this utterly stupid thing we'd have been reasonably quiet first day back! But no! Anything we can do to stop it assuming SIMS is already there and running? Mass reinstalling agents sort of sometimes works, occasionally!
3s-gtech Posted September 8, 2015 Posted September 8, 2015 If they don't have the SOLUS agent on them, I just select them and hit Reinstall Agent on the Environment section - didn't take long to do and I rebuilt 44 staff PCs this Summer.
clareq Posted September 8, 2015 Posted September 8, 2015 I go to the client machine and open the solus agent on there, check for updates, deploy. If I can't do that, sometimes checking client version on the management console can help
Liam Posted September 8, 2015 Posted September 8, 2015 Frustrating this.. I got around it by using sims remote app on a server 2012 environment . Delegate credentials so it's single sign on and within 5 seconds they are presented with their sims login box. Zero touch installs now for me.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now