[mssms] RE: test 3 - disregard

[Image result for life struggle] Duncan McAlynn, Sr. Solutions Specialist, Americas HEAT Software M: +1.512.391.9111 | duncan.mcal...@heatsoftware.com HEAT Software | 490 N McCarthy Blvd. Suite 100 | Milpitas, CA 95035 From:

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

That is exactly what we do. 35000 clients. Have had no complaints. But what does that mean in the big scheme? You could right click any client in the local network of all the sites and make them a DP. We were doing before Branchcache. On Fri, Jun 24, 2016 at 2:08 PM, Phil Wilcock

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

Works fine, PRO is supported and always has been, just do it! https://technet.microsoft.com/en-us/library/mt613461.aspx#bkmk_os From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jay Parekh Sent: 24 June 2016 14:45 To: mssms@lists.myitforum.com Subject:

Re: [mssms] Side by Side Migration

Awesome. Thanks for that. On Fri, Jun 24, 2016 at 1:26 PM, Daniel Ratliff wrote: > I don’t know best practice, but in my lab when I switch between multiple > sites I do the following. > > > > 1. Stop publishing to AD in the old site > > 2. Delete the Systems

RE: [mssms] Side by Side Migration

I don’t know best practice, but in my lab when I switch between multiple sites I do the following. 1. Stop publishing to AD in the old site 2. Delete the Systems Management container in AD 3. Recreate the Systems Management container in AD 4. Grant the new site server

[mssms] RE: sccm 2012 r2 sp1-->1602 questions

This is more or less the process we went through and for the most part it went well. We do not use MDT and have not done the SQL 2012 -> 2014 upgrade. The OS upgrade process was the part we had the most problems with. There were a few places where the upgrade reset permissions that broke

Re: [mssms] Side by Side Migration

That seems like the easiest thing to do. On Fri, Jun 24, 2016 at 11:26 AM, Marcum, John wrote: > I just left them in-place and deployed a script to move the clients from > one to the other side code. I let that sit out there for about week then > ripped out all the settings

RE: [mssms] Side by Side Migration

I just left them in-place and deployed a script to move the clients from one to the other side code. I let that sit out there for about week then ripped out all the settings from the old server. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of David

[mssms] RE: System Center 1602 Hotfix KB3155482

Ironically, I was just checking my inbox while waiting for this thing to complete and noticed your thread. I, too, am seeing the same thing this morning. Seems to be related to this guy: [cid:image001.jpg@01D1CE02.3F2104C0] The MSIEXEC process completed and closed, but this remained open for a

[mssms] Side by Side Migration

created 1511 from scratch and created all collections, packages, etc. It is ready to go now. The old system has 2 sites, the new system will only have one site. All we use the SCCM for is package/application distribution and inventory. We do use boundaries now because of the 2 sites. I assume we

[mssms] BranchCache, ConfigMgr, and PRO Sku

Posting for my colleague. Some reason he's post here is not coming through. Basically comes down to a client is looking to deploy a net new SCCM environment. They have 400 sites but the CTO doesn't want servers (DPs) at the sites and he will not pay for Nomad or OneSite. Also they are