56Seeker

A small update: The SQL collation errors are mine! I picked the wrong collation, there's far too many Latin variants.... I don't see a way to correct this retrospectively (I've corrected the individual databases, but the install check still fails); so I guess I'm looking at a roll back....

Well to be honest, I'm a crap scripter and avoid it where possible, so I just followed the manual steps in the guide. That's to say, I slavishly followed the manual steps and didn't change anything. As it's a lab, I even used the same variable values such as IP addressing and domain names. Errors by number: 1 + 3) SQL login. Normally we'd used mixed mode, but the manual steps specified Windows log in. I used the "current user" button in SQL administrators set up as shown in the screen shot in part 4. I did set the database engine as "SQL latin..... as shown in part 4 (which puzzled me, it's not a setting we normally play with, all our prod. databases are running the default setting, which considering the vast majority of our servers are US english OS with DK input, could be anything....). Reviewing Part 4 again, I see no instructions regarding GB108030 support, what ever that is, so I'm googling that right now to see how to remedy. 2) Publishing. I think this is a spurious warning, as I did the schema extensions and permissions as stated. 4) SQL memory. Again, this isn't something we normally fiddle with, and reviewing the article again I can see memory limits are stated in the script, but not in the manual "how-to". 5) RAM. I'll take this as just a warning as it's a laptop lab, RAM and CPU resources are quite limited. 6) No idea. I've installed the features stated, in the order stated. To be fair I haven't checked the associated script to see if it's installing more than the manual "how to". 7) as 6! Luckily I took plenty of snapshots along the way, so I can go back and try again..... (and thanks the help, by the way....)

Following the guide manually, I get the following errors on SCCM install: 1: The logon account for the SQL Server service cannot be a local user account, NT SERVICE\<sql service name> or LOCAL SERVICE. You must configure the SQL Server service to use a valid domain account, NETWORK SERVICE, or LOCAL SYSTEM. (failed) 2: The site server might be unable to publish to Active Directory. The computer account for the site server must have Full Control permissions to the System Management container in its Active Directory domain. You can ignore this warning if you have manually verified these permissions. For more information about your options to configure required permissions, see https://go.microsoft.com/fwlink/p/?LinkId=233190. (warning) 3. Configuration Manager requires that you configure your SQL Server instance and Configuration Manager site database (if already present) to use the SQL_Latin1_General_CP1_CI_AS collation, unless you are using a Chinese operating system and require GB18030 support. For information about changing your SQL Server instance and database collations, see https://go.microsoft.com/fwlink/p/?LinkID=234541. For information about enabling GB18030 support, see https://go.microsoft.com/fwlink/p/?LinkId=234542. (failed) (This surprised me, as I did change to latin, as per the guide, tho' I didn't do anything about GB18030 support) (and the MS links supplied in the error text don't work!) 4. SQL Server is configured for unlimited memory usage. You should configure SQL Server memory to have a maximum limit. (warning) (Didn't see any steps to configure this in the manual process) 5. 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 https://go.microsoft.com/fwlink/p/?LinkId=233759. (warning) 6. Background Intelligent Transfer Service (BITS) is required for the management point and distribution point site system roles. BITS is not installed, IIS 6 WMI compatibility component for IIS7 is not installed on this computer or the remote IIS host, or Setup was unable to verify remote IIS settings because IIS common components were not installed on the site server computer. Also, check if IIS/BITS services are running properly. Setup cannot continue until BITS is installed and enabled in the IIS settings. (warning) (I haven't seen BITS mentioned in the guide yet??) 7. Background Intelligent Transfer Service (BITS) is required for the management point and distribution point site system roles. BITS is not installed, IIS 6 WMI compatibility component for IIS7 is not installed on this computer or the remote IIS host, or Setup was unable to verify remote IIS settings because IIS common components were not installed on the site server computer. Also, check if IIS/BITS services are running properly. Setup cannot continue until BITS is installed and enabled in the IIS settings. (warning)

That's no problem, it's a good surface (I7, 16 gb ram, 1 tb disk). In effect I've two surface NICs available, the ethernet and Wifi, and I can map a switch to either of those two interfaces. I was thinking that communication inside the hosted domain could go through a private switch, but there'll need to be an internet facing link to fetch win updates and similar, so I was thinking of adding an extra Nic to the DC so it could act as the gateway.

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.