RE: [mssms] RE: Office 365 C2R Channel Inventory

Hmm that seems to answer some of my questions. Looks like what I initially had set up as “Current” is actually “Deferred Channel” and even though most of the build numbers I have for my “First Release” don’t exactly match up it looks like that is actually the “Current Channel” Regards, Freddy

RE: [mssms] RE: Office 365 C2R Channel Inventory

This link has all of the builds: https://technet.microsoft.com/en-us/library/mt592918.aspx. They are not necessarily unique to a channel though ☹ J From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Freddy Grande Sent: Tuesday, June 28, 2016 7:38 PM To:

RE: [mssms] RE: Office 365 C2R Channel Inventory

I am so confused about this now, especially with the below link about the different branch GUIDs and the supposed inability to go between them without a reinstall.

RE: [mssms] BranchCache, ConfigMgr, and PRO Sku

You sure about this one. Isn’t it foreground if user initiated, background for deadline initiated? J From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael Niehaus Sent: Tuesday, June 28, 2016 3:12 PM To: mssms@lists.myitforum.com Subject: RE: [mssms]

RE: [mssms] Incremental collection updates

Right, there is no hard ceiling in terms of collections. There is a hard ceiling based on the number of total updates that happen. The basic recommendation is to monitor your collections using the CEViewer from the toolkit and make sure your performance isn't affected as you enable incremental

RE: [mssms] Incremental collection updates

Thanks, Daniel. I was at MMS but must have missed getting that infothanks for the detailed notes! Sent from my Windows Phone From: Daniel Ratliff Sent: ‎6/‎28/‎2016 2:58 PM To:

RE: [mssms] BranchCache, ConfigMgr, and PRO Sku

There are two BITS bandwidth policies, one for content retrieved from the server and another for content retrieved from a peer. Limiting the server traffic is fine, but you’ll want the peer traffic to run at higher speed, since it doesn’t impact the rest of the network (just on that one

RE: [mssms] Incremental collection updates

Based on what I learned at MMS 2015, the ceiling is 10,000,000, but that's not # of collections. It a matter of processing. See my notes below. · Collections o Direct membership changes kick off Full Coll Eval! o Incremental updates are allowed when done right! o Have a CAS? §

[mssms] Incremental collection updates

Does ConfigMgr current branch overcome the ceiling for number of collections that have incremental updates enabled? Thanks, Jeff Sent from my Windows Phone

RE: [mssms] Latitude E5470 - Asset Tag (Serial Number) as PC name

I’m using UEFI for W10 migration, but the issue is the same using Legacy BIOS. The earlier generation models (E5450, E5440, etc) when set for either Legacy or UEFI have no issues. I don’t see any difference in BIOS for how the different models are configured for Asset Tag, Service Tag, etc. I

Re: [mssms] Latitude E5470 - Asset Tag (Serial Number) as PC name

Are these machines utilizing UEFI or Legacy BIOS? *---* *Adam Juelich* Pulaski Community School District Client Management Specialist 920-822-6075 On Tue, Jun 28, 2016 at 12:40 PM, Fast, David D.

RE: [mssms] BranchCache, ConfigMgr, and PRO Sku

On your application of the policy, are you targeting individual devices or just allow it to be active on all devices and stuff caches where it caches??? Did you set the per device limit at say… 5%? From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jay

Re: [mssms] BranchCache, ConfigMgr, and PRO Sku

So much great feedback! We were contemplating utilizing a pretty slow footprint for BITS policy, 1-2MB let's say, across the board, and then narrow that bandwidth further using networking equipment, where appropriate. Anyone else doing something similar? Thanks On Tue, Jun 28, 2016 at 10:29

[mssms] Latitude E5470 - Asset Tag (Serial Number) as PC name

I am using a Powershell script in SCCM OS Deployment to assign PC name based on a WMI query of the BIOS SerialNumber. This works for all of our previous generation models, but not on the new Latitude E5470 laptop, so the resulting PC name is MININT-something and it has to be manually changed.

RE: [mssms] Failing to Get CB Updates after 1602 Hotfix

Exactly. To get to 1606, you need to start with a TP build, TP5/1603 to be exact. This is downloadable at https://www.microsoft.com/en-us/evalcenter/evaluate-system-center-configuration-manager-and-endpoint-protection-technical-preview J From: listsad...@lists.myitforum.com

Re: [mssms] Failing to Get CB Updates after 1602 Hotfix

TP (Beta) installs are completely separate from CB (Production) installs, you can't switch back and forth between them. *---* *Adam Juelich* Pulaski Community School District Client Management Specialist 920-822-6075

[mssms] Failing to Get CB Updates after 1602 Hotfix

Hey y'all... I'm at a loss here. I've been trying to get to the 1606 TP release, but after updating to 1602 and then 1602 Hotfix (KB3155482) nothing else every shows up in the Updates and Servicing window. I've attempted several manual checks for updates and nadda! Below is the excerpt from

RE: [mssms] BranchCache, ConfigMgr, and PRO Sku

6am-6pm 2mb, full at night On Jun 28, 2016 9:50 AM, "Jimmy Martin" wrote: > I know it’s highly dependent on underlying network capabilities, but what > do you (collective you) use for your bits transfer rate settings? > > > > Jimmy Martin > (901) 227-8209 > > *From:*

RE: [mssms] BranchCache, ConfigMgr, and PRO Sku

Just make sure when you set it, don’t use the ConfigMgr policy (XP) as it cripples BranchCache. Use the AD policy objects that came with BranchCache (Windows 7). From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jimmy Martin Sent: den 28 juni 2016 15:43

RE: [mssms] BranchCache, ConfigMgr, and PRO Sku

“Collective you” = all y’all From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jimmy Martin Sent: Tuesday, June 28, 2016 8:43 AM To: mssms@lists.myitforum.com Subject: RE: [mssms] BranchCache, ConfigMgr, and PRO Sku I know it’s highly dependent on

RE: [mssms] BranchCache, ConfigMgr, and PRO Sku

I know it’s highly dependent on underlying network capabilities, but what do you (collective you) use for your bits transfer rate settings? Jimmy Martin (901) 227-8209 From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of David Jones Sent: Friday, June 24,

[mssms] RE: SCCM Client Network Consumption Stats

Free & yourself (not realtime) is to parse the Event Logs of BITS. (99% of traffic goes through BITS). Free and 2Pint Software (Still not realtime): Use our BITS & BranchCache reporting. Doesn’t have to use BC for that to work. Paid & Realtime: Our StifleR solution does this in realtime, not

[mssms] SCCM Client Network Consumption Stats

Hi Champs, Is there a way/tool to find out how much network is consumed by SCCM Client on daily, weekly basis cumulatively. This is real time network data that is consumed by SMS Agent…, ccmexe.exe or BITS processes whatever, but done by and consumed for SMS Agent, be it policies, status