Pepuri Server world Eng Version

Windows Server 2025 has been released.

To take advantage of the new OS, I'll upgrade the AD Domain Controllers DC01 and DC02 to Windows Server 2025.

In a real-world environment, many factors would need to be considered, but since this is a test environment, I will only cover the basic upgrade process.

The Windows Server 2025 installation image created earlier using Sysprep was utilized.

Test Environment

https://youtu.be/YcF0ztnJJ8A

The process was carried out in the following steps:

1. DC02: Windows Server 2022 Demote

2. DC02: Windows Server 2025 Promote

3. Change the Master role to DC02.

4. DC01: Windows Server 2022 Demote

5. DC01: Windows Server 2025 Promote

6. Change the Master role back to DC01.

Step 1. Remove DC02

Add roles and features

Start the Remove Roles and Features Wizard

Next

Next

Active Directory Domain Services

Remove Features

Demote this domain controller

Next

Proceed with removal -> Next

Next

Next

Demote

Close

Close

Verify that the Domain Controller (DC) has been successfully removed.

After rebooting, proceed with removing the roles again.

Switch the machine to WORKGROUP mode.

Remove DC02 from Active Directory Users and Computers (ADUC).

Yes

Step 2. Install the Domain Controller (DC) role on Windows Server 2025.

Proceed with joining the server to the Active Directory (AD).

Server Manager -> Add roles and features

Next

Next

Next

Active Directory Domain Services

Add Features

Next

Next

Next

Install

Promote this server to a domain controller

Add a domain controller to an existing domain -> Next

Enter the Password and click Next.

Next

Next

Next

Next

Next

Install

Once completed, the system will reboot.

Enter the following command to change the DC Master role to DC02:

Move-ADDirectoryServerOperationMasterRole -Identity DC02 -OperationMasterRole SchemaMaster, DomainNamingMaster, PDCEmulator, RIDMaster, InfrastructureMaster

Netdom query fsmo

Step 3. Remove DC01

Update the DNS Address to point to DC02.

Server Manager -> Add roles and features

Start the Remove Roles and Features Wizard

Next

Active Directory Domain Services

Remove Features

Demote this domain controller

Next

Proceed with removal -> Next

Next

Enter the Password and click Next.

Demote

Close

After rebooting, navigate back to the Roles and Features removal menu and proceed with the Active Directory Domain Services (AD DS) removal process.

Click Close and proceed with the system reboot.

Switch the machine to Workgroup mode.

Remove DC01 from Active Directory Users and Computers (ADUC).

Step 4.. Install DC01

On the new VM for DC01, configure the IP address and set the DNS server to DC02.

Domain Join

Add Roles and features

Next

Next

Next

Active Directory Domain Services -> Next

Promote this server to a domain controller

Next

Enter the Password and click Next.

Next

Next

Next

Next

Install

Click Close, and the system will reboot.

Set DC01 as the Primary DNS and DC02 as the Alternate DNS.

S and DC02 as the Alternate DNS.

Run the following command to change the Master role back to DC01:

Move-ADDirectoryServerOperationMasterRole -Identity DC01 -OperationMasterRole SchemaMaster, DomainNamingMaster, PDCEmulator, RIDMaster, InfrastructureMaster

Netdom query fsmo

Step 5. Raise Forest Functional Level

Active Directory Domains and Trusts

In Active Directory Domains and Trusts, right-click and select Raise Forest Functional Level to upgrade the forest functional level.

Raise

OK

Use the following command to verify the current functional level:

Get-ADDomain |fl name, DomainMode
Get-ADForest |fl Name, ForestMode

Windows Server 2025 has been released.

Whenever a new OS is launched, I create a disk image of the installed system using Sysprep to facilitate testing in a Hyper-V environment.

This method is highly convenient because, when creating a new VM, I can simply copy the disk image file to immediately load the OS.

Although I’ve covered this topic before, I’m writing it again as part of a renewal for a YouTube video.

This is based on Windows Server 2025 and Hyper-V.

https://youtu.be/snj74akjzCA

Hyper-V -> New -> Virtual Machine

Name specification -> Set Default Location -> Next

Name specification -> Set Default Location -> Next

Confirm Generation 2 -> Next

(From 2025, Generation 2 is set as the default.)

Set RAM -> Next

Specify Network Adapter -> Next

Confirm Disk Location -> Next

Specify Installation Disk -> Finish

Double-click on the created VM

Start

Enter the key to proceed with the installation process.

Select Language -> Next

Next

Agree -> Next

Enter Product Key -> Next (I entered an AVMA key as I am using it in a Hyper-V environment.)

Accept

Next

Install

Proceed with Installation

The system will automatically reboot.

Once the installation is complete, the screen will appear as shown. At this point, press Shift + Ctrl + F3 simultaneously.

The system will reboot, and the screen will appear as shown. Select OOBE, Generalize, and Shutdown, then click OK.

Sysprep will run, and once completed, the system will shut down.

Back up the created VHDX disk image. This disk can be used to streamline the OS installation process.

