Jump to content




anyweb

How can I install System Center Configuration Manager version 1606 (Current Branch) on Windows Server 2016 with SQL 2016



Recommended Posts

Introduction

In a previous guide I showed you how to install System Center Configuration Manager version 1511 (Current Branch) on Windows Server 2012R2. Times are changing fast in this cloud-first mobile-first world, and as a result the System Center Configuration Manager (Current Branch) releases are being released rapidly. In addition to these releases are new Windows Server and SQL Server releases.

 

Now that these new releases are all supported to run together, this guide will show you how to quickly install System Center Configuration Manager version 1606 (Current Branch) on Windows Server 2016 using SQL Server 2016, and then upgrade it to System Center Configuration Manager version 1610 (Current Branch). We use System Center Configuration Manager version 1606 (Current Branch) in this guide as it is the latest baseline version available on Microsoft's Volume License Service Center site (as of time of writing, December 2016).

 

Some PowerShell knowledge is desired. I will show you how to do most actions manually as well as automated.

 

Assumptions

In this guide I assume you have already installed two workgroup joined servers running Windows Server 2016 (choose Windows Server 2016 Standard (Desktop Experience)) as listed below, and that you've configured the network settings. I also assume you have some knowledge of PowerShell, if you don't, start learning it now !

 

Server name: AD01

Server status: Workgroup joined

  • IPv4 Address: 192.168.4.1
  • Subnet Mask: 255.255.255.0
  • Default Gateway: 192.168.4.199
  • DNS: 192.168.4.1

Server name: CM01

Server status: Domain joined

  • IPv4 Address: 192.168.4.2
  • Subnet Mask: 255.255.255.0
  • Default Gateway: 192.168.4.199
  • DNS: 192.168.4.1

Server name: Smoothwall

Server roles: A Linux firewall for sharing internet into these virtual machines, in hyperv you can add two legacy nics to achieve this.

 

Scripts used in this guide

The scripts used in this guide are available at the bottom of the guide in the Downloads section, download them before beginning and extract them to C:\scripts on your destination server(s).

 

Step 1. Configure Active Directory Domain Services (ADDS)

Note: Perform the following on the AD01 as Local Administrator on the workgroup joined server.

 

workgroup joined.png

 

To setup Active Directory Domain Services you could manually click your way through the appropriate wizard in Server Manager or automate it using PowerShell. For your benefit I'll show you both methods below, all you have to do is choose which one suits you.

 

Method #1 - Do it manually

1. To manually setup ADDS, in the start screen search for Server Manager

 

server manager.png

 

2. Click on Add roles and features, for Installation Type choose Role-based or Feature-based installation

 

role based or feature based.png

 

3. For Server Selection choose the local server (AD01)

 

select a server from the pool.png

 

4. For Server Roles select Active Directory Domain Services and DNS Server, answer yes to install any required components.

 

server roles.png

 

5. Continue the the wizard and click Install, then click Close to complete the wizard.

 

6. After it's finished, perform the Post Deployment Configuration by clicking on Promote this server to a domain controller

 

post deployment configuration.png

 

select the Add a new forest option, give it a root domain name such as windowsnoob.lab.local and click through the wizard, when prompted for the password use P@ssw0rd.

 

domain controller options.png

 

Method #2 - Automate it with PowerShell

To configure ADDS automatically, use the ConfigureADDS.ps1 PowerShell script.

 

1. Copy the script to C:\scripts.

2. Edit the variables as desired before running.

3. Start Windows PowerShell ISE as Administrator and run the script by clicking on the green triangle.

 

configure adds running.png

 

Step 2. Join CM01 to the domain

Note: Perform the following on the CM01 as Local Administrator on the workgroup joined server.

 

Method #1 - Do it manually

 

To join the domain manually, bring up the computer properties. Click on Change settings beside the computer name, click Change and enter the appropriate domain join details, reboot when done.

 

domain join manual.png

 

Method #2 - Automate it with PowerShell

To join the domain automatically, use the joindomain.ps1 PowerShell script.

 

1. Copy the script to C:\scripts.

2. Edit the variables as desired before running.

3. Start Windows PowerShell ISE as Administrator and run the script by clicking on the green triangle.

 

joindomain.png

 

 

Step 3. Create users
Note: Perform the following on the Active Directory Domain Controller server (AD01) as Local Administrator

You can do this step manually or automated using the supplied PowerShell script.

 

