Common Implementation Risks to Consider

Discussion created by James.Dalley on Jun 29, 2018
Latest reply on Aug 21, 2019 by GMSS

Having now successfully managed over 300 implementation projects for Snow License Manager, spanning across both versions 7 and 8, I wanted to take a moment to share the common risks associated to an implementation project.


I have outlined six common risks below that are pertinent for the implementation of Snow License Manager and should be considered during project initiation and planning. As standard, a Snow Project Manager would work with customers and partners alike to implement an effective risk mitigation strategy for these items to ensure success.


1. Network Connectivity and Firewall Rules  Connectivity will be crucial for the Snow License Manager solution and this should be appropriately planned with the network management team or potentially outsource(s). When planning the implementation, appropriate ports should be carefully selected to ensure successful communication across the entire estate. Commonly, ports 80, 8080 and 443 are used but the system can be configured to use other ports. There is also the option to use either HTTP or HTTPS traffic providing appropriate certificates are provided.

2. SQL SA Account (in Mixed Mode) Requirement  To complete the installation of Snow License Manager, a temporary SQL SA account running in Mixed Mode is mandatory. This requirement can make a Database Administrator (DBA) feel uneasy. The key thing to note is the SA account is only temporary but is mandatory for the installation. Should this be a show stopper, we would recommend creating the databases (through the installation media) into an isolated SQL server and then completing a database move. However, this approach is more time consuming and may have a commercial impact to a fixed price installation.

3. Anti-Virus Software Potential Conflicting  It is not uncommon for Anti-Virus to cause complications for software that is installed. After all, it's purpose is to stop unauthorised applications running on the estate it is protecting. As such, please ensure that you add all required exceptions into your Anti-Virus software to mitigate this risk.

4. Deployment Method and Timeline  After implementation, the next key activity is to ensure high coverage of your IT estate within Snow. We always recommend our Snow Inventory Agent which is deployment agnostic. As such, customers/partners can leverage common deployment tools or approaches such as SCCM, Group Policy, Puppet, Satellite, Putty, Scripting or even manual installation. The time required to ensure full coverage should not be underestimated and careful planning should be completed with the required deployment teams.

5. System Configuration – The initial system configuration should be agreed upfront to ensure all reporting requirements and SAM ambitions are met. This includes but it is not limited to creation of an appropriate Organisation Structure (OU), agreeing reporting currencies and defining user access.

6. Resource Availability  It is critical that the different contributing resources are available at the appropriate times to avoid delays. This can be mitigated through the creation of a project plan which is agreed by all contributing stakeholders.


Hopefully this content helps to prepare for future implementation projects and i'm happy to take any questions or comments on this article.


Thank you for taking time to read this content.


James Dalley
Snow Software
Head of Technical Delivery UKIMEA