Portal User asked a question.
SIM Best Practice - What Server should it reside on?
Is there a best practice for which Server the SIM application should be on. That is, so it doesn't impact other SNOW processes and operations. Ours is currently on the SNOW Inventory Server.
Our SIM setup has 15 VMware connectors, 1 each SCCM, IBM BigFix, Azure, AWS, Zoom SaaS, Adobe, Office 365, and ServiceNow (Test and Dev). SIM for ServiceNow Prod is on another server since we are on Madrid for SN.
With all these connectors should it be on a Server of its own or OK where it is?
Hi Mark,
Your mileage may vary - I think the answer is going to be different depending on the connectors and your setup.
I have had a couple of situations where a particularly long running (or hung) connector has caused the machine to crash or become totally non-responsive.
We ended up having to schedule a reboot everynight at 11:59PM which seemed to work until the the Office365 connector was updated and we stopped rebooting it.
This is something we can tolerate/recover from on a service gateway - but I wouldn't be too happy if my Inventory Server was being crashed on a regular basis. I've learnt the hard way and would no longer use SIM on a critical system.
However I would add that if you VM statisfies the Snow Requirements and it is currently stable, then I probaby wouldn't change until there was a compelling need to do so.
Tom
Hi Mark - I tend to install it on either the Master Inventory server, or a service gateway. It's never caused any issues for me like Tom. As long as you schedule the aggregates to run a different times there shouldn't be any issue running all those connectors on the same SIM either.
Hi Mark,
Our SIM for Inventory connectors are located on Master Inventory server
The SIM for ServiceNow connector is located on SLM server, because in the past it run very long and we needed to use another SIM version