If you don't have a centralized server, you just have a bunch of standalone machines. If they happen to be on a LAN they can share resources like printers, NAS boxes etc.

Standalone machines can be managed individually. However, if you're interested in cloud management solutions you might want to look at the upcoming Windows InTune: http://www.youtube.com/watch?v=bzzjrlGxYKM

>Al,
>
>Thanks for your input. It was very helpful. Just to explain, here is my situation:
>
>The server for my client was used to house FoxPro data for a home grown application written back in 2000. Remote users used Remote Desktop connection to access the system while local users accessed the system via the LAN. I have since re-engineered this application in .NET and created a web application hosted on a server in the cloud. I also used the server for file sharing in the office, but now I want to put the users on Google Apps for Business, thereby giving them file sharing in the cloud. Anti-virus is handled at the front door via the SonicWall firewall.
>
>The server is reaching the end of its life (5+ years old), so the question is do I really need a new server. To me the answer is no as the only use it would have would be for centralized user control. I just wanted to see how anybody else handles computers on a network without a centralized server.
>
>Thanks again.
>
>>
>>If you want to retain centralized control of user accounts, you still need a domain controller computer. If you're looking to get rid of the computer altogether, you'll lose all shared/centrally managed functions. In that case yes, you should first remove the workstations from the domain, then accounts get managed on individual computers.
>>
>>If your current server is actually Small Business Server, you may find it is doing a lot of other stuff like centralized antivirus update management and reporting, centralized Windows/Microsoft update of itself and workstations via WSUS, print queues etc.
>>
>>While not recommended, in very small environments you could consider using the server as a workstation as well. Or, it could be set up as a host for remote sessions - again, not recommended for a domain controller but possible for small environments.

bzzjrlGxYKM