Jump to content

Recommended Posts

Posted

Hi guys,

 

Just curious if anyone has had a positive experience with deploying SIMS into an Intune environment? Posting on behalf of a a friend who is struggling to deploy SIMS using Intune, as Solus is very reliant on AD (on-prem).

 

All of the new devices that are rolled out are AAD joined, no longer linked to on-prem AD, so getting SIMS out to the devices has been a painful experience.

 

Have any of you had similar issues or could perhaps point us in the right direction of an effective way to get SIMS out to these new devices?

 

Grateful for any help!

 

Best wishes,

A

  • 5 months later...
Posted
Did you manage to get anywhere with this, we also have comes across the same roadblock

 

I will also be looking this way in due course, hmm this could be a stickly point.

 

Can the devices access the Solus server > Extraction > SIMS folder and run the individual setups directly?

Posted

I've got this setup. It annoyingly requires an Intune app to be made every time there is a SIMS update though and definitely has its flaws. But essentially, have a Powershell script that installs SIMS update, then replaces the shortcut in the start menu to point directly to the Pulsar.exe. It also copies the connect.ini into the SIMS application folder if it is not already there. That connect.ini just points back to the SIMS SQL Server.

 

Then create an Intune app with the Microsoft tool and deploy it to staff laptops every time there's a SIMS update.

 

Point it to the Pulsar.exe file version for detection. Only problem can come is if the laptop is restarted during the update but after Pulsar version has changed.

Posted
You can 'cheat' if you copy the updates once download in Solus from \\solus3servername\Extraction\SIMS to S:\SIMS\Setups and run C:\Program Files (x86)\SIMS\SIMS .net\SIMSLoad.exe it will do the update instantly. The old chestnut of SIMS permissions but could be another workaround! I had to use this method for devices connected on IPv6 networks as SOLUS doesn't support IPv6!!
Posted

we install solus onto the laptops via the win32 method and then deploy to agents via solus.

has worked well for us except for upgrades which we are still figuring out.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...