<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Dcom on Aperture Zone</title>
    <link>https://aperturezone.com/tags/dcom/</link>
    <description>Recent content in Dcom on Aperture Zone</description>
    <image>
      <url>https://aperturezone.com/logo.webp</url>
      <link>https://aperturezone.com/logo.webp</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>fr-fr</language>
    <lastBuildDate>Fri, 01 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aperturezone.com/tags/dcom/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>GPO - Remote WMI management and scheduled tasks</title>
      <link>https://aperturezone.com/gpo/firewall-wmi/</link>
      <pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/gpo/firewall-wmi/</guid>
      <description>&lt;p&gt;It is possible to manage machines remotely without having to disable the firewall. You just need to open the right ports for WMI, DCOM, and RPC—nothing more, nothing less.
You can use WMI to query machines remotely—collect system information, run commands, and manage scheduled tasks from the console or a PowerShell script.&lt;/p&gt;
&lt;p&gt;When you run a Get-WmiObject command and get the error: &amp;quot;RPC access was denied,&amp;quot; the easy solution is to disable the Windows firewall on the target machines.
But this is a very bad idea on a network where machines with different trust levels coexist.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
