The D-spot

This kit will help you complete a Proof of Concept (PoC) at your organization, at a customer or get familar with some Microsoft products in a lab environment.

Allowing you to quickly evaluate the new Microsoft desktop technologies, including Windows 7, Office 2010, Internet Explorer 8, and Application Virtualization (AppV) with Microsoft Desktop Optimization Pack technology.

It will also familiarize you with some of the important deployment tools provided by Microsoft to assist with your broader deployment efforts. This PoC isn’t meant to be comprehensive training mechanism but rather an introductory set of modules to familiarize you with tools and technologies.

Included in the package:

• Microsoft Assessment and Planning Toolkit (MAP)
• Microsoft Application Compatibility Toolkit (ACT)
• Microsoft Office Migration and Planning Manager (OMPM) (A tool to assess and upgrade Office versions and files, like macro compatibility for example)
• Microsoft Deployment Toolkit (MDT)
• Windows 7 Enterprise 90-day Trial image
• Microsoft Office Professional Plus 2010
• Office 2010 with Application Virtualization (App-V)

In short, a package that any consultant arriving on a mission around Windows 7 should have.

Download: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=26301cd1-cc72-4dd8-819e-12ef48322743

Microsoft’s application virtualization solution has reached version 4.6 some weeks ago. The most important thing about version 4.6 is support for 64 bit. The Server parts could run on x64 operating systems, but it was impossible to install the AppV client on x64 operating systems. Time to upgrade!

As the client needs to be updated first, I will cover the client upgrade process only. (Client first, server next, sequencer last). Good to know that only the client and the sequencer are updated to version 4.6. No need to update your Management server as version 4.5.2.17140 is still the latest and greatest.

AppV has some Prerequisites, I will install them first. Then I will install the AppV client itself, using some command line parameters and a registry file import for applying custom settings.

Prerequisites

Application error reporting

msiexec /I SOURCE_PATH\dw20shared.msi /QN APPGUID={4C1CE627-6B28-436E-BD12-3A881065FB20} REBOOT=REALLYSUPPRESS ALLUSERS=1

Visual C++ 2005 runtime

SOURCE_PATH\vcredist2005_x86.exe /Q:A /c:”VCREDI~3.exe /Q:A /C:”"MSIEXEC /I VCREDIST.MSI /QN “”"

Visual C++ 2008 runtime

msiexec /i SOURCE_PATH\vc2008\vc_red.msi /qn /l*v “LOGFILE_PATH\vc2008runtime.log”

AppV 4.6 Client with command line parameters

Because storage is expensive, we have a different cache policy for virtual machines. Cache size on virtual systems don’t have to be as enormous as on physical machines. Not only the cache size is reduced in virtual machines, also the AutoLoad features are disabled via the MSI command line parameters.

To identify virtual machines I query on the computer name. As we use specific names for our VM’s, this should be a piece of cake!

We do an architecture check in a batch file. So I have two code blocks, one for x64 and another for x86 operating systems. Only the paths are different, so I will post only one.

AppV Client Installation

Echo install AppV x64 Client

rem Virtual Machine check
Echo %computername% | findstr /i “ISOPC99 VPC” >NUL && (
    Echo Installing AppV x64 client for Virtual Machines
    msiexec /i “SOURCE_PATH\x64\setup.msi” SWICACHESIZE=”4096″ autoloadTriggers=0 AutoLoadTarget=0 AutoLoadonLaunch=0 AutoLoadonRefresh=0 AutoLoadonLogin=0 SWIDCSDISPLAY=”Company Streaming Server” SWIDCSTYPE=”RTSP” SWIDCSHOST=”appvserver.domain.local” SWIDCSPORT=”554″ SWIDCSREFRESH=”on” SWIGLOBALDATA=”C:\Program Files\Microsoft Application Virtualization Client\GLOBAL\” SWISOFTGRIDDRIVE=”Q” /q REBOOT=REALLYSUPPRESS /l*v “LOGFILE_PATH\appv46.log”
    ) || ( 
   Echo Installing AppV x64 client for Physical Machines
    msiexec /i “SOURCE_PATH\Source\x64\setup.msi” MinFreeSpaceMB=”6000″ SWIDCSDISPLAY=”Company Streaming Server” SWIDCSTYPE=”RTSP” SWIDCSHOST=”appvserver.domain.local” SWIDCSPORT=”554″ SWIDCSREFRESH=”on” SWIGLOBALDATA=”C:\Program Files\Microsoft Application Virtualization Client\GLOBAL\” SWISOFTGRIDDRIVE=”Q” /q REBOOT=REALLYSUPPRESS /l*v “LOGFILE_PATH\appv46.log”
    )

