Windows 8 Enterprise available

Windows 8 Enterprise is now available for download from Microsoft at the following sites:
MSDN Subscription:
https://msdn.microsoft.com/subscriptions/securedownloads/hh442898
Microsoft Partner Network:
https://mspartner.microsoft.com/en/us/Pages/Solutions/windows-8.aspx
TechNet Professional Subscription:
https://technet.microsoft.com/subscriptions/securedownloads/hh442904
Microsoft Volume Licensing/Software Assurance:
http://go.microsoft.com/?linkid=9675329

You can also download an evaluation version at the following site:
http://msdn.microsoft.com/en-us/evalcenter/jj554510.aspx

The broken Operations Manager Shell

I have a management server with the Operations Manager Console installed. When I tried to start the Operations Manager Shell it failed with the following errormessage:
Import-Module : The specified module ‘OperationsManager’ was not loaded because
no valid module file was found in any module directory.
At line:1 char:14
+ Import-Module <<<< OperationsManager; .\OperationsManager\Functions.ps1; .\O perationsManager\Startup.ps1
     + CategoryInfo : ResourceUnavailable: (OperationsManager:String)
        [Import-Module], FileNotFoundException
       + FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Comm
        ands.ImportModuleCommand

The term ‘Start-OperationsManagerClientShell’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\Program Files\System Center 2012\Operations Manager\Powershell\OperationsManager\Startup.ps1:26 char:35
+ Start-OperationsManagerClientShell <<<< -ManagementServerName: “” -PersistConnection: $true -Interactive: $true;
         + CategoryInfo : ObjectNotFound: (Start-OperationsManagerClientShell:String) [], CommandNotFoundException
         + FullyQualifiedErrorId : CommandNotFoundException

The reason for this was that the path to “C:\Program Files\System Center 2012\Operations Manager\Powershell\” was missing in the envorinmental variable PSModulePath. Once completed and logged out and back in to the system everything worked as espected.