[mssms] RE: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602

2016-12-21 Thread Lindenfeld, Ivan
lto:mssms@lists.myitforum.com> Subject: [mssms] RE: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602 That’s disappointing, since it’s just a dang WMI setting. We workaround it by deploying a Config Item set to Remediate. [cid:image001.png@01D25B84.9994EB50] F

[mssms] RE: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602

2016-12-20 Thread Corkill, Daniel
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Lindenfeld, Ivan Sent: Thursday, 25 August 2016 12:07 AM To: mssms@lists.myitforum.com Subject: [mssms] RE: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602 That’s

[mssms] RE: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602

2016-08-24 Thread Lindenfeld, Ivan
9:27 PM To: mssms@lists.myitforum.com Subject: [mssms] RE: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602 You can’t set the location though using client settings, that’s the problem (at least as far as I can tell). You can only set the cache size. From: listsad

[mssms] RE: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602

2016-08-23 Thread Corkill, Daniel
: mssms@lists.myitforum.com Subject: [mssms] RE: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602 We filed a bug on this in March. It is unresolved and we have had no status for months. Best I can tell the “fix” is the ability to set the location in the Client

[mssms] RE: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602

2016-08-23 Thread Lindenfeld, Ivan
um.com] On Behalf Of Lindenfeld, Ivan Sent: Tuesday, 17 May 2016 11:51 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] RE: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602 Call Premier. This is a bug. There is no permanent

[mssms] RE: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602

2016-08-23 Thread Corkill, Daniel
@lists.myitforum.com Subject: [mssms] RE: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602 Call Premier. This is a bug. There is no permanent solution as yet. We have seen it twice in the lifecycle of SCCM, once in 2007, and right now, 1511. Very disappointed to hear it

[mssms] RE: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602

2016-05-18 Thread Lindenfeld, Ivan
ay, May 17, 2016 4:00 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] Re: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602 Hi Everyone, I’ve just assisted with an upgrade at a site from 2012 R2 SP1 to SCCM 1602. Everythin

[mssms] RE: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602

2016-05-18 Thread Lindenfeld, Ivan
mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] RE: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602 Hi Ivan, Thanks for the valuable feedback, we will be looking into how many clients have been affected today. The compliance bas

[mssms] RE: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602

2016-05-18 Thread Lindenfeld, Ivan
.com] On Behalf Of Johns, Damon (DoJ) Sent: Tuesday, May 17, 2016 4:00 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] Re: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602 Hi Everyone, I’ve just assisted with an upgrade at

[mssms] RE: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602

2016-05-17 Thread Johns, Damon (DoJ)
...@lists.myitforum.com] On Behalf Of Lindenfeld, Ivan Sent: Tuesday, 17 May 2016 11:51 PM To: mssms@lists.myitforum.com Subject: [mssms] RE: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602 Call Premier. This is a bug. There is no permanent solution as yet. We have seen it

[mssms] RE: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602

2016-05-17 Thread Corkill, Daniel
, Damon (DoJ) Sent: Tuesday, May 17, 2016 4:00 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] Re: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602 Hi Everyone, I’ve just assisted with an upgrade at a site from

[mssms] RE: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602

2016-05-17 Thread Johns, Damon (DoJ)
[mailto:listsad...@lists.myitforum.com] On Behalf Of Lindenfeld, Ivan Sent: Tuesday, 17 May 2016 11:51 PM To: mssms@lists.myitforum.com Subject: [mssms] RE: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602 Call Premier. This is a bug. There is no permanent solution as yet

[mssms] RE: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602

2016-05-17 Thread Lindenfeld, Ivan
Subject: [mssms] Re: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602 Hi Everyone, I’ve just assisted with an upgrade at a site from 2012 R2 SP1 to SCCM 1602. Everything’s working great accept the automatic client upgrade seems to have changed the default client

[mssms] Re: Client Cache Location and Size incorrect following upgrade to 1511 and then 1602

2016-05-17 Thread Johns, Damon (DoJ)
Hi Everyone, I’ve just assisted with an upgrade at a site from 2012 R2 SP1 to SCCM 1602. Everything’s working great accept the automatic client upgrade seems to have changed the default client installation path to c:\CCM and the default size to 250MB as per this: https://social.technet.microso