Otto Metsähukala - How to Implement Miradore to 10,000 Devices in 2 Weeks

How to Implement Miradore to 10,000 devices in 2 Weeks

Otto Metsähukala

Senior Technical Engineer, Miradore Ltd

How to Implement Miradore to 10,000 devices in 2 Weeks

Implementation in general

Case example

Summary

Miradore Management Suite

Implementation in general

Management Suite infrastructure example

Miradore server Miradore client

HTTPS (TCP 443)

Wakeup (TCP 32227)

MS SQL serverMiradore masterinstallation point

Domain controller

Miradore clientdeployer

AD connector

Workstation

Miradore clientMiradore

installation point

RPC (TCP 135)NetBIOS (TCP 139)SMB (TCP 445)

RPC (TCP 135)NetBIOS (TCP 139)SMB (TCP 445)

HTTPS (TCP 443)

Wakeup (TCP 32227)

Internet

+ Patch managerHTTP (TCP 80)HTTPS (TCP 443)

Remote controlserver

Endpointbackup server

Miradore remotecontrol client

Miradore remotecontrol ADMIN client

HTTPS (TCP 443)

TCP 10001TCP 10001

Miradore Endpointbackup client

HTTPS (TCP 443)HTTPS (TCP 443)

Asset management

SW & OS deployment

Patch management

Remote control

Endpoint backup

Management Suite implementation process

1Initiation

2Preparations

3Installations

4Implementation

5Closing

Management Suite implementation process

• Scoping decisions

• Platforms

• Features

• Coverage

• Integrations & data import

• Service architecture decisions

• Delivery model

• Rollout decisions

• Definition of done

• Roles

• Schedule

1Initiation

2Preparations

3Installations

4Implementation

5Closing

Management Suite implementation process

• Basic information

• Number of:

• Locations

• Devices

• Users

• Operative decisions

• Client deployment method

• Installation points (how many & where?)

• Connectors

• Delivery capacity

• Miradore server

• Database server

• Connectivity

• Connectors

1Initiation

2Preparations

3Installations

4Implementation

5Closing

Management Suite implementation process

• Infrastructure verifications

• Server capacity

• Connectivity

• Installations

• Instance setup

• Permissions

• Basic settings

• Connectors

• Client deployment

• Testing

• Connectors

• Client deployment

1Initiation

2Preparations

3Installations

4Implementation

5Closing

Management Suite implementation process

• Asset management

• Client deployment

• Configuring settings

• OS & SW deployment

• Installation point setup

• Configuration

• Software asset management

• Identifying software

• Creating license pools

• Endpoint backup

• Endpoint backup server setup

• Defining backup jobs

• Patch management

• Setting up Patch manager

• Creating asset groups

• Creating automatic approval rules

• Remote control

• Install server & clients

• Configuration

1Initiation

2Preparations

3Installations

4Implementation

5Closing

Management Suite implementation process

• Handover to production

• Server hosting

• Support

• Aftercare activities

• Tasks to be done after the project

• Sign-off

• Customer representative closes theproject if ”Definition of done” is met

1Initiation

2Preparations

3Installations

4Implementation

5Closing

Engineering company in Asia

Case example

Fast facts: Engineering company in Asia

Employees19,000

Revenue1,3 B€ (2016 fiscal)

Locations10 business units, 20 factories, 50 sales offices, 10 centres of competence and 10 R&D centres

Background

• 30+ days delivery of computer after request

• Hard to address costs to proper business units due to unreliable inventory

• Lost devices due to lack of asset tracking

• Inefficient use of resources, over/underpowered machines

• Hardware components changed by end users

• Inability to know where devices are

• Manual wall to wall asset discovery

Management Suite solution

• Scoping decisions

• Platforms: Windows only

• Features: HW asset mgmt

• Coverage: Single country

• Integrations & data import: AD, HR data sheet, OEM warranty

• Service architecture decisions

• Servers hosted on end customer’svirtual host

• Rollout decisions

• Definition of done: HW asset mgmtreports in place

• Roles: 1 technical resource fromService provider + 1 Miradore engineer

• Schedule: 10 days for Installations & Implementation

1Initiation

2Preparations

3Installations

4Implementation

5Closing

Management Suite solution

• Basic information

• Number of:

• Locations: ~100

• Devices: 10,000

• Users: 19,000

• Operative decisions

• Client deployment method: 3rd party sw deployment tool

• Connectors: AD (x 5)

• Delivery capacity

• 2 virtual machines and networkconnectivity ordered

1Initiation

2Preparations

3Installations

4Implementation

5Closing

Management Suite solution

Active directory

Manufacturerwarranty

HR Datasheet

Client deployment

Users and computersCustom attributes

SubnetsHW inventories

Change log

Assets

Locations

Reporting

1Initiation

2Preparations

3Installations

4Implementation

5Closing

10 days

Management Suite implementation process

• Handover to production

• Aftercare activities

• Training the Asset manager

• Sign-off

1Initiation

2Preparations

3Installations

4Implementation

5Closing

Challenges during the implementation

• Server software issues (preconfigured IIS)

• Virtual machine issues

• AD, subnet and location information wasnot prepared beforehand and getting theinformation was slow

• Using end customer’s own software deployment tools for Miradore clientdeployment

• Internet connectivity issues

Summary

10 days

Implementation process& template

Smart infrastructure

2 technical engineers Hardware assetmanagement

10,000 clientsdeployed

Implementation in general

Case example