September 2010 - Posts
Nice document from the MSSpringboard Twitter.
Download the document here.
Frequently Asked Questions
The Microsoft Office 2010 Office Deployment Kit for App-V is required for sequencing and deploying Microsoft Office 2010. It enables specific features for 32-bit versions of Microsoft Office 2010, including:
- Extend virtual Office 2010 usage via improved SharePoint integration to Open, Save, Edit files
- Find your email items quickly with Outlook’s Fast Search
- Connect to your inbox using Microsoft Outlook Send To functionality
- Print your documents directly to OneNote
- Find contents within your documents using Office Document Indexing
- Open Web-based calendar items and RSS Feeds in Outlook
- Perform advanced mail configuration using the Virtual Mail Applet
What benefits does the customer receive when using Office 2010 and App-V together?
Deploying Office 2010 with App-V 4.6 solves the top problems we hear from customers:
1. Speeds up deployment time
2. Easier migration to the latest version of Office
3. Easier application patching and management
Additional benefits include: App-V packages (including Office 2010) can be sent to client machines running 64-bit operating systems. App-V virtualized Outlook 2010 search is fast and instantaneous, just like non-virtualized Outlook search.
Can I use Click-to-Run to deploy Office 2010 with App-V to the enterprise?
Click-to-Run is a new delivery mechanism for certain retail Office 2010 SKUs intended for end users. Click-to-Run Office products are not customizable and cannot be deployed in the enterprise like other App-V packages. Enterprises interested in deploying Office 2010 via App-V must sequence their own Office 2010 packages. Sequencing Office 2010 requires use of the Microsoft Office 2010 Deployment Kit for App-V, which enables the licensing platform to work with App-V virtualized Office applications.
What OS versions does the Deployment Kit work with?
The following list outlines the supported operating systems for running the Microsoft Office 2010 Office Deployment Kit for App-V.
SP2 or SP3
Business, Enterprise, or Ultimate
No service pack, SP1, or SP2
Professional, Enterprise, or Ultimate
Windows Server 2003 Remote Desktop Services
Standard Edition, Enterprise Edition, or Datacenter Edition
SP1 or SP2
Windows Server 2008 Remote Desktop Services
Standard, Enterprise, or Datacenter
SP1 or SP2
Windows Server 2008 R2 Remote Desktop Services
Standard, Enterprise, or Datacenter
Does this solve the existing problems with Office 2007 and App-V?
No. This solution does not correct the current limitations when using Office 2007 and App-V together.
Are administrative rights required to install the Deployment Kit?
Yes. The Deployment Kit is an MSI that must be installed with administrative rights.
Can I deliver/install the Deployment Kit via System Center Configuration Manager or other software delivery tools?
The Deployment Kit can be deployed like any other MSI. Software delivery tools like System Center Configuration Manager can deliver and install the MSI.
Can I sequence/launch Office 2010 with App-V 4.5x/4.2?
No. Office 2010 is supported only on versions App-V 4.6 and later. We are evaluating the cost of supporting Office 2010 with App-V 4.5, but there are no current plans for support at this time.
Can I deploy Office 2010 to production using App-V?
No. Office 2010 Deployment Kit is pre-release. Production deployments are not supported.
Can I upgrade my existing App-V 4.6 Beta Client to the App-V 4.6 Client?
No. The App-V 4.6 Beta Client should be uninstalled before installing the App-V 4.6 Client.
What versions of Office 2010 require use of the Deployment Kit when deployed with App-V?
All. The Deployment Kit serves two purposes: to enable Office 2010 licensing to work for virtualized Office and to enable certain integration features. Please note that all versions of Office 2010 require the Deployment Kit for the licensing components, but the integration features are optional and only supported for 32-bit versions of Office.
Which Office 2010 Beta products can I sequence and deploy with App-V?
The following Office 2010 Beta products may be deployed with App-V:
· Office Professional Plus 2010 Beta
· Office Visio 2010 Beta
· Office Project 2010 Beta
Will I need to redeploy the Deployment Kit when App-V and Office final versions are released?
Yes – this is standard procedure. All beta versions should be removed before RTM version is deployed. To re-deploy, make sure to uninstall the Deployment Kit before installing the latest version.
Why does Office 2010 use the new SPP licensing platform?
The Software Protection Platform (SPP) is new for Office 2010 and leverages the same licensing functionality introduced in Windows Vista and included in all versions of Windows 7. SPP is included in, and required for, all Office 2010 client skus and is an important part of the Office anti-piracy strategy.
To learn more about volume activation of Office 2010, here are some useful links:
· Office Volume Licensing: http://blogs.technet.com/office2010/archive/2009/08/24/volume-activation.aspx
· Microsoft Office 2010 Activation Guidelines: https://partner.microsoft.com/40111510?msp_id=office2010activation
· Overview of Volume Activation for Office 2010: http://technet.microsoft.com/en-us/library/ee624349(office.14).aspx
When will Office 2010 be generally available?
Office 2010 will be available in the first half of 2010.
How does the Deployment Kit enable SPP licensing and the virtualization proxies to work?
Certain Office components like the SPP licensing platform or the Outlook Fast Search indexer cannot work when virtualized. These components integrate with local system features and will not function if they stay in the virtual environment. The Deployment Kit installs Office SPP and proxy components to the machine that facilitate communication between the native environment and the virtual environment.
You indicate the SPP Service must be installed on the Sequencer machine. So why doesn’t the Sequencer capture the SPP service so that I don’t have to install it natively?
All technologies physical or virtual require the SPP component to be installed in order to be in compliance with Office 2010 licensing. Virtualized Office 2010 will not self-install the SPP component when sequencing. Hence, the SPP must be installed in order to sequence Office 2010. The Sequencer actually does not care if the SPP service exists or not. The SPP service must also be natively installed on client machines because the licensing activates itself uniquely with the hardware (i.e., the client machine), and hence, requires a native presence on the machine.
Will Office 2010 work when deployed with App-V to both 32-bit and 64-bit Windows?
Yes. The licensing component is supported for both 32-bit and 64-bit Office on any 32-bit and 64-bit operating systems. Hence, Office 2010 will work when deployed to 32-bit or 64-bit. The caveat to remember is that the Office 2010 proxies are supported for 32-bit Office only.
Do I have to use the 4.6 Sequencer to sequence Office 2010?
Yes, Office 2010 will only work with App-V versions 4.6 and greater, including the Sequencer.
Will Office 2010 on App-V work on XP, Vista, and Windows 7?
Yes, this will work on XP, Vista, and Windows 7. We also support Windows 2003 Remote Desktop Services, Windows 2008 Remote Desktop Services, and Windows 2008 R2 Remote Desktop Services.
Will you publish an App-V recipe for how to do this once generally available?
Absolutely. We understand that virtualizing Office 2010 Beta is important so we have designed, created, and tested a recipe to sequence Office 2010 Beta to facilitate virtualizing the product. You can download the recipe from www.officeitpro.com
For normal MSI installations of Office 2010 Beta volume-license products, I need to have a Key Management Service (KMS) or Multiple Activation Key (MAK) volume activation solution. Does deploying Office 2010 Beta with App-V bypass these requirements?
No. Licensing for either MSI-deployed Office or App-V-deployed Office would require a MAK key(s) or activation against a KMS server. For more information, see http://technet.microsoft.com/en-us/office/ee691939.aspx
Is the Deployment Kit only to be used with App-V?
The Microsoft Office 2010 Deployment Kit for App-V is designed for App-V.
Great post by Michael from back in June. People often want to filter the Wizard presented by LTI to only display certain things depending on what you pick. Michael has a nice post on how to use selection profiles to do just that.
Read the full blog here.
Here’s a snippet:
I’ve talked with several people who have wanted to filter the list of items that are displayed in the Lite Touch wizard. Fortunately, that’s pretty simple to do as you can set the WizardSelectionProfile task sequence variable via CustomSettings.ini to specify the name of the selection profile that should be used to do the filtering: only the folders in the selection profile will be displayed for task sequences, applications, and language packs.
Full Article and download is linked here.
Installing Windows 7 isn't just about migrations. It's about daily management. It's about rapid deployment to fix problems. It's about provisioning virtual desktops in a VDI infrastructure. With today's technologies for user virtualization and application virtualization, fixing some IT problems can be fastest accomplished by simply rebuilding the computer. For all of these reasons, the outwardly simple process of installing Windows grows to become a much more critical activity than ever before. Installing Windows through automated means is even more important. That's why this book exists. While installing Windows the manual way requires as few as seven clicks and a bit of time, fully automating its installation requires quite a bit more effort. You need a project plan to get you started and a cookbook of step-by-step solutions to finish the job.
In Automating Windows 7 Installation for Desktop and VDI Environments, you'll deep dive into the steps required to automate Windows 7 installation. But you won't stop there. You'll dig deep into the ways in which that automated installation will fundamentally change how you do IT. You'll learn exactly how to automate Windows for an OS migration project, whether from Windows XP or Windows Vista. You'll discover the steps to wrap your automated installation into a VDI infrastructure, enabling virtual desktops to be provisioned automatically and on-demand. You'll learn the tips and tricks for layering the Windows OS, enabling you to fix common IT problems by simply rebuilding the user's computer - all while maintaining their applications and profile information and without needing to resort to roaming profiles.
Keep this book handy. You will find yourself turning back to it again and again as you fully automate one of the most time-consuming parts of your job: Windows 7 Installation.
Great post over the The Configuration Manager Support Team Blog talking about USMT 4.
Here’s a snippet:
Suppose you want to use the USMT 4 feature of hardlinking in a System Center Configuration Manager 2007 Task Sequence, but you notice that the "Capture User State"/"Capture User Files and Settings" and "Restore User State"/"Restore User Files and Settings" tasks do not have any options to perform a local capture with hardlinking. What's up with that?
Well what's going on is that USMT 4, which introduced hardlinking, shipped after ConfigMgr 2007 so the hardlinking option was not available in ConfigMgr 2007. However, USMT 4 support was added in ConfigMgr 2007 SP2, and via the OSDMigrateAdditionalCaptureOptions and OSDMigrateAdditionalRestoreOptions variables, a hardlink user migration can be accomplished in a ConfigMgr 2007 SP2 Task Sequence.
Out of the box, ConfigMgr 2007 SP2 only supports USMT 4 online captures, or captures that take place while in the full Windows OS. ConfigMgr 2007 SP2 does not support USMT 4 offline captures, or captures that take place while in WinPE. Offline captures are possible using the UDI feature of MDT 2010 Update 1 when it is integrated with ConfigMgr 2007 SP2.
With that said, there are several ways that a USMT 4 hardlink migration can be accomplished in a ConfigMgr 2007 Task Sequence, including:
- Create a new ConfigMgr 2007 Task Sequence that supports USMT 4 hardlinking.
- Modify an existing ConfigMgr 2007 Task Sequence that have the "Capture User State" and "Restore User State" tasks to support USMT 4 hardlinking.
Since USMT 4 support was not added until SP2 of ConfigMgr 2007, SP2 of ConfigMgr 2007 is required for hardlinking.
USMT 4 is supported in the following refresh scenarios:
- Windows XP --> Windows Vista
- Windows XP --> Windows 7
- Windows Vista --> Windows Vista
- Windows Vista --> Windows 7
- Windows 7 --> Windows 7
USMT 4 is not supported for Windows XP --> Windows XP scenarios.
Read the full article here.
The known issues in P2V Migration for Software Assurance beta are categorized as follows:
· On Windows XP operating systems, Disk2vhd.exe is hidden during the Capture VHD phase, but it is minimized to the task bar in Windows Vista. Clicking Help/Cancel in the Disk2vhd.exe tool while the Capture VHD task is running is not supported.
· If a non-administrative user has to run the Add Old Apps to Windows 7.hta script to add old operating system applications to the Windows 7 Start menu, that user would need Administrator credentials.
· In all System Center Configuration Manager scenarios and LTI Domain Join scenarios, the Add Old Apps to Windows 7.hta script does not run automatically: You must run it manually.
For Lite Touch Installation (LTI) deployments using MDT 2010 Update 1, P2V Migration for Software Assurance requires the following components:
· A functional installation of MDT 2010 Update 1 with mapped deployment shares on the client computer targeted for P2V Migration installation. The installation process for P2V Migration automatically copies required components to the MDT 2010 installation folder and deployment shares mapped in the MDT 2010 Deployment Workbench.
· An Internet connection or downloadable components listed in the previous section, available in C:\Program Files (x86)\P2V Migration for Software Assurance\Tools. If no Internet connection is available, you will need to copy these files manually.
· Sysinternals Disk2vhd 1.62 or later. The P2V Migration for Software Assurance installer will download Disk2vhd as part of the installation process. Pre-1.62 versions of Disk2vhd are not supported.
For Zero Touch Installation deployments using Microsoft System Center Configuration Manager 2007, P2V Migration requires the following components:
· A configured System Center Configuration Manager Operating System Deployment environment, with MDT 2010 Update 1 add-in components installed.
· An Internet connection or downloadable components listed in the previous section, available in C:\Program Files (x86)\P2V Migration for Software Assurance\Tools.
The client computers targeted for VHD conversion must meet the following requirements:
· 32-bit Windows 7 Professional or Windows 7 Enterprise, Windows Vista Business or Windows Vista Enterprise with SP1 or SP2, or Windows XP Professional with SP3 must be installed.
· Client computers were installed and activated using Microsoft Volume Licensing or full packaged product installation media. Installations using OEM installation media are not valid. Full packaged product installation media provide the right to transfer the installation to another computer but will require reactivation once the system has been converted to a VHD.
· Windows is installed to a single partition without using a separate system or boot partition. Note that this limitation should be resolved in a subsequent beta or the final release of P2V Migration for Software Assurance.
· Hard disks must be 127 gigabytes (GB) or smaller in size, regardless of the amount of data stored on them. This is a limitation of Windows Virtual PC. For example, if the computer has a 160-GB hard disk consuming only 20 GB of data (even if it is configured with partitions smaller than 127 GB), P2V Migration will not work in either configuration.
· The P2V and deployment processes will target Disk 0 partitions only (Windows and system partitions). Attached disks other than Disk 0—including USB storage and external hard disks—will not be converted to a VHD in the process.
· For multinational clients targeted for P2V Migration and starting with Windows XP with SP3, KB961742-v3.exe should be installed in advance, with the language-appropriate version matching the operating system language. By default, P2V Migration installs the English-language version of KB961742-v3.exe on Windows XP with SP3 systems prior to VHD conversion.
The client computers on which the new operating system will be installed must meet the following requirements:
· 32-bit or 64-bit Windows 7 Professional or Windows 7 Enterprise
· Software Assurance covers the device in order to provide rights for up to four VM installations per device
· Hardware meets the minimum requirements of Windows 7 with Windows Virtual PC (2 GB of RAM recommended)
Note Hardware-assisted virtualization is not required with this solution.
Microsoft Connect: P2V Migration Beta 2
The Microsoft Deployment Toolkit team is working on a new solution incorporating Sysinternals Disk2VHD into the desktop migration process. Participation in the Beta Program for P2V Migration for Software Assurance is happening now, and we'd like your help!
If you are not already a member of the MDT beta program, click here to join.
Great blog post here talking about the various application virtualization methods available.
Read the full article here.
Are you looking for an independent overview of the Application Streaming and Virtualization solutions and curious about the different features and functions each Application Virtualization vendor is offering!? This is the blog and whitepaper you definitely must read!
In the current market there is an increasing demand for unbiased information about Application Virtualization solutions. This white paper is focused on solutions that are anticipated to have an important role in Application Virtualization deployments. An overview of available features of each solution is created to better understand each solution's capabilities.
The growing reality of the transition to a dynamic and optimized desktop is causing many IT organizations to reevaluate traditional IT operations, deployment, delivery, packaging, support, and management methods. Application Virtualization is a key component in the Optimized Desktop. It’s important to have a Vision and Strategy around Application and Desktop Delivery. Designing, building, managing and maintaining the Application Virtualization infrastructure using the right technologies, corresponding vendors, and products is an important last step.
We see a lot organizations primarily focusing on products and vendors and lacking a clear and profound vision and strategy. This approach isn’t good or bad, it depends on what the goal of the organization is. When the organization needs a point solution, the various vendors and corresponding products can help to solve this issue and fill-in the demands. When the organization is investigating possibilities, advantages, use cases and functionality of the vNext “Optimized desktop”, a profound vision and strategy should be in place.
Select “Client Status Reporting” from the main installation wizard under the “Additional Content” section. You can also browse to the “Client Status Reporting” folder on the CD as the install will take you there anyways.
Launch the “Clientstatusreporting” MSI.
Select “I accept the license agreement” and select “Next”.
Select the destination folder and select “Next”.
Select “Next” to start the installation.
You will have a new menu option in the Start menu. Launch the “Configure Client Status Reporting” to finalize the installation.
On the “Site Settings” tab, you will need to configure the SQL server and instance, along with what account you want the Client Status reporting to run under. I typically will configure it to use the local system account.
On the Options tab, you will want to select the “Update Configuration Manager 2007 site database with inactive client information”, you will also want to configure the client activity periods for your environment.
On the Schedule tab, you will want to enable the Client pulse settings along with the Client ping settings. You will also want to configure the schedules for those settings.
Importing the Client Status reports into Configuration Manager
Select “Import Objects” on the Reporting node.
Browse to the path you see below. Then select “Open”.
After the reports have been imported, you can see them listed in the reports folder.
Open up the installation and select “Configuration Manager 2007 R2” under the Install section.
Select “I accept the license agreement” and select “Next”.
Open the ConfigMgr console and expand Site Database – Site Management- Site Settings – Site Systems.
Right click on the site you want to add the role to and select “New Roles”.
Click on “Next”.
Select the “Fallback status point” and click on “Next”.
Change the messages and throttle interval if required. Otherwise click “Next”.
Review the summary and click “Next”.
Review the installation summary and click “Close”.
You will want to set the FSP on the Client Push Installation Properties.
In your Task Sequences, you will want to set a client installation property on the “Setup Windows and ConfigMgr” Task Sequence step.
Download WSUS 3.0 SP2 from here:
Launch the installation. Click “Next”.
Select “Full server installation including Administration Console” and click “Next”.
Click “I accept the terms of the License agreement” and click “Next”.
Select the location to store the WSUS updates and click “Next”.
Select “Use an existing database server on this computer” and click “Next”.
The installation will connect to the database, once it does, click “Next” to continue.
Select “Create a Windows Server Update Services 3.0 SP2 Web Site” and select “Next”.
Click on “Finish” to exit the installation.
When the WSUS Configuration Wizard pops up after installation, simply select “Cancel”.
Open up Server Manager and select “Add Roles”.
Click on “Next”.
Select “Windows Deployment Services” and click “Next”.
Click “Close” once the installation has completed.
More Posts Next page »