Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update prepare-environment.md #8015

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update prepare-environment.md #8015

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion WindowsServerDocs/manage/windows-admin-center/deploy/prepare-environment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,7 +118,11 @@ Microsoft Hyper-V Server 2012 R2 is now ready for management with Windows Admin

## Port configuration on the target server

Windows Admin Center uses the SMB file sharing protocol for some file copying tasks, such as when importing a certificate on a remote server. For these file copy operations to succeed, the firewall on the remote server must allow inbound connections on port 445. You can use the Firewall tool in Windows Admin Center to verify the incoming rule for ‘File Server Remote Management (SMB-In)' is set to allow access on this port.
Windows Admin Center uses the SMB file sharing protocol for some file copying tasks, such as when importing a certificate on a remote server. For these file copy operations to succeed, the firewall on the remote server must allow inbound connections on port 445. You can use the Firewall tool in Windows Admin Center to verify the incoming rule for ‘File Server Remote Management (SMB-In)' is set to allow access on this port.

In addition to file sharing, certain operations in Windows Admin Center rely on the EventLog Remoting Protocol, which depends on RPC for message transport. When RPC is used by the EventLog Remoting Protocol, it utilizes named pipes as its transport mechanism. Named pipes, in turn, rely on the Server Message Block (SMB) Protocol.

The EventLog Remoting Protocol is often used in conjunction with the Windows Remote Registry Protocol, as specified in [MS-RRP], because several aspects of the event log configuration are managed by modifying the registry rather than through the EventLog Remoting Protocol itself.

> [!Tip]
> Ready to install Windows Admin Center? [Download now](../overview.md#download-now)