Virtual disk could not be repaired because there is not enough free space in the storage pool. – Fun with storage spaces

Just a few fun notes with storage spaces:

I was trying to repair a failed storage spaces disk but didn’t have any spare disks or free slots available and the system was due to be decommissioned so investment was not really wanted.

Genius here thought that adding a iscsi disk and then repairing with that would work and as the system was going to be migrated it wouldn’t be much of an issue.

So i added a 2TB iscsi LUN and added the disk to the pool.

set the faulty disk to retired and then tried to repair the pool.

Error!:
Virtual disk could not be repaired because there is not enough free space in the storage pool.

But i have just added 2TB!?! what is going on? Free space for the pool is showing 2TB but yet i cannot use it to do the repair… Why?

Looking a bit harder i saw that the disk media type is showing as UnSpecified in the Physical Disks. Perhaps this is where the issue is – the iscsi disk is not a supported target and storage spaces doesn’t know what to do with it?

Can i force it to be a supported media type?

I know that when the tiered settings came out we could pretend to have SSD disks so why not give that a try?

Get-PhysicalDisk | Select-Object FriendlyName, MediaType, Size

find the Disk (PhysicalDisk9 in my case) and set it as media type HDD

Set-PhysicalDisk –FriendlyName PhysicalDisk9 -MediaType HDD

The command issued ok with no confirmation so just reissue the previous command to verify the disk has change media type

Get-PhysicalDisk | Select-Object FriendlyName, MediaType, Size

If all looks okay, try to start the repair.

Group Policy not applying – Inaccessible, Empty or Disabled

This is affecting Windows 8.1

Group Policies that used to work are now not applying. A quick check on the failing PC using gpresult –h shows that the policy is Inaccessible, Empty or Disabled.

GroupPolicy_Inaccessible_Empty_or_Disabled

No changes have been made to Group Policy.

Quick Solution

