PitbullTerje

Thanks for the reply! I found your website after I wrote this post, lots of really great stuff regarding branchcache! Especially regarding using branchache in WInPE and during OSD in general, something I must try out myself I was actually thinking about making a collection of Pioneers/Pilots, I think thats a requirement from the stores aswell. Just to make sure every application update or patch works in real world scenarios before rolling out to all the devices. At the moment Im just in the design/POC-stage, so when I get the opportunity to test this at a real site in a couple of months, your tools will surely come in handy. Again, thanks for the help and I will definitely keep checking your website!

Hi! I need some advice regarding designing a solution for remote sites in conjunction with SCCM 2012 R2. Im thinking about using BranchCache instead of DP´s, but I need some kind of approval that it actually works in practice. The scenario: We have 400 remote sites (retail stores). At 350 of the sites, theres 3-10 PC´s. At 50 sites, theres 10-30 PC´s. 95% of the PC´s are desktops used as cash registers. In total about 2000 Windows 7 clients. The bandwidth is 2mbit, and we shouldn´t/can´t use any bandwidth between 07-20. During the night we have to take some overhead into consideration since there´s a bunch of batchjobs running for the system used for the cash registers. In essence, we cant have 20 clients download a big update/application over the WAN-link. The staff at the sites wont have time for troubleshooting and/or reimaging the PC´s when they get new ones or if they have to reimage old ones, so we won´t have to take OSD inte account. They will use consultants at the local citys who will just come out and switch out the cash register/desktop when there´s a problem which cant be solved remotely or when they order new ones. So what I want is an easily managed solutions for getting applications and patches out over the WAN without using to much of the bandwidth. SCCM itself is up and running here at HQ. I could go with a bunch of local DP´s, either as dedicated servers or installed on one of the local desktops, but that seems like a high maintenance solution. Especially since the sites are remote and we have limited oppurtunities to troubleshoot/replace a DP when it breaks. My estimate is that we have to use about 30 DP´s at the sites with the most devices. Seems like a lot to manage, so I would really like to avoid that. Hence BranchCache! In theory, this seems like a solution that fits our needs perfectly, but I haven´t found any real world scenarios/case studys on the internets where this has been implemented with SCCM in a case like this. I can only find design studys on how to implement it. (and one case study from MS saying it works, but I dont know if i should trust them Maybe someone here has experience from implementing a solution like this? Does it work? Any particular problems we can expect? Will this solution give us less administration then using DP´s? Or will there be too many problems to recommend this solution in practice? Thanks in advance, any help appreciated!!

Thanks for the reply! Solving it with collection membership is something thats crossed my mind too, but in my mind the ideal is if its possible to have the application advertised to the computer, but in some way flag the advertsiment as succesfull since the application is already installed(altough not via advertisement, but via custom OSD task). That way i can keep the collections the way they are, and it allows the support organisation to reinstall applications via run advertised programs when needed(with all the custom switches whe have assigned). If the computer doesnt have the advertisement, the support have to reinstall the application manually, or wait for the computer to join the collection where the application is advertised(if I for example create 2 collections per application, 1 that contains the computers that has the application in Add/remove programs, 1 that doesnt)

Hi, i have a problem/dilemma regarding win7-OSD and installation of applications thorugh USB. The environment looks like this: 1 Primary site 30 DPs 150 sites without DP(many with a 2mb WAN-link) 40 local applications, besides the standard ones installed during ordinary task sequence, advertised to computers based on Adgroup membership The computers runs Win XP at the moment, but we´re in a migration project to update to Win7. At the 30 sites with a DP, everything works fine. The OS is installed with all the standard applications that every computer should have, and the rest is installed based on AD-group membership over the LAN from the DP at the site. But the problem is the other 150 sites, were we have like 5 users at each site. Some of these users runs very big local applications, ranging from 1 to 5gb in size. Since we doesnt have a budget to send a DP or BDP to every single one of these site, the best solution seems to be to prep a USBflashdrive to do the OSD. My understanding is that there is a limit of 32gb falshdrive as installation media? You cant use an external USB-drive at like 200gb as OSD standalone media, am i right? Since alla our applications combined sums up to 80gb, i cannot get all the applications onto the USB drive at 32gb, so my thought is to install the biggest of the non standard applications during the OSD via this method, http://www.windows-n...-task-sequence/ . This way, the users have to download like 500mb of data over WAN instead of 7gb, and they can start working with all their applications much faster. BUT, since the computer is still a member of the AD group for the bigger applications(thats already been installed during OSD), the applications is being advertised to the client, which is OK, but its being downloaded once again despite the fact that the application has already been installed during OSD. So basically i want to install an application based on AD-group membership during OSD task, and i want the application to still be advertised to the client, but i DONT want it to download the 7gb of data once again, since the application is allready installed. Is there a way to do this? Can i set a flag during the OSD application installation so that SCCM understands that this application is already installed, and doesnt download it all over again? Or is there a way to prestage the local cache on the client with media from the USB, so that when the advertisement kicks in, the installation files is already in place and the clients doesnt have to download GBs of data over WAN? Or maybe I´m overcomlicating things? Maybe there´s a simpler solution to this problem? Any advice is welcome! Thanks in advance!

Hello, me and my colleague have been handed a client environment for a customer that wants to move from XP to Win7 and I have some questions regarding updating servers & clients to sccm 2007 sp2 r3. The environment looks like this at the moment: 1 central server running SCCM 2007 SP1 R2, 4.00.6221.1000, MDT 2008, Server 2008 50 secondary sites running SCCM 2007 SP1 R2, 4.00.6221.1000 client, server 2008 1500 clients running SCCM 2007 SP1 R2, 4.00.6221.1000 client, Windows XP SP3 We are going to use the same server for deploying Win7, but the exact details of the deployment plan haven't been decided on(site for site migration etc). The first step in this migration plan is to prepare the central system for deployment of win7, so i guess we have to update from SCCM 2007 SP1 R2, 4.00.6221.1000 to SCCM 2007 SP2 R3. I´ve found some guidelines regarding this this update and it seems that we have to do the update in 2 steps. First Upgrade from SP1 to SP2, and then from SP2 to R3. But do i need to do this on Central server, Secondary sites & Clients? Or can i upgrade the central server only to be able to start working on a Task sequence for Win7? Or do i need to update the secondary sites and client as well? I dont want to interrupt or cause any problems with the running XP environment during my laborations and preparation for the deployment of Win7. So im basically wondering if a XP Client running SP1 R2, 4.00.6221.1000, can talk with a central SCCM server running SCCM2007 SP2 R3? Can it still receive updates advertised to the client? And does this apply to the secondary sites as well? Can they "talk" with a central server running SP2 R3? If I want to update MDT 2008 to MDT 2010, what will happen to any existing task sequences etc for XP? For the sp1 to sp2 upgrade i was planning on following this guide: http://myitforum.com...p2-upgrade.aspx And for the R3 upgrade i was planning on following this guide: http://ckrim.blogspo...tion-howto.html Do you think this is a good plan and is there anything more that i need to take into consideration? The important thing is that i dont want to mess with the existing XP environment and cause any problems in it. I´m still a SCCM rookie, so be gentle Thanks in advance!