Requiring MSI packages for SCCM deployments

  • 2
  • Idea
  • Updated 11 months ago
  • Implemented
I would like to see you guys provide .MSI builds of your Frontdesk application so that we can silently deploy the installs and updates to computers via products such as SCCM and the alike.

We find that we now have +10 devices that are in different locations around QLD and it becomes a very time consuming finding times to manually install the product.

Is this something that will be on your roadmap in 2018?
Photo of Alex McDonald

Alex McDonald

  • 2 Posts
  • 0 Reply Likes

Posted 11 months ago

  • 2
Photo of Heidi

Heidi

  • 18 Posts
  • 2 Reply Likes
Agreed. Because the update process is manual and time consuming we can only update once per year. We did our yearly update last week for 30+ computers for one clinic. There is another clinic yet to be done with a similar number of computers.
Photo of Timothy

Timothy, Business Care Manager

  • 761 Posts
  • 220 Reply Likes
Hi Alex. Currently, we do not support rollout installs using MSI packages. The reason for this is that there are limitations in relation to the functionality of an MSI package, such as checking for prerequisites on a machine and installing or updating other libraries, which need to be rolled out separately. Historically, our aim has been to provide a single installer to make it a more reliable process for the majority of users. We are open to feedback from other users as to whether an MSI rollout in an SCCM environment would be useful. It would require users to follow a set of instructions.
Photo of Heidi

Heidi

  • 18 Posts
  • 2 Reply Likes
I'll clarify that I'm a clinician not a IT Professional so my 'vote' relates to a general 'make the update process for large clinics less manual'. Our updates are completed by a university IT team not the end users.
Photo of Alex McDonald

Alex McDonald

  • 2 Posts
  • 0 Reply Likes
Thanks Timothy
I think for the sites that are wanting to use MSI packages for rollouts would have an understanding of installing prerequisites etc. 
Having our own IT department internally that can comfortable package and deploy software I don't think it would be an issue following a set of instructions to get it working.
I understand that these packages could cause some headaches for your other customers so maybe these MSI installation options can be provided on a 'request' basis and not made available for download via the website.
More than happy to work with the Smartsoft Team to test and deploy these kinds of things to get a process locked down for the future
Photo of Joel

Joel

  • 2 Posts
  • 1 Reply Like
Hi Timothy, I don't think any of us really care the exact file extension of the installer - the issue is being able to deploy in a silent and autonomous manner. Even if it remains the existing .exe just add a /q switch of something so we can run it without requiring any user input and so we can roll it out using whatever network management tools we use.
Photo of Tony Taddeo

Tony Taddeo, Managing Director

  • 76 Posts
  • 33 Reply Likes
Hi Guys

We are happy to consider a silent install that can be automated after some investigation. We have no technical issues creating MSI's or silent installers, however we don't fully understand the possible issues that may arise at this time.

The dev team is currently busy on some high priority matters at this time.  Look out for our response within the next month. 

Tony
Photo of Tony Taddeo

Tony Taddeo, Managing Director

  • 76 Posts
  • 33 Reply Likes
Hi Alex and Joel, you will be happy to know that we are currently investigating the creation of a MSI/silent installer to help our larger practices roll out Front Desk updates. Could you please contact us by opening a support case (link below) so that we can provide you an installer when it becomes available for testing.

https://www.smartsoft.com.au/support/

Tony