About Thomas.Marcussen

Technology Architect & Evangelist, Microsoft Trainer and Everything System Center Professional with a passion for Technology

File cannot be loaded because the execution of scripts is disabled on this system

Error when trying to execute powershell script

cannot be loaded because the execution of scripts is disabled on this system

The machine was a x64 bit Windows Server 2012 so had to set the Powershell policy for BOTH x86 and x64 to solve my problem

command: Set-ExecutionPolicy Unrestricted
The x86 version can be found here: %windir%SysWOW64WindowsPowerShellv1.0

About Execution Policies: http://technet.microsoft.com/da-DK/library/hh847748.aspx
Using the Set-ExecutionPolicy Cmdlet: http://technet.microsoft.com/en-us/library/ee176961.aspx

Simple, but nice script to install the ConfigMgr Client

This is simple, but nice script to install the ConfigMgr Client – very handy in transition phases.

‘Install-CMClient.vbs
on error resume next

Dim currentVer
currentVer = “5.00.7711.0000”

‘Init common variables
Dim wshShell
Dim objFileSystem
Set wshShell = wscript.CreateObject(“wscript.Shell”)
Set objFileSystem = CreateObject(“scripting.FileSystemObject”)

‘Main Flow
If CheckSCCM = False Then
InstallSCCMAgent
ElseIf CheckSCCMVersion maxVer Then
maxVer = thisVer
End If

Next
CheckSCCMVersion = maxVer
End Function

System Center 2012 Configuration Manager RC Now Available

System Center 2012 Configuration Manager provides a unified management infrastructure across physical, virtual, and mobile client environments. System Center 2012 Endpoint Protection builds on this infrastructure to provide industry-leading antimalware protection for client and server operating systems.

 

http://www.microsoft.com/en-us/server-cloud/system-center/configuration-manager.aspx

 

Windows 8 Build 7989 contains a number for new features

Windows 8 Build 7989 contains a number for new features

  • Storage
    Virtual Fibre Channel Adapter
    Storage Resource Pools
    New .VHDX virtual hard drive format (Up to 16TB + power failure resiliency)
  • Memory/Processor Enhancements

Support for more than 4 cores! (My machine has 12 cores)
NUMA – Memory per Node, Cores per Node, Nodes per Processor Socket

  • Netwroking Enhancements

Hardware Acceleration (Virtual Machine Queue & IPsec Offload)
Bandwidth Management
DHCP Guard
Router Guard
Monitor Port
Virtual Switch Extensions
Network Resource Pools

Among the features are also Hyper-V 3.0 and the .VHDX virtual drive format
hypervisor-based virtualization system for x86-64 systems, will allow us to see self contained AppV applications.
If this is correct, and if Microsoft does include Hyper-V 3.0 in Windows 8, this could potentially
make Windows 8 a huge game-changer when it comes to virtualization.

Microsoft Application Virtualization 4.6 SP1 is now supported on Configuration Manager 2007 R3 with Configuration Manager 2007 SP2

The changes will be reflected in the Supported Configuration pages within a few months.

Microsoft Application Virtualization 4.6 SP1 is now supported on Configuration Manager 2007 R3 with Configuration Manager 2007 SP2

System Center Configuration Manager 2007 R3 with System Center Configuration Manager SP2 now supports Microsoft Application Virtualization (App-V) 4.6 SP1 Desktop Client and Application Virtualization Client for Remote Desktop Services. This client release enables support for Windows 7 SP1 and Windows Server 2008 R2 SP1.

The following are the limitations and workaround to import App-V packages using Configuration Manager.

Configuration Manager fails to import App-V packages when there is more than one XML in the package folder. App-V Sequencer 4.6 SP1 creates the file Report.xml when creating an App-V package. Configuration Manager expects to find only one xml file in the package folder and will fail when it identifies more than one XML file in the folder. To work around this problem delete the file report.xml manually from the package folder before you import the App-V package.

No software updates are required.