Voice scenarios with OCS 2007

THB - This is just the Overview for each scenario, see complete post for details!

Office Communications Server (OCS) 2007 offers multiple voice scenarios that are not necessarily easily understandable just by their names. However, it is essential to understand the different “flavors” of OCS voice in order to determine the best voice integration option for the specific customer environment. For this reason, I have explained and summarized the different voice integration options as follows:

PC-PC communication

Overview

This voice scenario was already available in OCS 2007 predecessor Live Communications Server 2005 SP1. OC acts as a soft client (software telephone), does not have a phone number (extension) assigned (only it’s SIP URI like someone@somewhere.com) and needs an audio or audio/video device connected to the PC in order to make and receive audio conversations by using your PC. Tricky: This is a VoIP scenario, but does not use any of the voice functionality, that has been added for OCS 2007! It’s peer-to-peer voice only between OC clients by using the SIP URI, no phone numbers.

Remote Call Control (RCC)

Overview

Also this voice scenario was already available in OCS 2007 predecessor Live Communications Server 2005 SP1. The users OC client does not act as a soft phone, does not need an audio or audio/video device connected to the PC and the user is not able to make or receive phone calls by using her/his PC. This is not a VoIP scenario!

Enterprise Voice

Overview

This scenario is new with OCS 2007. OC acts as a soft client (software telephone), has a phone number (extension) and needs an audio or audio/video device connected to the PC in order to make and receive phone calls by using your PC. This is a VoIP scenario!

Enterprise Voice with PBX integration – blank SIP Server URI (aka Dual Forking)

Overview

This scenario is new with OCS 2007. OC acts as a soft client (software telephone), has a phone number (extension) and needs an audio or audio/video device connected to the PC in order to make and receive phone calls. This is a VoIP scenario! In addition to that the user has a PBX/IP PBX phone standing next to her/his PC with OC on his desk that has the same phone number (extension) as OC! OC and the PBX/IP PBX phone will ring both on an incoming call to your extension.

No CSTA GW is deployed, but only a Media GW!

Enterprise Voice with PBX integration (aka Dual Forking with RCC)

Overview

This scenario is new with OCS 2007. OC acts as a soft client (software telephone), has a phone number (extension) and needs an audio or audio/video device connected to the PC in order to make and receive phone calls. This is a VoIP scenario! In addition to that the user has a PBX/IP PBX phone standing next to her/his PC with OC on his desk that has the same phone number (extension) as OC! OC and the PBX/IP PBX phone will ring both on an incoming call to your extension.

At least one CSTA and one Media GW need to be deployed!

 

 

Jochen Kunert : Voice scenarios with OCS 2007

Visual LINQ Query Builder

   Visual LINQ Query Builder

 

Resource Page Description

Visual LINQ Query Builder is an add-in to Visual Studio 2008 Designer that helps you visually build LINQ to SQL queries. Functionally it provides the same experience as, for instance the Microsoft Access Query Builder, but in the LINQ domain. The entire UI of this add-in uses Windows Presentation Foundation. The goal of this tool is to help users become more familiar with the LINQ syntax. The tool may also demonstrate to users how to create their own Visual Studio 2008 add-in using Windows Presentation Foundation.
This academic project was developed by two students during an internship at Microsoft France, under the supervision of one of our Developer Evangelists. The project was in full collaboration with the STB International CPE team in Redmond.
Here is a quick presentation: http://blogs.msdn.com/mitsu/archive/2008/04/02/visual-linq-query-builder-for-linq-to-sql-vlinq.aspx
See it in French here: http://blogs.msdn.com/mitsufu/archive/2008/04/02/visual-linq-query-builder-pour-linq-to-sql-vlinq.aspx

Requirements

You will need to have Visual Studio 2008 installed. You can use the Visual LINQ Query Builder in any kind of project that supports LINQ to SQL.
Please note that Visual LINQ Query Builder is only supported with C# and VB.Net projects, and is not supported in Visual Studio Express Editions.

Quick Reference Guide

A Quick Reference Guide and a video showing how to start Visual LINQ Query Builder are available for download from the 'Releases' tab.

User Documentation

You can download the user documentation from the 'Releases' tab.

Installation

Download the VLinqSetup.msi file from the 'Releases' tab and follow the instructions.

