Solus3 and Imaging

[ultima170387]

Does anybody know if solus 3 can be included on a sysprepped disk image without issues? TIA

[BKGarry]

Page 77 of the SIMS Documents here http://simspublications.com/747571/assets/solus3school.pdf

 

States

If your school uses imaging software such as Microsoft System Centre to enable quick re-installation of your staff workstations, SOLUS3 can be part of the image. You will need the SIMS, FMS or Discover client to be installed on the image using the client installers from an auto-extracted SOLUS3 download file, as well as the SOLUS3 agent. The SOLUS3 agent should be installed on the image as per the manual agent installation instructions. Because of the way SOLUS3 creates a unique identifier based on your hardware, a re-imaged machine will update the client details on the SOLUS3 Deployment server and you will not need to remove the old Agent entry from the DS screen.

[sparkeh]

Wait, is this new? Everyone used to warn that this was a bad idea didn't they?

[BKGarry]

I haven't tried it personally.

 

I could never get the exported installer from SOLUS3 to work and always ended up deploying from the Console.

[synaesthesia]

There's a spate of these questions of late, indeed. And it's still a bad idea. It's easy enough to push install from Solus3 console, and if you can't there's a problem which you should get fixed first.

[ITJS2015]

Solus 3 is a bad idea especially with imaging, solus 3 doesn't pickup the agent within the agents tab when deploying sims as it still looks for the old address when it last time was on.

 

It only take 2 minutes to install solus 3 and 10mins max for sims

[dapaulio]

It doesn't work. Tried it before. Just easier to deploy within s3 and I have never had any issues with any of my client agents

[sturgeo]

For those struggling with the exported installer this is how i got it to work:

 

Create a batch file with the following:

 

start /wait xcopy "\\fileserver\packageshare\SOLUS3\Installer" "C:\SolusInstallerLocation" /y

cd C:\SolusInstallerLocation

start /wait AgentInstaller.js "agent_installer.log" "net.tcp://localhost:52966" "net.tcp://simserver:52965" "Solus3.Keys.DeploymentService.Public.xml" "SOLUS3AgentInstaller_x86.msi" "SOLUS3AgentInstaller_x64.msi"

 

The Installer folder contains all of the exported files and the batch file is deployed via Burconix Management Tools