But here's the problem - the ISP Redundancy feature within TMG required a static IP address and DNS entries. Most residential/mass markets ISPs make it very challenging to get a static IP address now.

So here's a handy script to update your ISP redundancy gateway settings if you're using multiple ISPs providing DHCP addressing. In this example I've named my external network adapters "DSL" & "Cable" for easy reference and set this script to as a scheduled task on the TMG server:

$root = new-object -comobject "FPC.Root"

$isaArray = $root.GetContainingArray()

$networks = $isaarray.networkconfiguration.networks

$External = $networks | ? {$_.Name -eq "External"}

$IspConfig = $External.IspRedundancyConfig

$ISPs = $IspConfig.Isps

$Cable = $ISPs | ? {$_.Name -eq "Cable"}

$DSL = $ISPs | ? {$_.Name -eq "DSL"}

If($Cable.GatewayIPAddress -ne ((netsh interface ip show address "Cable" | `

select-string "Default Gateway") -replace '^[^\d]+'))

$Cable.GatewayIPAddress = (netsh interface ip show address "Cable" | `

select-string "Default Gateway") -replace '^[^\d]+'

$Cable.Save()

If($DSL.GatewayIPAddress -ne ((netsh interface ip show address "DSL" | `

select-string "Default Gateway") -replace '^[^\d]+'))

$DSL.GatewayIPAddress = (netsh interface ip show address "DSL" | `

select-string "Default Gateway") -replace '^[^\d]+'

$DSL.Save()

 Here's a sample of the script we use - keeping in mind that we're making Powershell Inoke-Command calls (icm as noted in the script) and have Windows Remote Management enabled:

# Making life easier by creating the iSCSI drive mappings via Powershell.

# However, the Microsoft Initiator isn't natively powershell enabled, the calls

# must be made through the command line interface of iscsicli.exe.

# This script addresses the pain involved in dealing with larger numbers of servers,

# in our data center this includes numerous Hyper-V Clusters with

# Clustered Shared Volumes where we'd have quite a lot of UI clicking to do.

### Import CSV for the list of Hostnames, Portals and Targets (volumes)

### The comma seperated file is easily managed with native powershell cmdlets.

#

### The file header includes: Hostname,Cluster,IP,InitiatorIQN,iSCSI_Portal,iSCSI_Target

### Hostname: Server Hostname, ie: "command prompt 'hostname'"

### IP: Preferred source IP for the initiator

### InitiatorIQN: Not required for the scripts, but useful as a reference

### iSCSI_Portal: IP of the target portal

### iSCSI_Target: Full IQN of the target volume

$FileName = "\\jamels-server\scripts\iscsi\VolumeMaps.csv"

# check for second argument, which would be a ServerName

# in this case we only need to execute commands for that specfic server

# rather than the entire Data Center

if($args.count -gt 1)

{

      $args[1]

      $VolumeMaps = Import-CSV $FileName

      $ServerName = $args[1]

      $VolumeMaps = $VolumeMaps | ? {$_.Hostname -ilike $ServerName}

}

else

{

      $VolumeMaps = Import-CSV $FileName

}

# Constants - if using standard target ports, the Microsoft iSCSI Initiator

# and leveraging MPIO

$iSCSI_Port = "3260"   

$iSCSI_Initiator = "Root\ISCSIPRT\0000_0"

$iSCSI_MPIO = "0x00000002"

if($args.count -eq 1)

{

      ForEach($MapItem in $VolumeMaps)

      {

            # Dynamic Variables

            $iSCSI_Portal = $MapItem.iSCSI_Portal

            $iSCSI_Target = $MapItem.iSCSI_Target

            $ServerName = $MapItem.HostName

            # Get the iSCSI Port Number for the specified IP address

            # We first convert the needed iSCSI source address to the IPv4 format within WMI

            # Then Via WMI we query into the MSiSCSI_PortalInfoClass to find the correct Interface Index Number

            # this index number will be used for several iscsicli.exe invoke-expression calls

            $IPAddress = [system.Net.IPAddress]$MapItem.IP

            $PortalList = get-wmiobject -ComputerName $ServerName -namespace root\wmi -query "select portalinformation from MSiSCSI_PortalInfoClass"

            $iSCSIPortID = ($PortalList.PortalInformation | ? {$_.IpAddr.IPV4Address -match $IPAddress.Address} | select port)

            # Always refresh the target portal list and the currently connected target volumes

            $Command = [scriptblock]::Create("iscsicli.exe refreshtargetportal $iSCSI_Portal $iSCSIPort")

            icm $ServerName -ScriptBlock $Command

            start-sleep 2

            #Verify info

            $ServerName

            $MapItem.IP

            $iSCSIPortID.Port

            $iSCSI_Portal

            $iSCSI_Target

            ### Add the Target to the Favorites list, doesn't login until a reboot (reconnects for every reboot)

            if($args[0] -ilike "Favorites")

            {

                  $Command = [scriptblock]::Create("iscsicli PersistentLoginTarget $iSCSI_Target T $iSCSI_Portal $iSCSI_Port $iSCSI_Initiator $iSCSIPortID.Port * $iSCSI_MPIO * * * * * * * * * 0")

                  icm $Servername -ScriptBlock $Command

                  start-sleep 2

            }

            ### Login to the target for this session since PersistentLoginTarget Doesn't Login until reboot

            if($args[0] -ilike "LoginTarget")

            {

                  $Command = [scriptblock]::Create("iscsicli LoginTarget $iSCSI_Target T $iSCSI_Portal $iSCSI_Port $iSCSI_Initiator $iSCSIPortID.Port * $iSCSI_MPIO * * * * * * * * * 0")

                  icm $Servername -ScriptBlock $Command

                  start-sleep 2

            }

      }

}

With this in mind, during the first week of November we deployed to our core production network a unified data center fabric of 10 gigabit Ethernet. Migrating well over 600 Hyper-v based virtual machine from a fiber channel fabric to hosts using the Microsoft iSCSI iniatior, Intel dual port 10gigE NICs and multi-session/target based iSCSI connections.

 I viewed 10 gigabit ethernet from a different perspective than just performance and service delivery of multiple data center services. 10gigE has the potential of providing a unified data center fabric which in turn provides our small and agile operations staff with the ability to manage a more intuitive infrastructure. To build unified and reusable sets of automation tools that can easily span across multiple services such as data center storage (SAN) and provisioning of networks (802.1q trunks to Hyper-V virtualization hosts).

 However, I was very pleasantly surprised when we discovered the performance improvement and ability to fully utilize our investment in our new gear. There were concerns that iSCSI wouldn't perform, couldn't achieve over 60-70% line rates or rumors that it was still just for small or mid-sized networks. But these concerns were quickly dispelled - we are able to fully tax our links to our iSCSI targets with surprisingly minimal impact on the host and target CPU and memory (task manager perfmon attached showing over 90% utilization via one server and port).

Perfmon.png

Also – keep in mind that publishing VMRC through a reverse NAT, ISA or TMG gateway can be tricky since the client will attempt to resolve back to the Hyper-V host. This will need to be taken into consideration if clients require VMRC access. 

Connection type	Protocol	Default port	Where to change the port setting
VMM server to VMM agent on Windows Server–based host (control)	WinRM	80	During VMM setup, registry
VMM server to VMM agent on Windows Server–based host (data)	SMB	445	Registry
VMM server to remote Microsoft SQL Server database	TDS	1433	Registry
VMM server to P2V source agent	DCOM	135	Registry
VMM Administrator Console to VMM server	WCF	8100	During VMM setup, registry
VMM Self-Service Portal Web server to VMM server	WCF	8100	During VMM setup
VMM Self-Service Portal to VMM self-service Web server	HTTPS	443	During VMM setup
VMM library server to hosts	BITS	443	During VMM setup, registry
VMM host-to-host file transfer	BITS	443	Registry
VMRC connection to Virtual Server host	VMRC	5900	VMM Administrator Console, registry
VMConnect (RDP) to Hyper-V hosts	RDP	2179	VMM Administrator Console, registry
Remote Desktop to virtual machines	RDP	3389	Registry
VMware Web Services communication	HTTPS	443	VMM Administrator Console, registry
SFTP file transfer from VMWare ESX Server 3.0 and VMware ESX Server 3.5 hosts	SFTP	22	Registry
SFTP file transfer from VMM server to VMWare ESX Server 3i hosts	HTTPS	443	Registry

NOTE: This process will erase everything on your thumb drive, replacing the data with the installation files for the OS. Also, at leat a 4GB thumb drive is required. 

 To setup a USB thumb drive for either Windows 7 or Windows 2008 R2 installs you have to prepared the thumb drive using the following commands:

1)  From an elevated privileges command prompt (run as administrator) execute 'diskpart'

2) list disk

3) select disk 1 (or the drive number that is your thumb drive, be cautious here and verify that you choose the correct drive)

4) clean