Visual LINQ Query Builder - Home

Convert your Windows Server 2008 to a Workstation!

 

Convert your Windows Server 2008 to a Workstation!

Windows Server 2008 to Workstation Manual

This manual will help you to install Microsoft Windows Server 2008 and to configure your pc so you can use it as a workstation. Thanks to DAz999, you can also download the full manual as a 6MB pdf file from here! You can use the Windows Server 2008 Workstation Converter made by sawo if you want to automate the whole process. If you need any help, don’t hesitate to post your question on the forums.  You can watch screenshots of my final Windows Server 2008 workstation here.

If you are still not convinced why to use Windows Server 2008 as your workstation OS, read this article, and you will be installing Windows Server 2008 right after reading it!

Convert your Windows Server 2008 to a Workstation!

Robert Larson : Installing Updates on Server Core

 

Installing Updates on Server Core

I love Windows Server 2008 installed with Server Core. It’s small footprint (although it could be even smaller), simplistic command line UI, and the boot speed.  One thing I dislike (until recently) is installing updates on Server Core. Well I found a nice little sample script that works beautifully to check and install all available updates from the command line

http://msdn.microsoft.com/en-us/library/aa387102(VS.85).aspx

This is a VBScript  that uses the built in Windows Update Agent (WUA) to check for all available updates, provide you a list, and allow you to select to download and install the updates on your machine.

This makes updating a Server Core image a breeze.

Enjoy.

Robert Larson : Installing Updates on Server Core

Hyper-V Planning and Deployment Guide

 

Hyper-V Planning and Deployment Guide

The Hyper-V Planning and Deployment Guide is live in the download center today.

30 pages, covers:

• Overview of Hyper-V
• Before You Install Hyper-V
• Hardware Considerations
• About Virtual Machines and Guest Operating Systems
• Install the Hyper-V Role on a Server Core Installation of Windows Server 2008
• Install the Hyper-V Role on a Full Installation of Windows Server 2008
• Install and Configure Hyper-V Tools for Remote Administration
• Configuring Virtual Networks

What did we miss? Leave feedback here.

TONYSO : Hyper-V Planning and Deployment Guide

SSIS Stuff : Regular Expression Flat File Source

 

Regular Expression Flat File Source

The RegEx flat file source is one of the new community samples for SQL Server 2008 we’ve published to Codeplex. It uses regular expressions to extract values from a text file. It works similar to the flat file source, except that it’s not limited to CSV-type files (I saw a demo where the developer who created the sample used it to extract class names from a source files).

Note, when I ran the installer for the sample, it didn’t put the RegExFlatFileSource.dll file under 100\DTS\PipelineComponents. It only put the source down. We’ll either update the installer, or update the docs on the site. To get the component, I opened the project in Visual Studio, and ran a build. The project has a post build step which places the DLL under the PipelineComponents directory, and runs gacutil.exe to place it in the GAC.

SSIS Stuff : Regular Expression Flat File Source

Description of the Replay Markup Language (RML) Utilities for SQL Server

 

INTRODUCTION

The Microsoft SQL Server support team uses several internally written utilities to ease the work that is related to a typical customer support case. Database developers and system administrators can also use these utilities to work with Microsoft SQL Server 2000 or with Microsoft SQL Server 2005. These utilities are collectively called the Replay Markup Language (RML) Utilities for SQL Server.

 

MORE INFORMATION

You can use the RML Utilities for SQL Server to perform the following tasks:

•You can determine the application, the database, the SQL Server login, or the query that is using the most resources.

•You can determine whether the execution plan for a batch is changed when you capture the trace for the batch. Additionally, you can use the RML Utilities for SQL Server to determine how SQL Server performs each of these execution plans.

•You can determine the queries that are running slower than before.

After you capture a trace for an instance of SQL Server, you can use the RML Utilities for SQL Server to replay the trace file against another instance of SQL Server. If you also capture the trace during the replay, you can use the RML Utilities for SQL Server to compare the new trace file to the original trace file. You can use this technique to test how SQL Server behaves after you apply changes. For example, you can use this technique to test how SQL Server behaves after you do the following:

•You install a SQL Server service pack.

•You install a SQL Server hotfix.

•You update a stored procedure or a function.

•You update an index or create an index.

