SOLVED
Home

Using MMC Snap-Ins remotely

%3CLINGO-SUB%20id%3D%22lingo-sub-277587%22%20slang%3D%22en-US%22%3EUsing%20MMC%20Snap-Ins%20remotely%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-277587%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20there%3B%3C%2FP%3E%3CP%3EJust%20joined%20Microsoft%20Tech%20Community%20and%20I'm%20not%20really%20sure%20if%20it's%20the%20exact%20place%20to%20ask%20about%20this%20problem.%3CBR%20%2F%3EThe%20problem%20is%20that%20I%20have%20set%20up%20a%20virtual%20environment(I'm%20using%20Hyper-V)%20with%202%20virtual%20machines(Windows%20Server%202016%20Data%20Center%20%26amp%3B%20Server%20Core%202016%20Data%20Center)and%20I've%20been%20trying%20to%26nbsp%3Bmanage%20the%20Server%20Core%26nbsp%3Bremotely.%20Despite%20the%20fact%20that%20both%20servers%20have%20been%20added%20to%20the%20Server%20pool%2C%20I%20get%20an%20error%20while%20trying%20to%20set%20the%20appropriate%20firewall%20settings%20for%20MMC%20Snap-Ins.%3C%2FP%3E%3CP%3EI'll%20be%20truly%20grateful%20if%20someone%20helps%20me%20figure%20out%20the%20solution.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F58178iCC61272EB2751017%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Capture.PNG%22%20title%3D%22Capture.PNG%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EThe%20error%20occurs%20when%20I%20try%20to%20enable%20COM%2B%20Network%20Access(DCOM-In)%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-278629%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20MMC%20Snap-Ins%20remotely%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-278629%22%20slang%3D%22en-US%22%3E%3CP%3EOk%2C%20I%20see%20now.%20I%20was%20under%20the%20impression%20you%20were%20working%20between%20the%20two%20Hyper-V%20hosts.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20just%20loaded%20up%20a%20Server%20Core%202016%20and%20Server%202016%20w%2F%20GUI%20(both%20Datacenter)%20and%20can%20confirm%20that%20firewall%20rule%20does%20not%20exist%20on%20ServerCore.%20Here's%20the%20code%20I%20used%20to%20check.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%3EWrite-Host%20%22Server%202016%20with%20GUI%22%0A%3CSPAN%3EGet-NetFirewallRule%3C%2FSPAN%3E%20%E2%80%93Name%20COMPlusNetworkAccess-DCOM-In%20%7C%20select%20Name%2C%20Enabled%0A%3CSPAN%3EGet-NetFirewallRule%3C%2FSPAN%3E%20%E2%80%93Name%20RemoteEventLogSvc-In-TCP%20%7C%20select%20Name%2C%20Enabled%0A%3CSPAN%3EGet-NetFirewallRule%3C%2FSPAN%3E%20%E2%80%93Name%20RemoteEventlogSvc-NP-In-TCP%20%7C%20select%20Name%2C%20Enabled%0AGet-NetFirewallRule%20%E2%80%93Name%20RemoteEentLogSvc-RPCSS-In-TCP%20%7C%20select%20Name%2C%20Enabled%0A%0AInvoke-Command%20-Computer%20ServerCore%20-ScriptBlock%20%7B%0A%20%20%20%20Write-Host%20%22%22%0A%20%20%20%20Write-Host%20%22Server%202016%20Core%22%0A%20%20%20%20%3CSPAN%3EGet-NetFirewallRule%3C%2FSPAN%3E%3CSPAN%3E%20%E2%80%93Name%20COMPlusNetworkAccess-DCOM-In%20%7C%20select%20Name%2C%20Enabled%20%3CBR%20%2F%3E%3C%2FSPAN%3E%3CSPAN%3E%20Get-NetFirewallRule%3C%2FSPAN%3E%3CSPAN%3E%20%E2%80%93Name%20RemoteEventLogSvc-In-TCP%20%7C%20select%20Name%2C%20Enabled%20%3CBR%20%2F%3E%3C%2FSPAN%3E%3CSPAN%3E%20Get-NetFirewallRule%3C%2FSPAN%3E%3CSPAN%3E%20%E2%80%93Name%20RemoteEventlogSvc-NP-In-TCP%20%7C%20select%20Name%2C%20Enabled%20%3CBR%20%2F%3E%20Get-NetFirewallRule%20%E2%80%93Name%20RemoteEentLogSvc-RPCSS-In-TCP%20%7C%20select%20Name%2C%20Enabled%3C%2FSPAN%3E%0A%20%20%20%20%7D%0A%0A%3CSTRONG%3EServer%202016%20with%20GUI%3C%2FSTRONG%3E%0AName%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20Enabled%0A----%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20-------%0AComPlusNetworkAccess-DCOM-In%20%20%20%20%20False%0ARemoteEventLogSvc-In-TCP%20%20%20%20%20%20%20%20%20False%0ARemoteEventLogSvc-NP-In-TCP%20%20%20%20%20%20False%0ARemoteEventLogSvc-RPCSS-In-TCP%20%20%20False%0A%0A%0A%3CSTRONG%3EServer%202016%20Core%3C%2FSTRONG%3E%0ANo%20MSFT_NetFirewallRule%20objects%20found%20with%20property%20'InstanceID'%20equal%20to%20'complusnetworkaccess-dcom-in'.%20%20Verify%20%0Athe%20value%20of%20the%20property%20and%20retry.%0A%20%20%20%20%2B%20CategoryInfo%20%20%20%20%20%20%20%20%20%20%3A%20ObjectNotFound%3A%20(complusnetworkaccess-dcom-in%3AString)%20%5BGet-NetFirewallRule%5D%2C%20CimJobExc%20%0A%20%20%20eption%0A%20%20%20%20%2B%20FullyQualifiedErrorId%20%3A%20CmdletizationQuery_NotFound_InstanceID%2CGet-NetFirewallRule%0A%20%20%20%20%2B%20PSComputerName%20%20%20%20%20%20%20%20%3A%20ServerCore%0A%20%0ARemoteEventLogSvc-In-TCP%20%20%20%20%20%20%20%20%20False%0ARemoteEventLogSvc-NP-In-TCP%20%20%20%20%20%20False%0ARemoteEventLogSvc-RPCSS-In-TCP%20%20%20False%3C%2FPRE%3E%0A%3CP%3ESo%2C%20that%20rule%20is%20related%20to%20the%20Desktop%20Experience%20(GUI)%20that%20is%20installed%20when%20you%20go%20the%20non-core%20route.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EI%20can%20also%20confirm%20that%2C%20that%20rule%20won't%20prohibit%20you%20from%20managing%20a%20Core%20Server%20via%20Server%20Manager%2C%20as%20yo%3C%2FSPAN%3E%3CSPAN%3Eu%20can%20see%20below%20in%20the%20screenshot.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F58372i92E6808EFC2025F9%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Capture.PNG%22%20title%3D%22Capture.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESo%2C%20it%20looks%20as%20if%20that%20rule%20existed%20at%20one%20point%20in%20Server%20Core%20which%20was%20later%20removed%20from%20Server%20Core%20during%20a%20release%2C%20however%2C%20again%2C%20it's%20not%20required%20to%20manage%20it%20via%20Server%20Manager.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you're%20running%20the%20full%20GUI%20Server%2C%20you%20need%20to%20and%20can%20enable%20that%20rule.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20the%20sake%20of%20the%20exam%2C%20that%20content%20may%20be%20out%20of%20date%2C%20but%20if%20you're%20asked%20that%20question%2C%20assume%20you%20need%20to%20use%20those%20four%20firewall%20rules%20to%20enable%20the%20communication%20channel.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20just%20pulled%20up%20that%20book%20and%20it%20was%20written%20in%20Jan%202017%20so%20a%20lot%20of%20things%20have%20changed%20in%20Server.%20Unfortunately%20it%20looks%20like%20you've%20ran%20into%20one%20of%20those%20instances%20where%20pieces%20of%20the%20exam%20content%20isn't%20accurate%20any%20longer.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-278343%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20MMC%20Snap-Ins%20remotely%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-278343%22%20slang%3D%22en-US%22%3E%3CP%3EWell%2C%20as%20far%20as%20I%20understand%2C%20this%20link%20is%20about%20managing%20VMs%20using%20host's%20PowerShell%20commands%20right%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20what%20I%20meant%20was%20managing%20a%20server's%20Snap-Ins%20remotely%20via%20another%20server(and%20both%20of%20these%20servers%20are%20actually%20Virtual%20Machines).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F58327iAC0852E95FB9D433%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%221.PNG%22%20title%3D%221.PNG%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EAs%20you%20can%20see%20in%20the%20picture%20above%2C%20I'm%20trying%20to%20manage%20Core1%20via%20DC1%20and%20get%20this%20error.%3C%2FSPAN%3E%3C%2FSPAN%3E%26nbsp%3BAccording%20to%20Microsoft's%20%22Exam%20Ref%2070-740%22%2C%20I%20had%20to%20type%20these%20commands%20in%20Core1%20in%20order%20to%20set%20the%20Firewall%20rules%20for%20Remote%20Management%3B%26nbsp%3B%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F58324i731216DEE5C7DFF2%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%2220181024_201517.png%22%20title%3D%2220181024_201517.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3BHowever%2C%20something%26nbsp%3Bgoes%20wrong%20with%20the%20first%20command%20(the%20other%20commands%20work%20properly).%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F58326i7BEBF6046CA695EE%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Capture.PNG%22%20title%3D%22Capture.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-278086%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20MMC%20Snap-Ins%20remotely%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-278086%22%20slang%3D%22en-US%22%3E%3CP%3EI%20don't%20believe%20that%20rule%20exists%20on%202016%2B%20which%20would%20explain%20why%20you%20are%20seeing%20the%20error%20you%20shared.%20If%20I'm%20not%20mistaken%2C%20that%20rule%20opened%20up%20port%20135%20which%20is%20satisfied%20by%20other%20rules%20by%20default%20on%20Server.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20steps%20to%20enable%20remote%20management%20on%20Hyper-V%20on%202016%20are%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fvirtualization%2Fhyper-v%2Fmanage%2Fremotely-manage-hyper-v-hosts%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fvirtualization%2Fhyper-v%2Fmanage%2Fremotely-manage-hyper-v-hosts%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'd%20recommend%20reviewing%20that%20to%20confirm%20you%20have%20it%20configured%20properly.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Soheil Badri
Occasional Contributor

Hello there;

Just joined Microsoft Tech Community and I'm not really sure if it's the exact place to ask about this problem.
The problem is that I have set up a virtual environment(I'm using Hyper-V) with 2 virtual machines(Windows Server 2016 Data Center & Server Core 2016 Data Center)and I've been trying to manage the Server Core remotely. Despite the fact that both servers have been added to the Server pool, I get an error while trying to set the appropriate firewall settings for MMC Snap-Ins.

I'll be truly grateful if someone helps me figure out the solution.

Capture.PNGThe error occurs when I try to enable COM+ Network Access(DCOM-In)

 

 

 

3 Replies

I don't believe that rule exists on 2016+ which would explain why you are seeing the error you shared. If I'm not mistaken, that rule opened up port 135 which is satisfied by other rules by default on Server.

 

The steps to enable remote management on Hyper-V on 2016 are here: https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-...

 

I'd recommend reviewing that to confirm you have it configured properly.

Well, as far as I understand, this link is about managing VMs using host's PowerShell commands right?

 

But what I meant was managing a server's Snap-Ins remotely via another server(and both of these servers are actually Virtual Machines).

 

1.PNGAs you can see in the picture above, I'm trying to manage Core1 via DC1 and get this error. According to Microsoft's "Exam Ref 70-740", I had to type these commands in Core1 in order to set the Firewall rules for Remote Management; 
20181024_201517.png

 However, something goes wrong with the first command (the other commands work properly).Capture.PNG

 

 

 

Solution

Ok, I see now. I was under the impression you were working between the two Hyper-V hosts. 

 

I just loaded up a Server Core 2016 and Server 2016 w/ GUI (both Datacenter) and can confirm that firewall rule does not exist on ServerCore. Here's the code I used to check.

 

 

Write-Host "Server 2016 with GUI"
Get-NetFirewallRule –Name COMPlusNetworkAccess-DCOM-In | select Name, Enabled
Get-NetFirewallRule –Name RemoteEventLogSvc-In-TCP | select Name, Enabled
Get-NetFirewallRule –Name RemoteEventlogSvc-NP-In-TCP | select Name, Enabled
Get-NetFirewallRule –Name RemoteEentLogSvc-RPCSS-In-TCP | select Name, Enabled

Invoke-Command -Computer ServerCore -ScriptBlock {
    Write-Host ""
    Write-Host "Server 2016 Core"
    Get-NetFirewallRule –Name COMPlusNetworkAccess-DCOM-In | select Name, Enabled 
Get-NetFirewallRule –Name RemoteEventLogSvc-In-TCP | select Name, Enabled
Get-NetFirewallRule –Name RemoteEventlogSvc-NP-In-TCP | select Name, Enabled
Get-NetFirewallRule –Name RemoteEentLogSvc-RPCSS-In-TCP | select Name, Enabled
} Server 2016 with GUI Name Enabled ---- ------- ComPlusNetworkAccess-DCOM-In False RemoteEventLogSvc-In-TCP False RemoteEventLogSvc-NP-In-TCP False RemoteEventLogSvc-RPCSS-In-TCP False Server 2016 Core No MSFT_NetFirewallRule objects found with property 'InstanceID' equal to 'complusnetworkaccess-dcom-in'. Verify the value of the property and retry. + CategoryInfo : ObjectNotFound: (complusnetworkaccess-dcom-in:String) [Get-NetFirewallRule], CimJobExc eption + FullyQualifiedErrorId : CmdletizationQuery_NotFound_InstanceID,Get-NetFirewallRule + PSComputerName : ServerCore RemoteEventLogSvc-In-TCP False RemoteEventLogSvc-NP-In-TCP False RemoteEventLogSvc-RPCSS-In-TCP False

So, that rule is related to the Desktop Experience (GUI) that is installed when you go the non-core route.

 

I can also confirm that, that rule won't prohibit you from managing a Core Server via Server Manager, as you can see below in the screenshot.

Capture.PNG

 

So, it looks as if that rule existed at one point in Server Core which was later removed from Server Core during a release, however, again, it's not required to manage it via Server Manager.

 

If you're running the full GUI Server, you need to and can enable that rule.

 

For the sake of the exam, that content may be out of date, but if you're asked that question, assume you need to use those four firewall rules to enable the communication channel.

 

I just pulled up that book and it was written in Jan 2017 so a lot of things have changed in Server. Unfortunately it looks like you've ran into one of those instances where pieces of the exam content isn't accurate any longer.

 

 

 

 

 

 

 

 

 

 

 

Related Conversations
Extentions Synchronization
Deleted in Discussions on
3 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
35 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
29 Replies