Implementing and Managing

[Kodiak]

I see most of the training courses are for 250 to 5000 user, are there any courses for small business at less then 100 users. Don't tell me "well if you learn for 5000 don't you think you could manage 100". Learning for 5000 throws in a lot of extra garbage I don't need to know. I would like to just setup small servers for up to 15 PC's.

[confus-ed]

Do pretty much what you just suggested on another thread & buy yourself a 5 'seat' licence, for say server 2003, & then 'play' a lot ?

Obviously you need some machines too to use to test matters with, but none of them need to be that powerful for 'testing/learning' - it's how I've learnt every server o/s 'enough' to be able to at least install them since NT 3.51.

[Ahcoraj]

What kinds of questions do you have? The MCSA cirriculum seems to fit well with my experience as a small business admin, without needing the exchange, sql...etc PM me if you'd like.....

[Kodiak]

Do pretty much what you just suggested on another thread & buy yourself a 5 'seat' licence, for say server 2003, & then 'play' a lot ?

Obviously you need some machines too to use to test matters with, but none of them need to be that powerful for 'testing/learning' - it's how I've learnt every server o/s 'enough' to be able to at least install them since NT 3.51.

I like that confused. I'm indeed doing just that. I have a Athlon 1400+ I'm working with and have it all working and just need to make it the domain Controller and change my winxp boxes over to a domain. I did find some good information here http://www.microsoft.com/technet/pro.../domcntrl.mspx I'm sure I could set up something for a business to but it's getting that first one behind you. I would like to learn about laying one out and setup of mainframe servers rather then a PC type servers but then again maybe a PC server would be enough since my concern is 15 pc's tops.

[Kodiak]

What kinds of questions do you have? The MCSA cirriculum seems to fit well with my experience as a small business admin, without needing the exchange, sql...etc PM me if you'd like.....

Basicly what I want to do is setup of the hardware and OS and admin to it for no more then 15 pc's. With you folks here and determination I have allready learned a great deal. User, groups and restrictions and are a simple matter. Switching the whole thing over to a domain is what I'm working on now. The link I posted above may provide this. Setting up ip addressing and getting the connection to work is what I'm shaddy on. Not sure where you even put it in 2003 to start. Once I get it figure out how then I need to figure out what is best for the company and there future growth. Won't take me long to learn just need someone to point a fingure here or there. Not the middle one.

[Kodiak]

Can the server be taken out off the workgroup and DHCP and Domain Controler setup be ran before emplemented into the network? Along with whatever else needs to be setup.

[confus-ed]

.. Setting up ip addressing and getting the connection to work is what I'm shaddy on..

Meh, M$ are shaddy on this !

As soon as you leave the world of a single machine setup, M$ magically assume that you understand how they mean certain words which are used much more widely with different meanings both in real life & by the rest of the computing world & can see the wood for the trees in their forest .. (if you already thought you knew what a 'domain' was try & figure out how you can have a collection of those ! I still can't reconcile M$'s meaning & the true definition !).

Noo put me straight on this dilema a while back, with the most sage advice (nicked form Nike) & advised me to 'just do it' & it does indeed make some more sense once you've perserved a bit, but you do come out the other end thinking that matters could definately get better put ..

So some resources on setup, as really I can't quite grasp just where you are stuck - How can I install Windows Server 2003 on my server?
Windows Server 2003 Setup Guide

[Kodiak]

Oh well right now I think I'm stuck in my mind more then anything. The advice of "just do it" may be the best of all. I use my pc constantly so I can't afford to have it down is one thing. I make my money off it in other words. So if I go fooling around and dig a hole I can't get out of I will end up loosing money. Time is also a factor. I'm getting very busy. If I'm not on my PC I'm working on someone elses and when I'm here I'm using this one. I may have to make me a tree here and setup a dummy network in another room. I have 3 spare PC's so thats no problem and the networking supplys. Problem is this also. I use my network to do work on customer pc's and do updating so I may need 2 seperate networks anyway. Is that possible? Setup a workgroup and a domain? Maybe not. Not sure my isp would give me another modem. I have verizon DSL. Maybe this just isn't going to work.

EDIT: Then again I suppose one could, once you have the knowhow, you could just have an IP set asside for that customers PC to be added to the domain to do the backups then reset it once done correct?

[Kodiak]

Well now here is a question, if I hook it up as follows in a line from ISP to end user like so.

ISP/MODEM/ROUTER/SERVER/SWITCH OR HUB/END USER sine it is before the server can I not just plug into the router and access the internet as a workgroup computer like usuall to get my updates for pc repairs?

EDIT: I love this work.

[confus-ed]

Yup .. in a workgroup, that's what you do.

If its in a domain then you want WSUS & that 'enterprise type stuff'.. or just download the patches invidiually if all else fails & apply the things mannually.

You are as bad as me though ! - so maybe you are getting at something else .. Are you concerned about not having a working machine still ?

[Kodiak]

I absolutely have to have a working machine. If it all can be done in a short time like on Saturday (a free one that is) then I would go fo it. I'm doing as much preperation as I can before hand as possible before the atempt. Another concern is to have some way of getting customer pcs completely updated with all patches and thats why I was wondering with the router on the isp side of the server if a guy could just hook up there and access the internet as normal or would the server see it and try and set an ip for it messing up that connection. Seems like I read something to that effect.

[Kodiak]

Well I have now set up a server and implemented it in a domain inviorment and all is well. I have found that no matter where you hook up another PC it will still get through to the internet for updates on the system and just won't be part of the domain so no worries there. So well on the wat to being able to install and admin to win2003. Thanks for your help.