We have limited funds at my company and are getting ready to purchase a
Windows 2003 Server to be accessed by 35 users. I know we can put the DC,
DNS, and DHCP all on the same machine. However, I'd like to know what kinds
of problems we might run into by combining all these services. Also, if it's
recommended that they be separated (may not be an option for us though)
which services are more likely to play nice with each other?
If you need more information from me in order to answer this question,
please let me know what I've missed. Thanks in advance.
Pitfalls of Combining DC, DNS, DHCP ... We have limited funds at my company and are getting ready to purchase a ...Windows 2003 Server to be accessed by 35 users. ... (microsoft.public.windows.server.setup)
Re: Macs not used in business? ... This 25-person firm recently unplugged its traditional Windows server architecture to install a similar system from none other than Apple. ... The company considered upgrading its aging Windows XP terminal server but endured Microsoft sticker shock when it calculated the cost of deploying collaborative software: Chief Operating Officer Shani Magosky got a quote for $100,000. ... Twenty additional Windows Server 2008 TS CALs (User or Device, chosen at time of purchase) ... Whoops...misread the number of CALs in the TS package. ... (comp.sys.mac.advocacy)
Licensing Help ...purchase a Windows 2003 server and set is up for Teminal Services. ... new company has about 40-50 employess that will have to access our ... (microsoft.public.windows.terminal_services)
Is there a samba server for windows? ... then buy Windows for the ... >I don't mean set up a linux server and run a Samba ...>SMB server, and running an OSS server instead that is ... >you MUST purchase Windows Server to up the licenses, ... (microsoft.public.win2000.networking)
Need advice on purchasing licenses ... I was wondering someone can advise me what Windows 2003 ... Deploy brand new Windows 2003 Active directory on one server... what would be the best cost effective license purchase... (microsoft.public.windows.server.general)
