# Mapping network drive confusion

**URL:** <https://forum.inductiveautomation.com/t/mapping-network-drive-confusion/88338>\
**Category:** Ignition\
**Created:** [April 4, 2024, 11:28am UTC](https://forum.inductiveautomation.com/t/mapping-network-drive-confusion/88338 "2024-04-04T11:28:07Z")\
**Posts on this page:** 1\
**Showing post:** 32

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [April 24, 2024, 10:55pm UTC](https://forum.inductiveautomation.com/t/mapping-network-drive-confusion/88338/32 "2024-04-24T22:55:58Z")

</div>

Also be aware that if your target share is not available when Ignition is restarted, Ignition will take longer to start up, due to those retries. And if your target share ever disconnects, it won't reconnect until you restart the Ignition service.

Using the service wrapper's drive mapping ability is **not** fit for production use. Full stop.

---

_[View the full topic](https://forum.inductiveautomation.com/t/mapping-network-drive-confusion/88338)._