<div>
Just like XP. With 15 workstations I wonder how they have managed to avoid any connection problems up to now.<br />
Thanks.
</div>


<div>
<div class="content wysiwyg-content">
Hi,<br />
A couple of months ago I started working for a company running a Windows Server 2003 set up in workgroup configuration with 15 workstations connecting to various shared folders. I have advised them that this is an administrative headache that will need to be dealt with at some point. <br />
<br />
There have been a number of things that have come up that I have had to learn how to deal with (versus a domain setting). A new question came up this morning. I was wondering how many concurrent connections we can support, so I went to the Licensing dialogue in the Control Panel. It says the licensing mode is per server, and the number of concurrent connections is 9999. However the licensing service is not running. So is licensing not a factor in this situation? And how many concurrent connections can we have?<br />
<br />
Thanks,<br />
Bill
</div>
</div>


Hi,
A couple of months ago I started working for a company running a Windows Server 2003 set up in workgroup configuration with 15 workstations connecting to various shared folders. I have advised them that this is an administrative headache that will need to be dealt with at some point. 

There have been a number of things that have come up that I have had to learn how to deal with (versus a domain setting). A new question came up this morning. I was wondering how many concurrent connections we can support, so I went to the Licensing dialogue in the Control Panel. It says the licensing mode is per server, and the number of concurrent connections is 9999. However the licensing service is not running. So is licensing not a factor in this situation? And how many concurrent connections can we have?

Thanks,
Bill

Windows Server workgroup setup

A server is a computer program or a machine that waits for requests from other machines or software (clients) and responds to them. This architecture is called the client–server model. The clients may run on the same computer or may connect to the server over a network. The purpose of a server is to share data or hardware and software resources among clients. Typical computing servers are database servers, file servers, mail servers, print servers, web servers, game servers, and application servers.

Server Software

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.

Network Management

The Windows operating systems have distinct methodologies for designing and implementing networks, and have specific systems to accomplish various networking processes, such as Exchange for email, Sharepoint for shared files and programs, and IIS for delivery of web pages. Microsoft also produces server technologies for networked database use, security and virtualization.