Introducing Shared Content Store in App-V 5.0 (Goodbye Read Only Shared Cache!)
This post has moved here
Comments
Anonymous
January 01, 2003
Thanks for the additional info Roel, very useful observations.Anonymous
January 01, 2003
Hi Rob, If by bypass the management and publishing server you mean you don't want the infrastructure involved in the delivery on the app then you want to use standalone mode to publish the app as described here: blogs.technet.com/.../app-v-5-0-standalone-mode-adding-and-publishing-a-package.aspx The -Path argument will specify where the client can retrieve the content on aper app basis and because you have put your client into SCS mode it will simply stream the content directly from there and not attempt to bring it locally. The PackageInstallationRoot you mentioned in registry has nothing to do with where you will stream packages from but where they get stored locally in cache. This should be left as the %ProgramData%App-V location unless you have a specific reason to change it. Hope that helps and let me know how you get on...Anonymous
January 01, 2003
Is there any performance lose if Shared Content Mode is enabled? Like longer loading time and slow response.Anonymous
January 01, 2003
Ok, what am I missing here. I want to bypass the management and publishing server altogether and just use a share content store. I installed my client and set the registry to HKLMSoftwareMicrosoftAppvstreamingSHAREDCONTENTSTOREMODE=1 I created my packages and put then in a packages share (ensuring everyone had read access) How do I set the location of where the actual packages are? Is that the PackageInstallationRoot String? I set that to \servernamepackagesharelocation but my client is still not picking up any packages, even after restarting the client service. Any help would be greatly appreciated. Thanks!Anonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
Hi Jason, Pre-staging can be done by using the add-appvclientpackage command. Pre-caching can be done via the mount-appvclientpackage command. Then all you need is to publish the packages via your method of choice. Please let me know if that makes sense and more importantly if it improves your experience.Anonymous
January 01, 2003
Hi Kevin, Your exactly right in your thinking. Specifying the PackageSourceRoot setting as your root directory for your alternative content share will make sure your RDS machines stream from that location. If they are in SCS mode then they will work from that location exactly as above. Hope that helps!Anonymous
January 01, 2003
Hi Aku, There is no dependency on the management/publishing server. Along as the client has the relevant registry key set and it has an accessible location for the package assets, it will be able to utilise shared content store. Hope that helps!Anonymous
January 01, 2003
ThanksAnonymous
January 01, 2003
thanks!Anonymous
January 01, 2003
Thanks Omar!Anonymous
January 01, 2003
Hi Surrender, we use the intelligence of Windows memory management to reduce that load in terms of RAM in the case of multiple users running the same application. in terms of the data itself, this solution would primarily be used in data centre environments where there is fast attached storage.Anonymous
November 21, 2012
nice articleAnonymous
November 28, 2012
Is management server required to use shared content store?Anonymous
November 28, 2012
Ok i did some testing.... This works with standalone scenario... Cool:)Anonymous
December 09, 2012
Good blog and informative nice one mate!Anonymous
April 12, 2013
Hi Thamim, If we are enabling the SCS then user has to stream the application directly from the content source. Suppose multiple users are using the content source at the same time. will there be any performance issue.Anonymous
April 24, 2013
Hi Thamim, In a mixed environemnt scenario with the desktop client and the RDS client is it possible to point the RDS client to a local content source, I am thinking a disk near the XenApp servers, would the PackageSourceRoot in the RDS client pointing to the local disk mean that with shared content mode enabled the files would be streamed from the local disk regardless of the original publishing location? (I have seperate content stores for the desktop clients). ThanksAnonymous
May 29, 2013
I would like to add some information. If you have packages loaded allready, you need to remove and add the packages. If you change scs after installation, the common users are able to precache the applications. If you set scs during installation, the users arent able to precache applications.Anonymous
September 04, 2013
The comment has been removedAnonymous
November 18, 2013
Hello Karim, We're seeing some delay when building up the start menu as well as Jason describes (If I've understood his post correctly). A user logs on and it takes up to 3 minutes before his applications are shown. How can we speed this up? by pre-staging the applications? Do we do this by running Powershell cmdlets? Thx! FilipAnonymous
November 18, 2013
Hi Filip, Have you tried pre-adding the packages? This is done via the add-appvclientpackage command, this should speed up the time to publish substantially. The general speed of publish is definitely on our radar internally and I would be interested to know how much pre-adding the applications helps you speed the process up so please do let me know!Anonymous
November 18, 2013
Hello Karim, I just tried this but get an error stating that admin rights are required. In our organisation, users don't have admin rights.. How can I get around this? Thx! FilipAnonymous
November 19, 2013
Hi, just to let you know that if we run the ps cmdlets, then the application is published in under 45 seconds. Now all we need is a workaround that allows users to run them.. FilipAnonymous
November 19, 2013
Dear Tamim, I am running Windows Power Shell V4.0 on Windows 7 SP1 Pro, is App-V 5 SP1 client supports Power Shell 4.0 yet? I am facing publishing issues on the client with POS V4.0, I tried the same packages on a client with POS 3.0 and everything is working fine. Please advise. Thank you.Anonymous
November 20, 2013
Hi, We do support PowerShell 4.0. Can you provide examples of packages that do not publish? Is it only certain packages?Anonymous
November 20, 2013
Thank you dear Thamim for your prompt reply, I am having issues with Office 2010 X86 and Office365 on PowerShell 4.0 using App-V Client Standalone mode. Other applications are working fine. I am testing as you suggested with Standalone before using Full Infrastructure mode. The Client OS is Windows Embedded 7 Professional x86 SP1 with POS 4.0. Please advise? Regards,Anonymous
November 20, 2013
I believe this might be to do with the platform rather than PowerShell version. Are you sure all other factors are the same? If you upgrade the working platform to PowerShell 4.0 does this stop working?Anonymous
December 04, 2013
Hi Thamim, Usefull article. I tried with one package, if we publish a package normally before launching the application the size of the .exe is around 190kb. i.e., when published futere block is loaded. if we publish a package after giving /SHAREDCONTENTSTOREMODE=1, the size of the .exe file is 4kb. what makes the difference. both are published future blocks onlyAnonymous
December 28, 2013
Pingback from Shared Content Store in Microsoft App-V 5.0 ??? Behind the Scenes - Dynamics AX Sustained Engineering - Microsoft Dynamics AX - Microsoft Dynamics CommunityAnonymous
December 29, 2013
Pingback from Shared Content Store in Microsoft App-V 5.0 ??? Behind the Scenes : Windows Server team Blog : The Official Microsoft IIS SiteAnonymous
January 24, 2014
Hi, currenty I'm testing with Shared Content Store. When published and refreshed on the VDI client the application consists of sparsefiles. When started the full application is loaded and runs from %programdata%/App-V. Sharedcontentstoremode is enabled through policies though. What could be wrong ?Anonymous
January 24, 2014
Trying the install using the option /SHAREDCONTENTSTOREMODE=1 but I'd rather have a generic install, so the same SCCM package with the same program is usable for fat clients, and VDI's.Anonymous
January 30, 2014
Problem was solved, my 'persistant VDI' was not..