Client Management Suite

 View Only
  • 1.  Architecture Design for Large Company

    Posted Feb 18, 2011 05:11 PM

    For a company with more than 6000 computers, where the main office are more than 3000 computers.
    Office 2 more than 2000 computers with 90 MB of bandwidth..
    Office 3 more than 1000 computers with 18 MB of bandwidth.
    Office 4 more than 700 computers with 18 MB of bandwidth.
    All this in an MPLS network, how many would need to Altiris Notification
    Server 7 or 7.1 CMS?
     



  • 2.  RE: Architecture Design for Large Company
    Best Answer

    Posted Feb 18, 2011 05:33 PM

    How many need a notification server?  Assuming you have no requirement for replication or hierarchy, and that the reporting load is normal, you need a single NS in your datacenter and site servers at each site (office) where you did not place the NS.  And you'll need a site server where you did place your NS if your NS will handle more than 500 nodes.

    Office 1 - NS + site

    Office 2 - site

    Office 3 - site

    Office 4 - site



  • 3.  RE: Architecture Design for Large Company

    Posted Feb 18, 2011 05:52 PM

    Thank you very much

    I was thinking

    Office 1 - NS + site

    Office 2 - NS (because they are more than 2000 computer)

    Office 3 - site

    Office 4 - site

    ans Site Server in remote locations



  • 4.  RE: Architecture Design for Large Company

    Posted Feb 18, 2011 05:55 PM

    Site servers can actually handle more computers than a notification server, even if the NS has better hardware.  A site server offers bandwidth benefits at any site over a slow connection with multiple systems.  It's up to you to decide the point at which you would like the additional overhead for a site server.  Budget constraints on WAN bandwidth may also have something to say about it, as might your network administrator.  Technology might demand a site server, for example if you wish to do imaging on-site at a remote office, you'll need a site server (package and task) with the deployment task handlers.



  • 5.  RE: Architecture Design for Large Company

    Posted Feb 18, 2011 06:00 PM

    a question

    a site server downloads the packages from the NS, a server site can download packages from another site server?



  • 6.  RE: Architecture Design for Large Company

    Posted Feb 18, 2011 06:22 PM

    You can make site servers constrained servers, in which case they only download from unconstrained site servers.  An unconstrained site server can download from the NS.  A constrained site server must download from other site servers.

    Let's say you have 14 sites in North America, one is HQ with 40k nodes, and the other sites are across WAN links and have several hundred to a thousand nodes each.  You also have 5 sites in South America, one which is 20k nodes and the others, located across a South America-specific WAN, are 2k nodes each.

    You would locate an NS in North America, with perhaps five unconstrained site servers, and place an unconstrained site server at each of the other 13 sites.  (They are unconstrained because they download directly from the NS.  You do not obtain a bandwidth benefit to the 13 sites by asking them to download from other site servers, because this still consumes WAN bandwidth anyway.)

    Meanwhile, because there is no NS in South America, you have placed one unconstrained site server at the 20k node site.  You've also placed two constrained site servers there, and one constrained site server at each of the remaining 4 sites.  (They are constrained because you want them to download from the nearest, fastest unconstrained site server, which will definitely be the one located in South America.  You save on WAN bandwidth because, rather than download all packages 7 times across the WAN link between North America and South America, you download it once for the unconstrained server.  Of the remaining 6 site servers, the two at your large site use physical LAN links and the four at your branch offices use locally-available, less-strained South America WAN bandwidth.)

    I hope I've represented the concept properly.  I do not manage any environments where a constrained site server is required.



  • 7.  RE: Architecture Design for Large Company

    Posted Feb 20, 2011 10:55 AM

    The only thing I would add is that the unconstrained PS at a remote site  *should* be able to download its packages from a PS local to the NS, so as to take file replication load off of the NS.  I'm only implemented one constrained PS so far (at a remote site which was uplinked to another but needed its own PS), but it worked fine.  In the near future we'll be standing up a new NS for our Brazil offices but using the constrained model to replicate from US --> Brazil, then from the main office in Brazil to all the PSes in the country.



  • 8.  RE: Architecture Design for Large Company

    Posted Feb 24, 2011 06:43 PM

    doubt, as set up a Site Server constrained and unconstrained?

    is constrained to have a subnet assigned?