<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Powershell on Evan Hoffman</title><link>https://evan.wtf/tags/powershell/</link><description>Recent content in Powershell on Evan Hoffman</description><generator>Hugo</generator><language>en-US</language><copyright>Evan Hoffman</copyright><lastBuildDate>Sat, 20 Apr 2013 14:59:36 +0000</lastBuildDate><atom:link href="https://evan.wtf/tags/powershell/index.xml" rel="self" type="application/rss+xml"/><item><title>Use PowerShell to disconnect the CDROMs from all VMs in vCenter</title><link>https://evan.wtf/2013/04/20/use-powershell-to-disconnect-the-cdroms-from-all-vms-in-vcenter/</link><pubDate>Sat, 20 Apr 2013 14:59:36 +0000</pubDate><guid>https://evan.wtf/2013/04/20/use-powershell-to-disconnect-the-cdroms-from-all-vms-in-vcenter/</guid><description>&lt;p&gt;Recently I was moving all VMs from one NFS datastore to another so we could destroy the old volume. Storage vMotion took care of this for the most part, but even after moving the files, vCenter still showed that the VMs were using the old datastore. It turned out this was due to the VMs having mounted ISOs on that datastore. The solution was to eject/unmount the CDrom, but I didn&amp;rsquo;t want to do &amp;ldquo;Edit Settings&amp;hellip;&amp;rdquo; and manually remove the CDrom for 200+ VMs.&lt;/p&gt;</description></item><item><title>Exchange 2010 Post-Upgrade weirdness: can't edit Mail Non-Universal Group or Security Group</title><link>https://evan.wtf/2010/10/21/exchange-2010-post-upgrade-weirdness-cant-edit-mail-non-universal-group-or-security-group-2/</link><pubDate>Thu, 21 Oct 2010 22:29:38 +0000</pubDate><guid>https://evan.wtf/2010/10/21/exchange-2010-post-upgrade-weirdness-cant-edit-mail-non-universal-group-or-security-group-2/</guid><description>&lt;p&gt;Now that everyone&amp;rsquo;s been moved to Exchange 2010 we&amp;rsquo;ve started using the 2010 Exchange Managment Console/Shell exclusively which has revealed some weirdness. First, we created a new group in AD using an old script (which used LDAP) and created a Mail-enabled Global Security group. We put people in the group, and everything seemed to be working fine until it was discovered that users in the group couldn&amp;rsquo;t see the group in the Global Address List. Users not in the group had no problem seeing the group. Additionally, users in the group couldn&amp;rsquo;t see &lt;em&gt;users&lt;/em&gt; added directly in 2010. This only appeared to affect the GAL; the users were able to send/receive email fine with the full SMTP addresses.&lt;/p&gt;</description></item><item><title>Exchange 2010 Post-Upgrade weirdness: can't edit Mail Non-Universal Group or Security Group</title><link>https://evan.wtf/2010/10/21/exchange-2010-post-upgrade-weirdness-cant-edit-mail-non-universal-group-or-security-group/</link><pubDate>Thu, 21 Oct 2010 22:29:38 +0000</pubDate><guid>https://evan.wtf/2010/10/21/exchange-2010-post-upgrade-weirdness-cant-edit-mail-non-universal-group-or-security-group/</guid><description>&lt;p&gt;Now that everyone&amp;rsquo;s been moved to Exchange 2010 we&amp;rsquo;ve started using the 2010 Exchange Managment Console/Shell exclusively which has revealed some weirdness. First, we created a new group in AD using an old script (which used LDAP) and created a Mail-enabled Global Security group. We put people in the group, and everything seemed to be working fine until it was discovered that users in the group couldn&amp;rsquo;t see the group in the Global Address List. Users not in the group had no problem seeing the group. Additionally, users in the group couldn&amp;rsquo;t see &lt;em&gt;users&lt;/em&gt; added directly in 2010. This only appeared to affect the GAL; the users were able to send/receive email fine with the full SMTP addresses.&lt;/p&gt;</description></item><item><title>Changing all Exchange mailboxes to use database defaults for quota limits with PowerShell</title><link>https://evan.wtf/2010/10/12/changing-all-exchange-mailboxes-to-use-database-defaults-for-quota-limits-with-powershell/</link><pubDate>Tue, 12 Oct 2010 16:38:03 +0000</pubDate><guid>https://evan.wtf/2010/10/12/changing-all-exchange-mailboxes-to-use-database-defaults-for-quota-limits-with-powershell/</guid><description>&lt;p&gt;Here&amp;rsquo;s an example of why I&amp;rsquo;ve come to love PowerShell. Under Exchange 2003, we set users&amp;rsquo; mailbox quota limits per-user, since we initially set them ridiculously high (around 20 GB). The reason we did that was that prior to this year we actually didn&amp;rsquo;t have &lt;strong&gt;any&lt;/strong&gt; quotas on user mailboxes and the average mailbox was about 9 GB. In preparation for moving Exchange to the datacenter (over our measly 5Mbps upload line) we introduced quotas and over the course of about 2 months gradually lowered the limits as people whittled away their old email until they were under the quota we had established (about 2.25 GB for the no-send limit &amp;ndash; I forgot the rationale for that number &amp;ndash; and 1.75 GB for the warning limit [the no-receive limit was set to about 40GB since I never wanted users to hit that limit]).&lt;/p&gt;</description></item></channel></rss>