--- This is a non-sequitur. This conclusion doesn't follow from logical reasoning.
Our policy is to set up the SIMS Host as a dedicated server and a
Setting up the server this way has several advantages:
• More effective and efficient support which can isolate and
establish whether a problem is caused by a network, a
client or a software issue.
--- You don't run client apps on a server. You're introducing extra complexity.
• Some legacy SIMS modules are 16-bit and will not run
on Windows Server 2008 R2 (64-bit) - which negates the
advantages of the workstation set up.
--- There are plenty of advantages to running 64 bit server and 64 bit SQL server, and plenty of disadvantages to running 32 bit server software. The SIMS client is indeed 32 bit, but the architecture of the underlying servers is opaque. A high performance back-end is better than a low performance back-end.
• SIMS itself is 32-bit, so there are no performance
enhancements gained by installing a 64-bit operating
--- This is an argument? Seriously?
• During upgrades it is sometimes required to access the
SIMS client application - this saves the need to move to
--- An earlier argument stated that running SIMS client on a server is a positive thing. Yet now running other software on a server is a negative thing?
• During support and upgrades, it is sometimes necessary
to reboot a server. If the server is used for other purposes
and running other software, this affects all users
(sometimes in the classroom) in addition to SIMS users.
--- Quite so. Which is why you don't install client software on a server. Logging in to the server and running the SIMS client will degrade the server performance.
• If the server is not dedicated to SIMS, performance may
be affected and conflicts can occur - making it more
difficult and time consuming to isolate issues.