This version of the RML Utilities for SQL Server supersedes the earlier version. The earlier version of the RML Utilities for SQL Server is described in Microsoft Knowledge Base article 887057. For more information, click the following article number to view the article in the Microsoft Knowledge Base:  887057 (http://support.microsoft.com/kb/887057/) Description of the SQL Server Performance Analysis Utilities Read80Trace and OSTRESS

The earlier version of the RML Utilities for SQL Server supports the SQL Server 2000 trace file format only. This version of the RML Utilities for SQL Server supports the SQL Server 2005 trace file format and the SQL Server 2000 trace file format. If SQL Server 2005 is installed in your environment, you should always use this version of the RML Utilities for SQL Server even if you do not process SQL Server 2005 trace files. This version of the RML Utilities for SQL Server contains important software updates, new features, and performance improvements.

 

How to obtain the RML Utilities for SQL Server

The following files are available for download from the Microsoft Download Center:
Download the RMLSetup_X86.msi package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=7EDFA95A-A32F-440F-A3A8-5160C8DBE926&displaylang=en)

Download the RMLSetup_AMD64.msi package now. (http://www.microsoft.com/downloads/details.aspx?familyid=B60CDFA3-732E-4347-9C06-2D1F1F84C342&displaylang=en)

Note Microsoft provides the RML Utilities for SQL Server as-is. Microsoft Customer Support Services (CSS) does not provide support or updates for the RML Utilities for SQL Server. If you have a suggestion or if you want to report a bug, use the e-mail address in the Help file (RML Help.xps).

Description of the Replay Markup Language (RML) Utilities for SQL Server

Vyatta - Welcome to the Dawn of Open-Source Networking

 

http://www.vyatta.com/products/vyatta_514_datasheet.pdf

Vyatta has changed the networking world by commoditizing router, firewall and VPN deployment in the same way that Linux commoditized the operating system market. Each month more than 15,000 users worldwide download Vyatta's open-source networking platform in their search for an alternative to over-priced, inflexible products from proprietary vendors. Download your free copy of the Vyatta software today to test, build, and grow advanced networks...

Vyatta - Welcome to the Dawn of Open-Source Networking

Feature Pack for SQL Server 2005 Feb 2007 - OLEDB Provider for DB2

 

Microsoft OLEDB Provider for DB2

The Microsoft OLE DB Provider for DB2 is a COM component for integrating vital data stored in IBM DB2 databases with new solutions based on Microsoft SQL Server 2005 Enterprise Edition and Developer Edition. SQL Server developers and administrators can use the provider with Integration Services, Analysis Services, Replication, Reporting Services, and Distributed Query Processor. Run the self-extracting download package to create an installation folder. The single setup program will install the provider and tools on x86, x64, and IA64 computers. The package includes product updates in the form of an integrated Service Pack 1. Read the installation guide and Readme for more information.
Audience(s): Customer, Developer

Package (DB2OLEDB.exe) - 8276 KB

Download details: Feature Pack for SQL Server 2005 Feb 2007

/n software inc - NetCmdlets for Windows PowerShell

 

The /n software NetCmdlets extend the features of Microsoft Windows PowerShell with a broad range of network management and messaging capabilities. The current release contains more than 30 Cmdlets providing access to network and host protocols such as SNMP, LDAP, DNS, Syslog, HTTP, WebDav, FTP, SMTP, POP, IMAP, Rexec/RShell, Telnet, and more.

NEW: NetCmdlets V2.0 - BETA

NetCmdlets V2 is packed full of exciting new features including PowerShell Server (formerly PowerShell Remoting), Parameter Sets, Object Pipelining, and new Cmdlets for SSH Enabled Remoting and Amazon Web Services (S3) Integration.

Networking & Internet Technologies

Using Windows PowerShell and NetCmdlets, System Administrators can easily script common network management tasks including router configuration, switch port monitoring, directory access, VLAN administration, remote execution, etc.

Device Management
SNMP device monitoring and management capabilities, complete with SNMPv3 Security.

Remote Access
Secure Shell enabled remote execution using Rexec, Rshell, or SSH.

Directory Administration
Access Active Directory or OpenLDAP servers through LDAP Directory Access.

Email Send & Receive
Send HTML Emails or Emails with file attachments. Retrieve Email through POP or IMAP Connectivity.

File Transfer
File transfer capabilities through FTP, TFTP, & RCP connectivity.

Instant Messaging
Jabber Instant Messaging, SMS messaging, and Alphanumeric Paging.

Network Monitoring
Listen and react to SNMP Traps and Syslog event messages or access raw Ethernet Packet captures.

Access to Web Services
Connect to web services through HTTP and RSS client capabilities.

DNS Configuration
Monitor DNS and other network configuration changes.

Encoding / Decoding
A complete array of utility encoding and decoding capabilities including MIME, UUEncoding, URL, Hex, etc.

Zip Compression
File compression including password protection, AES Encryption, and 4GB+ archive support.

/n software inc - NetCmdlets for Windows PowerShell

MS-SQL 2005 - tablediff

Tablediff is a really handy tool which can be used to fix data sync issues.  It is located in the 90\COM directory.  If you are ever in a situation whereby replica databases are out of sync then tablediff can save your life.  It will compare two tables and generate and output, which includes the T-SQL to fix the data, really handy for avoiding a re-initialisation of the data.

Take a look at the info here: http://msdn.microsoft.com/en-us/library/ms162843.aspx

It’s also listed as one of the top 10 hidden gems in SQL Server 2005 http://www.microsoft.com/technet/prodtechnol/sql/bestpractice/gems-top-10.mspx

Benjamin Wright-Jones : tablediff

Practices for Shared Virtual Machines

 

Turn off the Shutdown Event Tracker

The Shutdown Event Tracker is a feature in Windows Server that prompts the user to explain why they are shutting down or restarting the server. While this is a useful feature for production servers, it's just annoying for shared virtual machines. If you're not sure what I'm talking about, here's a screen shot of the dialog displayed by the Shutdown Event Tracker:

To prevent Windows Server from display this dialog when someone shuts down the virtual machine, follow the steps below:

1. Run the Group Policy Object Editor (gpedit.msc)
   
2. Navigate to the Local Computer Policy > Computer Configuration > Administrative Templates > System node in the tree control on the left and double click the "Display Shutdown Event Tracker" item on the right.
   
3. Click the "Disabled" radio button to disable the Shutdown Event Tracker.
   

Turn on Automatic Logon

Keeping track of logon credentials for shared virtual machines is cumbersome. You generally end up creating a text file with the credentials and placing that text file in the directory with the virtual machines files and hope that they stay together as a set. The easier way to do it is to enable automatic logon in the virtual machine.

1. Run the Registry Editor (regedt32.exe).
   
2. Locate the following key in the registry:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
   
   Double-click the DefaultUserName entry, type your user name, and then click OK.
3. Double-click the DefaultPassword entry, type your password, and then click OK. NOTE: If the DefaultPassword value does not exist, it must be added. To add the value, follow these steps:
   • On the Edit menu, click New, and then point to String Value.
   • Type DefaultPassword, and then press ENTER.
   • Double-click DefaultPassword.
   • In the Edit String dialog, type your password and then click OK.
     NOTE: If no DefaultPassword string is specified, Windows automatically changes the value of the AutoAdminLogon key from 1 (true) to 0 (false), disabling the AutoAdminLogon feature.
4. On the Edit menu, click New, and then point to String Value.
5. Type AutoAdminLogon, and then press ENTER.
6. Double-click AutoAdminLogon.
7. In the Edit String dialog box, type 1 and then click OK.
8. Quit the Registry Editor.

Note: To bypass the AutoAdminLogon process and to log on as a different user, hold down the SHIFT key after you log off or after Windows restarts.

Additional Software

Consider installing some additional software for to make the virtual machine more convenient to use.

• BgInfo. How many times have you walked up to a system in your office and needed to click through several diagnostic windows to remind yourself of important aspects of its configuration, such as its name, IP address, or operating system version If you manage multiple computers you probably need BGInfo. It automatically displays relevant information about a Windows computer on the desktop's background, such as the computer name, IP address, service pack version, and more. You can edit any field as well as the font and background colors, and can place it in your startup folder so that it runs every boot, or even configure it to display as the background for the logon screen.

Jim Lamb : Best Practices for Shared Virtual Machines

Carpe Datum : Free "Basic Training" for SQL Server

 

Basics Podcast: http://edge.technet.com/Tags/Database+Administration/feed/ipod/

Free SQL Server Learning Videos: http://www.microsoft.com/sql/editions/express/learnvideos.mspx

General SQL Server Learning and Education: http://www.microsoft.com/sql/techinfo/default.mspx

General SQL Server Learning and Education: http://technet.microsoft.com/en-us/sqlserver/bb331758.aspx

Learning SQL Server using the Sample Databases: http://msdn.microsoft.com/en-us/library/ms124501.aspx

SQL Server for the Oracle DBA: http://www.microsoft.com/sql/prodinfo/compare/oracle/oracledba/quickguide/index.htm

SQL Server DBA Handbook (oldie but a goodie): http://www.microsoft.com/technet/prodtechnol/sql/2000/books/adminpoc.mspx

SQL Server Express – Sample Applications: http://www.microsoft.com/sql/editions/express/samplewebapps.mspx

Lots of free database schemas: http://www.microsoft.com/sql/editions/express/starterschemas.mspx

SQL Server Basics in Flash: http://www.eggheadcafe.com/videodemo/default.asp

Webcasts, Virtual Labs and Podcasts: http://www.microsoft.com/events/series/Technetsqlserver2005.aspx

SQL Server Whitepapers: http://www.sqlskills.com/whitepapers.asp

“Ask Stan”: http://sqlserverpedia.com/blog/

Basic Programming Training videos: http://msdn.microsoft.com/en-us/beginner/default.aspx

SSIS Learning Resources: http://sqlserver-qa.net/blogs/tools/archive/2008/04/07/sql-server-integration-services-ssis-learning-materials-and-web-resources-for-beginners.aspx

Carpe Datum : Free "Basic Training" for SQL Server

Good video tutorials on the game of Go

 

Video Tutorial for the Game of Go (WeiQi, Baduk) - Part 1

Video Tutorial for the Game of Go (WeiQi, Baduk) - Part 2

Video Tutorial for the Game of Go (WeiQi, Baduk) - Part 3a

Video Tutorial for the Game of Go (WeiQi, Baduk) - Part 3b

John Coyne's Embedded Blog : It's the End for 3.11!!

 

It's the End for 3.11!!

for those that were not aware, we recently announced that effective November 1st, 2008, OEM's will no longer be able to license Windows for Workgroups 3.11 in the embedded channel. Now we all know that it's been long gone in the standard (retail/OEM) channel, but one of the unique things in the embedded business is that we allow the classic OS products to be sold longer than the other channels. it's *finally the end of an era!

John Coyne's Embedded Blog : It's the End for 3.11!!

Windows PowerShell : Update-Gac.ps1

 

Update-Gac.ps1

Below is the content of the Update-GAC.ps1 script that I run whenever I install a new version of PowerShell. Our installation is supposed to ngen the assemblies in the background. If that works, it doesn't work fast enough for me. Also I've seen lots of examples where people run this script long after their install and things get a TON faster so …. The install team is looking into the issue but until then – here is the script I use:

Set-Alias ngen @(
dir (join-path ${env:\windir} "Microsoft.NET\Framework") ngen.exe -recurse |
sort -descending lastwritetime
)[0].fullName
[appdomain]::currentdomain.getassemblies() | %{ngen $_.location}

Cheers!

Jeffrey Snover [MSFT]
Windows Management Partner Architect

Windows PowerShell : Update-Gac.ps1

Debian OpenSSL Predictable PRNG Toys

 

 

The Bug

On May 13th, 2008 the Debian project announced that Luciano Bello found an interesting vulnerability in the OpenSSL package they were distributing. The bug in question was caused by the removal of the following line of code from md_rand.c

	MD_Update(&m,buf,j);
	[ .. ]
	MD_Update(&m,buf,j); /* purify complains */

These lines were removed because they caused the Valgrind and Purify tools to produce warnings about the use of uninitialized data in any code that was linked to OpenSSL. You can see one such report to the OpenSSL team here. Removing this code has the side effect of crippling the seeding process for the OpenSSL PRNG. Instead of mixing in random data for the initial seed, the only "random" value that was used was the current process ID. On the Linux platform, the default maximum process ID is 32,768, resulting in a very small number of seed values being used for all PRNG operations.

The Impact

All SSL and SSH keys generated on Debian-based systems (Ubuntu, Kubuntu, etc) between September 2006 and May 13th, 2008 may be affected. In the case of SSL keys, all generated certificates will be need to recreated and sent off to the Certificate Authority to sign. Any Certificate Authority keys generated on a Debian-based system will need be regenerated and revoked. All system administrators that allow users to access their servers with SSH and public key authentication need to audit those keys to see if any of them were created on a vulnerabile system. Any tools that relied on OpenSSL's PRNG to secure the data they transferred may be vulnerable to an offline attack. Any SSH server that uses a host key generated by a flawed system is subject to traffic decryption and a man-in-the-middle attack would be invisible to the users. This flaw is ugly because even systems that do not use the Debian software need to be audited in case any key is being used that was created on a Debian system. The Debian and Ubuntu projects have released a set of tools for identifying vulnerable keys. You can find these listed in the references section below.

Debian OpenSSL Predictable PRNG Toys

Hyper-V RTM and WinPE Synthetic Devices

 

Hyper-V RTM and WinPE Synthetic Devices

Now that we've reached the RTM milestone with Hyper-V (and why I'm actually on vacation), here's the updated script for how to add the Hyper-V synthetic drivers to WinPE (original post here)

