Infrastructure Design

Hi All,
I'm looking for a bit of advice around SQL Server infrastructure design.  Currently we have around 35 instances of SQL Server installed in our organisation all on separate servers.  Most instances have only a couple of database running on them although
there are a few which have more. When implementing new applications we are often told by vendors that they require a dedicated SQL Server for their applications to perform well.  Going forward I'd like to implement a good quality robust infrastructure
for our SQL Servers that would see a reduction in the number of servers and more database per instance.  Any advice on this and what other are doing within their organisations would be appreciated.
Cammie 

Hi Cammie,
Yes I hear this all the time from vendors.  We're using larger VMs with lets say 128gb of ram assigned with 16 processors and just using multiple SQL instances per VM.  You just have to make sure you tune the instances correctly for proper sizing
on the CPU and memory side.  The only problem you will really run into is if your dealing with a vendor that hasn't put much thought into their product line and can only operate out of the default SQL instance and over the default SQL port.  Most
vendors take a different design approach and can deal with sqlservername\instance type installs and non standard ports. 

Similar Messages

  • New Network Infrastructure Design and Architecture Community

    All,
    I'm pleased to announce our new Network Infrastructure Design and Architecture Community.  In this community we encourage everyone to share their knowledge and start conversations on design and overall network topology. All topics are welcome, including requirements and constraints of the network, tools and techniques, issues of hierarchy, leading practices, services, build strategies, architectures and solutions to solve business problems.        
    Who will be the first to make it on that leaderboard?
    Cheers,
    Dan     

    Mike,
    Thanks for the kind words about the community.  It's always nice to hear the things we do make a difference. 
    Launching a scripting community has come up a few times in the past and I'm open to it.  Anyone else have thoughts on this?
    On a separate note, you'll be thrilled to hear what one of our CSC booth give-aways will be at Cisco Live San Diego next week.  Your best friend the cross-over-cable    For those of you out there attending the event be sure and stop by the CSC booth.
    Cheers,
    Dan

  • Complex Infrastructure Design Challenges

    Hi 
    I need some advice on a infrastructure design. I am hoping someone can help or point me in the right direction.
    Requirements are as follows
    - Sharepoint 2013 3-Tier Design
        -> Front-End Cluster
        -> App Tier
        -> SQL Cluster
    Aside from the requirements from a server perspective which provides it's own challenges there needs to be Single-Sign On, however multi-domain support will be challenging since there will be two AD Forests with no trust relationship being allowed. 
    I have the following challenges:
    - One of the two domains there will be full control on the service accounts and the management environment, but using the servers on that domain as the initial domain will be very limiting in it's own sense. The other domain there will be limited or no control
    - Single sign on nightmare is that these two domains have no trust relationship and never will. How could I manage that with the above point also holding true. I saw an article on ADFS that will be able to provide the transparent authentication level but
    what would be required from access perspective to have ADFS tied in with the domain which there will be no control over
    - The servers is currently joined on the domain with the limited control the possibility to intall cluster services, sql services and sharepoint services is a bit limited. This can be switched to the domain with the complete control but the Single sign on
    nightmare will be the ultimate deciding factor 
    Help, advice or any resource documents with examples of such scenario's would be helpful
    Can someone point me in the direction I need to be. I am happy to read up on any knowledge articles if there are any

    Starting with ADFS, you will want to establish ADFS Federation. This means that the domain you have no control over also has an ADFS server. The only requirements for that implementation is opening TCP/443 to the ADFS server (or ADFS proxy) and it must be
    a member of the domain (an ADFS proxy does not).
    Alternatively, you could provide Active Directory accounts to all of the users for the other domain in the domain you do have control over, but this likely isn't desirable.
    As for the servers, you won't be able to just disjoin them and join another domain. Instead, you're going to have to build a brand new implementation and copy content over (e.g. copy the databases from the first implementation to the second).
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • DNS Server Infrastructure Design

    Good day IT Folks,
    Currently I'm on the planning stage of designing DNS infrastructure of our company. I've read a lot of reading materials available online about DNS. According to what I've gathered, two (2) DNS server is the minimum and three (3) is the recommended for the
    usual set up of DNS. What I want to my DNS infrastructure is to have two (2) DNS servers for my LAN (internal network) and one (1) DNS for my LAN-to-Internet connection (external network).
    The two (2) DNS servers will resolve LAN request and will forward requests to the another one (1) DNS server if internet-related sites is requested. I would like to ask for your help to give me insights how am I going to do this, where to start and what
    are the things I should consider.
    Thanks.
    akosijesyang - the conqueror

    You could go with a secure design such as the following (click on it to open a larger image in a new page):
    See if the following threads help:
    Technet Thread: Problem with Windows 2008 R2 Dns Server getting SERVFAIL resolving one domain, 1/18/2012
    Includes a secure DNS forwarder in the DMZ image
    http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/b00fc041-ba44-45b6-a8a1-a00374a20edf
    Technet Thread: DNS Structure to rebuild efficiently - Question about the resolution process, 10/27/2011
    Includes a secure DNS forwarder in the DMZ image
    http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/3a5fb6ac-6ab7-45b1-abab-e0d928a7e06c
    Good discussion on DMZ secured resolver design, and the use of "Unbound DNS Resolver (http://unbound.net/) to use on your DMZ DNS server instead of Windows DNS. (Note: IMHO, for AD, I would rather use Windows DNS. - Ace)
    Technet Thread: W2003 DNS cache snooping vulnerability for PCI-DSS compliance, 10/10/2011
    http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/67e9189b-606a-40d2-9944-8b4c7d084017/
    And dealing with internal and external names:
    Can't Access Website with Same Name (Split Zone or no Split Brain)
    Published by Ace Fekay, MCT, MVP DS on Sep 4, 2009 at 12:11 AM  1278  0
    Note - In an AD same name as the external name (split zone) scenario, if you don't want to use WWW in front of URL, such as to access it by
    http://domain.com, then scroll down to "So you don't want to use WWW in front of the domain name"
    http://msmvps.com/blogs/acefekay/archive/2009/09/04/split-zone-or-no-split-zone-can-t-access-internal-website-with-external-
    name.aspx
    Ace Fekay
    MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/
    This post is provided AS-IS with no warranties or guarantees and confers no rights.

  • Welcome to the Design and Architecture Community

    Welcome to the Network Infrastructure Design and Architecture Community.  We encourage everyone to share their knowledge and start conversations on design and overall network topology. All topics are welcome, including requirements and constraints of the network, tools and techniques, issues of hierarchy, leading practices, services, build strategies, architectures and solutions to solve business problems.
    Remember, just like in the workplace, be courteous to your fellow forum participants. Please refrain from using disparaging or obscene language or posting advertisements.
    Cheers,
    Dan BruhnCSC Community Manager

    been waiting to see a forum like this. This forum should amalgamate all the other areas like R&S, security, DC design, and provide more quality , proven solns and discuss problems/challenges as well. Will be following this forum regularly
    thanks dan for creating this community
    Regards Kishore

  • Ask the Expert: Hierarchical Network Design, Includes Core, Distribution, and Access

    Welcome to the Cisco® Support Community Ask the Expert conversation.  This is an opportunity to learn and ask questions about hierarchical network design. 
    Recommending a network topology is required for meeting a customer's corporate network design  needs in their business and technical goals and often consists of many interrelated components. The hierarchical design made this easier like "divide and conquer" the job and develop the design in layers.
    Network design experts have developed the hierarchical network design model to help to develop a topology in discrete layers. Each layer can be focused on specific functions, to select the right systems and features for the layer.
    A typical hierarchical topology is
    A core layer of high-end routers and switches that are optimized for availability and performance.
    A distribution layer of routers and switches that implement policies.
    An access layer that connects users via lower-end switches and wireless access points.
    Ahmad Manzoor is a Senior Pre-Sales Engineer at AGCN, Pakistan. He has more than 10 years of experience in first-rate management, commercial and technical skills in the field of data communication and services lifecycle—from solution design through sales pitch, designing RFPs, architecture, and solution—all with the goal toward winning projects (creating win/win situations) of obsolete solutions.  Ahmad also has vast experience in designing end-to-end data centers, from building infrastructure design to data communication and network Infrastructure design. He has worked for several large companies in Pakistan and United Arab Emirates markets; for example, National Engineer, WATEEN Telecom, Emircom, Infotech, Global Solutions, NETS International, Al-Aberah, and AGCN, also known as Getronics, Pakistan.
    Remember to use the rating system to let Ahmad know if he has given you an adequate response. 
    Because of the volume expected during this event, Ahmad might not be able to answer every question. Remember that you can continue the conversation in the  Solutions and Architectures under the sub-community Data Center & Virtualization, shortly after the event. This event lasts through August 15, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

    Dear Leo,
    We are discussing the following without any product line, discussing the concept of hierarchical design, which will help you to take decision which model is better for you Two Layer or Three Layer hierarchical model.  
    Two-Layer Hierarchy
    In many networks, you need only two layers to fulfill all of the layer functions—core and aggregation
    Only one zone exists within the core, and many zones are in the aggregation layer. Examine each of the layer functions to see where it occurs in a two-layer design:
    Traffic forwarding—Ideally, all interzone traffic forwarding occurs in the core. Traffic flows from each zone within the aggregation layer up the hierarchy into the network core and then back down the hierarchy into other aggregation zones.
    Aggregation—Aggregation occurs along the core/aggregation layer border, allowing only interzone traffic to pass between the aggregation and core layers. This also provides an edge for traffic engineering services to be deployed along.
    Routing policy—Routing policy is deployed along the edge of the core and the aggregation layers, generally as routes are advertised from the aggregation layer into the core.
    User attachment—User devices and servers are attached to zones within the aggregation layer. This separation of end devices into the aggregation permits the separation of traffic between traffic through a link and traffic to a link, or device. Typically, it is best not to mix transit and destination traffic in the same area of the network.
    Controlling traffic admittance—Traffic admittance control always occurs where user and server devices are attached to the network, which is in the aggregation layer. You can also place traffic admittance controls at the aggregation points exiting from the aggregation layer into the core of the network, but this is not common.
    You can see, then, how dividing the network into layers enables you to make each layer specialized and to hide information between the layers. For instance, the traffic admittance policy implemented along the edge of the aggregation layer is entirely hidden from the network core.
    You also use the core/aggregation layer edge to hide information about the topology of routing zones from each other, through summarization. Each zone within the aggregation layer should have minimal routing information, possibly just how to make it to the network core through a default route, and no information about the topology of the network core. At the same time, the zones within the aggregation layer should summarize their reachability information into as few routing advertisements as possible at their edge with the core and hide their topology information from the network core.
    Three-Layer Hierarchy
    A three-layer hierarchy divides these same responsibilities through zones in three vertical network layers,
    Traffic Forwarding—As with a two-layer hierarchy, all interzone traffic within a three- layer hierarchy should flow up the hierarchy, through the layers, and back down the hierarchy.
    Aggregation—A three-layer hierarchy has two aggregation points:
    At the edge of the access layer going into the distribution layer
    At the edge of the distribution layer going into the core
    At the edge of the access layer, you aggregate traffic in two places: within each access zone and flowing into the distribution layer. In the same way, you aggregate interzone traffic at the distribution layer and traffic leaving the distribution layer toward the network core. The distribution layer and core are ideal places to deploy traffic engineering within a network.
    Routing policy—The routing policy is deployed within the distribution layer in a three- layer design and along the distribution/core edge. You can also deploy routing policies along the access/distribution edge, particularly route and topology summarization, to hide information from other zones that are attached to the same distribution layer zone.
    User attachment—User devices and servers are attached to zones within the access layer. This separation of end devices into the access layer permits the separation of traffic between traffic through a link and traffic to a link, or device. Typically, you do not want to mix transit and destination traffic in the same area of the network.
    Controlling traffic admittance—Traffic admittance control always occurs where user and server devices are attached to the network, which is in the access layer. You can also place traffic admittance controls at the aggregation points along the aggregation/core edge.
    As you can see, the concepts that are applied to two- and three-layer designs are similar, but you have more application points in a three-layer design.
    Now the confusion takes place in our minds where do we use Two Layer and where the Three layer hierarchical model.
    Now we are discussing that How Many Layers to Use in Network Design?
    Which network design is better: two layers or three layers? As with almost all things in network design, it all depends. Examine some of the following factors involved in deciding whether to build a two- or three-layer network:
    Network geography—Networks that cover a smaller geographic space, such as a single campus or a small number of interconnected campuses, tend to work well as two-layer designs. Networks spanning large geographic areas, such as a country, continent, or even the entire globe, often work better as three layer designs.
    Network topology depth—Networks with a compressed, or flattened, topology tend to work better as two-layer hierarchies. For instance, service provider networks cover large geographic areas, but reducing number of hops through the network is critical in providing the services they sell; therefore, they are often built on a two-layer design. Networks with substantial depth in their topologies, however, tend to work better as three-layer designs.
    Network topology design—Highly meshed networks, with many requirements for interzone traffic flows, tend to work better as two-layer designs. Simplifying the hierarchy to two levels tends to focus the design elements into meshier zones. Networks that focus traffic flows on well-placed distributed resources, or centralized resources, such as a network with a large number of remote sites connecting to a number of centralized Data Centers, tend to work better as three-layer designs.
    Policy implementation—If policies of a network tend to focus on traffic engineering, two-layer designs tend to work better. Networks that attempt to limit access to resources attached to the network and other types of policies tend to work better as three-layer designs.
    Again, however, these are simple rules of thumb. No definitive way exists to decide whether a network should have two or three layers. Likewise, you cannot point to a single factor and say, “Because of this, the network we are working on should have three layers instead of two.”
    I hope that this helps you to understand the purposes of Two Layer & Three layer Hierarchical Model.
    Best regards,
    Ahmad Manzoor

  • Data Warehouse Infrastructure

    I have a requirement to build a Data Warehouse and Analytics / Reporting capability with the following requirements...
    Maximum of 1TB for Production Data + DR + Test/Dev Env.
    SSIS (up to 25 sources), SSAS (cubes, 5 concurrent users) and SSRS (2 concurrent users, max 500 reports).
    I needs a Production, DR and Test/Dev Environment 
    I have been told that I will require 12 servers each having 4 cores and 12GB of storage (4 for Prod, 4 DR and 4 Test/Dev).
    To give you an idea of load we plan to have 1 full time ETL developer, 5 Data Analysts, 2 Reporting Analysts. We are quite a small business and don't have a particularly large
    amount of data. 
    The model has SQL Server, SSIS, SSAS, SSRS on different servers across each Environment. 
    Any idea if this is overkill? I also have an estimate of 110 days for Setting up the Servers, Installing the SQL Server software and general Infrastructure design activity.

    Agree. Overkill. Big overkill.
    I would recommend production/DR/Dev each have 2 servers. I'd put SSAS, SSRS and SSIS one one and the DB on the other.
    In production, SSAS/SSRS will be active during the daytime; SSIS will likely be active off hours. So putting all that on one box should be fine for sharing the load. The DB on a second box would be good since it will likely be busy during the daytime
    and night time. Four processors may be heavy depending on the types of queries and usage patterns. I suspect you can get by with 2 processor servers, but would recommend buying the 4 processor boxes for dev and production, get them configured and run
    some performance baselines before putting in the DR environment. Then, if you find the CPUs idling, you can always cut the DR environment to 2 processor boxes. Not sure it's worth the minor cost savings to save 2 processors on 2 boxes with that effort, but
    if you're looking to cut corners, you may find that a 2 processor per server DR environment is within your performance comfort zone.
    For the dev environment, one box may well handle it all, but I'd go for 2. On average, a Dev environment isn't all that busy, but when you need the horsepower, you need it. And since it's Development AND Test, you help yourself by having realistic production
    level performance on what you're testing. Four processors is fine, but max it out on memory.
    As for hard drives, be careful about configuration. You need the space on your DW server and maybe for the SSAS server depending on how the cubes are built (ROLAP/MOLAP). When you speak about amounts of data, be careful since you'll want a lot of indexes,
    and that can double the DB size for a DW. Your DW will also run faster if you have different filegroups for data/indexes/temp DB, but only if those different filegroups are on different physical media that work well in parallel. You can always get fancier
    with more filegroups to have different ones for staging tables, for segregating fact & dimension tables etc. But for this size DB, that's overkill as well.
    Mainly, I'd look at spending hardware $s on memory for the servers, but get less of them.
    Now... two questions...
    1) Can you clarify the disk space needs? How much total data space in one environment, without indexes? Based on that, add the same for indexes, add half as much (?) for TempDB and you have the core disk needs. Depending on how much it is,
    you can decide on RAID, filegroup configuration, etc. And if the disk space with indexes is small enough that it all fits in memory, then disk and filegroup configuration becomes inconsequential except for ETL loads.
    2) The 25 sources... can you clarify that? 25 source systems? Total of 25 source applications? Total of 25 tables? Curious, because I'm wondering about how long you'd keep 1 full time ETL developer busy.

  • Design pattrens in xi

    hi,
    what is design pattern.
    explain in detail.
    vijay

    Hi
    refer
    SAP Network Blog: Design Patterns in Exchange Infrastructure
    /people/sap.user72/blog/2005/12/20/design-patterns-in-exchange-infrastructure
    Design Patterns and Best Practice for SAP NetWeaver Exchange Infrastructure - Webinar Powerpoint
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f0ad6de0-7cd6-2910-f894-dd7fe18b6fbf
    SAP Network Blog: Summarization : Mapping Pattern in PI
    /people/sunil.ojha5/blog/2008/01/16/summarization-mapping-pattern-in-pi
    thanks
    Swarup

  • Design question - best order of implementation

    Please see attached an existing core network infrastructure design. I am planning to implement the following:
    1. A secondary DMVPN hub (dual DMVPN hub)
    2. A secondary ASA (active/active configuration)
    3. A secondary ISP (BGP multihoming)
    What would be the best/right order to start implementing these technologies?
    Thanks,

    Hello jimiohara,
    jimiohara wrote:
    The question I have is what would be the best way to store these constant parameters as strings so they can be retrieved using a single identifier such as the graphs type or class name(bearing in mind there are about 20+ different graphs)?I am not really sure, whether I understand the question right? But why not using a hash table (e.g. HashMap). In this key/value-list you can store whatever you like. The key only have to be "hashable" (implement equals() and hashCode(), e.g. String!!!). If you want to use TreeMap you also have to define an order with Comparable or Comparator.
    Or use the Properties-class where the key and the value are always Strings.
    regards
    tk

  • ITS infrastructure

    Hi,
    I am putting together an ITS infrastructure design and I have a couple of questions that I am hoping someone can assist me with:
    1. I am putting AGATE and WGATE on the same server, but I will have multiple AGATE/WGATE servers for resiliency. My question is can I load balance the AGATE components between the different servers? i.e. WGATE on box A can use AGATE on box  B or A and WGATE on box B can use AGATE on box B or A. Is this possible? And does it make any sense to do this? I am thinking that if one box is less loaded somehow it could offload handle the AGATE processing from the other box if needed?
    2. Are there any guidelines / benchmarks around server sizing the AGATE component? Or even both agate and wgate. My feeling is the WGATE doesnt require to much grunt but the AGATE bits will.
    Any thoughts, help, comments greatly appreciated.
    Thanks,
    James

    Hello James,
    Yes it makes sense to put a cross in place for (wgate/agate) loadbalancing and failover.
    Just put the agates in your (logical) instance at the wgate side (all wgates);  Assuming 3 agates on three hosts pointing to the same R3 then extend all wgate configurations to:
    - Instance XXX
    --  Agate1 Host1
    --  Agate2 Host2
    --  Agate3 Host3
    Remember to check the "services" files at the original hosts for the portnumbers of the Agate and Mapping Manager.
    there is some information on agate sizing in http://help.sap.com/saphelp_47x200/helpdata/en/82/4d5739d335a85ee10000000a114084/frameset.htm
    maintenance see: http://service.sap.com/~form/sapnet?_SHORTKEY=01200572170000061091
    Regards,
      Fekke

  • [Solved] Any alternatives to a very buggy Evolution Mail 3.6?

    Hi All,
    I've kind-of had it with Evolution mail. I've been running 3.x for a long time, and it's always been a very "klunky" experience, with constant issues of hanging, bad HTML mail rendering, and the occasional (twice in a year) need to fix it in the terminal after upgrades (completely corrupted mail stores, etc).
    The reason why I put up with it, is that I really want to at least use an application suite where my contacts are centrally managed (Evolution Data Server) and other apps (like Empathy chat) can re-use the central contacts store. Other mail clients manage their own contacts internally in an isolated island (e.g Mozilla Thunderbird). I really want to use a Linux desktop environment where the *basics* (such as centralised contacts) are in place. I mean, we are in 2012. I've been promised flying cars and a semantic desktop :-)
    After the update to GNOME 3.6, I have well and truly had it with Evolution. Every now and then it starts to recursively spawn "Saving user interface state" and "Unknown background task" tasks that just bring it to its knees, requiring a process kill. It cannot be regarded as anything more than alpha quality software, and it's starting to cost me a lot of lost productivity.
    This is only e-mail, right? It's been around since before 1980. Surely there are alternatives for an intelligent, integrated suite of e-mail/calendar/contacts on the linux Desktop? What do you gentleman and ladies use? Mutt is starting to look real good, and that's just sad for a previous Apple user that switched to Arch Linux (which has generally been a wonderful experience in all non-mail aspects).
    I'm at my wits' end, and looking for some advice from fellow users of the thinking man's Linux...
    Surely GNOME/Evolution can't be "it" in terms of offering competition to the Apple/Microsoft desktop?
    Last edited by dawid.loubser (2012-11-05 08:09:36)

    *david_a* wrote:
    Integrated with every app on the desktop? KDE.
    I believe you are stuck choosing between desktop integration and performance/quality; apparently "both" is not an available option.
    Not necessarily integrated with every app, but integrateable at least. Something using an infrastructure designed for integration, with basic integration already done between the basic components mentioned in my original post. I feared that I would have to choose between quality and desktop integration - this really saddens me, and must be a big stumbling block for the adoption of the Linux desktop.
    *david_a* wrote:
    Emacs/Gnus/bbdb?
    Thunderbird?
    Apple? Microsoft?
    You may already have the best available.
    I believe desktop integration is losing steam as Google and similar ventures take the integration outside the machine. A bad plan IMO, constructed to support disparate and poorly-built operating systems (including those on phones) but at the same time taking users' data away from them.
    You are right, I don't want my data taken away from me, and it goes against my grain to rely on a free online service of a publicly-traded corporation 10,000km away from me for my personal communication needs. I want to own and manage my data, and I suspect so do many other Linux users...
    I can only hope a renaissance of sorts will happen when people realise that they are no longer in control of their own data, and that hopefully then we will see the emergence of better desktop communication in Linux. I don't care about the masses, who will probably never care about this. I do care about the fellow computer geeks who understand and appreciate this, and are in search of something that at least matches what a Mac/Windows box could do a decade or so ago :-)
    For the time being, I guess I have to slog it out with Evolution, and start filing bug reports in the hope that the quality may one day improve.
    What surprises me, is that this thread has not drawn a single reply from a fellow frustrated user. I'd have loved a "me too" or two - why does everybody put up with this? You can't all be happy to be stuck in 1990 as far as integration of desktop communication is concerned? I have a lot of respect for minimalist, powerful, single-purpose programs, yet such a setup demands good integration between those components. Are there at least some forward-thinking projects on the go somewhere that is working towards this that anybody knows of?
    I thank you for your reply :-)

  • SharePoint via VPN in a hosting environment

    Hello everybody,
    today I come across with a question regarding infrastructure design. Beforehand you have to know, I am not an architect, until now I was just an Sharepoint admin :)
    We have a scenario, that one of my customers want us to host a sharepoint 2013 in our datacenter. They also want to use their already existing active directory infrstructure, so they can use all their AD properties for mysite and profiles.
    My question is, what could be a supported or feasible configuration?
    My first consideration is to connect the customer site via VPN to our DATACENTER with a 50 meg internet connection, placing a RODC in our datacenter which is replicating the AD structure from the customer site via VPN to our DATACENTER, so that the
    sharepoint machines can join their domain, replicate all the profile data and also authenticate the users against the active directory in a performant way!
    In my opinion, this is the only option because building up an own Active Directory and create an ADFS trust between the brand new active directory and the already existing active directory from the customer, will end up in trouble to replicate the user profiles,
    I guess! Not to mention that there will possibly be some performance issues in authenticating the user aganst the sharepoint.
    Until now I have no experince in scenarios like this, where technology is spanning via DATACENTERS. In former configurations we had everything (including Active Directory) in our datacenter!
    Are there any caveats to do it like I mentioned?
    Every hint or thought will be valuable.
    Greetings Andre

    Hello,
    as I recently figured out, there has to be a read/write DC to be reachable for several reasons.
    Creating a new sitecollection, people search with people picker and running the farm configuration wirzard are just a few of them.
    Here is a KB article I triped over:
    http://support.microsoft.com/kb/970612/de
    Is there a configuration with ADFS possible, has anybody experience with this?
    Regards
    AR-Oldenburg

  • Client manageability in SCCM 2012

    Hi All
    I am Planning to have test SCCM 2012 environment and for that i need few architecture suggestions. Kindly suggest me on the same so that i can implement an effective infrastructure design.
    Total Number of Clients to Support - 58000
    First Draft version of design consist of 1 Primary Site and 3 Seconadry Sites. Kindly confirm if 1 primary and 3 secondary site will be able to cater 58000 clients. As per my understanding secondary site supports 5000 clients and Primary sites can support
    25000 Clients.
    Also confirm that clients under secondary site will be considered as client of primary site (linit of 25000) or seperately counted (25k +5K).
    Regards
    Regards Suresh

    Kent's book talks about a limitation of 50 000 when using a local SQL server. 
    Kent's book does state this. 
    Note that the Technet article states the following (from the link supplied by John):
    Client group 1 includes Windows Server and client.
    Site type
    Configuration Manager version
    Client group 1
    Client group 2
    Client group 3
    Stand-alone primary site, with a local site database, or a remote site database
    System Center 2012 Configuration Manager with no service pack 1
    100,000
    50,000 4
    25,000
    System Center 2012 Configuration Manager with SP1
    100,000 2
    50,000 4
    25,000
    System Center 2012 R2 Configuration Manager
    100,000 2
    50,000 4
    25,000
    Child primary site with a local site database
    System Center 2012 Configuration Manager with no service pack 1
    50,000
    50,000 4
    25,000
    System Center 2012 Configuration Manager with SP1
    50,000 2
    50,000 4
    25,000
    System Center 2012 R2 Configuration Manager
    50,000 2
    50,000 4
    25,000
    Child primary site with a remote site database
    System Center 2012 Configuration Manager with no service pack 1
    100,000
    50,000 4
    25,000
    System Center 2012 Configuration Manager with SP1
    100,000 2, 3
    50,000 4
    25,000
    System Center 2012 R2 Configuration Manager
    100,000 2, 3
    50,000 4
    25,000
    Secondary site
    Any version 1
    5,000 5
    Cheers
    Paul | sccmentor.wordpress.com

  • Windows Server 2008 R2 Performance Monitor information / thresholds

    Dear Users,
    I have been in search for information about the Performance Monitor for Windows Server 2008 R2.
    Unfortunately not with exactly what I wanted to, so I have some information but still not complete.
    What I'm trying to find is a sort of table with information which counters are good to monitor to make sure the server has enough hardware available.
    We are working in a virtual environment so that makes it easy to give more hardware, but this also means that there is a possibility we are handing out to much and that we need to take some hardware back.
    But I find it hard to find the right information about the counters to use and with the thresholds.
    I got already a lists with counters, explanation and the thresholds, but there are way more counters.
    Is there anyone who could point me out to a website were I can read more information about this subject?
    Because I really want to spend more time about what is using resources and if we are working efficiency.
    Any other information regarding the Performance Monitor is as well welcome.
    Kind regards,
    Martijn

    Hiya,
    I use the following table as a rule of thumb.
    Objects & Counters
    Issue thresholds
    Processor - % Processor Time
    Above 
    75-85%
    Disk - Avg. Disk Queue Length
    Slowly rising until poor performance is experienced.
    Disk - % Idle Time
    Larger than 90%
    Disk - % Free Space
    Less than 20%
    Memory - Available Mbytes
    Less than 2GB on Web server.
    Memory - Cache Faults/sec
    Larger than 1
    Memory - Pages/sec
    Larger than 10
    Page File - % Used and % Used Peak
    Trend analysis on occurrence. The more often, the worse.
    Network - Total Bytes/sec
    Larger than 40-50% of network capacity.
    Process - Working Set
    Larger than 80% of total memory
    From my own guide:
    https://jesperarnecke.wordpress.com/2014/05/19/sharepoint-infrastructure-design-specification/

  • Cannot install Exchange 2010 on Win Server 2k8R2

    I am working in a Hyper-V lab trying to install Exchange 2010 on a Windows Server 2008 R2 server. When the installer gets to the Readiness Checks it keeps failing on the Client Access Role prerequisites, and Mailbox Role prerequisites with the following 2 errors:
    Unable to read data from the Metabase. Ensure that Microsoft Internet Information Services is installed.
    Unable to access the 'Default Web Site' on this computer.
    I have checked in Server Manager and IIS is definitely installed.
    I opened the IIS Manager, and from there I *can* browse to the Default Web site.
    For the 1st message, there is a link to http://technet.microsoft.com/en-us/library/aa997645.aspx, but that site doesn't contain any useful information for Exchange 2010.
    For the 2nd message, there is a link to http://technet.microsoft.com/en-us/library/aa997698.aspx, but I tried that and still get the same error.
    Any help is greatly appreciated.
    Thanks
    James.

    Can you make sure that you have installed the pre-requisites for Windows 2008 R2? You may run it again which will install if some components of IIS are missing... 
    Open Powershell with elevated rights using "Run As Administrator", and run below cmdlets to install prerequisites...
    Import-Module ServerManager
    Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy -Restart
    Set-Service NetTcpPortSharing -StartupType Automatic
    Exchange 2010 Prerequisites
    http://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspx
    Exchange 2010 RC: Quick Installation Guide
    http://www.messagingtalk.org/exchange-2010-rc-quick-installation-guide
    Amit Tank
    MVP: Exchange Server | MCTS: Microsoft Exchange Server 2010, Configuration
    MCITP: EMA | MCSA: M | Blog: http://ExchangeShare.WordPress.com
    Thanks a lot!
    I wonder why the Exchange 2010 installation doesn't just install these features automatically. I guess it's not that hard to let these PS commands run prior to installing Exchange 2010 files.
    Ruud van Strijp
    Ruud van Strijp - Network Infrastructure Design in the Netherlands. MCSE: 70-270, 70-284, 70-290, 70-291, 70-294, 70-297. Cisco: CCNA, CCDA, CCNP, CCDP.

Maybe you are looking for