Method #1 - Do it manually

To create users manually, add the following users in AD using Active Directory Users and Computers:

 

* <your user name>, a domain user, this user will become a local administrator on CM01
* Testuser, a domain user
* CM_BA, used for building ConfigMgr created images

* CM_JD, used for joining computers to the domain
* CM_SR used for reporting services.
* CM_CP, a domain user used when installing the Configuration Manager Client for Client Push.
* CM_NAA, a domain user, (Network Access Account) used during OSD

 

Method #2 - Automate it with PowerShell

To create users automatically, use the Create Users Usergroups and OUs in AD.ps1 PowerShell script.

 

Tip: You need to edit the script and adjust the variables to your liking, for example if you want to change the default password. You may also want to rem out the MDT and MBAM user/groups that are created and change some of the user names within the script. To rem out a line place a # in front of it.

 

1. Copy the script to C:\scripts.

2. Edit the variables [lines 68-80] as desired before running.

3. Start Windows PowerShell ISE as Administrator and run the script by clicking on the green triangle.

 

After running the PowerShell script in Windows PowerShell ISE you'll see something like the following.

 

create users powershell.png

 

Step 4. Create the System Management Container
Note: Perform the following on the Active Directory Domain Controller server (AD01) as Local Administrator

 

For details of why you are doing this see https://technet.microsoft.com/en-us/library/gg712264.aspx.

 

Method #1 - Do it manually

Open ADSI Edit, click on Action, Connect To and click Ok, Double Click on Default Naming Context and the DC= that appears below it. Click on the + and scroll down to CN=System. Right Click on CN=System and choose New, Object, choose Container from the options, click Next and enter System Management as the value as shown below

 

system management container.png

 

Method #2 - Automate it with PowerShell

To create the System Management container automatically, use the Create System Management container.ps1 PowerShell script.

 

Step 5. Delegate Permission

Note: Perform the following on the Active Directory Domain Controller server (AD01) as Local Administrator

 

Method #1 - Do it manually

Open Active Directory Users and Computers. Click on view, select Advanced Features. Select the System Management Container, and right click it, choose All Tasks and Delegate Control.

 

delegate control.png

 

When the Welcome to Delegation of Control Wizard appears click next, then click Add. click on Object Types, select Computers. Type in your Configuration Manager server name (CM01) and click on Check Names, it should resolve. Click Ok, then Next.

 

create a custom task to delegate.png

 

Choose Create a Custom Task to Delegate, click next, make sure This folder, existing objects in this folder and creation of new objects in this folder is selected. Click next, select the 3 permissions General, Property-Specific and Creation-deletion of specific child objects are selected then place a check mark in Full Control.

 

Tip: Repeat the above process for each site server that you install in a Hierarchy.

 

Method #2 - Automate it with PowerShell

To delegate permissions to the System Management container automatically, use the Delegate Permissions.ps1 PowerShell script on CM01. That's right, on the ConfigMgr server.

 

 

Step 6. Install Roles and Features on CM01

Note: Perform the following on the Configuration Manager server (CM01) as a Local Administrator

 

To support various features in System Center Configuration Manager, the setup wizard requires some Server Roles and Features pre-installed. On CM01, login as the username you added to the Local Administrators group and navigate to C:\scripts. The XML files within the Scripts Used in This Guide.zip were created using the Export Configuration File option in Server Manager after manually installing roles and features and the accompanying PowerShell script simply installs it.

 

Note: Make sure your Server 2016 media is in the drive specified in the script or edit the script to point to the location of the media.

 

Method #2 - Automate it with PowerShell

To install the roles and features needed, start Windows Powershell ISE as Administrator and run the install roles and features.ps1 script.

 

install roles and features cm01.png

 

Step 7. Download and install Windows ADK 10 version 1607

Note: Perform the following on the Configuration Manager server (CM01) as a Local Administrator

 

The ConfigMgr prerequisite checker will check for various things, including ADK components such as USMT and Windows Preinstallation Environment (amongst others), therefore you need to install Windows ADK on your server. To do so, either download ADKsetup from here and manually install it or run the setup ADK and WDS.ps1 PowerShell script to download and install the correct components for you. This script not only downloads the components needed, it's also installs ADK 10 and then installs Windows Deployment Services. The setup ADK and WDS.ps1 PowerShell script is available in the Scripts Used in this Guide zip file.

 