%echo off

set MSUSOURCE=D:\synth\rtm\amd64

set PESOURCE=D:\winpe_x64_synthetic

mkdir %temp%\IC

c:\windows\system32\expand.exe -F:* %MSUSOURCE%\Windows6.0-KB951634-x64.msu %temp%\ic

mkdir %temp%\IC\binaries

c:\windows\system32\expand.exe -F:* %temp%\ic\Windows6.0-KB951634-x64.CAB %temp%\ic\binaries

"C:\Program Files\Windows OPK\Tools\PETools\peimg.exe" /inf=%temp%\IC\binaries\amd64_wnetvsc.inf_31bf3856ad364e35_6.0.6001.18016_none_b337f91d87dbf1d0\wnetvsc.inf %PESOURCE%\mount\Windows

"C:\Program Files\Windows OPK\Tools\PETools\peimg.exe" /inf=%temp%\IC\binaries\amd64_ws3cap.inf_31bf3856ad364e35_6.0.6001.18016_none_f2e1ba67fcb48f61\ws3cap.inf %PESOURCE%\mount\Windows

"C:\Program Files\Windows OPK\Tools\PETools\peimg.exe" /inf=%temp%\IC\binaries\amd64_wstorflt.inf_31bf3856ad364e35_6.0.6001.18016_none_1cadbbeed0ad55a3\wstorflt.inf %PESOURCE%\mount\Windows