This is due to a Microsoft Patch to plug some holes in the way Group Policy is deployed ( https://support.microsoft.com/en-gb/kb/3159398 ) and affects group policies where there are security filtering enabled.

Find the Group Policy that is being affected and on the delegation tab give “read” permission to the “authenticated users” group. This will not apply the policy to all users as that is controlled using the “Apply group policy” permission. This will simply allow the GPO to be read and thus interpreted by the PC.

GPODelegation_Inaccessible_Empty_or_Disabled

Once updated, run a gpupdate /force and things should be back to the way they were.

Fixed_GPO_Inaccessible_Empty_or_Disabled

Alternative Solution

Remove the patch KB3159398 from all affected PCsUninstall_Patch_Inaccessible_Empty_or_Disabled

Export Windows Drivers to Central Store

Just made a script to export Drivers to a central store. Handy for when you need to grab a the drivers off of a PC to look at later or to update the rest of the estate with.

Link to resource on Spiceworks: https://community.spiceworks.com/scripts/show/3689-export-drivers-to-central-store

Script:

##########################################
###                                    ###
###         Script to extract          ###
###         latest drivers from        ###
###         windows system and         ###
###         dump to central store      ###
###                                    ###
### By Patrick Louis-Jean     v1       ###
##########################################


### Variables ###
$CentralStore = "\\server\Shares\Drivers" #Where Drivers will be stored centrally
$LocalStore = "C:\Drivers" #working folder on local machine

### Showtime! ###
$SystemOS = (Get-WmiObject -class Win32_OperatingSystem).Caption
$ComputerMake = "$((Get-WmiObject -Class win32_computersystem).Manufacturer)"
$DateTime = Get-date -Format yyyy-MM
$DriverStore = "$LocalStore\$SystemOS\$ComputerMake $((Get-WmiObject -Class win32_computersystem).Model) $DateTime"
mkdir $DriverStore
cd $DriverStore
$DriversList = Export-WindowsDriver -Online -Destination $DriverStore

foreach ($Driver in $DriversList) {
    #Make Class Directory
    $ClassDirectory = $DriverStore+"\"+$Driver.ClassName
    if (!(Test-Path $ClassDirectory)){
                 New-Item $ClassDirectory -type directory
    }
    #Make Provider Directory
    $ProviderDirectory = $ClassDirectory+"\"+$Driver.ProviderName
    if (!(Test-Path $ProviderDirectory)){
                 New-Item $ProviderDirectory -type directory
    }
    #Move Drivers to Folder
        #Get Original Folder Name
        $OrigDriverFolder = $Driver.OriginalFileName
        $OrigDriverFolder = $OrigDriverFolder.replace("C:\Windows\System32\DriverStore\FileRepository\","") #Assuming all drivers are stored here!
        $position = $OrigDriverFolder.IndexOf("\")
        $OrigDriverFolder = $OrigDriverFolder.Substring(0,$position)
        $OrigDriverFolder
        #Make New Folder Name
        $NewDriverFolder = $ProviderDirectory+"\"+$OrigDriverFolder+"_v"+$Driver.Version
        $NewDriverFolder
        #Move Folder
        robocopy $DriverStore"\"$OrigDriverFolder $NewDriverFolder /E /MOVE /NP
}

#Output List of Drivers to CSVFile
$DriversList | Select OriginalFileName, ClassName, ClassDescription, ProviderName, Version |Sort-Object OriginalFileName |  Export-Csv -Path $DriverStore"\DriverList.csv" -NoTypeInformation

#Move to Central Store
robocopy $LocalStore $CentralStore /E /MOVE /NP

System Center Config Manager 2012 R2 Error 0x80004005 when loading task sequence on Surface Pro 3

Windows Command Prompt time and date commands
Windows Command Prompt time and date commands

This is an interesting one that i came across recently whilst trying to deploy an image to a brand new Microsoft Surface Pro 3.

I had two sitting on the bench ready to deploy our stock Windows 8.1 image. The first Surface PXE booted fine and jumped straight into the task sequence as normal however the second one came up with an error 0x80004005 when trying to look for the task sequences.

I knew that it wasn’t the image as surface numberone was working fine. I checked all of the usual things, replaced the ethernet cable etc and after a few reboots, I still had the same error.

After a little digging I found the solution.

The time in the UEFI BIOS was wrong.

The problem is that there is no option to change the time in the UEFI BIOS so you must change it using the PE environment instead:

  1. Make sure that your boot image has command support enabled.
  2. Boot into the Config Manager image.
  3. Before proceeding any further, press the F8 key (Fn + F8).
  4. At the command prompt type the ‘time’ command to change the current time.
  5. Next type the ‘date’ command and enter the correct date following the format for the locale of the PE.
  6. Verify that it has applied by typing

    time /t’

    and then

    date /t

  7. Close the command prompt and continue with your build.

 

Interesting Article – Microsoft rolls out new Windows 10 preview with Cortana and Continuum

We spent a decent chunk of our Wednesday getting a load of what Microsoft’s added to Windows 10 since the last time we saw it, and now the bravest among you can take (most of) that new stuff for a spin. The company launched the next build of the Windows 10 Technical Preview earlier this afternoon, and with it comes long-awaited features like Continuum — for when you’re running Windows on shape-shifting devices — and a new Xbox app that focuses on “the basics.”

And the biggest addition to the mix? Cortana has finally migrated from her home on Windows Phone to the desktop, though not everything works the way it should just yet. A post on the company’s Windows blog written by Microsoft engineering general manager Gabe Aul confirms that the virtual assistant can take down notes and answer questions about weather and finance, but she still has a little trouble transcribing more complex reminders. And the rub? A few of Microsoft’s juicier tidbits still aren’t ready for public consumption. There’s no mention made of the new Project Spartan browser or the company’s updated take on Office, but they’re expected to become available to Windows Insiders later this year. Patience, grasshoppers. Meanwhile, the rest of you can mosey over to the Windows Insider site to take Windows 10 for spin right here and now.

Read more…  via LinkedIn. January 23, 2015 at 10:57PM http://ift.tt/1Eb7HsH