Hi Kim

These are persistent VDIs (again, don't get me started) so no profile



> On 23 Sep 2014, at 17:27, Kim Oppalfens <[email protected]> wrote:
> 
> Jason,
> 
> Are you using roaming profiles at all?
> Or are you reinstalling at every logon?
> 
> Have a customer with similar setup and would love to compare notes.
> 
> Sent from my Windows Phone
> From: Jason Wallace
> Sent: ‎23/‎09/‎2014 18:03
> To: [email protected]
> Subject: Re: [mssms] App Model - avoid client cache
> 
> Hi Paul
> 
> One hefty PVS image is what they do have and that in itself present some 
> problems.
> 
> The whole app is streamed into the cache on startup however to enable all 
> that content to be deduped at the NetApp and to save the iOPs associated with 
> dragging that content down to the clients.
> 
> I agree that we absolutely need to have something to allow icons to appear 
> (at the least) on startup.
> 
> Daniel's right about a DCR on this but I think that would be a pain to 
> programme, quite simply because the content has to be reconstructed somewhere 
> from the Content Library - we can do that on a share at the DP or in the 
> client cache
> 
> 
> 
> On 23 Sep 2014, at 15:46, Paul Winstanley <[email protected]> wrote:
> 
>> Jason - Are these persistent VDI's as this would be a real mess in a 
>> non-persistent environment? 
>> On the App-V side, personally - until ConfigMgr sorts out publishing at 
>> startup rather than on policy run - I would cache all App-V FB0 to the 
>> master image rather than the whole app and then stream from DP with SCS 
>> switched on. Otherwise you are going to have one hefty gold image.
>> 
>>> On Tue, Sep 23, 2014 at 3:38 PM, Daniel Ratliff <[email protected]> wrote:
>>> Jason you are right, it doesn’t look like you can run non-App-V apps from 
>>> the DP. They must be downloaded and ran locally. Sounds like another DCR.
>>> 
>>>  
>>> 
>>> Daniel Ratliff
>>> 
>>>  
>>> 
>>> From: [email protected] 
>>> [mailto:[email protected]] On Behalf Of Marcum, John
>>> Sent: Tuesday, September 23, 2014 10:33 AM
>>> To: [email protected]
>>> Subject: RE: [mssms] App Model - avoid client cache
>>> 
>>>  
>>> 
>>> That's just yucky! LOL…. Why aren't they deploying the App-V apps to the 
>>> users? Better yet, why aren't they deploying all apps to the users?
>>> 
>>>  
>>> 
>>> Or deploy the app-v apps to XenApp servers and let CM deploy the XA apps to 
>>> the users.
>>> 
>>>  
>>> 
>>>  
>>> 
>>>  
>>> 
>>>  
>>> 
>>> From: [email protected] 
>>> [mailto:[email protected]] On Behalf Of Jason Wallace
>>> Sent: Tuesday, September 23, 2014 9:29 AM
>>> To: [email protected]
>>> Subject: RE: [mssms] App Model - avoid client cache
>>> 
>>>  
>>> 
>>> Yes, but that is an App-V application.  Bizarrely they have decided NOT to 
>>> stream App-V apps from DP but to stream these apps into the image which 
>>> they PVS.  This means that on first run all systems see all apps but then 
>>> CM comes along and uninstalls the ones not valid for the system.
>>>  
>>> The apps which they are publishing to Software Center are .MSI and .EXE 
>>> based thick client installers for applications which cannot be App-V'd
>>>  
>>> 
>>> From: [email protected]
>>> To: [email protected]
>>> Subject: RE: [mssms] App Model - avoid client cache
>>> Date: Tue, 23 Sep 2014 14:20:57 +0000
>>> 
>>> To stream from DP the settings are in the Deployment properties. See an 
>>> example below.
>>> 
>>>  
>>> 
>>> <image001.png>
>>> 
>>>  
>>> 
>>> Daniel Ratliff
>>> 
>>>  
>>> 
>>> From: Daniel Ratliff 
>>> Sent: Tuesday, September 23, 2014 10:18 AM
>>> To: [email protected]
>>> Subject: RE: [mssms] App Model - avoid client cache
>>> 
>>>  
>>> 
>>> Why aren’t you running from the DP? Are you just asking how you tell it to?
>>> 
>>>  
>>> 
>>> Daniel Ratliff
>>> 
>>>  
>>> 
>>> From: [email protected] 
>>> [mailto:[email protected]] On Behalf Of Jason Wallace
>>> Sent: Tuesday, September 23, 2014 10:12 AM
>>> To: [email protected]
>>> Subject: [mssms] App Model - avoid client cache
>>> 
>>>  
>>> 
>>> Hi there folks
>>>  
>>> I have an issue with a customer who is implementing a VDI solution based 
>>> around CM12R2CU1 (at the moment).
>>>  
>>> They have a lot of applications which are available to the computer and 
>>> appear in Software Center for the user to choose to install.  This 
>>> therefore is APPMODEL data.
>>>  
>>> When we select an application it is downloaded into client cache of course 
>>> and installed from there.
>>>  
>>> In the instance of this customer some users have more than 5GB of content 
>>> which they want to deploy.  When they do of course they fill the client 
>>> cache and that content remains for 24 hours.
>>>  
>>> Now one solution would be for us to dynamically increase the client cache 
>>> size when we deploy an application and then shrink (and clear) the cache 
>>> but they don't want to do this (storage is expensive).  Ideally I'd like to 
>>> have something like run from DP but for App Model.
>>>  
>>> Suggestions appreciated
>>>  
>>> Jason
>>> 
>>>  
>>> 
>>> 
>>> The information transmitted is intended only for the person or entity to 
>>> which it is addressed
>>> and may contain CONFIDENTIAL material. If you receive this 
>>> material/information in error,
>>> please contact the sender and delete or destroy the material/information.
>>> 
>>>  
>>> 
>>> 
>>> Confidentiality Notice: This e-mail is from a law firm and may be protected 
>>> by the attorney-client or work product privileges. If you have received 
>>> this message in error, please notify the sender by replying to this e-mail 
>>> and then delete it from your computer.
>>> 
>>>  
>>> 
>>> 
>>> Confidentiality Notice: This e-mail is from a law firm and may be protected 
>>> by the attorney-client or work product privileges. If you have received 
>>> this message in error, please notify the sender by replying to this e-mail 
>>> and then delete it from your computer.
>>> 
>>>  
>>> 
>>> 
>>> The information transmitted is intended only for the person or entity to 
>>> which it is addressed
>>> and may contain CONFIDENTIAL material. If you receive this 
>>> material/information in error,
>>> please contact the sender and delete or destroy the material/information.
> 
> 

Reply via email to