Scribd
Upload
25 views

Penyebab Tidak Efisiennya Pengelolaan Thinclient: Hardware System

The document discusses some of the inefficiencies in thin client management including limited hardware types, outdated devices, limited free tools with more full-featured tools requiring payment, and ineffective patch management processes. It also mentions challenges with support including uneven knowledge and experience across locations, geographic distances between support areas, and an imbalance between the number of thin clients and support staff.

Uploaded by

bachank
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
25 views

Penyebab Tidak Efisiennya Pengelolaan Thinclient: Hardware System

The document discusses some of the inefficiencies in thin client management including limited hardware types, outdated devices, limited free tools with more full-featured tools requiring payment, and ineffective patch management processes. It also mentions challenges with support including uneven knowledge and experience across locations, geographic distances between support areas, and an imbalance between the number of thin clients and support staff.

Uploaded by

bachank
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Penyebab Tidak Efisiennya Pengelolaan ThinClient

X1 Hardware X2 System

Tools Imaging
ThinClient Update patch Free Tools
Type Terbatas
Device
Tools Support
USB Tools
Obsolete Massive
Pay Tools

Tidak Efektifnya
Proses
Patch management
Rasio Handling FS : 7BA
ThinClient
SLA Agreement

Resource IT Lokasi Geografis


Support cabang

Knowledge & Experience Jarak Area Support


ITSupport Belum Merata

X3 People
X4 Environment
2016 2017
Oct Nov Dec Jan Feb Mar Apr May Jun Jul

Jan 1 W2
- Scripting Apr W1
Early Start 1st Stage 1 - Testing on Deployment
- Scripting month (1 life Lab
- Testing on Lab cycle, until
Area Tier 2 &
closing) at 1 Feb W1 Apr W1 3
branch 1st Stage 1 month Create Template
(1 life cycle, until Image TC May W4
closing) at 1 branch End Project
Hand Over To
Apr W2 operation
2nd Stage 1
Deliver Image/ tools
month (1 life
cycle, until
closing) at 2- Apr W4
Jan 2 W1 Deployme
3 branch
Start Project nt Image
- Analyze Requirement Area tier 1
Apr W3
- Scenario Design Deployme
nt Image
Area tier 1

You might also like