RE: First Time Server Setup

From: Carsyn Gu [MSFT] (kshengu_at_online.microsoft.com)
Date: 12/24/04


Date: Fri, 24 Dec 2004 14:57:00 GMT

Hi Tufty,

Thanks for your posting.

Based on my understanding, you are running the environment is a workgroup
environment without domain. All the resource are shared on the workstations
in the workgroup and no domain level shares. What you want to do:

 

1. Backup workstations easily.

2. Make domain level sharing.

3. Control printer easily.

4. Make different users with different privileges on the file shares.

 

I think all this can be done if you make an AD domain.

 

1. We can make a schedule task on the main workstation. The schedule
task calls the NTBackup tool to backup the main workstation every day.

2. If all the client machines join the domain, we can set the file
shares on domain level with domain user ACLs. All the shared data can be
put on a file server and assign different domain users with different
permissions.

3. We can setup Printer server. All the printers are managed on the
server, so every clients/servers in the domain can share the printers.

4. We can easily make different users with different privileges on
shares in the domain.

 

What you need to do is just setup a Windows 2003 AD domain. You can follow
the guideline below:

 

http://www.microsoft.com/windowsserver2003/technologies/directory/activedire
ctory/default.mspx

 

Sincerely,
Carsyn Gu
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: First Time Server Setup
| thread-index: AcTo+8D1CCHmCe/0SjKVF5/CU1PjUQ==
| X-WBNR-Posting-Host: 81.134.168.244
| From: "=?Utf-8?B?VHVmdHk=?=" <Tufty@discussions.microsoft.com>
| Subject: First Time Server Setup
| Date: Thu, 23 Dec 2004 06:29:04 -0800
| Lines: 24
| Message-ID: <76537B48-4FF1-498A-8C70-15A19422C567@microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.windows.server.migration
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
| Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.windows.server.migration:16142
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| Hi,
|
| I'm shortly (timescale 1-2 weeks) going to be setting up a server for a
| local company. We've decided on using 2003 Server, as there's no previous
| server installed.
|
| Basically, up to now we've been using a mix of WindowsXP and Win98
| workstations, using workgroups to share information where necessary. This
is
| starting to get unwieldy, as we now have over 30 workstations - so
obviously,
| updates and backups are getting more difficult to do.
|
| Ideally we want to be able to back up all the systems from the main staff
| workstation, as simply and easily as possible. We also need to allow our
| users to be able to login and access their documents from anywhere in the
| building (which is the main driving factor for installing a server).
Ideally
| we'd like to be able to control printing from the main workstation also,
but
| as the printers are connected via parallel and USB rather than being
network
| printers, we don't mind so much about that.
|
| There's perhaps 10 different subprojects within our organisation, so my
| thought was to create a different subdomain/group within Active Directory
to
| allow them to stay separate on one level while sharing resources on the
other.
|
| Any suggestions on how/what to do to get this going?
|



Relevant Pages

  • Re: !!HELP!! Pulling my hair on this one. Printer problems. Really need some help on this.
    ... Yes Larry I have already moved them off of the SBS server and onto a high ... When the printers were connecte they did show as being offline. ... have workstations connected are plugged into the same. ...
    (microsoft.public.windows.server.sbs)
  • Re: !!HELP!! Pulling my hair on this one. Printer problems. Really need some help on this.
    ... Yes it is becoming a concerning issue with my SBS server. ... When the printers were connecte they did show as being offline. ... It can't be my hub because other wall jacks that have workstations ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Misconfigured?
    ... up one of the workstations via remote web connection, ... but why are you looking at the server rather than the workstation? ... (this will show you the DHCP lease info). ... The Netgear, or whatever you use as your gateway to get out to the Internet. ...
    (microsoft.public.windows.server.sbs)
  • Remote Networking Assistance Requested
    ... Server 1 and the one workstation HAVE to be a specific workgroup name. ... Server 2 and the associated 8 workstations HAVE to be a different specific ... The Router is a 3COM OfficeConnect Secure Router 3CR860-95. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: !!HELP!! Pulling my hair on this one. Printer problems. Really need some help on this.
    ... If the server tried to contact a printer and could not, say because of a sporadic hardware issue, it might report the printeras offline. ... I think that what I would do next would be to delete all the printers, then go into Server Properties and delete all the drivers. ... So I think for now if I can resolve the issue as to why I cannot remove and delete the print queues from my SBS server then I can try to reinstall from scratch without the existing print queues still in place. ... By centralizing the spooler you can control access, do "grouped" deployments, such as department/building/remote printer locations using group policy, upgrade a driver on the server and have all workstations get the new driver automatically, and...ultimately...usually a better troubleshooting experience when problems arise because you know the driver, the port, and don't have several workstations with different configurations floating out there. ...
    (microsoft.public.windows.server.sbs)