Deploy SIMS via SCCM 2012 R2

[rob998]

Hello,

 

Can anyone give me a step by step for deploying SIMS via SCCM 2012 R2?

 

Thanks,

 

Rob

[CyberDrac]

I thought the whole purpose of SOLUS3 was that this wouldn't be required?

[rob998]

I've never used SOLUS3. At the moment I install it using a script? I would like to deploy it via SCCM.

[clareq]

I plan to deploy the solus3 agent as the last step in my task sequence, after the machine has been added to the domain, and then add the machine to the Solus 3 management console by searching for agent computers. Does anyone see a flaw in that plan?

[TheScarfedOne]

Here are the programs I use in my SCCM package. This is pointed at a folder containing the Setup executables and signature files.

 

[rob998]

Here are the programs I use in my SCCM package. This is pointed at a folder containing the Setup executables and signature files.

 

[ATTACH=CONFIG]25609[/ATTACH]

 

How do you copy the connect.ini files to the machine?

[TheScarfedOne]

How do you copy the connect.ini files to the machine?

 

Group policy

[FN-GM]

If your using Solus 2 have a look at this - SIMS .Net Install Script - Blogs - EduGeek.net

 

I thought the whole purpose of SOLUS3 was that this wouldn't be required?

 

If you re-image the machine, SIMS won't install automatically.

[Sam_Brown]

I do similar to @theSacredOne although use a batch file instead of calling each setup individually. Using the batch file also means I can copy the connect.ini and sims.ini at the same time

[tmcd35]

If you have an EES subscription then you have access to App-V. What we've done here is installed SIMS as normal on a virtual machine and have App-V monitor the install. It then creates a single package that can be sent out via App-V. Does need the App-V client on all machines though. That said, so far, it's the single best, easiest method of mass installing SIMS I've found. And new versions are pretty quick to install on clients using this method.

[Sam_Brown]

If you have an EES subscription then you have access to App-V. What we've done here is installed SIMS as normal on a virtual machine and have App-V monitor the install. It then creates a single package that can be sent out via App-V. Does need the App-V client on all machines though. That said, so far, it's the single best, easiest method of mass installing SIMS I've found. And new versions are pretty quick to install on clients using this method.

 

This is something I'm keen to do in the near future as well

 

Do you not also need licensing for MDOP as well as EES though? It's been a long time since I've looked at it so might be wrong.

[tmcd35]

This is something I'm keen to do in the near future as well

 

Do you not also need licensing for MDOP as well as EES though? It's been a long time since I've looked at it so might be wrong.

 

yes you do, I don't remember it being that expensive on top of the basic EES though. Must admit I clean forgot about the MDOP requirement. We're hopefully rolling out most of our application software out using it this summer.