Enable PowerShell V2 on Windows 8

November 4, 2012

Enable PowerShell V2 in Windows 8

I’ve been working with Windows 8 for a week or so on my laptop, and I’ve noticed something.
While trying to start a PowerShell V2 host, I get a message that The .NET Framework Version 2 isn’t installed – a requirement for PowerShell V2 to work.

Here is a solution:

Very Important – In order for this to work, you need to assure 2 things:

  1. You need to open an elevated Shell.
  2. You need to open a 64 bit command shell if you’re using a 64 bit Windows OS.

.NET framework version 3.5 is available for installation – as a Windows Feature (which contains all past versions – including version 2) in Windows 8. I know that by using V3’s Get-WindowsOptionalFeature cmdlet, which is part of the DISM PowerShell Module:

PS C:\Windows\system32>; Get-WindowsOptionalFeature -Online | where {$_.FeatureName -Like ‘netfx3’}
Feature Name : NetFx3
State : DisabledWithPayloadRemoved

Now that I know its there, I have to enable that feature (you can also just pipe the former example):

PS C:\Windows\system32>; Enable-WindowsOptionalFeature -Online -FeatureName netfx3Path :
Online : True
Restart Needed : False

installation will take a few minutes. once it’s finished, I can now load a V2 Host:

I can confirm it by checking the $PSVersionTable variable, and its PSVersion property :

PS C:\Windows\system32>; $PSVersionTableName
—- —–
CLRVersion 2.0.50727.6387
BuildVersion 6.1.7600.16385
PSVersion 2.0
WSManStackVersion 2.0
PSCompatibleVersions {1.0, 2.0}
PSRemotingProtocolVersion 2.1

Set User’s Home Folder That Is Managed With FSRM – PowerShell

October 24, 2012

Managing Home Folders with FSRM

Important! The following article only applies to FSRM Roles that are installed on Windows Server 2003/2008/R2, as 2012 FSRM has it’s own PowerShell module!

In our organization, we got users asking us to increase their Home Folder’s capacity on a daily basis. We manage these home folders on our file servers using the File Server Resource Manager (FSRM) server role.

Everytime you want to set a quota limit that is managed wtih FSRM, you have to do it with the FSRM MMC, and its biggest downside, is that even when you only need to set just one quota limit, you need to wait for all the other data to load, and that can take well more than 8 or so seconds on most occasions – enough time to set quotas for multiple users through a script.

Where I work, we got at least 1000 quotas on each file server, scattered around 8 file server across the country. loading all that data over WAN can sometimes be annoying.

Now when it comes to setting those quotas with powershell, one possibility is to load the Fsrm.FsrmQuotaManager COM Object into the shell and use it to set Quotas. But this COM object doesn’t exists in Windows 7, only on the server itself (Server 2003 / 2008 ) and I don’t want to access the relevant file server with Remote Desktop every time I need set a quota limit… and my security team doesn’t allow me to start PS Sessions to most of our servers..

Using dirquota.exe With PowerShell to Set Home Folders That are Managed with FSRM

Throughout my search for a solution, I found out that Microsoft’s Storage Team supply the dirquota.exe utility, that comes along when you install the FSRM RSAT Tool (in “turn windows features on or off”, select Remote Server Administration Tools > File Services Tools > File Server resource Manager Tools)

I’ve played with it, and like most .exe utilities, it’s not as syntax-friendly and easy to use as a PowerShell Cmdlet. one of the reasons is that you have to type the original path of that folder (D:\Users\James), and that can be a problem, because that path can be different from one file server to another. therefore, it’s easier for me to use a UNC.

So I decided I’ll just write a Cmdlet that will pass its data to the relevent parameters of dirquota.exe.

instead of finding out the true location of the UNC (D:\Users\James. or is it E:\Users\James? errh!) and then use dir quota:

PS C\:> dirquota.exe q m /remote:FileServer /path:D:\Users\James /Limit:1400MB

I will run a PowerShell Cmdlet:

PS C:\> Set-FSRMQuota -User James -Limit 1700

Lets get to Work!

Writing the Script Cmdlet

By understanding how dirquota.exe accpets input, I know 3 things:

  • I need to know the name of the file server that is hosting the home folder.
  • I need to know the home folder’s original path on that server.
  • I’ll need to take this data, and populate dirquota’s appropriate parameters.

Sounds like a classic PowerShell mission…

For the first task, we will use Get-ADUser to store the user information in a variable.

Next, we’ll export the UNC out of the user’s HomeDirectory attribute:

Now I’ll need to extract the Share name and the Server name out of the UNC. I’ll try to minimize the use of string editing. first,

I’ll use Get-Item to extract the shared folder’s name:

PS C:\> $FolderUNC = (Get-Item $UNC).parent | select -ExpandProperty name

and then I’ll just trim the original UNC in two phases:

PS C:\> $ServerUNC ($UNC -Replace “$FolderUNC.*”).Trim(‘\’)

Note that im using “Select -ExpandProperty” (Select is an alias for Select-Object). I do it because I need that object as a type of string, because the original object is the type of ActiveDirectory.Management.ADUser, and it’s value is something that i cant edit, or attach to Get-Item.

Now, We need to find the UNC’s original path on the file server. For this task, I’ll use WMI’s Win32_Share class. I’ll use it on $ServerUNC, because that is the file server that hosts the home folder. I’ll filter the results with Where-Object to try to find a folder that its name matches $FolderUNC:

We’ll extract that path and save it in a variable:

Only thing left, is to populate dirquota’s “/limit:” parameter, which accepts data as a number, followed by a “MB” suffix (for example – “1700MB”). because the final script is accessible like a Cmdlet, it has a variable that accept’s parameter input, with a “param ()” block at the start of the script. We will use this for illustration:

Now we can run direquota.exe and populate its parameters with all the data we collected. this command will live inside the final script:

dirquota.exe q m /remote:$serverUNC /path:$path\$($ad.SamAccountName) /limit:$limit
Quotas modified successfully

Informing us that the “Quotas modified successfully” is very helpful. but i want a final report on the operation I just did! I’ll store all the data that I collected into a custom object that I’ll create using New-Object:

finally, We will put everything we wrote in an Advanced Function construct, so we can use it like we wanted to in the first place – without typing the File Server and the original path, because the file servers and the path’s can be configured and named differently from one server or user to another.

PS C:\> Set-FSRMQuota -User James -Limit 500

This is how the final script looks like.

A link to download from MS TechNet gallery: