Search the Community

Dear Experts, I Would like to get some inputs from you Please. My Data Center is located in 2 Regions. This data center is supplying the services (Windows Server, Network., etc) At Present we are planning to perform SCCM CB Implementation with High Availability for SCCM Client Roles. In fact not for SQL (Due to Commercial items) Single Standalone Primary Site is fair enough for the environment. However, We would like to reduce the usage of SQL Server, and make the Client facing roles with HA. Hence your inputs would be helpful for us Data Center Region A: Server 1 - SCCM Site Server - A Primary Site with Roles (Component Server, Site Server, Site System, Reporting Service Point, Other Non Client Facing Roles) Server 2 - SCCM Site System - Client Facing Roles (Management Point, Software Update Point/WSUS, Distribution Point (With WDS/PXE OSD Capabilties) Data Center Region B: Server 3 - SCCM Site System - Client Facing Roles (Management Point, Software Update Point/WSUS, Distribution Point (WithOut WDS/PXE OSD Capabilties) So all Client facing role, will be working with HA Option. However, PXE Boot for OSD will work only with SERVER 2 from WDS (Which respond to the Client during the OS Imaging) - To make this happen I need to mention the IP Details of WDS Server (Server 2 from Region A) in the DHCP Scope. Am I correct? The reason, I do not preferred to give the SERVER 3 (From Region B)as WDS Role with PXE, which we do not need to give the multiple entries with DHCP Scope (Option 66, 67) for OSD Please suggest, if this is looks good for an organization. The Ultimate goal is to reduce the SQL CPU Utilization.

Hey guys, So I am rolling out SCCM and OSD. I am learning this totally from scratch, so it's kind of a long road. The tutorials and help guides in this forum have been a HUGE benefit, so let me thank you for that. My questions are more procedural at this point. I have SCCM set up, and I've followed every step in the SCCM 1511 deployment guides on the forum. I have my Windows 10 x64 image set up and have tested PXE booting, which works perfectly. So now...how do I go about this whole process for my help desk guys? I'm thinking right now I'm able to tell my help desk guys that I have deployed a clean image of Windows 10 x64, that will do some basic tasks (add to the domain, add to correct OU, enable .NET 3.5). They could start using this tomorrow. In the mean time, I will continue to work in the background on deploying each application we use. I envision that I can slowly roll out each one as I test it. Office 365 tomorrow, then our Loan Ops app, then another, etc. Is there a 'best practice' for setting up a build lab environment to test with, then migrate it to production once I'm happy? I have to imagine it's setting up a Device Collection specifically for testing, then create a test Task Sequence that I can use. Once I'm happy, is there a best way to push the new task sequence to production? Or do I just un-distribute the old Task Sequence to OSD Deploy and then distribute the new one? Sorry if I'm all over the place, I'm having a hard time knowing even exactly what I'm asking for. tl,dr: I want my help desk guys to be able to use what I've got ready so far with SCCM and OSD, and then push out new configurations as I test/implement them. Thanks in advance.

Hello everyone, I was wondering if anyone has experience in the field in migrating SCOM 2007 to SCOM 2012 R2. I understand there are effectively 2 methodologies: in-place or standalone upgrade. But apart from exporting/importing Management Packs, what other areas need be to looked at? How can you tell if an MP is using unsupported features in 2012? Looking forward to hearing any experiences you can provide. Thank you :-)

Just wondering if anyone had a recommended best practice for page file size and settings for Windows Server 2012. Does the old 1.5 X installed memory rule still apply? A quick Google found this: http://social.technet.microsoft.com/wiki/contents/articles/13383.best-practices-for-page-file-and-minimum-drive-size-for-os-partition-on-windows-servers.aspx What is everyone out there using for their page file settings? Thanks!