Install SCOM 2022 on Windows Server 2022

Mike 2 20 Reputation points
2024-05-30T21:27:08.9133333+00:00

Hi, I have evaluations of Windows Server 2022, SQL Server 2022 and SCOM 2022. I have a Windows Server VM on VMware Workstation. I want to install SCOM. I'm using this link "https://kevinholman.com/2022/05/01/scom-2022-quickstart-deployment-guide/." It's just me at Home. I'm having problems joining a Dummy Domain (.LOCAL.) I'm getting the error "The error was: "DNS name does not exist." I'm using a Static IP. On the VM. My question is, how do I join the VM to a Dummy Domain? At Home? Is .LOCAL deprecated? What should I use? Also, do I need to join a Domain BEFORE Installing SQL Server? I think I need to Install SSRS before Promoting to a Domain Controller (DC.) And I think I shouldn't Install SQL on a Domain Controller. So I'd like to install SQL Before promoting to DC. But I'd like to install SQL AFTER joining a fake Dummy Domain. For Users etc... So, can anyone help? Join a Domain? .LOCAL? Please reply. Thanks

Microsoft System Center
Microsoft System Center
A suite of Microsoft systems management products that offer solutions for managing datacenter resources, private clouds, and client devices.
883 questions
SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,091 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,436 questions
{count} votes

7 answers

Sort by: Most helpful
  1. Mike 2 20 Reputation points
    2024-05-30T22:48:40.61+00:00

    Here's the full error Message...

    The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "xxxxx.LOCAL":

    The error was: "DNS name does not exist."

    (error code 0x0000232B RCODE_NAME_ERROR)

    The query was for the SRV record for _ldap._tcp.dc._msdcs.xxxxx.LOCAL

    Common causes of this error include the following:

    • The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:

    192.168.xx.x

    • One or more of the following zones do not include delegation to its child zone:

    xxxxx.LOCAL

    LOCAL

    . (the root zone)

    ***So, how do I join a fake Domain? What should I use besides ".LOCAL"? I see a lot on the web about this Error. I'm not sure how it relates to me at Home. Dummy Domain. Please reply. Thanks

    0 comments No comments

  2. AlexZhu-MSFT 5,551 Reputation points Microsoft Vendor
    2024-05-31T07:13:14.9466667+00:00

    Hi Mike,

    To setup the test environment, we need at least 2 virtual machines, one is the domain controller, and the other is the database server and operations manager.

    Since the domain is intranet (not Internet facing), we can name it whatever we want, for example, home.companyname.com, companyname.com.local, companyname.com.lcl or even microsoft.com if you like. For Internet facing domain, we should consider the conflict with existing domains.

    In one VM, we install the ADDS role and promote it to domain controller and in the other VM, we join it to the domain created and continue with the remaining staff.

    For DC setup, you can refer to this guide. For SCOM 2022, the guide can be referenced.

    If there is anything unclear, feel free to drop a note here.

    Regards,

    Alex

    0 comments No comments

  3. Mike 2 20 Reputation points
    2024-05-31T18:13:54.1866667+00:00

    Hi, thanks for your reply. I will try (2) VM's. One with a DC. And I will try your Link. I had SCOM working once on a VM. Without a second VM. But the DC makes sense. Explains the Error. DNS. I will report back. Thanks

    0 comments No comments

  4. Mike 2 20 Reputation points
    2024-06-01T04:18:42.4666667+00:00

    Hi, I'm back... I created a second Server 2022 VM. Added AD_DS, DHCP and DNS. Promoted to a Domain Controller. (xxx.LOCAL.) And added IIS. From the Guide. I went back to the first VM. Clicked "Workgroup" and tried connecting to a Domain. I got the same error. DNS. The (2) VM's can ping each other. But it won't connect to the Domain. How should I connect them? Also, what should I use for DNS address? I'm using (2) Static IP's and (1) DNS Entry from ipconfig. (I used the same IP's DHCP was using.) Including the DNS Address. Just one Address. I've read about using 127.0.0.1 for DNS. For Server 2022. So, what should I use for a Static DNS? And how do I connect to the DC? DNS? Thanks again for the fast reply. Here's a log from "C:\Windows\debug\dcdiag.txt." Can anyone take a look?

    dcdiag.txt

    0 comments No comments

  5. Mike 2 20 Reputation points
    2024-06-01T04:27:47.7+00:00

    Is the problem my DNS? IP?

    "The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:"

    0 comments No comments