Google IT Support study materials
Google IT Support study resources

Four Gigabytes and a Month-End Close

Google IT Support · Put your knowledge to work in context.

All case studies

Four Gigabytes and a Month-End Close

A finance analyst's Windows 10 laptop (Core i5, 4 GB RAM, 5400 rpm hard drive) takes six minutes to boot and freezes constantly in Outlook and Excel. Task Manager shows disk at 100 percent and memory at 92 percent; the page file is thrashing. The drive has 40 GB free of 500 GB. Month-end close is in two days and the analyst expects to work 30 hours of overtime that week. No SSD purchase is approved this quarter. The only spares are 8 GB refurbished laptops with SSDs, but imaging plus migration is a four-hour job and must be scheduled around the analyst's work. The analyst refuses to lose 12 GB of local PST files and does not want to start over on a different machine.

1. What do you do today, and in what order? Explain why the 100 percent disk is not your real target.

Read the worked answer

The disk is a symptom; the 4 GB of RAM is the constraint. With 92 percent memory in use, Windows pages heavily to a slow mechanical disk, which is why the disk sits at 100 percent. Freeing disk space will not fix it. Buying an SSD would help, but the memory ceiling remains.

Today, in order:

  1. Reduce memory pressure immediately: trim startup programs, close background sync clients, cut Outlook's offline cache window (this also shrinks the local data footprint), limit browser tabs and extensions.
  2. Reduce disk contention: confirm the page file is system-managed and not manually capped, pause non-essential Windows Search indexing on the bulk folders, check for a pending update or a stuck background task, and scan for malware.
  3. Schedule the migration to the 8 GB SSD spare for tonight, with the analyst's agreement on a start time that does not overlap a deliverable. Four hours overnight is far cheaper than four days of lost productivity during close.
  4. Set a rollback plan: leave the original laptop intact and untouched until the analyst confirms Outlook, Excel, and the PST files work on the new machine.

Trade-off: doing quick wins and delaying migration means the analyst limps through close again. Doing only the migration without quick wins leaves a window of risk if the migration slips.

2. How do you handle the 12 GB of PST files and the analyst's refusal to change machines?

Read the worked answer

Treat the PSTs as data with a real risk, not as an obstacle. A 12 GB PST on a failing-feeling mechanical drive is one bad sector away from disappearing, and it is likely outside any server backup.

  • Copy first, verify second, cut over third. Copy the PSTs to a network share or external drive and confirm they open and match size before touching the source. Do not move them; copy them.
  • Explain the mechanism, not the policy. Tell the analyst that the freeze is memory exhaustion and paging, and that the new machine has twice the memory and a faster drive, so the same files will open faster on it. Show the numbers from Task Manager rather than asserting it.
  • Make the new machine feel identical: same Outlook profile name, same desktop layout, PSTs reattached, favorites and signature carried over, and the old laptop kept available for two working days as a fallback.
  • Address the real fear. 'I do not want to start over' usually means 'I am afraid something will be missing during the busiest week of my quarter.' Give a concrete rollback guarantee and a 15-minute check-in the morning after migration.

3. What do you recommend to your manager for this quarter, and what evidence supports it?

Read the worked answer

Recommendation: standardize finance laptops on 8 GB RAM minimum with SSDs, and stop issuing 4 GB mechanical-drive machines to anyone running Outlook and Excel all day.

Evidence to bring:

  • This analyst lost measurable hours per week to boot and freeze time during the highest-value week of the quarter.
  • Memory at 92 percent and sustained paging on a 5400 rpm drive is a configuration that cannot meet the workload, regardless of how well it is tuned.
  • Your team already owns 8 GB SSD spares, which means the fix is available in inventory but is being applied reactively and at overtime cost.
  • Count how many other machines in the fleet share this configuration; if the number is more than a handful, this is a fleet decision, not a one-off.

Also recommend the process fix: a minimum spec for finance roles, an agreed migration window before quarter-end rather than during it, and a documented PST handling procedure so the data question does not resurface every time.

What to avoid: presenting this as 'the user complained.' Present it as downtime cost, inventory you already own, and a repeatable spec decision.