Echo Import Regkeys
regedit /s SOURCE_PATH\appv64_v2.reg

The registry file that is imported in the last line specify the sftlog.txt log file location, and some other tweaks, have a look:

Registry import (x86)

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\Configuration]
“SystemEventLogLevel”=dword:00000004
“LogFileName”=”C:\\PATH_OF_YOUR_CHOICE\\sftlog.txt”
“UserDataDirectory”=”%APPDATA%”
“ApplicationSourceRoot”=”RTSP://server.domain.local:554″
“LaunchRecordMask”=dword:005a0000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\DC Servers\Company Streaming Server]
“Period”=dword:00000000
“Refresh”=dword:00000001
“Reporting”=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\AppFS]
“UnloadLeastRecentlyUsed”=dword:00000001
“MinPackageAge”=dword:00000001

Registry import (x64)

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Client\Configuration]
“SystemEventLogLevel”=dword:00000004
“LogFileName”=”C:\\PATH_OF_YOUR_CHOICE\\sftlog.txt”
“UserDataDirectory”=”%APPDATA%”
“ApplicationSourceRoot”=”RTSP://server.domain.local:554″
“LaunchRecordMask”=dword:005a0000

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Client\DC Servers\Company Streaming Server]
“Period”=dword:00000000
“Refresh”=dword:00000001
“Reporting”=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Client\AppFS]
“UnloadLeastRecentlyUsed”=dword:00000001
“MinPackageAge”=dword:00000001

That’s it.

When the SQL Server is on the same machine as the App-V Management Server (formerly known as the VAS Server), the App-V Management Server Service doesn’t start after a reboot.

Solve this by adding the MSSQLSERVER as dependency to App-V service in the registry. (Use MSSQL$SQLEXPRESS when using SQL Server Express edition).

To finalize, add a DWORD named ‘DelayedAutostart’ with value 1.

Reboot the server, the Application Virtualization Management Server service should start (with a slight delay).

This morning I came across the Office 2010 deployment kit for APPV, so I figured why not give this  a go…

I had already downloaded the office 2010 beta and have an appv client and sequencer running in 4.6 RC for a while already in my 4.5 SP1 environment.

The thing is, I do not really get the purpose of this deployment kit so far; You have to install it on your sequencer machine before creating the 2010 package AND on the client.  I did find that it installs a licensing service which can be configured with the included OSPP.vbs script.

On with the preparation part, First of all I created a transform file for Office 2010.  this can still be done with the command line setup /admin (hurray for that !).  While comparing the OCT from office 2010 with the one in Office 2007, I noticed some new things in there.  Fortunately they did not change the majority that was already there…

The first thing I noticed is that you can configure your KMS host for office 2010 licensing from within the OCT wizard:

Under the Modify User Settings part of the wizard I noticed an entry Disable Items in User Interface where you can choose to disable commands or shortcut keys for a certain office application.  Configuration of the Outlook Cached Exchange mode is now brought under the Exchange part instead of elsewhere like in office 2007, good one!

Another useful entry in there is the File Block Settings where you can configure whether users can open, view or edit office application files for a large number of different versions:

Time to save my customizations into an MSP file

On with the sequencing part (after installing the Office deployment kit on the sequencer machine)

If you haven’t been able to try out the slightly revamped sequencer of APPV 4.6, it acts similar but yet more user-friendly.  For instance, it doesn’t minimize any longer on the point where you have to start the actual installation:

The rest of the steps are quite similar as any other application sequencing, so I’m not going to describe them (fyi: I haven’t activated Office 2010 yet).

Saved the Sequence and imported it into my APPV console.