5) create partition primary

6) select partition 1

7) active

8) format fs=fat32

9) assign

10) exit

11) Using your mounted ISO image and/or your installation media:

xcopy d:\*.* /s /e /f e:\ 

(the drive letter being the letter of the thumb drive and destination drive letter of your USB thumb drive)

Hopefully these qucik steps and process will save you some time!

-Jeff Amels

MPSC Technical Operations Lead

To address this requirement the MPSC looked at several pre-existing technologies used for massive file distribution systems such as the Windows Update services and discovered the common component of BITS (Background Intelligent Transfer Service). BITS enables applications and powershell access for asynchronously transfering large files while preserving the the responsiveness of other network applications. And provided the ability to restart file transfers in the event of a network outage/latency or even if the system reboots.

A primer for using BITS can be found in the MSDN site https://msdn.microsoft.com/en-us/library/aa362708(VS.85).aspx however there are two critical pieces, the server and the client. In our case we needed the server to be highly available to a large number of customers. And for the client we decided on the use of powershell for easier automation through the use of powershell.

Using IIS for receiving files via BITS:

• On Windows Server 2008, use the Server Manager to install the BITS Server Extensions feature. From Server Manager, click Features in the left pane. In the Add Features Wizard, check BITS Server Extensions. Note that the IIS 6 Management Compatibility roles must be installed.
• To use the IIS user interface to configure the virtual directory for BITS uploads, select Properties from the context menu of the virtual directory. Press the BITS Extension tab to access the BITS properties page (the BITS server extension ISAPI must be installed). Change the default property values as appropriate and enable the directory for uploads; you cannot upload files until the directory is enabled. For details on setting the property values, see the online Help.

