You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currenly have a SnipeIT instance running a Windows Server 2012 installation on IIS. I have another department in our company that wants to use SnipeIT for asset tracking, but they want their own separate database/list of assets, and they don't want cross over with the department currently using SnipeIT.
What's the best practice for a scenario like this? I imagine spinning up another server with a SnipeIT Installation would be the easiest, but if I can prevent the overhead of another server that'd be nice.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We currenly have a SnipeIT instance running a Windows Server 2012 installation on IIS. I have another department in our company that wants to use SnipeIT for asset tracking, but they want their own separate database/list of assets, and they don't want cross over with the department currently using SnipeIT.
What's the best practice for a scenario like this? I imagine spinning up another server with a SnipeIT Installation would be the easiest, but if I can prevent the overhead of another server that'd be nice.
Beta Was this translation helpful? Give feedback.
All reactions