"C:\Program Files\Windows OPK\Tools\PETools\peimg.exe" /inf=%temp%\IC\binaries\amd64_wstorvsc.inf_31bf3856ad364e35_6.0.6001.18016_none_836399a4204c4863\wstorvsc.inf %PESOURCE%\mount\Windows

"C:\Program Files\Windows OPK\Tools\PETools\peimg.exe" /inf=%temp%\IC\binaries\amd64_wvmbus.inf_31bf3856ad364e35_6.0.6001.18016_none_959a72f36267838a\wvmbus.inf %PESOURCE%\mount\Windows

"C:\Program Files\Windows OPK\Tools\PETools\peimg.exe" /inf=%temp%\IC\binaries\amd64_wvmbushid.inf_31bf3856ad364e35_6.0.6001.18016_none_4ccff81064c7c78f\wvmbushid.inf %PESOURCE%\mount\Windows

"C:\Program Files\Windows OPK\Tools\PETools\peimg.exe" /inf=%temp%\IC\binaries\amd64_wvmbusvideo.inf_31bf3856ad364e35_6.0.6001.18016_none_af52382097951fd7\wvmbusvideo.inf %PESOURCE%\mount\Windows

"C:\Program Files\Windows OPK\Tools\PETools\peimg.exe" /inf=%temp%\IC\binaries\amd64_wvmic.inf_31bf3856ad364e35_6.0.6001.18016_none_5dfb8c2804cc9e9a\wvmic.inf %PESOURCE%\mount\Windows

Published Wednesday, July 02, 2008 5:39 AM by mikester

Filed under: Hyper-V WinPE IC

Mike's Blog, or how I learned to love the virtual machine... : Hyper-V RTM and WinPE Synthetic Devices