Adding a Windows Server 2019/2016 Domain Controller
KB ID 0001262 Problem Once upon a time, adding a domain controller that was running a newer version of the Windows Server family involved opening command line and schema prepping, and GP prepping etc. Now all this happens in the background when adding a 2019 domain controller and the wizard is doing the heavy lifting for you. Solution 2008 to 2019 Domain Controller 2008 to 2016 Domain Controller Obviously the server needs to be a...
Add a 2012 Domain Controller to a 2008 Domain
KB ID 0000680 Problem This is considerably less painfull than adding a 2008/2008 R2 domain controller to a 2003 domain was. You dont have to maually prep the schema on the schema master, or run forestprep and domainprep. The wizard does everything for you. Solution 1. Launch server manager from the taskbar > Select Local Server > Manage > Add Roles and Features. 2. Role Based… > Next. 3. Select local server >...
Install SCCM 2007 on Windows Server 2008 R2 – Step by Step
KB ID 0000297 Problem I had to work out how to do this for a client, and as is my modus operandi, I’ll try and save you some of the pain I endured, Products Used System Center Configuration Manager 2007 SP2 Windows Server 2008 R2 SQL 2008 R2 (At time of writing neither officially supported or not supported on SCCM) Note: I was originally going to use SQL 2005 – hence the reason the SQL servers name is SCCM-SQL2005, however...
Exchange 2010 SP3 – Can I Upgrade to Exchange 2013
KB ID 0000770 Problem At the time of writing (14/02/13), the answer is NO, for full coexistence with Exchange 2013 you need to have Exchange 2013 CU1 (Cumulative Update), which at this time is unreleased (Expected Q1 of 2013 – so we are not far away). Note: CU2 is now released. Solution So What do I get with Exchange 2010 SP3? 1. You can install Exchange 2010 on Windows Server 2012, (though you can’t in-place upgrade the...
ADPREP /FORESTPREP error “There is a schema conflict with Exchange 2000”
KB ID 0000257 Problem Seen when running “adprep /forestprep” to raise the domain schema to Windows Server 2003. Error: Adprep was unable to extend the schema. [Status/Consequence] There is a schema conflict with Exchange 2000. The schema is not upgraded. [User Action] The schema conflict must be resolved before running adprep. Resolve the schema conflict, allow the change to replicate between all replication partners, and...