Method #2 - Automate it with PowerShell

To download and then install Windows ADK 10 with the components needed, start Windows Powershell ISE as Administrator and run the setup ADK and WDS.ps1 script.

 

setup ADK and WDS.png

 

Step 8. Install SQL Server 2016

Note: Perform the following on the Configuration Manager server (CM01) as a Local Administrator

 

The following script will create a ConfigurationFile.ini used to automate the installation of SQL Server 2016, and after it's installed the script will download the SSMS exe (Management Studio) and install it. SQL Server no longer comes with the Management Studio and it's offered as a separate download, don't worry though, my PowerShell script takes care of that for you.

 

Note: Make sure your SQL Server 2016 media is in the drive specified in the script or edit the script to point to the location of the media.

 

Method #2 - Automate it with PowerShell

To install SQL Server2016 use the Install SQL Server 2016.ps1 script.

 

1. Copy the script to C:\scripts.

2. Edit the variables [lines 17-75] as desired before running.

3. Start Windows PowerShell ISE as Administrator and run the script by clicking on the green triangle.

 

install sql server 2016.png

 

Step 9. SQL Memory Configuration

Note: Perform the following on the Configuration Manager server (CM01) as a Local Administrator

Depending on your memory configuration and server setup, you may also want to configure SQL memory limits as per the following guidance prior to installing ConfigMgr otherwise you'll get warnings in the Prerequisite checker when it runs the Server Readiness checks.

  • Configuration Manager requires SQL Server to reserve a minimum of 8 gigabytes (GB) of memory for the central administration site and primary site and a minimum of 4 gigabytes (GB) for the secondary site. This memory is reserved by using the Minimum server memory setting under Server Memory Options and is configured by using SQL Server Management Studio. For more information about how to set a fixed amount of memory, see here.
  • If your SQL Server is configured for unlimited memory usage, you should configure SQL Server memory to have a maximum limit.

Method #1 - Do it manually

Open Management Studio, select CM01, right click, choose Properties, select memory and configure the values as appropriate for your environment.

 

8192.png

 

Method #2 - Automate it with PowerShell

Use the following PowerShell in ISE on the server that you installed SQL Server 2016 on, thanks go to SkatterBrainz for the code snippet, you might want to adjust the $SqlMemMin and $SqlMemMax variables to suit your environment.

$SqlMemMin = 8192
$SqlMemMax = 8192
[System.Reflection.Assembly]::LoadWithPartialName('Microsoft.VisualBasic') | Out-Null
[System.Reflection.Assembly]::LoadWithPartialName('Microsoft.SqlServer.SMO') | Out-Null
$SQLMemory = New-Object ('Microsoft.SqlServer.Management.Smo.Server') ("(local)")
$SQLMemory.Configuration.MinServerMemory.ConfigValue = $SQLMemMin
$SQLMemory.Configuration.MaxServerMemory.ConfigValue = $SQLMemMax
$SQLMemory.Configuration.Alter()

Step 10. Restart the Server

Note: Perform the following on the Configuration Manager server (CM01) as a Local Administrator

 

Open an administrative command prompt and issue the following command:

shutdown /r

Step 11. Install the WSUS role

Note: Perform the following on the Configuration Manager server (CM01) as a Local Administrator

 

Now that SQL server is installed, we can utilize that for the WSUS database. To install WSUS and configure it to use the SQL servers database instead of the Windows Internal Database, do as follows:

 

Method #1 - Do it manually

<Coming soon>

 

Method #2 - Automate it with PowerShell

 

Browse to the location where you extracted the scripts, C:\scripts. Start Windows PowerShell ISE as administrator, open the Install roles and features_WSUS.ps1 script, edit the $servername variable and replace CM01 with the ServerName your are installing ConfigMgr on (SQL server). Make sure to have your Windows Server 2016 SXS media in the path referred to by $Sourcefiles.

 

install wsus.png

 

Step 12. Download and extract the ConfigMgr content

Note: Perform the following on the Configuration Manager server (CM01) as a Local Administrator

 

To install System Center Configuration Manager version 1606 you'll need to download the content. You can download it from Microsoft's Volume license site for use in production or from MSDN for use in a lab. The VLSC download can be found be searching for Config and then selecting System Center Config Mgr (current branch and LTSB 1606) as shown below.

 

vlsc.png

 

Method #1 - Do it manually

