This article describes one method that you can use to sequence Microsoft Visual Studio 2010 for use with Microsoft Application Virtualization (App-V). The method that is described in this article is not the only possible method. Additionally, you may have to adapt the information in this article as appropriate for your particular environment.
Application Name: Visual Studio 2010
Application Version: Service Pack 1
Company Name: Microsoft Corporation
Sequencer Version: App-V 4.6 SP1
App-V Client Version Tested On: App-V 4.6 SP1
Operating System Sequenced On: Windows XP SP3; Windows Vista; Windows 7 SP1; Windows Server 2003 R2 SP2; Windows Server 2008 SP2; Windows Server 2008 R2 SP1
You must have the following to sequence Visual Studio 2010 for use with Microsoft Application Virtualization:
· A volume license for Visual Studio 2010
· Visual Studio 2010 Service Pack 1 or a later version
· Hotfix 2526163 for Visual Studio 2010 Service Pack 1
· Microsoft Application Virtualization 4.6 SP1 or a later version
· Microsoft .NET Framework 4 Full Profile natively installed on the App-V Sequencer and App-V Clients to which the sequencing will be deployed.
· If you are using Windows 7 or Windows Server 2008 R2, you must use Windows 7 SP1 or Windows Server 2008 R2 SP1 or later on the App-V Sequencer and App-V Clients.
Client Operating Systems Successfully Deployed To: Windows XP SP3; Windows Vista; Windows 7 SP1; Windows Server 2003 R2 SP2; Windows Server 2008 SP2; Windows Server 2008 R2 SP1
Posted by Microsoft Employee: Jim Boyles
Corresponding KB Article Reference:
For Visual Studio 2010 Service Pack 1, you have to obtain Hotfix 2526163. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2526163 FIX: Error message when you try to start a sequenced Visual Studio 2010 application package on an Application Virtualization client: "Invalid license data. Reinstall is required"
Obtain Background Information
· Review the Microsoft Application Virtualization 4.6 SP1 Sequencing Guide white paper available on TechNet.
· Install Visual Studio 2010 to become familiar with the functionality of the program.
Prepare the Environment
Make sure that you allocate at least 3 gigabytes (GB) of random access memory (RAM) to the computer on which you will sequence Visual Studio.
Sequence Visual Studio 2010
Note: Please complete all sequencing steps logged in as a local administrator.
1. Install Microsoft .NET Framework 4 Full Profile on the Sequencer machine. Using Microsoft Update, install all updates for Windows and .NET Framework.
2. Make sure that the following update was installed by Microsoft Update on the Sequencer machine. If not, install it manually. 2468871 Update for the .NET Framework 4
3. On the Tools menu, click Options. Click on the Exclusion Items tab.
4. Add the following exclusions:
For Windows XP and Windows Server 2003, also add the following exclusions:
5. On the File menu, click Save As Template… to save these exclusions as a project template.
6. On the File menu, click New From Template… to start sequencing using the newly created template.
7. Complete the initial pages of the New Package Wizard.
8. Start monitoring the installation.
9. Install Visual Studio 2010. Use the default options, except for the following:
a. Be sure to specify the install location as Q:\VS2010.
b. Install everything except Microsoft SharePoint Developer Tools and SQL Server 2008 Express.
10. On 64-bit systems (x64), open regedit and create the following keys after Visual Studio 2010 installation completes:
11. Install Visual Studio 2010 Service Pack 1
12. Install Hotfix 2526163 for Install Visual Studio 2010 Service Pack 1
a. Launch an elevated Visual Studio 2010 Command prompt while monitoring. Note: You do not need to run elevated on Windows XP or Windows Server 2003. b. Run DDConfigCA.exe from the command prompt. c. Exit the command prompt.
a. Launch an elevated Visual Studio 2010 Command prompt while monitoring. Note: You do not need to run elevated on Windows XP or Windows Server 2003.
b. Run DDConfigCA.exe from the command prompt.
c. Exit the command prompt.
13. After installation completes, run the following from an elevated command prompt: %WINDIR%\Microsoft.NET\Framework\v4.0.30319\ngen executeQueuedItems
14. On 64-bit systems (x64), also run the following from an elevated command prompt: %WINDIR%\Microsoft.NET\Framework64\v4.0.30319\ngen executeQueuedItems
15. Launch an elevated Visual Studio 2010 Command prompt. Note: You do not need to run elevated on Windows XP or Windows Server 2003. Execute the command:
a. On 32-bit systems (x86): gacutil /i “%ProgramFiles%\Microsoft Silverlight\4.0.50826.0\System.Windows.dll” b. On 64-bit systems (x64): gacutil /i “%ProgramFiles(x86)%\Microsoft Silverlight\4.0.50826.0\System.Windows.dll”
a. On 32-bit systems (x86): gacutil /i “%ProgramFiles%\Microsoft Silverlight\4.0.50826.0\System.Windows.dll”
b. On 64-bit systems (x64): gacutil /i “%ProgramFiles(x86)%\Microsoft Silverlight\4.0.50826.0\System.Windows.dll”
16. If you are sequencing Visual Studio 2010 Ultimate, modify intellitrace.exe.config. Modify the startup xml node to add an attribute useLegacyV2RuntimeActivationPolicy: <startup useLegacyV2RuntimeActivationPolicy="true"> in the following 2 locations:
a. Q:\VS2010\Common7\IDE\PrivateAssemblies\DataCollectors b. Q:\VS2010\Team Tools\TraceDebugger Tools
b. Q:\VS2010\Team Tools\TraceDebugger Tools
17. For64-bit systems (x64), perform the following steps:
a. Open the registry key HKLM\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\App Paths\Iexplore.exe. b. Modify the Default value of this key to place quotes around the path. For example, if the current value is C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE,change the value to “C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE”. c. Modify the Path value of this key to place quotes around the path. For example, if the current value is C:\Program Files (x86)\Internet Explorer, change the value to“C:\Program Files (x86)\Internet Explorer”.
a. Open the registry key HKLM\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\App Paths\Iexplore.exe.
b. Modify the Default value of this key to place quotes around the path. For example, if the current value is C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE,change the value to “C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE”.
c. Modify the Path value of this key to place quotes around the path. For example, if the current value is C:\Program Files (x86)\Internet Explorer, change the value to“C:\Program Files (x86)\Internet Explorer”.
18. Stop monitoring the installation.
19. Continue to the customization page
20. On the Tools menu, click Diagnostics | Command Window.
a. Run regedit. b. Delete the value HKLM\Software\Microsoft\VisualStudio\10\SetupCommandLine c. Exit regedit and the command prompt.
a. Run regedit.
b. Delete the value HKLM\Software\Microsoft\VisualStudio\10\SetupCommandLine
c. Exit regedit and the command prompt.
21. Go to the VFS tab on the Sequencer. Delete all files named webengine4.dll. If no files are found with the specified name, skip this step.
22. On the OSD tab, add the following environment variable to all the OSDs:
a. On 32-bit systems (x86):PATH=%PATH%;%WINDIR%\Microsoft.NET\Framework\v4.0.30319 b. On 64-bit systems (x64): PATH=%PATH%;%WINDIR%\Microsoft.NET\Framework64\v4.0.30319;%WINDIR%\Microsoft.NET\Framework\v4.0.30319
a. On 32-bit systems (x86):PATH=%PATH%;%WINDIR%\Microsoft.NET\Framework\v4.0.30319
b. On 64-bit systems (x64): PATH=%PATH%;%WINDIR%\Microsoft.NET\Framework64\v4.0.30319;%WINDIR%\Microsoft.NET\Framework\v4.0.30319
23. Save the package.
On the App-V Client
Be sure to complete the following steps on all App-V Clients to which the sequencing will be deployed.
1. Install Microsoft .NET Framework 4 Full Profile. Using Microsoft Update, install all updates for Windows and .NET Framework.
2. Make sure that the following update was installed by Microsoft Update. If not, install it manually. 2468871 Update for the .NET Framework 4
3. Run services.msc and disable the Windows Presentation Foundation Font Cache service.
The above text was originally published by Jim Boyles here:
J.C. Hornbeck | System Center Knowledge Engineer
App-V Team blog: http://blogs.technet.com/appv/ AVIcode Team blog: http://blogs.technet.com/b/avicode ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ OOB Support Team blog: http://blogs.technet.com/oob/ Opalis Team blog: http://blogs.technet.com/opalis Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/ SCMDM Support Team blog: http://blogs.technet.com/mdm/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
Followed to the letter this will never work.
Problem #1: C:\Windows\Installer
That alone pushes it WELL over 6GB. Deleting it and cleaning up as much as you dare still nets an install that, rather ironically, refuses to sequence with Compression enabled, and when you uncheck it it decides to update the filesize (why it doesn't do this as part of the steps when you start to save I don't know).
Problem #2: It is INCREDIBLY unstable. Across the usual three machines in three companies every one of us has encountered either the "sharing access violation has occured" which then brilliantly renders the entire sequence moot (see a 2008 post by Tim Mangan where the resulting "version lineage" issue came up, yes, 2008, still a problem) or the sequencer just flat out crashes when switching between random tabs (this happened to all of us at least once, primarily it seems when going from the VFS to Files tabs, but also when going from VRG to Files tab).
And you can say about #1 that, well, you should know to exclude that. But it kinda moots the point of a recipe if you are going to go to the lengths to tell them to exclude things and then...not exclude them.
While I'm at it...two questions. 1 why is the VS2010 install TWO installs? Downloaded direct from the MS licensing service center you have to download 2 ISO's...why. 2 Why, with these mega huge applications, do you not just release a sequence? As far as I can tell there is no need to put the license info INTO the sequence, and the same is true with Office 2010. Why even have this problem running around? Why not just post the stupid thing and be done with it.
No wonder it took a year to get this working. App-V is, again, showing itself as not up to the challenge when it comes to complex software. The very area it's "benefits" are most worthwhile.
And btw, if the answers were less "see how great is is!" and more "we know there are serious areas of improvement, these are what we think they are and this is what we are doing to address them" you might get less frustrated exasperation and more patience.
Pretending we're stupid and suggesting you sacrificed perfect (hah) for relevance in a field where it's you, and thin app...and not a whole heck of a lot of people are using either thanks in LARGE part to the very "perfection" you fail to strive for just irritates.
The one thing 4.6 SP1 showed was that you have ALMOST no clue what is really important to the future of App-V and would rather PR over it than put your head down and sort it out.
The "options must be templates" issue alone is...frankly...somebody should be fired for that. That's the kind of stupid thing that slips through when you compile a debug version for testing and go "heh whoops!"...not makes it into a full on production version. Or better yet, hire someone, anyone, to do QA (unless you already do, in which case...there's who you fire).
You release accelerators and then call it a "known issue" that they don't "rehydrate" because all the deployment info is hardcoded. I wrote a XPATH powershell script that can batch configure thousands of OSD's with whatever deployment info I want in around a minute...is this more of that "perfection" you eschewed for the relevance you didn't attain because so many simple things remain painfully beyond App-V's grasp?
And you are getting this novel on your blog btw because there appears to be no interest in feedback so this is about the only option.
We’re sorry that you’ve run into issues trying to get VS2010 sequenced and while there is not enough detail in your posting about your environment or about the exact steps you followed to allow us to reproduce the problem, here is some general guidance for the problems you encountered:
Regarding Problem #1: The posted recipe has been used successfully to create a compressed VS2010 package below 4 GB. As indicated in the recipe, you will need to ensure that the following items are excluded from the Visual Studio 2010 installation:
1. Microsoft SharePoint Developer Tools
2. SQL Server 2008 Express
Please also ensure that .NET 4.0 and the .NET update KB2468871 are preinstalled on the sequencing machine before starting to sequence.
Regarding Problem #2: It is possible that some application on the machine is interfering with the sequencing during Visual Studio 2010 installation. As a sequencing best practice, please disable any antivirus software, Windows Defender, and Windows Search before starting to sequence. These applications are known to cause “sharing access violation” errors during sequencing.
If you have already tried the above suggestions or try them now without success, please contact Support who can work with you to troubleshoot the specifics of the problem.
Thanks for the article.
can you plz let me know in detail on how to update environmnent varialble path under All OSDs.
If possible can you share me the screen shot.
I have sequenced the Visual Studio 2010 Ultm software while saveing the package. In Deploymnet Tab i have enabled output option is Compress package.
I am geting the below error messege:
The package cannot be larger than 4gb.you can trun in compression on th deployment tab, or remove items from the package.
Let me know how to remove items from the package.
I was able to virtualize VS2010 (version from our MSDN) but when I start the application, it request a product key. If I enter the one provided, I have the error: "The product needs to be reinstalled"
At the installation (during the sequence) there were no mention about a product key nor when I started it within the sequencer.
Any idea why ?
Thanks in advance
i have proceed the injection sequence of VS2010 ultimate as per explained steps on WIN XP SP3... Licensing problem [Invalid license data. Reinstall is required] is resolved...but noticed another issue. i.e
Error = The operation could not be completed.
and one more point to add.. while installing Hotfix = KB2526163 in my machine. it says :-
KB2526163 does not apply, or is blocked by another condition on your computer.
so, i had continued the sequencing without installing this hotfix.
is this the reason, of error exception = The operation could not be completed.
i am not sure but this hotfix was specifically meant for the elimination of licensing problem.
Thank you very much for your help
We are also experiencing problems with the package size. Approx 6.5GB uncompressed and over 4GB compressed. This is for VS 2010 Ultimate SP1.
Should we not be creating a feature block? If so, won't we have performance issues?
Delete c:\windows\installer\*.* after sequencing, before saving the package. This way your package will be <4GB (with compression!).
Did you applied SP1 before installing the hotfix?
Works nicely, and yes, you need to empty the Installer-folder to reduce the package size.
KB2526163-hotfix installation fails with the following error message:
KB2526163 Does not apply or , blocked by another condition on the computer.
Followed the above exactly about 12 times on 3 different systems / environments and still i get the "The product needs to be reinstalled". Although the initial dialogue displayes " This product is licensed to:..."
Anyone have any ideas. We really need to get this out to our in-house developers in our VDI environment but are currently stuck.
Anyone created a accelerator for this?
Is there a way to bypass the licensing ?
I managed to get this working by running a prelaunch script which checks for a certain registry key. If this didnt exist it run DDConfigCA.exe which recreates the license details correctly. This then loads Visual studio fine.
For some reason DDConfigCA.exe run during sequencing doesn't work, no matter how many times i ran it. As soon as i ran it from a virtual CMD it allowed me to start Visual studio.
Anyway. Im happy. The customer is happy.