The Windows Driver Kit (WDK) includes the tools and documentation you need to develop drivers. Windows Driver Kit (WDK) 8.1 is integrated into Microsoft Visual Studio 2012 (Professional, Premium, and Ultimate) to provide you with a complete set of tools to develop, build, package, test, and debug drivers.
Direct Download Link: http://go.microsoft.com/fwlink/?LinkID=317353
This sample pack includes all the app code examples developed and updated for Windows 8.1 RTM. These samples should only be used with the released version of Windows 8.1 and Visual Studio 2013 RC. The sample pack provides a convenient way to download all the samples at once. The samples in this sample pack are available in C#, C++, and JavaScript
Direct download link: http://go.microsoft.com/fwlink/?LinkId=322042
Following criticism from TechNet and MSDN subscribers, Microsoft has announced plans to release the Core and Pro RTM builds for Windows 8.1 and Windows Server 2012 R2 to users of those services. Additionally, the release candidate build for Visual Studio 2013 will be provided to TechNet and MSDN subscribers.
A few facts about SEDO
When the UI crashes and causes locks, you can easily unlock or locate the Locks
run sql mangement studio against your DB
Show locks: select * from SEDO_LockState where LockStateID <> 0
Delete locks: delete from SEDO_LockState where id=’PLACE ID FROM ABOVE HERE’
This took me quite some time to figure out.
When running a build and capture task sequece from ConfigMgr, it won’t give any errors
Even after the image is captured and ready for re-deployment, the error appears when trying to run Setup Windows and Configmgr from a deployment task sequence. It would just break/stop right in the middel of that process, leaving your with pretty mush a useless deployment
Solution:
Set permission for group Administrators ( Full Control ) to
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionSetupSysprepCleanup
Value Name
{EC9FE15D-99DD-4FB9-90D5-5B56E42A0F80}
Value Data
C:WindowsSysWOW64iesysprep.dll,Sysprep_Cleanup_IE
replace with
C:WindowsSystem32iesysprep.dll,Sysprep_Cleanup_IE
Set permission for group Administrators ( Full Control ) to
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionSetupSysprepGeneralize
Value Name
{EC9FE15D-99DD-4FB9-90D5-CE53C91AB9A1}
Value Data
C:WindowsSysWOW64iesysprep.dll,Sysprep_Generalize_IE
replace with
C:WindowsSystem32iesysprep.dll,Sysprep_Cleanup_IE
Set permission for group Administrators ( Full Control ) to
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionSetupSysprepSpecialize
Value Name
{EC9FE15D-99DD-4FB9-90D5-676C338DC1DA}
Value Data
C:WindowsSysWOW64iesysprep.dll,Sysprep_Cleanup_IE
replace with
C:WindowsSystem32iesysprep.dll,Sysprep_Cleanup_IE
setting this from a batch file:
IEhotfix.cmd:
regini -m \%computername% iesysprep.dll.txt reg add HKLMSOFTWAREMicrosoftWindowsCurrentVersionSetupSysprepCleanup /v {EC9FE15D-99DD-4FB9-90D5-5B56E42A0F80} /t REG_SZ /d “C:WindowsSystem32iesysprep.dll,Sysprep_Cleanup_IE” /f reg add HKLMSOFTWAREMicrosoftWindowsCurrentVersionSetupSysprepGeneralize /v {EC9FE15D-99DD-4FB9-90D5-CE53C91AB9A1} /t REG_SZ /d “C:WindowsSystem32iesysprep.dll,Sysprep_Cleanup_IE” /f reg add HKLMSOFTWAREMicrosoftWindowsCurrentVersionSetupSysprepSpecialize /v {EC9FE15D-99DD-4FB9-90D5-676C338DC1DA} /t REG_SZ /d “C:WindowsSystem32iesysprep.dll,Sysprep_Cleanup_IE” /f
iesysprep.dll.txt
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionSetupSysprepCleanup [1] HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionSetupSysprepGeneralize [1] HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionSetupSysprepSpecialize [1]
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
Windows 8 Build 7989 contains a number for new features
Support for more than 4 cores! (My machine has 12 cores)
NUMA – Memory per Node, Cores per Node, Nodes per Processor Socket
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.
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.