You can select the disk image from the menu below to create a new VM.

https://youtu.be/QduayEDT3DY

I tried to create a Custom Connector to link something created in Azure AI Studio with Copilot Studio.

However, the technical documentation suggests navigating to Data -> Custom Connectors as shown on the screen, but I was unable to find it.

Create a custom connector from scratch | Microsoft Learn

I realized that, while this menu was easily visible in many older YouTube videos, it no longer exists now.

At first, I thought it might be because my license wasn't premium, but that wasn't the case.

After searching through some more recent YouTube videos, I was able to find it.

https://youtu.be/X5654jxAatw?t=703

Power Automate -> More -> Discover all

In the Data section, click on Custom connectors or click the Pin icon to pin it for easy access.

You can now see the Custom connectors menu as shown on the screen.

This time, let's create a flow where a specific message entered into the chatbot is sent as a Teams notification to the person in charge.

With some modifications, you can create automated flows from the chatbot, such as sending emails.

In the existing Copilot, you can see that topics have default settings to trigger actions based on specific conditions.

Here, we will create a flow that sends a Teams notification to the person in charge when Escalate is triggered.

https://youtu.be/NyJqE8SJZ7Q

First, click Settings.

Security -> Authentication

Ensure that the authentication settings are configured as shown on the screen.

(If they are not set up, refer to the SSO setup video and complete the configuration.)

Topics -> Escalate -> Add Node

Call an action -> Create a flow

Add an action

Runtime -> Standard -> Microsoft Teams

Post message in a chat or channel

Select and enter the information as shown on the screen.

Change the flow name

Save draft

Test

Manually -> Publish & Test

Receive messages from Workflows.

Return to the Copilot Studio page -> Click Done.

Add Node -> Call an action -> Escalation Case

Publish

Enter Escalate to run the test.

The permission configuration process is required. -> Connect

Connect

Submit

Confirm the status

Retry

The configured message is delivered, and

You can confirm that it has been delivered to Teams.

With this pattern, you can create various connection flows between M365 and other services using Power Automate.

When troubleshooting in M365, it's common for administrators to use PowerShell for the process.

However, it raises the question of whether this really needs to be done within Copilot Studio. Nonetheless, I decided to write about it since there are tasks that occasionally require PowerShell.

This was carried out with reference to the technical documentation below.

PowerShell support for Power Apps and Power Automate - Power Platform | Microsoft Learn

https://youtu.be/q3fEnEcXH0k

The steps were carried out on Windows 11.

Click the Start button -> Right-click -> Select Terminal (Admin).

Execute the following command:

Install-Module -Name Microsoft.PowerApps.Administration.PowerShell
Install-Module -Name Microsoft.PowerApps.PowerShell -AllowClobber
Set-ExecutionPolicy -ExecutionPolicy Unrestricted

If the following message appears, enter Y or A.

Since Power Apps and Power Automate are different areas, each requires a separate login.

Unlike Exchange Online, there is no need to enter separate connection commands. Simply enter the command you wish to use, and it will prompt you to provide your credentials.

Enter the following command to connect to Power Apps:

Get-AdminPowerAppEnvironment

Enter the following command to connect to Power Automate:

Get-AdminFlow

In the future, if a PowerShell connection is needed for Copilot Studio, you can access and utilize it as required.

In the previous post, a new Copilot was published on the site.

2024.10.05 - [Copilot Studio] - Copilot Studio. Deploying Copilot to an IIS Site.

This time, I have written about how to configure Entra ID and SSO in cases where the organization requires that only authenticated users have access.

The following technical documentation was used as a reference.

Configure user authentication with Microsoft Entra ID - Microsoft Copilot Studio | Microsoft Learn

Configure single sign-on with Microsoft Entra ID - Microsoft Copilot Studio | Microsoft Learn

Entra Admin Center -> Applications -> App registrations -> New registration

After entering the App name, click Register (At this stage, the Redirect URI is optional. The URL below was created based on my test page.).

Navigate to Authentication.

Add the following URL mentioned in the technical documentation.

https://token.botframework.com/.auth/web/redirect

https://europe.token.botframework.com/.auth/web/redirect

Check Access tokens and ID Tokens -> Click Save.

Certificates & secrets -> Client secrets -> New client secret

Input Description  -> Add

Save the Value in advance.

Go to Overview and save the Application ID information.

API permissions -> Add a permission -> Delegated permissions

Add the permissions offline_access, openid, and profile. -> Grant admin consent for Contoso

Go to Copilot Studio and navigate to the Settings menu of the Custom Copilot you want to modify the authentication for.

Security -> Authentication -> Authenticate manually

Select Require users to sign in -> Enter Client ID (App ID) and Client secret (Value) -> Click Save -> Click Publish.

A message indicating that a login is required will appear as shown below.

Access the Copilot web page in a separate browser -> Click Login -> Complete the Login process.

Copy the Validation Code provided after logging in.

Enter a message in the chat window to confirm that the authentication was successful.