Using Powershell to upload files:

Simple sample powershell script to upload a file -

Import-Module BitsTransfer

NOTE: The powershell CmdLet for BITS changed from the Windows 7 Beta to the Windows 7 RC. Primarily the modiule changed from Filetransfer to BitsTransfer.

Jeffrey Amels - MPSC Technical Operations Lead

jamels@microsoft.com

 Manually Assign a KMS Host

If your network does not support DDNS, you need to manually assign a KMS host to your KMS clients. Manually assigning a KMS host disables auto-discovery of KMS on a KMS client.

To manually assign a KMS host to a KMS client

1.      Log on to the KMS client computer.

2.      Open an elevated command prompt. To do this, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

3.      At the command prompt, type one of the following options and press Enter:

a.      To assign a KMS host using the host's FQDN, type:
cscript \windows\system32\slmgr.vbs /skms <KMS_FQDN>:<port>

b.     To assign a KMS host using the host's version 4 IP address, type:
cscript \windows\system32\slmgr.vbs /skms <IPv4Address><:port>

c.     To assign a KMS host using the host's version 6 IP address, type:
cscript \windows\system32\slmgr.vbs /skms <IPv6Address><:port>

d.     To assign a KMS host using the host's NETBIOS name, type:
cscript \windows\system32\slmgr.vbs /skms <NetbiosName><:port>

After assigning the KMS host, the system can then be actived by again using the slmgr.vbs script along with the activation parameter:

cscript \windows\system32\slmgr.vbs /ato

Jeffrey Amels - MPSC Technical Operations Lead - jamels@microsoft.com

MPSC supports: MCS ROINow Virtualization Workshop

The Microsoft Partner Solutions Center

        9 Multi-processor Fujitsu Hyper-V Server hosts

        3 identical Virtualization & System Center based data centers consisting of:

        Windows 2008

        Core domain services

        Microsoft Hyper-V

        System Center Virtual Machine Manager

        Each datacenter pod is a replica – a copy of the ‘gold copy’

        Multiple & concurrent workshop attendee or customer access from various global locations:

        Enabled with Microsoft based remote access features such as Remote Desktop Gateways

        Rapid redeployment of workshop server images:

        Using the Windows Automated Installation Toolkit for Windows 2008

Description of Engagement:

The goal of these workshops is to provide customers a “behind the scenes with MCS” proof-of-concept experience and a customized report showing how they can achieve ROI Now using Microsoft Integrated Virtualization.

ü  Focus on reducing costs for customers and how virtualization can quickly show a return on investment

What is the MPSC?

