Jump to content

Dirthat

Members
  • Posts

    3
  • Joined

  • Last visited

Reputation

5 Neutral

About Dirthat

Personal Information

  • Occupation
    IT Ops Manager
  • Location
    SE London
  1. @Boredguy, All of my SIMS updates are run at night manually and it usually means having to babysit the servers. We have our workstations set to deploy 6am to 12pm as that usually covers everyone. I'll change the concurrent downloads to 99 to see if that helps and speeds things up. @Warwick_Tech, I had the same issue. I did the same thing that neilenormal suggested, extract the patch to the desktop and then ran the SOLUS3DeploymentServiceInstaller_x64 and the SOLUS3DeploymentServerUIInstaller_x64 restarted the Solus3 Deployment Service and this seemed to resolve the issue. Any workstations that are still sitting on pre .59 versions of SOLUS3 we have been able to update from SOLUS3 now by clicking Environment > Agents > Reinstall agent.
  2. Hi All, Bit of a long shot, but, is there a way to stop Solus3 auto deploying to workstations during the initial update deployments? Server 1 - Summer 2021 has installed the SQL server, database, fileserver and now it's trying to deploy to 400+ workstations, most of which are off. I'm now sitting here wasting my time waiting for Solus3 to try to update machines that are turned off, it's been trying to install to a PC that is switched off for 20 minutes now! Server 2 - Missing the Solus3 3.12.59.5 patch, it's now sitting there, and has been for 40 minutes, trying to deploy onto one workstation. I still have the Summer update to do on this box which will be a nightmare because of this setting. Any ideas? DH
  3. Have you tried deleting the PC from Solus3 and then redeploying? I had a similar error before with the "agent target id" bit and that seemed to solve it.
×
×
  • Create New...