Re: SMS site server HDD allocation

From: BDerr (user_at_example.net)
Date: 10/27/04 

Date: Wed, 27 Oct 2004 08:48:56 -0400

Fahad:

A lot of this will depend on several factors, broken into hardware and
SMS settings:

You didn't say how much RAM, Processes or processor speed you had
available. Keep in mind that the SMS server is a database server.
However, looking at the server specs, if you had a dual proc machine
with 1GB ram, you should be able to support 2000+ clients. However,
when it comes to software distribution, the amount of software
distribution will need to be factored in. Typically you would have
multiple distribution points set up for redundancy and a simple load
balancing scheme, to prevent one server from getting overtaxed.

With what I see, what you have should work, but monitor performance, and
it would be best to set up multiple distribution point servers though.
You didn't mention if your site had any slow WAN links, as that can
cause issues as well.

Ben

Fahad wrote:
> I have a 380 G3, how many users can I load on it without off-loading any of
> the components. 1000, 2000, 3000 etc...? I want all the site roles to be on
> the same server including the site database.
>
> "BDerr" wrote:
>
>
>>Fahad wrote:
>>
>>A lot of this depends on how big your site will be, where the site
>>system roles will be placed, where the SQL database will be, etc.
>>Typically, for performance, you would want to split the SQL database and
>>Logs onto different drives if possible. Definetly keep the OS on a
>>separate drive if possible. If you have a hardware RAID controller, a
>>RAID 1 or RAID 5 will be good.
>>
>>For more info, read the Capacity Planner guide here:
>>http://www.microsoft.com/downloads/details.aspx?familyid=009e0c30-bded-4b95-a8f9-06037de85c57&displaylang=en
>>
>>The Client Installation Wizard is used to remotely install, or push, the
>> SMS 2003 client to a target system or collection, without needing to
>>go and run the client setup program on that system.
>>
>>If you are, and you should be, using Advanced Security, all the SMS 2003
>>related services will use the local system context for their functions.
>> If you have legacy clients, you will need to specify Client
>>Connection accounts to allow the clients to connect and write to the
>>caps. These accounts should be just normal user accounts (members of
>>domain users), and you should have at least 2, preferably 3.
>>You will need to specify an account for the remote installation, and
>>that account needs to have administrator priveleges on the target systems.
>>
>>For SMS 2003 Security, read the guide here:
>>http://www.microsoft.com/downloads/details.aspx?familyid=3d81b520-a203-4376-a72d-fd34a6c4a44c
>>
>>And as always, the Concepts, Planning and Deployment guide has a lot of
>>good info as well:
>>http://www.microsoft.com/downloads/details.aspx?FamilyId=784838B3-34E0-4122-B3E2-17C5B4EEF8F4&displaylang=en
>>
>>
>>
>>
>>>when setting up site server, how should I configuire and allocate the HDD. I
>>>have a 380, should I just have one partition and throw everthing on it, such
>>>as sms files, site database, dist point etc...?
>>>
>>>What is client installation wizard, how is it beneficial?
>>>
>>>What security accounts do I need for SMS 2003 advance client, service
>>>account and connection account, what rights should these accounts have and
>>>where in SMS do I specify these accounts?
>>

Relevant Pages

  • Re: After reinstallation
    ... If you manually install the client and open the system manager in control ... See Ccm.log on site server ... SMS Active Directory System Group Discovery Agent reported errors for 3 ... The MP installation was succesful, ...
    (microsoft.public.sms.setup)
  • Re: Adv Client with Workgroup Computers
    ... I was trying to use the SMS tools from the SMS server to initiate harware ... Inv for example the account is a domain account but the Client PC is in a ... Is there a procedure for installing the ADV client localy on a workgroup ... I have manually added to the WINS server. ...
    (microsoft.public.sms.admin)
  • Re: After reinstallation
    ... I guess what you say is that my server is running fine, but I should not expect client push to work. ... SMS Active Directory System Group Discovery Agent reported errors for 3 ... "Todd Hemsell" wrote: ...
    (microsoft.public.sms.setup)
  • Re: 4912: Cannot update the already existing object. Need some he
    ... Also, as far as the client pointing to the wrong server, you should use SMS ... SP3 client through a logon batch file. ...
    (microsoft.public.sms.admin)
  • Re: How to set up DCOM properly to allow server and client connect remotely
    ... their accounts if said accounts have the same username ... I need to know how to set up DCOM properly so the OPC server and client ... local user ...
    (microsoft.public.win32.programmer.ole)
Quantcast