Mathias R. Jessen's questions

If I have a script that I need to run against multiple computers, or with multiple different arguments, how can I execute it in parallel, without having to incur the overhead of spawning a new PSJob with Start-Job?

As an example, I want to re-sync the time on all domain members, like so:

$computers = Get-ADComputer -filter * |Select-Object -ExpandProperty dnsHostName
$creds = Get-Credential domain\user
foreach($computer in $computers)
{
    $session = New-PSSession -ComputerName $computer -Credential $creds
    Invoke-Command -Session $session -ScriptBlock { w32tm /resync /nowait /rediscover }
}

But I don't want to wait for each PSSession to connect and invoke the command. How can this be done in parallel, without Jobs?

I have a Windows Server 2008 R2 box hosting 3 virtual SMTP servers; vSMTP01, vSMTP02 and vSMTP03.

The first two are configured to deliver all messages to dedicated smarthosts, while the last is set to just deliver the messages on its own. All other delivery settings are as default

                                    ----(vSMTP01)-----> {SMARTHST01}
                                   /
----Inbound mail--->---SMTPSRV01---[----(vSMTP02)-----> {SMARTHST02}
                                   \
                                    ----(vSMTP03)-----> { Internet }

Now I want to take SMARTHST01 out for maintenance, but I don't want to reject submissions to vSMTP01 while doing so, so I just let it continue running.

When SMARTHST01 is no longer responding, vSMTP01 queues the messages and wait for the first retry interval to pass (15 minutes). So far so good.

Let's say SMARTHST01 gets online again after 20 minutes. The first interval has passed, and I'll have to wait another 25 minutes for the second retry interval to pass.

If I stop and start the SMTP Service (Services.msc -> Simple Mail Transfer Protocol service -> Stop), the server will retry all deliveries, but that would cause a service interruption for ALL virtual SMTP servers on the machine, which is highly undesirable.

How can I manually force vSMTP01 to retry delivery of all queued messages without interrupting the service of vSMTP02 and vSMTP03?

I've been working for some time at a super lean IIS 7.5 configuration for a static file serving purposes web site. To achieve this, I've simply stripped the designated web site for all dynamic modules, and only specified native modules such as the StaticFileModule, AnonymousAuthenticationModule, HttpCompressionModule etc.

This has already proved to cause a significant decline in the memory footprint and processing overhead for the worker process, and the overall performance is much better than the default web site.

Now, as a next step, I would like to see if I can trim down the number of modules loaded into memory even further.
I could just remove the modules one-by-one and try to see how it affects performance and functionality, but I would rather investigate what the functionality the individual modules actually has/governs.

Some of the modules are pretty self-explanatory (ie. DefaultDocumentModule, DirectoryListingModule), but some are not.

Is there anywhere I can find the documentation for the builtin native modules?

I have an Active Directory setup consisting of 2 forests:

• 1 multi-domain forest with 1 forest root domain, and 2 direct child domains
• 1 single-domain forest for DMZ publishing purposes

I have created 3 outgoing trusts in the DMZ domain, 1 transitive forest trust against the forest root domain, and 2 External Non-transitive trusts (aka. Shortcut Trusts).

All DC's in all four domains are Global Catalog servers.

I've tried to visualize it below:

Now, here is the problem. When I grant access on a resource in dmzRoot.tld to a security group in the childA domain, it works for users in childA who are member of the Security group, but not for users in the childB domain, even though they are members of the security group in childA.

Let's say I want to give local administrator access to a member server in the dmzRoot.tld for example. I add childA.ForestRoot.tld\dmzAdministrators to the local builtin Administrators group on the member server.

childA.ForestRoot.tld\dmzAdministrators has the following members:

• childA\dmzAdmin
• childB\superUser

Now, if I authenticate as childA\dmzAdmin, I can log on to the member server as a local Administrator, and if I take a look at the output from whoami /groups, the childA.ForestRoot.tld\dmzAdministrators group is clearly listed.

If I authenticate as childB\superUser however, I get a message that the account is not authorized for remote logon. If I check whoami /groups for the childB\superUser account, the childA.ForestRoot.tld\dmzAdministrators group is NOT listed.

It almost seems like the childA group SID's never get included in the PAC when authenticating childB users, even though all DC's are GC's.

I disabled PAC validation on the machine in dmzRoot.tld that I tested it on, but this did not help.

Any suggestions as to how I troubleshoot this effectively? How do I follow the trail of authentication to determine where it fails?

What I would like to accomplish is to install the Snipping Tool (most of you probably recognize this feature from Windows 7 and Vista), on a Windows Server 2008 R2.

This can be done by installing the Desktop Experience feature.

What I would like to know is: Is there any way I can install the Snipping Tool alone? Without having to install the other components in the Desktop Experience feature (like Defender, Themes, Windows Media Player), for which I have no use.

I'm going over some SMTP log files from an open relay server (IIS 6 SMTP Virtual Server), used to collect and route all automated email within a private network, to an internet smarthost (qmail at another ISP). Using SawMill 8.5 to parse the logs, it appears that there is a big difference between the number of messages delivered from my server, and the number of emails that the internet smart host sends out. For a period where I have delivered 2000 emails to the smart host, the smart host has delivered 3000 emails to the internet. I guess this has something to do with emails having multiple recipients. So my question is this:

When does a single message with multiple recipients get split and routed to the individual recipients' MX? At submission? At the last hop before the internet? Or is this MTA specific?

Let me now if I need to clarify anything