Garrett804

Asset Hardware Inventory, Licensing Inventory, Windows update compliance, 3rd party application update compliance, fast deployment and patching for any critical changes that need to take place quickly enterprise wide. AD Group Discovery isn't really useful in my opinion as so many AD environments are disorganized and junk. A simple way for application monitoring and licensing is to deploy anything licensed to devices and anything not licensed to users. That way user 1 can't go to user 2's machine and install a licensed product but they can install adobe reader or something else that isn't licensed if they need it. The biggest benefit for SCCM is deployment, Compliance, and reporting.

I run mine by putting the ClientPatch folder under both the x64 and i386 folders with the appropriate patch for that architecture.

Are you deploying them as required? Do you have maintenance windows set? Are you keeping your Update Groups down below 1,000 updates? Care to share your settings for the deployment with us to help diagnose your issue?

The password is 24/7/365 for the boot environment. If you don't type it correctly you don't get access to your task sequences for imaging.

Those look like optional updates. The classification of those updates is labelled as "Updates" so if you don't have your SUP configured to sync "Updates" then it won't pull them into your DB for WSUS.

You'll find the SMSPXE.log under the SMS_CCM\Logs folder. Also for option 67 make sure you include the \ for the \smsboot\x64\wdsnbp.com Option 66 if you have DNS issues should be the servers IP for the DP that is going to do OSD.

you can avoid this by putting a password requirement. The password option is under the PXE tab for the Distribution Point.

I'd agree with Garth here. I've never heard of this issue or experienced it first hand. Usually a high pagefile usage would be due to not enough RAM to be available for the .dll and .exe paging executions to take place. Being that these are VM's have you tried adding some RAM on one of them?

I stopped using SCUP because of that exact issue so I do updates via packages now.

Thanks so much. We have had users with admin rights trying to do this already and causing problems. I was looking into a way to disable it.

It looks like your WMI Query is wrong Jeff. You are calling for a ComputerSystemProduct version when what you should be doing is calling for the "Model" of "ComputerSystem"

Are you sure you don't have the option selected to install and/or restart outside of a Maintenance Window?

It would be a setup just like any other DP. You simply just add the role onto the existing server in your environment.

Well first you need a server that hosts your DC, DHCP, DNS and is connected back via VPN to your main office. Once you have established that and confirmed you are replicating correctly for AD then you can move on to adding the DP role to that server for your SCCM DP. Another option would be to put hyper-v on that box and do a separate hyper-v server just for SCCM but you have additional licensing costs of a 2nd OS if you go that route. The benefit is you don't mess with your DC in any way for configuration though. Cliff Notes: 1. Build out DC at remote location 2. Verify DC is operating correctly and AD replication is working 3. Either add DP role to the DC directly or go the hyper-v route and build out a separate system for SCCM.

Have you tried manually running a data discovery cycle on one of the machines with the issue to see if it then updates the data in the console?

It has the initial pop-up and then the option to just leave it up. It doesn't really seem logical to have it keep popping up over and over and over again.

I run my entire environment on Server 2012 R2. I never set it up originally with 08 R2 so I can't say for sure if you can run a hybrid environment or not due to versions of things like the windows update agent being different for instance. I'm not sure how that would affect deployments or not. In thinking it over I don't see any issue with it since a DP is strictly just a location based software distribution point with a backend brain. It's no different than having a file server except it has a remote system with a brain allowing it to service the files individually and automatically rather than having to manually install one by one on each machine. That may not make much sense but that's how I would relate it to. A File server with a backend brain dictating who and what gets the files and when they get them.

What you are looking for is a built in report from Microsoft. Simply go to your SCCM reporting site. Go under the "Software Updates - A Compliance" reports and select the "Compliance 5 - Specific Computer" report. Fill out the fields and select the machine you are wanting and run the report.

try running a discovery data cycle and application deployment evaluation cycle on them. I'm wondering if they are reporting back successfully. If you don't have the right click tools I highly suggest you get them as they will help run this on them all very easily. http://www.nowmicro.com/recast/

the CCMCache folder is where all files are stored when they download from within SCCM. You can simply just create some task sequence that clears the cache on the machines. I'm not sure what the installer folder is for specifically but the WinSXS folder stores data on your hardware on the machine etc so you don't want to do anything with that one. My recommendation would be to just clear out the ccmcache folder to start with. Also if you do one-drive at all it stores 2 copies of everything it sync's so it can quickly fill up a drive as well.

Did you inject the surface nic drivers and HDD controller possibly as well to the boot image?

ok so I think we need some more information on your environment. 1. You say you have DHCP disabled so where exactly are you pulling IP's from then to do PXE? 2. Do you run WDS on the same subnet as this machine you are testing with? (this wouldn't require ip-helpers)

I always go from TOP down in any structured environment. I don't run a CAS though as I don't need to since I don't have over 100,000 devices.

Why not just set a maintenance window time and that way they will all automatically reboot in the maintenance window and you don't have to deal with users at all.

It's in the client settings. Look under the "Computer Restart" tab. I guess you could simply just make it pop-up and set the timer for like 8 hours or something ridiculous like that so that they can't make it go away unless they restart. That box would be the lower of the 2, the top one is for the temporary pop-up and the bottom for the permanent pop-up.