For the purposes of this guide I used the 1606 release from VLSC. This iso is named SW_DVD5_Sys_Ctr_ConfigMgrClt_ML_1606_MultiLang_ConfMgr_SCEP_MLF_X21-16461.ISO and is 1.20GB in size.

 

Once downloaded, I mounted the ISO in Windows File Explorer and copied the contents to C:\Source\SCCM 1606 on CM01.

 

sccm1606.png

 

Step 13. Download the ConfigMgr Prerequisites

Note: Perform the following on the Configuration Manager server (CM01) as a Local Administrator

 

You can download the prerequisites during ConfigMgr setup or in advance. As you'll probably want to install more than one copy of ConfigMgr (one lab, one production) it's nice to have the prerequisites downloaded in advance. To do that, open a PowerShell prompt with administrative permissions and navigate to the following folder:

 

C:\Source\SCCM 1606\smssetup\bin\X64

 

Run the following line

.\SetupDL.exe C:\Source\Downloads

download prereqs.png

 

Tip: Browse to C:\source\SCCM 1606\SMSSETUP\TOOLS and double click on CMTrace.exe, answer Yes to the default logging question. Then, using Windows File Explorer, browse to C:\ and double click on ConfigMgrSetup.log which will open the log file in CMTrace. This will allow you to view any errors or problems with the download of the prerequisites in real time.

 

cmtrace prepres.png

 

Step 14. Extend the Schema

Note: Perform the following on the Domain controller server (AD01) as Administrator. You do not have to extend the Active Directory schema if it was already extended for Configuration Manager previously.

 

1. Using Windows File Explorer on the Active Directory Domain Controller, browse to \\<server>\c$\Source\SCCM 1606\SMSSETUP\BIN\X64 where <server> is your ConfigMgr server

2. locate extadsch.exe, right click and choose Run As Administrator.

3. A command prompt window will appear briefly as the schema is extended, check in C:\ for a log file called ExtADSch.log it should look similar to this

 

 

schema extended.png

 

Step 15. Install SCCM Current Branch (version 1606)

Note: Perform the following on the ConfigMgr server (CM01) as Administrator.  If you are NOT using eval (as in my example) then you need to add this section to the configuration.ini file

[SABranchOptions]
SAActive=1
CurrentBranch=1

Method #1 - Do it manually

<Coming soon>

 

Method #2 - Automate it with PowerShell

You will need to edit the Install SCCM Current Branch version 1606.ps1 script and replace the variables inside with those that work in your environment. For example, to change the ProductId open the script in Windows ISE, locate the line that reads $ProductID= and either enter your ConfigMgr Product Key or use the evaluation version of ConfigMgr by entering the word EVAL.

 

1. Copy the script to C:\scripts.

2. Edit the variables [lines 16-17 & lines 32-57] as desired before running.

3. Start Windows PowerShell ISE as Administrator and run the script by clicking on the green triangle.

 

install sccm 1606.png

 

Once the script completes successfully, System Center Configuration Manager Current Branch (version 1606) is installed.

 

1606 installed.png

 

Note: Currently there is a bug when using System Center Configuration Manager 1606 (Current Branch) and Windows ADK 1607 when used with Windows Server 2016 and SQL Server 2016, in that the boot images will not be created. The error shown in ConfigMgrSetup.log will be "ERROR: Failed to call method ExportDefaultBootImage. Error 0x80041013". If you experience this issue add your voice to Microsoft Connect ID 3116118. The solution at this point is to continue onto the next step and use Upgrades and Servicing to upgrade to System Center Configuration Manager 1610 (Current Branch). After completing that upgrade, the ADK 1607 boot images will be correctly added to ConfigMgr.

 

Step 16. Upgrade to SCCM Current Branch (version 1610)

Note: Perform the following on the ConfigMgr server (CM01) as Administrator.

 

Method #1 - Do it manually

As the upgrade process is a whole blog post by itself, please follow my guide here.

 

Summary

In this guide you used a lot of PowerShell to automate most of Installing System Center Configuration Manager Current Branch (version 1606), including installing and configuring SQL Server 2016 on Windows Server 2016. You then upgraded to version 1610 using Updates and Servicing.

 