Since login cannot be implemented directly in the chat, it seems that the authentication process is carried out using a separate validation code.

By configuring it this way, you can set up security so that only users with an account can access the Custom Copilot.

In the previous post, we created a Custom Copilot that answers questions by crawling specific sites.

2024.10.05 - [Copilot Studio] - Copilot Studio. Create New Copilot

In the last post, we deployed it to Teams. This time, it will publish it to an IIS site.

I am not a developer but an engineer. Please consider this as a guide to understand the overall process and flow.

https://youtu.be/cx4l5QeFwcY

Settings in the upper right corner.

Security -> Authentication

No authentication -> Save

Save

Publish

Publish

Click Channels -> Demo website to verify if the deployed Copilot is functioning correctly on the web.

Ask a question to verify that it is functioning correctly.

Custom website

You will receive the embed code as shown below.

I have set up a test web server on an IIS server using Visual Studio as shown below. Now, let’s add the Copilot to it.

If you would like to build a test environment from scratch, please refer to the articles below.

2024.09.16 - [Microsoft 365/Graph & IIS] - Microsoft Graph & IIS. (1) Setting up the basic testing environment.

2024.09.16 - [Microsoft 365/Graph & IIS] - Microsoft Graph & IIS. (2) Publishing an ASP.NET Sample Page to IIS

I used Visual Studio as the development environment and added the following code to the Index.cshtml file.

<div style="margin-top: 20px;">
    <iframe src="CopilotURL"
            frameborder="0"
            style="width: 500px; height: 500px;">
    </iframe>
</div>

You can also run Copilot on a custom website as shown below.

Previous Post

2024.10.03 - [Copilot Studio] - Copilot Studio. How to check specific SharePoint folders

It took longer to write this post because the Copilot Studio page was not displaying in English.

From this experience, I learned a few things:

1. There is a difference between using English or not in Copilot Studio.

- Two-byte characters like Korean, in particular, could have an impact. It is recommended to test using English first and then check for differences in behavior when using the actual language of use.

2. The default region of Power Platform is important.
- Some regions do not support Copilot Studio. If you try to access https://copilotstudio.microsoft.com from these regions, an error will occur. In this case, you need to create an environment in the Power Platform Admin Center.

Copilot Studio is constantly evolving and changing.

So what is true today might change tomorrow.

Let’s try creating a Copilot in Copilot Studio.

This Copilot is similar to what is commonly called a ChatBot. Some people even call it a "Custom Copilot."

The post was created with reference to the materials below.

Quickstart: Create and deploy a copilot - Microsoft Copilot Studio | Microsoft Learn

https://youtu.be/wrPf5eZf9io

Copilot Studio can be accessed at https://copilotstudio.microsoft.com.

Create -> New copilot

The screen below does not appear in certain languages. I will discuss the impact of the input here in a future post. For now, click Skip to configure.

It is recommended to set the default language to English. I plan to create a Copilot that responds based on the content from the MS Learn site.

After entering the information as shown below, click Add knowledge.

Public websites

Add https://learn.microsoft.com.

Add

Create

Enter a question in the Copilot test chat window on the right to verify that the response is accurate.

You can see that the responses reference content from the MS Learn site.

Settings in the upper right corner.

You can select generative AI responses from the Generative AI menu. This menu is also only available in certain languages.

Publish

I will deploy it so that users can use it in Teams.

Channels at the top -> Microsoft Teams

When you click Open, it will run directly in Teams. If you click Availability options,

You can choose sharing or deployment options.

Click Open in the previous menu to run Copilot in Teams. Select Add or Open.

Ask the Copilot ChatBot questions just like you did during the test.

So, what’s the advantage of using it this way? You might have this question.

The benefit is that you can receive precise answers based on the content of a specific site. BizChat generates fairly good responses. However, since it provides answers based on the Bing engine and references various sources like Wiki and blogs, its accuracy can be lower.

When specifying a SharePoint URL in Copilot Studio, there may be cases where you need to designate only a specific folder.

However, the URL structure in a specific folder may be complicated, making it difficult to designate.

Although it's not specific to Copilot Studio, you can refer to the document below for guidance.

Configure Copilot to use specific SharePoint folders | Microsoft Learn

Check the folder -> Click Open the Details pane at the top.

Path -> Copy direct link

Copy and paste directly in Copilot Studio -> Click Add.

Path successfully added.

Even if the user language is set to English, the Power Platform Admin Center and Copilot Studio pages may not be displayed in English.

I couldn't find any official Microsoft documentation to change this to English.

From the comments on the post below, I found that it is affected by the browser's language settings.

Change language settings in Power platform admin center - Microsoft Community Hub

I will explain based on the Edge browser.

https://youtu.be/KncqZGvB5Ng

https://youtube.com/shorts/hlZLwBGAkKs?feature=share

Go to Settings in the Edge browser.

Add the language you want to set in the Language section -> Click the More Options button.

Click Display Microsoft Edge in this language. If it is grayed out, click Move to the top.

After restarting the browser, the display language will be changed.