Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Download
Standard view
Full view
of .
Look up keyword
Like this
1Activity
0 of .
Results for:
No results containing your search query
P. 1
Symantec Management Platform at BOP Polytechnic

Symantec Management Platform at BOP Polytechnic

Ratings:
(0)
|Views: 16|Likes:
Published by Sean Liddall

More info:

Published by: Sean Liddall on Jan 10, 2012
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOCX, PDF, TXT or read online from Scribd
See more
See less

11/15/2013

pdf

text

original

 
Symantec Management Platform at BOP Polytechnic
Background
BOP Polytechnic currently utilises Symantec Management Platform with the following modulesincorporated and licensed:
y
 
Software Management Solution
y
 
I
nventory Solution
y
 
I
nventory for Network Devices
y
 
PCAnywhere
y
 
R
eal-Time System Manager
y
 
Deployment Solution
y
 
Patch Management Solution Windows
y
 
Patch Management Solution Mac
y
 
Patch Management Solution LinuxWe have 875 device licenses for the above with the exception of 
R
eal-Time System Manager of which we are licensed for 10 devices. The infrastructure resides on two virtual servers running MSWindows Server 2003. Notification Server runs the software management, patch management andinventory solutions, while Deployment Server manages the deployment of Windows XP SP3.Notification Server by default is also a Task Server and OOB management server.
 
 With well over 1000 different devices incorporating 800 PCs, 100 Macs and 150 mobile devices, therequirement to effectively and efficiently manage these is paramount to the day to day functioningof the Polytechnic. We currently manage around 670 of these devices through SMP. These areprimarily student computers and exclude Macs and mobile devices. This may change in future asrequirements change.Software delivery is done via Microsofts App-V Server 4.5 and MS App-V client 4.6. Virtualisation of software is the best and most efficient way of delivering software to lab environments and requiresvery little interaction from the rest of Customer Services. Whilst this has proven to be effective thusfar, other technologies within the SMP framework will increase efficiency and stability. Despite this,there are still certain applications which must be installed on the base image. These include :
y
 
MS Office
y
 
J
ava runtimes
y
 
Agents (Virtualisation, Desktop, Deployment, Patch Management)
y
 
Drivers for hardware / software
y
 
Antivirus
y
 
Multimedia packages
y
 
Visual Studio runtimes and redistributablesCurrently, an Access database is used to hold licensing and ownership details. There is also acentralised licensing server model in place which holds details for the following :
y
 
PASW 16 - 19
y
 
Solidworks
y
 
Minitab
y
 
Lectra
y
 
Citrix
y
 
E
dgeCAM
y
 
Typequick
I
deally a mechanism to manage and control all licensing  from MS products to MYOB  is required.SMP 7.1 has a module available for asset management including software licensing. Building thisasset database up will enable us to generate and catalogue our software and services for publicationif required. See attached documentation for quotations as provided by Gen-
I
.
 
R
eports thus far are non-existent and we are not utilising the tools within SMP to its full capability.Version 7.1 introduces us to
I
T Analytics which is effectively drag and drop reporting for high levelreporting and overviews. The upgrade from 7.0  7.1 is a pre-requisite in this occurring.
R
emote management is done via PC Anywhere with newly SMPd machines.
E
xisting Ghostmachines utilise VNC. Whilst VNC is very good at what it does, PCAnywhere is quickly becoming theindustry standard for remote management. Within the polytechnic, the agent is deployed to eachdesktop at build time and properties set to enable remote access. Customer Services dekstops willrequire PCAnywhere to be installed. This can be deployed via SMP quickly and without fuss.Patch Management is done on an as required basis. Patches are pushed out to all machines with thePatch Management agent installed. As this is installed at build time, there should be no machinemissing out on any updates. Whilst this is an important part of machine health and maintenance,more time needs to be invested in Patch Management for it to be effective. Adobe updates aredone when they are recognised as being released. Microsoft updates are done on a monthly basis after testing of any patches that are deemed required, including but not limited to :
y
 
H
ardware updates
y
 
Security updates
y
 
Application updates

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->