On my 4.6 test client, the Office 2010 sequence launched really well.  But oops, haven’t installed the deployment kit on that client yet…  Strangely enough Office did not complain, but shows unlicensed version in the titlebar.  After installing the Office 2010 deployment kit for Appv on my test system with appv 4.6 rc I imported my license with the following command: cscript ospp.vbs -inpkey:XXXXX-XXXXX-XXXXX-XXXXX (note: you must replace the X’s).  Right before this Office 2010 asked for the license, copy-paste didn’t work ??  So now the license is present, but Office 2010 is still not activated…

I guess the option to insert the Office 2010 licence into our KMS server will be the best one, less work and no fiddling around.  The Office 2010 deployment kit for APPV might come in handy in some cases, but will need some documentation first…

Windows 7 is the NEW Desktop Operating System around. Recently we hosted an event about “Managing the Dynamic Desktop”. This seminar not only listed many of the new features and functionality that are included in Windows 7 but also answered many deployment questions. Some of them were “how do I know which deployment system is best-suited for my organization?” and “how can I certify this to be my final mass deployment”

 The result can be found here:

http://seminar.the-d-spot.org/Windows 7 Presentation_part1.pdf

http://seminar.the-d-spot.org/Windows 7 Presentation_part2.pdf

In an older post on The D Spot we announced MDOP 2009 R2. As of today the product is available for MDOP customers. You can download MDOP 2009 R2 through Microsoft Volume Licensing Site (MVLS).  For others who wish to evaluate MDOP products, the MDOP software is available at MSDN and TechNet (in accordance with your MSDN or TechNet agreements, except for AIS).

If you’re not using MDOP, we recommend you take another look because it can provide immediate savings with little IT investment, especially when integrated into your Windows 7 plans. For example:

• By using Application Virtualization, you can optimize your Windows 7 deployment by reducing PC provisioning time, simplifying application delivery and update, and increasing productivity with user roaming
• You can enhance your Windows 7 manageability by addressing common system/application failures (with DEM), repairing unbootable PCs (with DaRT), and controlling Group Policy change (with AGPM).

Beyond MDOP 2009 R2, the MDOP roadmap includes:

1. Microsoft Enterprise Desktop Virtualization (MED-V) V 1.0 SP1 – This updated tool will support Windows 7 and enable enterprise deployment of virtual Windows XP environments to support incompatible applications. A Beta version of MED-V 1.0 SP1 will be available by the end of 2009 and final release is scheduled for the first quarter of calendar year 2010.
2. Asset Inventory Service (AIS) 2.0 – AIS 2.0 can track your existing assets to improve Windows 7 deployment planning and will have a series of enhancements that customers have requested: Enhanced hardware inventory, new Silverlight-based user interface, scale to 100,000 PCs, improved volume license reconciliation and ability to track virtual applications. The AIS 2.0 beta is now available (registration closes by October 24th) and the final release will be available in H2 CY2010.

Encouraging feedback

Already MDOP has been licensed for over 21 million desktops worldwide and more customers are looking forward to MDOP 2009 R2 and Windows 7! Below are a few quotes from some of our top customers who are seeing real and immediate value with MDOP:

BMW completed a proof of concept of application delivery with Application Virtualization. “We expect cost savings on desktop support once we start deploying App-V with Windows 7,” said Mr. Bernhard Huber, Head of IT Workplace Systems at BMW. “We are also considering AGPM [Advanced Group Policy Management] and MED-V [Enterprise Desktop Virtualization] at a later stage of Windows 7 deployment.”

Heinz Koehler, VP of Infrastructure for E.O.N., Power and Gas Company with 85,000 desktops that are being upgraded to Windows 7, talks about MDOP: “We also expect to use App-V to help reduce the packaging and testing costs of applications and use MED-V to help resolve any application compatibility issues.”

“…MDOP, specifically App-V, has been a hidden gem our customers have found to help them quickly deploy, and then easily manage and maintain their applications in an efficient manner.  In an economy when they are being asked to do more with less, the timing couldn’t have been better for MDOP 2009 R2 to help our clients meet their IT initiatives…,” said Rand Morimoto, President of Convergent Computing.

In addition, Answers Research recently surveyed 1000 IT pros across five countries (commissioned by Microsoft) and we found out that:

• 66% of MDOP customers deployed three or more of the MDOP products
• 52% of them deployed MDOP across more than half of their PCs
• 94% of MDOP customers said they would recommend MDOP to a colleague
• When comparing MDOP and non-MDOP customers, customer satisfaction with Software Assurance increases by 25%

