Remove Orphaned Network Share After Server Migration

draft · network network-shareserver-migration

Generated by docuprocessor (prompt article/v3) · 2026-04-22 08:20

Source thread

thread_id: spaces/AAAA05BdS6s/threads/JWJ4otrAf30 · 4 msgs · first 2024-06-28 · participants: Tech ATech B

Tech A 2024-06-28 15:04

Was there a server migration at Dwight Hershman recently? I noticed that there are two computers with a network share pointing to "\\server," but it's not responding. The current running server is svr22, and I can't find the same path on it.

Tech A 2024-06-28 15:04

The path is this one

image/png image.png

**Windows Command Prompt — `net use` Output** Windows version **10.0.22631.3737** is displayed. The `net use` command shows a single mapped network drive: **Status: Disconnected**, **Local: T:**, **Remote: \\server\TiME**, **Network: Microsoft Windows Network**. The command completed successfully, and the session is set to remember new connections.

Tech B 2024-06-28 15:20

almost 2 months ago we migrated everything

Tech B 2024-06-28 15:20

that share should be dropped

---
title: "Remove Orphaned Network Share After Server Migration"
category: network
tags: ["network-share", "server-migration"]
source_thread_id: "spaces/AAAA05BdS6s/threads/JWJ4otrAf30"
source_space: "spaces/AAAA05BdS6s"
generated_at: "2026-04-22T08:20:47"
participants: ["Tech A", "Tech B"]
---

# Remove Orphaned Network Share After Server Migration

## Problem
After a server migration approximately two months prior, workstations retained mapped network drives pointing to the old server hostname "\\server". The mapped drive T: pointing to "\\server\TiME" shows as disconnected status since the old server is no longer accessible. The current server is now svr22, but the equivalent share path was not found on the new server.

## Resolution
1. Remove the orphaned network drive mapping using the command prompt:
   ```
   net use T: /delete
   ```
2. Verify the mapping is removed by running:
   ```
   net use
   ```
3. If the share is needed on the new server, locate the equivalent path on svr22 and create a new mapping to the correct server hostname.

The orphaned share should simply be dropped as it points to infrastructure that no longer exists.

## References
- Source discussion: `spaces/AAAA05BdS6s/threads/JWJ4otrAf30`
- Attachments: - ![image.png](../attachments/JWJ4otrAf30.8ALruloDhbI/image.png) — **Windows Command Prompt — `net use` Output**

Generated article

draft