Академический Документы
Профессиональный Документы
Культура Документы
Abstract
This document will describe how to deploy Office 2007 Professional using System Center
Configuration Manager 2007.
The information contained in this document represents the current view of 4sol Ltd
on the issues discussed as of the date of publication. Because 4sol must respond
to changing market conditions, it should not be interpreted to be a commitment on
the part of 4sol, and 4sol cannot guarantee the accuracy of any information
presented after the date of publication.
This document is for informational purposes only. 4SOL MAKES NO
WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION IN THIS
DOCUMENT.
Complying with all applicable copyright laws is the responsibility of the user.
Without limiting the rights under copyright, no part of this document may be
reproduced, stored in or introduced into a retrieval system, or transmitted in any
form or by any means (electronic, mechanical, photocopying, recording, or
otherwise), or for any purpose, without the express written permission of 4sol Ltd.
4sol may have patents, patent applications, trademarks, copyrights, or other
intellectual property rights covering subject matter in this document. Except as
expressly provided in any written license agreement from 4sol, the furnishing of
this document does not give you any license to these patents, trademarks,
copyrights, or other intellectual property.
The example companies, organizations, products, people and events depicted
herein are fictitious. No association with any real company, organization, product,
person or event is intended or should be inferred.
© 2006 4sol Ltd. All rights reserved.
The names of actual companies and products mentioned herein may be the
trademarks of their respective owners.
Microsoft Office 2007 will be released some time during the next 12 months. It would be
beneficial to know how to deploy it quickly and efficiently.
Ideally, all desktop applications will be virtualised using Softricity Desktop, offering new
deployment and management techniques. However, this is not an option for every organisation.
Microsoft will be releasing a successor to SMS 2003 and SMS 2003 R2 in 2007 called System
Center Configuration Manager 2007, formerly known as SMS V4. This document will describe a
likely scenario that administrators may face next year, i.e. how to deploy Microsoft Office
Professional 2007 using Microsoft SCCM 2007.
Microsoft SCCM 2007 is a solution for managing desktops, laptops, servers and Windows mobile
devices. It offers auditing, software management, reporting and security
configuration/management for the complete network.
Note: the process described in this document applies to all Microsoft Office desktop products, e.g.
Visio, Project, etc. This process is only valid for Volume License editions of the Microsoft Office
products.
You can specify where to install the Office product. You can also enter an organisation name.
Enter your volume license key. Make sure you have this correct or your installation will fail. You
must also accept the license agreement.
Modify User Settings enables you to pre-configure Microsoft Office Professional. It will be
important for early adopters of Microsoft Office 2007 to know that it saves in a new XML based
file format by default, e.g. a Word 2007 document uses .DOCX. This new format is incompatible
with previous versions of Microsoft Office. You may want to pre-configure Microsoft Office to
save as Office 97-2003 compatible format. This can be done here.
You can now add, edit or remove shortcuts for Microsoft Office.
We are now ready to build a package in SCCM 2007 from the files and folders in the package share.
Note how I have mimicked my folder configuration from the package share in the Packages and
Advertisements containers in the SCCM 2007 administration console.
The command line option is the actual command that will install Microsoft Office 2007. SETUP.EXE
can be typed or browsed for inside of the package. The full command, SETUP.EXE /ADMINFILE
STANDARD.MSP, will tell SETUP.EXE to perform a customised installation according to the
specifications I have put in the listed MSP file.
We can now specify under what conditions that Microsoft Office 2007 will be installed. For a new
deployment it doesn’t matter if a user is logged in or not. But for an upgrade, it would be best to
ensure that previous versions of Office are not running or else the installation of Microsoft Office
2007 may fail. The best way to accomplish this is to ensure that users are not logged in.
Complete the wizard. No further customisations will probably be required. The last tab does offer support
for installations onto servers that are monitored by MOM2005 or System Center Operations Manager 2007.
You can choose to disable agent monitoring of the host and raise an alert if the installation has failed. This
would be very useful to avoid noise and to get an alert if Terminal Servers or application servers will have
problems after a failed deployment.
SCCM 2007 offers a new type of distribution point called the Branch Distribution Point. It is
intended to be used in small branches. It doesn’t even require a secondary site server; it can be
installed on a Windows XP Professional computer. This would be limited to 10 simultaneous
connections due to Windows desktop operating system licensing limitations. A BDP should only
be used in small to medium sites. A secondary site server offers traffic optimisation for client
connections and reporting that cannot be obtained by using a BDP.
I have taken a short cut by navigating to the package program “Per-System Unattended”. I right
clicked on it and selected “Distribute – Software”. This launched a partially pre-populated wizard
for me to create an advertisement.
We now specify when the advertisement will be available for SCCM 2007 clients to access. This is
not the installation schedule. This is the date and time when SCCM 2007 clients will start to
download the policy and the source files for the package from the DP.
I like to have this happen well before the scheduled release date or installation date of the
software. This will enable all clients to pre-download the content and will even enable roaming
users to have the software installed even if they are away from the network on the installation
date.
4sol was founded by three directors with a wealth of experience in the IT and business consulting
arena. Helping to design and project manage for some of the world’s largest corporates has
provided them with a unique understanding of how to maximize return from any IT investment.
We offer a unique approach built around our own project management methodology utilizing our
bespoke project toolkit jumpstart. Based on the best practices of the Microsoft Solutions
Framework (MSF) and further enhanced by our experience in the deployment of infrastructure
based solutions, jumpstart can significantly reduce the timeframe and costs in developing
technology solutions.
All our consultants and engineers are fully qualified and accredited in their respective disciplines
allowing us to provide sound systems analysis and to recommend long term cost effective solutions.
4sol are committed to developing strong relationships with our clients, working in a partnership role
providing you with a trusted technology advisor.
Our People
Our team of experienced personnel applies innovative thinking to address both tactical and strategic
infrastructure requirements in order to identify the correct solution. At 4sol we know that our people
are the key to our success. Continuous certification exams and product training ensure that our skills
are at the forefront of our industry.
We invest in our people, and encourage an environment that promotes innovation, creativity and
personal development. Our peoples' technical expertise is combined with excellent project
management and problem solving skills as well as sound business knowledge of our chosen
markets.