To sum up, MDOP 2009 R2 is available today and it’s there to help you save money and reduce complexity, especially with your Windows 7 deployment.

Source: The Official MDOP Blog and Windows Team Blog.

Error message when you try to import an .osd file into the SoftGrid Management Console: “Error code: 0000C81D”

Error message:

Unable to import OSD file. The file specified is not a valid SoftGrid OSD file. Please ensure the file conforms to the SoftGrid OSD file schema and contains well formed XML. Error code: 0000C81D

Error code: 0000C81D

When searching Google I always came with MS solution (http://support.microsoft.com/kb/930562): package name is more then 64 chars. But changing this didn’t solve the problem.

I tried to import the package in the Package container.  And add an application (OSD file) afterwards (instead of importing the app). This works like a charm.

I even had this error in an App-V 4.5 environment lately.

When troubleshooting App-V applications looking into the bubble can ease your work.
Sneaking into the bubble gives you information about which files are stored local and which virtual.  This way you know what files actually will be used by the application.  You can modify some configuration files without resequencing the whole application.

There are some ways to view inside the virtual Softgrid / App-V bubble.

1. First method is a PRE LAUNCH script in the OSD file that would launch a Command Prompt window inside the bubble

Editing the .OSD file, inside the <DEPENDENCY> tag add:

<SCRIPT EVENT="LAUNCH" TIMING="PRE" PROTECT="TRUE" WAIT="TRUE" TIMEOUT="">
<HREF>cmd.exe</HREF>
</SCRIPT>

Launching the OSD file will present you a DOS BOX inside the bubble.  With this box you can do anything.  Browsing the Q: drive, starting regedit, changing config/ini files, map a drive, copy some files ..

2. Second way by using sfttray

• sftmime /query obj:app /short -> gives you a list of all Softgrid applications on your client

• sfttray /EXE cmd.exe /launch “Notepad++ 5.4.2″ -> launches a command prompt in the bubble

3. Third method using SFT Explorer

With SFT Explorer you can look inside the SFT file without ever having to load it. You can see files and registry keys would look like if the App-V application was loaded on the target machine. It only supports viewing in the SFT file, you cannot make any changes.

Microsoft announced that Desktop Optimization Pack (MDOP) 2009 R2 will be released in late October 2009 and will add Windows 7 support for all components, except for MED-V.  Server and management components will support Windows 2008 R2.

Microsoft is promising that the new MDOP tools will have management components that support Windows Server 2008 R2, which was released to manufacturing on Sept 14 and available through MSDN as we speak.  In addition, all of the components in MDOP 2009 R2, except for MED-V, will support Windows 7.  Microsoft expects to add Windows 7 support in MED-V when it releases MED-V 1.0 Service Pack 1 sometime in the “first quarter of calendar year 2010″, according to the blog.

MDOP employs six innovative technologies to increase desktop manageability, reduce TCO, and improve overall infrastructure satisfaction:

• Application Virtualisation. Deploy software applications that are never installed and never require regression testing, yet follow users anywhere, on demand.

• Advanced Group Policy Manager. Help IT take control of the desktop through effective change management, versioning and resets.

• Asset Inventory Service. Scan software inventory and transform title data into information that can help administrators make better asset-management decisions.

• Diagnostics and Recovery Toolset. Quickly repair unbootable or locked-out systems, restore lost data, remove malware from infected systems and diagnose problems.

• Microsoft Enterprise Desktop Virtualisation (MED-V). Enhance deployment and management of Virtual PC images on a desktop running the Windows operating system. Simultaneously provide a seamless user experience on a virtual PC environment independent of the local desktop configuration and operating system.

• Microsoft System Center Desktop Error Monitoring. Prevent or reduce the response time for system crashes and freezes with granular error filtering and automated alerts.

With its virtualization technologies and manageability components, MDOP 2009 R2 is an essential part of your Windows 7 planning and deployment strategy.
This is a great opportunity to highlight the key innovations of MDOP 2009 R2 and talk about how MDOP can help you rapidly migrate to Windows 7, deploy applications with greater ease, resolve application incompatibility, and reduce desktop management costs.

Full Article on The Official MDOP Blog.