Related Reading

  • Configuration Manager and the Windows ADK for Windows 10, version 1607 here.
  • Documentation for System Center Configuration Manager here.
  • What's new in version 1610 of System Center Configuration Manager here.
  • Recommended hardware for System Center Configuration Manager here.
  • Supported operating systems for sites and clients for System Center Configuration Manager here.
  • Support for SQL Server versions for System Center Configuration Manager here.
  • Use a command line to install System Center Configuration Manager sites here.
  • Supported operating systems for System Center Configuration Manager site system servers here.
  • Install-WindowsFeature here.

Downloads

You can download a Microsoft Word copy of this guide here dated 2016/12/6 How can I install System Center Configuration Manager version 1606 (Current Branch) on Windows Server 2016 with SQL 2016.zip

 

You can download the PowerShell scripts used above here Scripts Used In This Guide.zip

  • Like 1

Share this post


Link to post
Share on other sites


 

Hello,

very good job. In Step 9. SQL Memory Configuration should the maximum Value for SQL Server Memory not be also 8192 (192 make no sense)!

  • Like 1

Share this post


Link to post
Share on other sites

yes of course it was a screen capture error which I have now fixed, well spotted!

Share this post


Link to post
Share on other sites

that comes later, the focus here was sql server 2016 on windows server 2016 with the latest Current Branch baseline installer

  • Like 1

Share this post


Link to post
Share on other sites

Here's a chunk of PowerShell that I use for setting SQL memory limits, in case it helps...

$SqlMemMin = 8192
$SqlMemMax = 8192
[System.Reflection.Assembly]::LoadWithPartialName('Microsoft.VisualBasic') | Out-Null
[System.Reflection.Assembly]::LoadWithPartialName('Microsoft.SqlServer.SMO') | Out-Null
$SQLMemory = New-Object ('Microsoft.SqlServer.Management.Smo.Server') ("(local)")
$SQLMemory.Configuration.MinServerMemory.ConfigValue = $SQLMemMin
$SQLMemory.Configuration.MaxServerMemory.ConfigValue = $SQLMemMax
$SQLMemory.Configuration.Alter()

And, forgive me for not saying so in the first place, but thank you for posting this! Very nice work!

  • Like 1

Share this post


Link to post
Share on other sites

Here's a chunk of PowerShell that I use for setting SQL memory limits, in case it helps...

$SqlMemMin = 8192
$SqlMemMax = 8192
[System.Reflection.Assembly]::LoadWithPartialName('Microsoft.VisualBasic') | Out-Null
[System.Reflection.Assembly]::LoadWithPartialName('Microsoft.SqlServer.SMO') | Out-Null
$SQLMemory = New-Object ('Microsoft.SqlServer.Management.Smo.Server') ("(local)")
$SQLMemory.Configuration.MinServerMemory.ConfigValue = $SQLMemMin
$SQLMemory.Configuration.MaxServerMemory.ConfigValue = $SQLMemMax
$SQLMemory.Configuration.Alter()

And, forgive me for not saying so in the first place, but thank you for posting this! Very nice work!

 

thanks for the code update and the comments, i appreciate it :-)

Share this post


Link to post
Share on other sites

One thing about using the unattend setup file and giving it a real product key rather than EVAL. If you do that, you'll need to add this to your configuration ini file:

[SABranchOptions]
SAActive=1
CurrentBranch=1

The official documentation on these is sort of confusing: https://docs.microsoft.com/en-us/sccm/core/understand/install-the-ltsb

