According to your reply to my message, I'd like to offer you an overview on how to setup a web application in a server computer so that all client computers in your company/organization can access the web application without a need to install in every computer.
This has a lot of advantages, the most important being data centralization.
Please keep in mind this is just an overview, and for every step mentioned you may need to read additional materials.
Assuming all your computers are in the same network...
1. Disregard your current approach of installing an ASP.Net application on every client computer. This is because installing that on every computer for every new version is gonna take you time -as you already know.
2. Get a server computer (it can be just any computer with Windows Professional or later if there are not going to be over 5 PCs connecting simultaneously, otherwise use Windows Server). Good RAM (4GB sounds right) and a big hard drive like 70+GB may be good enough for most web applications.
Most people believe server computers should be special somehow, but this is not true, any computer can act as a server; the decission to get more and more powerful computers to act as servers should depend on the amount of traffic you are expecting. What makes a server is the software that makes it stay "open" to requests from clients. In this case IIS is the software that will be expecting to catch client requests of your web application.
3. Install SQL Server and your application in the server computer.
At this point, it may be possible for the rest of the computers (the clients) to access the website/webapp via the IP address of the server computer, example, http://123.1.2.3 (the lack of a "www" means this is in an intranet, not in the actual WWW).
This way you'll only need 1 deployment anytime there is a change in your application.
4. Aftwerwards, if you need your clients to access the web application by a domain name (ex. "http://MyCompanyIntranet.us") you'll need to setup a DNS service, which is where all computers will go and be directed to the IP Address that belongs to the domain name so they can access by domain name instead of IP.
To set up a DNS, you do need Windows Server or any other operating system that has support for DNS service, an article on how to set up DNS with Windows Server:
http://technet.microsoft.com/en-us/library/cc725925.aspx[
^]
However seting up a DNS Server is not enough to have all computers referring to it. It is at the router level where you'll tell what IP Address should be accessed as a DNS Server. An example from Cisco:
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a00801da572.shtml[
^]
Best of luck!