HOTSPOT - You need to meet the technical requirements for Server4. Which cmdlets should you run on Server1 and Server4? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Hot Area:
I think this is the other way round. Surely you would use Set-Item on the Workgroup server to "trust" the Server1 that's going to manage it remotely? Otherwise you're setting Server4 to manage Server1 and that's not the requirement?
Then Enable-PSRemoting on Server1 as you can use it for firewall related settings for remote connections. Technically you do this on both servers though, it's not a good question.
Technically these are all missing answers- that don't address the whole situation. both sides need to use set-item and both sides need to be enabled for psremoting. this may be to conservative answer but in the real world i would do :
Server 4
Enable-psremoting
Set-Item WSMan:\localhost\Client\TrustedHosts -Value "Ip of server1" -Force
Server 1
Enable-psremoting
Set-Item WSMan:\localhost\Client\TrustedHosts -Value "Ip of server4" -Force
It doesnt matter what order you run any of these- you will read trusted host is not needed on the domain computer- except- its connected to a non-domain server- so its... needed.
"PowerShell remoting is enabled by default on Windows Server platforms."
https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/enable-psremoting?view=powershell-7.3
So it looks like all you need to do is to add trusted hosts on both sides?
Since no answer was really clear in explanation on why and what, i've tested it, answer given was correct:
Server 4,
Enable-PSRemoting -Force
On Server1, since Server4 is a workgroup server, you'll need to set Server4 as a trusted host for remoting. Run the following on Server1:
Set-Item WSMan:\localhost\Client\TrustedHosts -Value "Server4" -Force
To make this work add Server4 to DNS or Hosts file
Setup connection for testing:
$cred = Get-Credential
Enter-PSSession -ComputerName Server4 -Credential $cred
Type hostname, should see Server4
Exit
Get list of all trustedhosts on Server1:
Get-ChildItem WSMan:\localhost\Client\
or
Get-Item WSMan:\localhost\Client\TrustedHosts
The source computer needs to add the destination computer in "TrustedHosts" file: Set-Item WSMan:\localhost\Client\TrustedHosts -Value "SERVER4-IP" -Concatenate -Force
The destination computer needs to allow remote connection: Enter-PSRemoting
PS: Remoting Powershell is enabled by default in Windows Server (regardless of whether it is in the domain or not) but, in this kind of context, shows that the remote powershell needs to be enabled.
Summary:
Server1 - Set-Item
Server4 - Enable-PSRemoting
if computer A (domain member) has to manage Computer B, and computer B is out of a domain, like Workgroup, Computer B has to be in private network and not public, the you run the command enable-psremoting -force; Computer A doesn't trust computer B, so you need to run Set-Item WSMan:\localhost\Client\TrustedHosts -Value "IP Computer B" -Concatenate -Force. Enjoy!
this is from Co-Pilot
Here are the steps to enable PowerShell remoting on each server:
Open PowerShell with administrative privileges on each server.
Run the following command: Enable-PSRemoting -Force.
If you are in a workgroup environment, add the IP address of the remote host to the trusted hosts list in the local machine 1.
On Server4, run the following command: Set-Item WSMan:\localhost\Client\TrustedHosts -Value <IP address of Server1> -Concatenate.
"PowerShell remoting is enabled by default on Windows Server platforms. "
Don't need to enable it
https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/enable-psremoting?view=powershell-7.3
Start-Service is out of the question
https://learn.microsoft.com/en-us/powershell/module/servermanager/enable-servermanagerstandarduserremoting?view=windowsserver2022-ps
Provides one or more standard, non-Administrator users access to event, service, performance counter, and role and feature inventory data for a server that you are managing by using Server Manager
Answer is correct
https://4sysops.com/archives/enable-powershell-remoting-on-a-standalone-workgroup-computer/
Local (Workgroup) Server Set-Item
Remote (Domain) Server Enable-PsRemoting
Here's a highlighted answer from below link:
https://4sysops.com/wiki/enable-powershell-remoting/#:~:text=On%20workgroup%20group%20computers%20%5E,Value%20%2210.0.2.33%22%20%2DForce
Agree:
Enable-PSRemoting -Force -SkipNetworkProfileCheck
Authentication in PowerShell remoting relies on Active Directory. By default, only computers that are domain members can connect via PowerShell remoting. In a workgroup environment, you have to add the IP addresses of the computers to the TrustedHosts list manually:
Set-Item WSMan:\localhost\Client\TrustedHosts -Value "10.0.2.33" -Force
Wrong!
-SkipNetworkProfileCheck = Indicates that this cmdlet enables remoting on client versions of the Windows operating system when the computer is on a public network. This parameter enables a firewall rule for public networks that allows remote access only from computers in the same local subnet.
This parameter does not affect server versions of the Windows operating system, which, by default, have a local subnet firewall rule for public networks. If the local subnet firewall rule is disabled on a server version, Enable-PSRemoting re-enables it, regardless of the value of this parameter.
upvoted 2 times
...
...
...
This section is not available anymore. Please use the main Exam Page.AZ-800 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
gass
Highly Voted 2 years, 9 months agoPrettyFlyWifi
10 months, 1 week agojohosofat
Highly Voted 2 years, 5 months agoPayday123
1 year, 5 months agoltkiller
Most Recent 2 months, 3 weeks agodump3s
6 months, 3 weeks agosardonique
8 months, 2 weeks agoJoedn
11 months agorknichols01
1 year, 3 months agoPayday123
1 year, 5 months agoMR_Eliot
1 year, 7 months agosyu31svc
2 years agoJohnO1971
2 years, 6 months agoTheUltimateHac
2 years, 11 months agoAnonymousJhb
2 years, 9 months agoVinoTee
2 years, 11 months agoDavoo84
2 years, 11 months agoAS007
2 years, 12 months agoAvoKikinha
2 years, 11 months agoprepper666
2 years, 10 months ago