The Microsoft Partner Solutions Center (MPSC) is a place where customer needs meet innovation design. At the core of the MPSC Dynamic IT Datacenter is Microsoft’s virtualization technology for server consolidation which was recently migrated from 700 to 22 Sun servers within 3 months. The MPSC is designed to handle remote and/or onsite engagements in a virtual lab environment using Microsoft products. We offer an IT engagement lab that exists to support the field sales efforts of both Microsoft and our member partners by designing and demonstrating real customer solutions. We also specialize in world-wide applications and services offered either to or through the enterprise in the communications sector.

We are located on the Microsoft Redmond campus where our facilities and services are designed to engage the enterprise end-customer through executive briefing, technology demonstration, architectural design session, proof-of-concept, pilot, or training all of which can be customized for each specific opportunity.

MPSC Contacts:

David Hayes, Director MPSC, (dhayes@microsoft.com)

Jeff Amels, Technical Operations Lead, MPSC (jamels@microsoft.com)

MPSC Customer Event: How to configure carrier hosted voice within HMC 4.5 event

The Microsoft Partner Solutions Center

       A Sun Microsystems Sunfire 4450 providing Microsoft Hyper-V services

       Over 24 Virtual Machines representing a full carrier class HMC 4.5 and hosted voice service

       Hosted Voice gateway & IP PBX:

       Audiocodes PSTN gateway

       Broadsoft IP PBX & Mediation Services

       Virtualization environment also hosted the addition development/staging virtual machines

       Students access their environment through globally accessible Remote Desktop via Terminal Services Gateway

       2.5 T of SAN services

Description of Engagement:

Two-day technical training session in Redmond, Washington on how to configure carrier hosted voice within HMC 4.5. This training is for:

       NEPs (providing hosted VoIP)

       ISVs (offering HMC / VoIP provisioning solutions)

       Systems Integrators (deploying and supporting an integrated HMC / VoIP solution)

       Microsoft Hosting Technical Solution Specialists (required for pre-sales positioning)

The training is a fundamental part of the HMC / hosted VoIP solution that will be deployed by Service Providers worldwide. Sessions will be split between:

       HMC solution overview

       OCS configuration guidance demos of how to configure various solutions (RCC, OC as softphone, dual forking)

       Hands-on-lab

The training will be supported by members of the HMC and OCS product teams as well as two of our partners, Implement.com and tekVizion. tekVizion will wrap up the event with information on the HMC / VoIP certification program.

The training will be supported by members of the HMC and OCS product teams as well as two of our partners, Implement.com and tekVizion. tekVizion will wrap up the event with information on the HMC / VoIP certification program.

What is the MPSC?

The Microsoft Partner Solutions Center (MPSC) is a place where customer needs meet innovation design. At the core of the MPSC Dynamic IT Datacenter is Microsoft’s virtualization technology for server consolidation which was recently migrated from 700 to 22 Sun servers within 3 months. The MPSC is designed to handle remote and/or onsite engagements in a virtual lab environment using Microsoft products. We offer an IT engagement lab that exists to support the field sales efforts of both Microsoft and our member partners by designing and demonstrating real customer solutions. We also specialize in world-wide applications and services offered either to or through the enterprise in the communications sector.

We are located on the Microsoft Redmond campus where our facilities and services are designed to engage the enterprise end-customer through executive briefing, technology demonstration, architectural design session, proof-of-concept, pilot, or training all of which can be customized for each specific opportunity.

MPSC Contacts:

David Hayes, Director MPSC, (dhayes@microsoft.com)

Jeff Amels, Technical Operations Lead, MPSC (jamels@microsoft.com)

In a datacenter, each action taken represents a fraction of effort required. An update of a software component may take 4 minutes, but when considering the bigger picture that’s 4 minutes for every server in your datacenter. My point is that manageability/reusable work is essential. Cluster Shared Volumes delivers on that order.

Here at the MPSC, we manage a lot of virtual machines and physical hosts. We use SAN over fiber for storage and the Sun Sunfire 4450’s as high volume / small footprint Hyper-V hosts. This presents some challenges with respect to management over time as service delivery scales up. SCVMM 2008 curtails some of the headache but is agnostic in regards to storage and availability. CSV in Server 2008 R2 and the release of SCVMM 2008 R2 brings all of these issues into alignment.

Rather than managing tens or hundreds of LUN’s, this presents a LUN in a way that is mappable (with read/write) to more than one host and offers failover between them. Meaning one LUN to rule them all (if you so choose). In terms of virtual machines, not only does this make them highly available but also eliminates downtime due to host maintenance or other unforeseen failures. Add the self provisioning function of the Self Service Portal from SCVMM and we’re exposing an easily managed on-demand virtual machine environment. All I can say is someone has heard our prayers.