It implies that maybe those should go under [Options] rather than get their own section, and also has the name of the SAActive key incorrect (It's SSActive on that page, but the actual key is SAActive). But it does explain what the 1s and 0s mean for those two keys.

  • Like 1

Share this post


Link to post
Share on other sites
On 12/29/2016 at 9:04 PM, FISHMANPET said:

One thing about using the unattend setup file and giving it a real product key rather than EVAL. If you do that, you'll need to add this to your configuration ini file:


[SABranchOptions]
SAActive=1
CurrentBranch=1

The official documentation on these is sort of confusing: https://docs.microsoft.com/en-us/sccm/core/understand/install-the-ltsb

It implies that maybe those should go under [Options] rather than get their own section, and also has the name of the SAActive key incorrect (It's SSActive on that page, but the actual key is SAActive). But it does explain what the 1s and 0s mean for those two keys.

 

thanks for clarifying that, I never got around to it due to time constraints and went the eval route for my blog post, along with a follow up here > How can I change System Center Configuration Manager from an Eval edition to a Licensed edition ?

I've also added this point to the guide, thanks again !

Share this post


Link to post
Share on other sites

Thanks for another great post.

Just a qq, what are the rights do i need to assign for the created users?

* CM_BA, used for building ConfigMgr created images

* CM_JD, used for joining computers to the domain
* CM_SR used for reporting services

And CM_NAA, a domain user and CM_CP, a domain user just regular user accounts?

 

And do i need to open the ports 1433, 4022 for SQL with this install?

I see ports are open in PS script......Big Thank you.

 

Thank you,

Share this post


Link to post
Share on other sites

all the users are regular user accounts and yes do open the sql ports

Share this post


Link to post
Share on other sites

Thank you for reply. After SQL installation SQL browser and SQL Server Integration services are not running, is that normal?

Also should i change the log and backup path to a different drive "other then c:\"

Thank you,

Share this post


Link to post
Share on other sites

you can adjust the SQL services as you require them, but this script should be enough to get you up and running with SCCM in a SQL Server 2016 environment, I have it running just fine in 3 labs

 

as regards where you store the logs that only really matters if the drives are on different spinning disks

Share this post


Link to post
Share on other sites

Thank you for this comprehensive guide! Very easy to follow.

A question about 'Step 11. Install the WSUS role'. After this step, I see a 'Windows Internal Database' service running, but aren't we suppose to avoid that since we already installed a SQL Server?

 

 

Share this post


Link to post
Share on other sites

good point, i see a reference to it in the wsus xml file but it still uses the SQL DB, and in my lab the wid services are not even running are they running on yours ?

i'll see what i can find out in my lab...

Share this post


Link to post
Share on other sites

mystery solved, when generating the XML i add WSUS via the server manager, and as part of that process it automatically adds required features including WID, see here

wsus wid.png

Share this post


Link to post
Share on other sites

I expected that also. And yes, WID was running in my Lab. May I assume you are going to update your script repository and make it available to us?

Share this post


Link to post
Share on other sites

WID is required, see the screenshot. You can try manually removing it and scripting that yourself but why worry you are not using it, wsus is using SQL for the DB

Share this post


Link to post
Share on other sites

this might be enough, please test

 

Uninstall-WindowsFeature -Name Windows-Internal-Database -Restart

 

Share this post


Link to post
Share on other sites

Thank you, i already uninstalled WID feature and SCCM still works perfectly. I thought it would be cleaner to follow your guide without removing things afterwards. By the way, this guide does not mention about Reporting Services role e.g. which is also an important part when working with SCCM. But luckily i found your other guide else where in this website. I do haave Powershell scripts for this ready. Let me know and I'll send it to you to review. Hope I can contibute since you help the community a lot already. Kind regards.

  • Like 1

Share this post


Link to post
Share on other sites

for the next release of this guide (for SCCM 1702 or whichever release becomes the next baseline), i'll update the code then, thanks and feel free to add your contribs here or elsewhere in windows-noob, that's what it's all about :)

Share this post


Link to post
Share on other sites
On 4/2/2017 at 9:28 AM, anyweb said:

for the next release of this guide (for SCCM 1702 or whichever release becomes the next baseline), i'll update the code then, thanks and feel free to add your contribs here or elsewhere in windows-noob, that's what it's all about :)

The short version for installing Reporting services:

Add-CMReportingServicePoint -SiteCode <sitecode> -SiteSystemServerName <FQDNserver> -UserName <credential> -ReportServerInstance MSSQLSERVER

And speaking of 1702, there is a new exiting tool called Content Library Cleanup tool - finally! Check it out.

 

  • Like 1

Share this post


Link to post
Share on other sites

Great stuff as always. Thanks for your efforts.

I'm getting this error when I try to install 1606 on Server 2016 with SQL 2016 from your powershell script:
 

Quote

ERROR: Error reading branch status. SAActive and CurrentBranch needs to be specified when installing a CAS or standalone primary site.

I've stepped back through the setup, roles, prereqs, etc. and can't find the issue. The ConfigMgrSetup.log section where it fails has a lot of INFO: SQL blah blah entries, but everything looks OK in SQL as far as I can tell. Google and Bing bring up nothing remotely close to that error message.

Any ideas?

Thanks in advance.

Edit: Hmmm...Software Assurance? My keys are correct...

Share this post


Link to post
Share on other sites

if you are NOT using eval (as in my example) then you need to add this section to the configuration.ini file

 

[SABranchOptions]
SAActive=1
CurrentBranch=1

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×