Link to home
Start Free TrialLog in
Avatar of stevendawson
stevendawson

asked on

What is the best way to add new PC to SBS 2003

Hi,

I am new to SBS and as such I am trying to understand everything and alos learn best practises as I go along. I'm quite used to peer to peer networks so Domains tend to strike a little fear into me as I am not always certain of the best option to take I have historically fallen back on my old bad habits rather than learn or figure out the best way.

So, I have spent many an hour installing, testing, uninstalling configuring and reconfiguring SBS2003 to get myself a very nice stable running server. So far everything seems to work exactly as I want it to and its time to add some PC's to the network and al of a sudden I am faced with several more dilemas as there seems to be a number of conflicting areas of information.

So, here I am in an ideal world with a new clean install of SBS up and running. All of my pc's which are about to join the network are new with clean installs of XP Pro and the network PC's contain nothing else yet (although I will want to install Office on each) The SBS Server has 2 network cards, one for WAN and one for LAN, exchange is running and mail is accessible via the web for the single test user account that I set up.

So the question is, What is the best way of adding these PC's and users?
Should I install office on the local machines first or does that make no difference.

Thanks

Steve

SOLUTION
Avatar of Zadkin
Zadkin

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of stevendawson
stevendawson

ASKER

Thanks for the speedy reply which threw up 3 more related questions.

So, do I need to install office on the local PC's first or is SBS going o install it for me?

I am now running the wizard to connect the first PC, it is suggesting a name which I am happy to accept. Is the connectcomputer wizard going to rename that PC as it joins the network then?

Also, in the wizard it is asking me "During client setup allow the selected applications to be modified" and "after setup is finished logoff the client computer" I read the more information but that is not at all clear. Which options should I choose.

Thanks

Steve
Correctly joining PCs to the SBS domain is the most important.  

But it is possible to do an Office 2003 install  centrally:
1 Do an administrative install of office 2003 on the server with "setup /a" on \Clientapps (Outlook 2003 is probably already there)
2 Server Console - Computers - Set Up Client Applications
3 Server Console - Computers - Assign Applications to client computers

"During client setup allow the selected applications to be modified" allows the user to decide on location and chosen packages when he logs in and the install starts.

"After setup is finished logoff the client computer" Allows the administrator to start up the install on the PC knowing that his session will be closed.
Hi,

Thanks for that. As I said this is all new to me so I would apprecaite a little more clarification. As I said, I am trying to understand what is best practice rather than just making it work. I know I can install office on all the network PC's and use connectcomputer but...


1. Is it best to install office on each PC or is it best to install it on the server and push the application in that way.

2. You said do an administrative install of office 2003 on the server with setup /a" on \Clientapps - I really don't understand how to do that. Do I simply create a folder for office 2003 in \Clientapps and copy the files? I notice that folder already contains office2003_SP1. Can you explain in more basic terms how I add an application to the server please.

Thanks

Steve
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hi again,

I don't want to appear rude but I am not sure you really answered my question, yes of course you are correct I have installed office hundreds of times on PC's but is that the best route that I should take in the future every time I set up SBS 2003 and have nice shiny new PC's on the network? (remember I am trying to learn best practice)

The way I figured it might work is that if office was on the server then autoupdate would download once and rollout to the network automatically?

You also said I can copy the whole CD of office to \clientapps but should the folder into which office is then placed have a specific foldername?

As for Q2 you seem to offer an option and then remove it by saying "But doing that is guru stuff." so should I ignore that as an option? I'm not sure I really followed it anyway.

Thanks

Steve
To learn,  see http://www.petri.co.il/office_system_2003_sp_slipstreaming.htm
but use rather C:\clientapps\Office2003 than   D:\Office2003
ASKER CERTIFIED SOLUTION
Avatar of Jeffrey Kane - TechSoEasy
Jeffrey Kane - TechSoEasy
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
P. S.  This is also a good article on how to add a PC to an SBS domain:  http://sbsurl.com/add

Jeff
TechSoEasy
Hi Jeff,

Thanks for your help and those articles were a big help. All installed exactly as you described but I do have one small question which is just clarification of an observation really.

On the SBS 2003 server I added a user as a mobile user then I ran the /connectcomputer and I allowed SBS to rename the local PC and all is fine. What I noticed though is that in the local PC - Users - that user is in the group "Debugger User" is that correct?

I increased the points for the extra question.

Thanks

Steve
No, it's not correct and I haven't found out why that happens yet.  It has something to do with MSDE or SQL I think, but it is a problem that needs to be corrected manually.  (It happens to me all the time but I've yet to figure out the consistency).

If you remove the user from the DeBugger Group and put him in the Local Administrators group, he'll end up back in the DeBugger if you don't delete that group... I've found no reason to keep the group so go ahead and delete it after moving the user to the local admins.

Jeff
TechSoEasy