Jump to content


hooligan88

Established Members
  • Content Count

    13
  • Joined

  • Last visited

  • Days Won

    1

hooligan88 last won the day on July 22 2017

hooligan88 had the most liked content!

Community Reputation

1 Neutral

About hooligan88

  • Rank
    Member

Recent Profile Visitors

669 profile views
  1. Hi
    Kindly approve my post

  2. Hi Experts, We are currently implementing SCCM Current Branch 1702 afresh for one of our customers replacing BMC Marimba, and it was only a week back that we were informed about another existing installation of SCCM in one of the regions. They are using SCCM 2012 SP2.for managing patching for both server and desktop endpoints, with one Primary site and 8 distribution points. Now in our current implementation, we are looking to manage approximately 10000 endpoints and 1500 servers via a standalone Primary with additional management server and multiple secondaries in remote locations and distribution points in smaller branch offices. My question is how can we merge both these hierarchies and bring them up to the latest i.e. 1702 and then finally upgrade to 1706? Now, i understand that schema extenstion is a forest wide activity and since SCCM is already installed do I have to still extend the schema? Is there any change in attributes with current branch.
  3. Hi, As you have noted already, from a purely "supported" standpoint Windows Server 2003 is out of support for almost 2 years now. However, to my understanding it does work, but not sure how long term that solution is.
  4. Update - I have finally been able to convince the management to co-host SQL on the Primary server computer. This is how the final compute looks like PSS co hosting SQL DB - 8 Core, 64GB RAM Primary MP hosting (MP+DP+App+Reporting+SUP) - 4 Core, 32 GB IBCM Server (MP+DP+SUP) - 4 core, 8GB RAM 16 x DPs - 4 core, 16GB RAM SS in remote regional site with poor connectivity with the DC - (8 Core, 16GB RAM) I would probably not get a RAID and instead get a VM which would be sitting on a V-SAN pure Stroage. Any IOPS recommendations? As a general practice they wanted to keep all client facing roles separate from the primary site to reduce any load on the primary site. However I have recommended to keep the RP on the Primary site server. SUP will be using the site database. For DPs it is a typo, they will run *8GB* RAM. There are 16 branch offices with ~ 150-200 seats with good connectivity to the DC, and the sites for which the SS has been proposed is connected with a fairly small pipe 20M ( with the DC (sites are in India and US) and has nearly 1000 seats. Thus to prevent excessive WAN traffic due to content distribution the SS was proposed. There are remote sites with a DMVPN circuit and 5M/10M connectivity however lesser number of seats.
  5. Hi Experts, Looking for some help to understand a rather tricky topic. This has been my understanding so far: Core-based licensing System Center 2016 Standard and Datacenter Server MLs are Core-based licenses. A Server ML Core license must be assigned to each physical core in the server, with a minimum of 8 Core licenses per processor, and a minimum of 16 Core licenses per server. Used Case 1: a single processor server with 4 cores requires 16 Server ML Core licenses, and a 4 processor server with 8 cores on each processor requires 32 Server ML Core licenses. Server ML Core licenses are purchased in 2-packs from resellers and always include Software Assurance. Licensing Rules Software Assurance is included with all Client MLs .When purchased outside of the CAL Suites, Client MLs are available on a Per OSE or Per User basis When purchased via the CAL Suites, Client MLs are available on a Per Device or Per User basis Client MLs include the right to run the Management Server software and SQL Server. Virtualization Rights System Center 2016 Datacenter • The server must be fully licensed with Server ML Core licenses • An unlimited number of virtual machines may be managed on the server System Center 2016 Standard • The server must be fully licensed with Server ML Core licenses • 2 virtual machines may be managed on the server The server must be licensed again to manage a further 2 virtual machines. Used Case 2: A single processor server with 8 cores requires 16 Server ML Core licenses to manage 2 VMs. A further 16 Server ML Core licenses must be assigned to the server to manage another 2 VMs. Another statement in the whitepapers say A customer is eligible for License Mobility through Software Assurance that allows • System Center Standard 2016: rights to manage 2 VMs per licensed server • System Center Datacenter 2016 rights to manage 10 VMs per licensed server Could someone help understand, how would the license calculation work for an ESX on which 200+ VMs are hosted. Would we be licensing only the cores on the ESX box or the VMs hosted as per the matrix given above? Sorry, if this being repeated but I wasn't able to get a clear explanation which will help us calculate the ML licenses.We will get in touch withour licensing partner but need to project an approximate count with at least 10% growth to get a budget forecast.
  6. Update - I have finally been able to convince the management to co-host SQL on the Primary server computer. This is how the final compute looks like PSS co hosting SQL DB - 8 Core, 64GB RAM Primary MP hosting (MP+DP+App+Reporting+SUP) - 4 Core, 32 GB IBCM Server (MP+DP+SUP) - 4 core, 8GB RAM 16 x DPs - 4 core, 16GB RAM SS in remote regional site with poor connectivity with the DC - (8 Core, 16GB RAM) I would probably not get a RAID and instead get a VM which would be sitting on a V-SAN pure Stroage. Any IOPS recommendations?
  7. HI Garth, I am not in for a remote SQL and will have it co-hosted with the primary. That would take care of a lot of things. What in your view would be a realistic setup for an implementation similar to this? Assuming this setup would scale up to a ~ 15K (desktops+servers) in future.
  8. Hi Garth, Thanks for your response. The SUP and WSUS role will be installed on the Primary MP server. This will become the upstream data source location. The Windows and office Updates will be synced from Primary, Secondary and the DPs. RP will also reside in the Primary MP server and the reporting database will be installed on the SQL server. Yes, there will be a dedicated connection between SQL and the Primary server site (Datacenters). The reason for having a dedicated SQL is mostly IOPS and <billing> Everything will be virtual. Hi anyweb, Yes I'am all for fighting this battle once again especially keeping the future roadmap in mind. Thanks for your suggestions, much appreciated.
  9. Hi Experts, I am currently designing a Current Branch implementation for a customer who continues to ask for a Microsoft best practice evidence/ documentation. From whatever I have gathered over my past years of experience, i have never really come across a single "best practice rulebook" as one size can never fit all. In any case, could you guys direct me to any such guide which has design decisions/ used cases documented? other than these https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/supported-configurations https://docs.microsoft.com/en-us/sccm/core/plan-design/hierarchy/design-a-hierarchy-of-sites Meanwhile, just to get an idea i am planning an implementation for ~ 7K clients and below is what I have proposed - Single Primary at one of the Datacentre ( 8 Core, 48GB RAM) - Management server holding client facing roles in another Datacentre (4 Core, 32GB RAM) - Dedicated server for SQL (I was all for co-hosting the SQL on the same server as the primary but due to reasons more political in nature had to go with a dedicated SQL server) (4 Core, 16GB RAM) - 2x Secondary sites at remote sites (4 Core, 16GB RAM) - Distribution points (across various sites spread across the globe) - No CAS ( Future expansion possible) Let me know what you think, thanks in advance
  10. Hi Experts, Only recently, we found a bug with our Windows 8.1 Image. We have configured the TS to allow user choose the language while TS is executed. The selected language works fine on the Welcome Page and even on the login page where the user is prompted for user id and password. However, once logged in the start menu, desktop and icons appear in the English US. I have tested logging in using both administrator account as well as a standard user with the same results. The user gets the option to chose German and make it the primary language. However the language doesnt change to German on first time login. I am using the below in the unattend.xml: <InputLocale>%Keyboardlocale%</InputLocale> <SystemLocale>%Systemlocale%</SystemLocale> <UILanguage>%UILanguage%</UILanguage> <UserLocale>%UserLocale%</UserLocale> and tried the below: <InputLocale>%OSDInputLocale%</InputLocale> <SystemLocale>%OSDSystemLocale%</SystemLocale> <UILanguage>%OSDUILanguage%</UILanguage> Without any results. Any help will be much appreciated. BR, Hooligan88
  11. Hi Experts, Sorry about digging an old thread. Only recently, we found a bug with our Windows 8.1 Image. We have configured the TS to allow user choose the language while TS is executed. The selected language works fine on the Welcome Page and even on the login page where the user is prompted for user id and password. However, once logged in the start menu, desktop and icons appear in the English US. I have tested logging in using both administrator account as well as a standard user with the same results. I am using the below in the unattend.xml: <InputLocale>%Keyboardlocale%</InputLocale> <SystemLocale>%Systemlocale%</SystemLocale> <UILanguage>%UILanguage%</UILanguage> <UserLocale>%UserLocale%</UserLocale> and tried the below: <InputLocale>%OSDInputLocale%</InputLocale> <SystemLocale>%OSDSystemLocale%</SystemLocale> <UILanguage>%OSDUILanguage%</UILanguage> Without any results. Any help will be much appreciated. BR, Hooligan88
  12. Hi Experts Env: 1 Central Server 15 Primary servers 1 WSUS Server Multiple Active update sources (all primary servers) We are using SCCM to patch workstations and servers and have identified an issue with multiple WSUS update sources in the database. This is from a previous WSUS installation where in the stale entries still prevail in the database. We have determined to delete the inactive update source from the db and reinstall the SUP role alone. Apart from redoing the updates classification and custom site settings what impact is this going to have in the environment. e.g. on the old update lists, DMs, CIs. Am I going to lose all of that as well? I am currently testing the instance in the lab but wanted ideas from the community as well! Looking forward to a response
×
×
  • Create New...