Jump to content


How can I install System Center Configuration Manager (Current Branch) version 1902 on Windows Server 2019 with SQL Server 2017 - Part 1

Recommended Posts

Hi, Could you please help on fixing the error in management point in site configration.. I am getting this error in MPSetup log file :  Fatal MSI Error - mp.msi could not be installed.

mp.msi exited with return code: 1603
Backing up C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError
Fatal MSI Error - mp.msi could not be installed.

Do you have any solution on fixing this please? any link to follow?

Share this post

Link to post
Share on other sites


You wrote:

"Note: The SCCM 1902 Current Branch media is not yet available on MSDN or VLSC. When the new baseline media is released I'll update this note. In the meantime you can download the baseline media ISO from the Microsoft evaluation site here. This will be the same media that will make it's way to MSDN and VLSC. Once downloaded, extract the media to C:\Source\SCCM1902."

Since it now has been released, would you care to update your note?

Also - this terrific series could be seriously improved were you able to publish Part 8 on boundaries.

Thanks again for putting this all together. And, may I wish you Happy Birthday about 4 days early?


Share this post

Link to post
Share on other sites

Thanks for this.
However, a couple of pointers that could be of great help to a noob....

(base host, MS Surface running Win10 ENT in an office landscape....; this will be a Win10 hyper V lab)

1. HW configuration for the DC - just a single NIC? To which switch should it be attached, default, internal, private or a new custom switch?

2. I'm nervous about installing a DHCP server in an office landscape. A couple of explanatory lines on how to ensure this is done safely would be a great help.


Share this post

Link to post
Share on other sites

hi, if you are planning on doing this on a Surface that's fine as long as it has at least 16GB of ram (minimum) for all the virtual machines, and lots of storage.

for both #1 and #2 configure the switch as PRIVATE that way it won't matter that you are running DHCP as it will be self contained in it's own private network


Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.