- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2025 08:18 AM
Hello everyone,
I have a query regarding the installation of ServiceNow on-premises. Is it possible to set up a domain-separated ServiceNow instance on-premises? If yes, what are the typical hardware requirements for such a setup?
I would appreciate any insights, experiences, or suggestions.
Thank you!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2025 02:28 AM
The hardware specific recommendations are available on the support portal. You can off course start small and extend the system as you grow. We are currently running a 12 application node system on-prem with domain separation installed (for 12 years). We have about 4000 customer/vendor domains, so installing these plugins is no issue (everything is supported and works really smoothly). Required some effort at rollout that you plan and execute a domain model that will suite your needs.
With each upgrade we audit all critical components and data visibility before rolling out the changes to production. We have some end-user organisations that log on to our system and run their own data/process separated support processes on the on-prem instance. During the past 10 years only a few data visibility issues have been noticed and these have been fixed.
In overall maybe a more time/resource dependant when setting up the system and confirming with each upgrade that everything is fine, but other than that I would say that the domain separation plugin is one of the best working core features on the Servicenow platform. Nothing bad or sad to comment. 👍
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2025 02:28 AM
The hardware specific recommendations are available on the support portal. You can off course start small and extend the system as you grow. We are currently running a 12 application node system on-prem with domain separation installed (for 12 years). We have about 4000 customer/vendor domains, so installing these plugins is no issue (everything is supported and works really smoothly). Required some effort at rollout that you plan and execute a domain model that will suite your needs.
With each upgrade we audit all critical components and data visibility before rolling out the changes to production. We have some end-user organisations that log on to our system and run their own data/process separated support processes on the on-prem instance. During the past 10 years only a few data visibility issues have been noticed and these have been fixed.
In overall maybe a more time/resource dependant when setting up the system and confirming with each upgrade that everything is fine, but other than that I would say that the domain separation plugin is one of the best working core features on the Servicenow platform. Nothing bad or sad to comment. 👍
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2025 03:39 AM
Thank you!
I appreciate your insights and experience with running a domain-separated ServiceNow instance on-premises. It’s great to hear that it has been running smoothly for you over the years.
Would you be open to sharing some specifics about your implementation? I’d love to understand how you approached the initial setup, infrastructure planning, and any key challenges you faced. Also, how do you handle upgrades while ensuring domain data separation remains intact?
If possible, can we connect for a conversation? Let me know what works best for you. Thanks again!
