␡
- 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
This chapter is from the book
This chapter is from the book
This chapter is from the book
1.7 Handling a High Rate of Office Moves
- Work with facilities to allocate only one move day each week. Develop a routine around this schedule.
- Establish a procedure and a form that will get you all the information you need about each person’s equipment, number of network and telephone connections, and special needs. Have SAs check out nonstandard equipment in advance and make notes.
- Connect and test network connections ahead of time.
- Have customers power down their machines before the move and put all cables, mice, keyboards, and other bits that might get lost into a marked box.
- Brainstorm all the ways that some of the work can be done by the people moving. Be careful to assess their skill level; maybe certain people shouldn’t do anything themselves.
- Have a moving company move the equipment, and have a designated SA move team do the unpacking, reconnecting, and testing. Take care in selecting the moving company.
- Train the helpdesk to check with customers who report problems to see whether they have just moved and didn’t have the problem before the move; then pass those requests to the move team rather than the usual escalation path.
- Formalize the process, limiting it to one day a week, doing the prep work, and having a move team makes it go more smoothly with less downtime for the customers and fewer move-related problems for the SAs to check out.