Skip to tutorial content
Rate module Not yet rated

Planning Environments: Dev, Test and Production

4 min read
On this page

In this lesson, you will learn:

  • Why Discovery is different across instances
  • What each SNWR instance scans
  • How changes move

🔁 Quick look back: Last time: Designing CMDB and Identification Decisions. You learned how SNWR decided classes, identification rules and field ownership.

1 The Problem: Dev Can’t Scan Production Networks

In ITSM, you built on snwrdev and moved it to snwr. Discovery is different:

  • A MID Server talks to one instance only.
  • Scanning all of SNWR from dev would put production data in dev.
  • Credentials shouldn’t be copied between instances.

🎯 The problem: Dev can’t just scan SNWR’s production networks.

👉 The fix: Give each instance its own MID Server and a limited range.

Four instances and what each scans.
Figure 1. What each SNWR instance does in Clear View (DD-D07).

2 What each instance does

  • snwrdev: build and try settings on a small lab range.
  • snwrtest: pilot on 30 real servers and UAT.
  • snwrstage: rehearse moving the configuration.
  • snwr: scan everything, on schedule.

💡 Good to know: Need a refresher? See Fundamentals › ServiceNow Instance › Instance Types & Release Names for instance types.

3 What moves and what doesn’t

Configuration like patterns and rules moves between instances. MID Servers, credentials and most schedules are set up on each instance. You’ll plan this in detail in Production Rollout.

4 Project Clear View: How We Implemented It

📍 Situation: The team assumed Discovery works like ITSM across instances.

🧭 Decision: Give each instance its own role, range and MID Server.

🛠️ Steps we took:

  1. Chose a small SNWR Lab range for snwrdev.
  2. Chose a 30-server pilot range for snwrtest.
  3. Kept snwrstage for rehearsal only.
  4. Wrote DD-D07.

✅ What we verified:

  • Riya and Ravi agreed the ranges.
  • No instance except snwr scans all of SNWR.

📁 Evidence: DD-D07 in the design document.

5 Quick recap

  • A MID Server serves one instance.
  • Dev scans a lab range. Test scans a pilot.
  • Only production scans everything.
  • Configuration moves; MID Servers and credentials are set up per instance.

6 Check yourself

Think of your answer first. Then tap to check.

1 Why doesn’t snwrdev scan all of SNWR? Show answer

It would put production data in dev, and dev isn’t the place for it.

2 What does snwrtest scan? Show answer

The 30-server pilot range.

3 Name one thing set up separately on each instance. Show answer

MID Servers, credentials or most schedules.

Nice work! Each SNWR instance has a clear role. 🎉
Next up: The Design Review and Sign-Off

Was this lesson helpful?

Have a question or doubt?

Ask here and get help from instructors and fellow learners.

0 / 300

Only logged-in learners can post.