<div>
*Definately* a domain. It gives you a common logon, security, and administrative context.<br />
<br />
It is relatively easy if you do a little research and are prepared before you begin the operation.
</div>


<div>
A domain will make things easier for administration purposes.
</div>


<div>
Domain all the way -<br />
Centralization of all network functions security, shares, permissions, email....<br />

</div>


<div>
Ok, thanks guys. I thought you would say that.<br />
<br />
Now, questions.... (most probably there will be more questions) :)<br />
<br />
What is the best way to make the transition painfully? I mean, current workgroup must be available for file sharing while I am preparing the transition. So I first need to know all the things I will need to know/understand so I can make this work.<br />
<br />
What will be the order of the steps that should be done?
</div>


<div>
Well, of course I will first do this in test environment first, as a matter of fact, I already have 3 PC's at home, and on one I have started installed Win 2003 enterprise today (now installing drivers).<br />
<br />
Consultants in my area for the windows server - there aren't any. :) its a small city and those few metworks we have were done by people 150 km away.<br />
<br />
Now, one thing I need to know: since server PC is usually without a monitor attached to it, I should also try to setup this server from a client, right? what approaches do you use when you setup a server? RDC? or something else? <br />
<br />
And yes, there is only one windows 2003 in this network, and it is both DC &amp;&nbsp;file server.
</div>


<div>
I would use Remote Desktop.<br />
You can use other 3rd party apps as well, such as VNC (free).
</div>


<div>
Just one thing we didnt clarify: can I have both workgroup and domain working parallel, so if there would be some problems, then I could switch those users to workgroup until I resolve the problem? Or this is not possible?
</div>


<div>
Sure there is no issues running them side by side. &nbsp;As leew pointed out get the domain rolling and then have a test machine join the domain and further test.<br />
Once comfortable then join a machine and test and if things continue to go well move another over and so on....
</div>


<div>
ryansoto, just to be sure, when I meant parallel, I mean on the same PC - there is only one server, and at the moment it is used as a file server in a workgroup (with win 2003 installed on it). If I install AD on it, it will then become a part of a domain.<br />
<br />
In this case, will other users that are still part of the workgroup, be able to use their resources on this servier, even if it is now part of the domain?
</div>


<div>
You will be able to but accessing it will be a litle more difficult
</div>


<div>
hello ryansoto, I have installed AD on the server, and when trying to log from other machine, under microsoft windows network I have both workgroup name and domain name. When I select domain name, I am presented with the server PC. Double clicking it I an prompted for user name and password. When I supply them I am able to browse the shares on the server PC.<br />
<br />
What difficulties where you referring to. Is there something else I need to be aware of?
</div>


<div>
What ryansoto meant is that it is easier to share resources when everybody is in the domain, than from a workgroup computer in a mixed mode configuration.<br />
<br />
The computer you mentioned in your last post, seems to be joined to the domain, so it is the normal behavior.
</div>


<div>
What I meant was, it was EASY to access shares on a PC that has become a part of the domain (the only member so far). I didnt came up to any difficulties. Should I expect some later?
</div>


<div>
the other machine was still part of the old group.
</div>


<div>
<div class="content wysiwyg-content">
I have the opportunity to start maintaining a IBM server with windows 2003 server and about 40 clients. At the moment network is set as a workgroup and server is used as a file server and there is a backup software installed on it.<br />
<br />
What I was thinking is maybe to try to learn to work on a domain, so this opportunity is the unique one. First question would be: how would oyu organize this network: as a workgroup or as a domain, since it is at the moment only used for file sharing and for backup purposes.<br />
<br />
Based on your answer I will ask some more questions.<br />
<br />
Thanks,<br />
Goran
</div>
</div>


I have the opportunity to start maintaining a IBM server with windows 2003 server and about 40 clients. At the moment network is set as a workgroup and server is used as a file server and there is a backup software installed on it.

What I was thinking is maybe to try to learn to work on a domain, so this opportunity is the unique one. First question would be: how would oyu organize this network: as a workgroup or as a domain, since it is at the moment only used for file sharing and for backup purposes.

Based on your answer I will ask some more questions.

Thanks,
Goran

Transition from workgroup to domain

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

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.