␡
- 1.1 Building a Site from Scratch
- 1.2 Growing a Small Site
- 1.3 Going Global
- 1.4 Replacing Services
- 1.5 Moving a Data Center
- 1.6 Moving to/Opening a New Building
- 1.7 Handling a High Rate of Office Moves
- 1.8 Assessing a Site (Due Diligence)
- 1.9 Dealing with Mergers and Acquisitions
- 1.10 Coping with Frequent Machine Crashes
- 1.11 Surviving a Major Outage or Work Stoppage
- 1.12 What Tools Should Every SA Team Member Have?
- 1.13 Ensuring the Return of Tools
- 1.14 Why Document Systems and Procedures?
- 1.15 Why Document Policies?
- 1.16 Identifying the Fundamental Problems in the Environment
- 1.17 Getting More Money for Projects
- 1.18 Getting Projects Done
- 1.19 Keeping Customers Happy
- 1.20 Keeping Management Happy
- 1.21 Keeping SAs Happy
- 1.22 Keeping Systems from Being Too Slow
- 1.23 Coping with a Big Influx of Computers
- 1.24 Coping with a Big Influx of New Users
- 1.25 Coping with a Big Influx of New SAs
- 1.26 Handling a High SA Team Attrition Rate
- 1.27 Handling a High User-Base Attrition Rate
- 1.28 Being New to a Group
- 1.29 Being the New Manager of a Group
- 1.30 Looking for a New Job
- 1.31 Hiring Many New SAs Quickly
- 1.32 Increasing Total System Reliability
- 1.33 Decreasing Costs
- 1.34 Adding Features
- 1.35 Stopping the Hurt When Doing This
- 1.36 Building Customer Confidence
- 1.37 Building the Teams Self-Confidence
- 1.38 Improving the Teams Follow-Through
- 1.39 Handling an Unethical or Worrisome Request
- 1.40 My Dishwasher Leaves Spots on My Glasses
- 1.41 Protecting Your Job
- 1.42 Getting More Training
- 1.43 Setting Your Priorities
- 1.44 Getting All the Work Done
- 1.45 Avoiding Stress
- 1.46 What Should SAs Expect from Their Managers?
- 1.47 What Should SA Managers Expect from Their SAs?
- 1.48 What Should SA Managers Provide to Their Boss?
This chapter is from the book
1.43 Setting Your Priorities
- Depending on what stage you are in, certain infrastructure issues should be happening.
- Basic services, such as email, printing, remote access, and security, need to be there from the outset.
- Automation of common tasks, such as machine installations, configuration, maintenance, and account creation and deletion, should happen early; so should basic policies.
- Documentation should be written as things are implemented, or it will never happen.
- Build a software depot and deployment system.
- Monitor before you think about improvements and scaling, which are issues for a more mature site.
- Think about setting up a helpdesk—Section 13.1.1.
- Get more in touch with your customers to find out what their priorities are.
- Improve your trouble-ticket system—Chapter 13.
- Review the top 10 percent of the ticket generators—Section 13.2.1.
- Adopt better revision control of configuration files—Chapter 17, particularly Section 17.1.5.1.