mikedisd

When disabling performance monitoring, is it best to override the Parent aggregate rollup or each individual monitor underneath it?

One year on, found that putting all unhealthy servers into maintenance mode for 10 minutes sorted them out.

Gave up, restored from backup, now back at 1511....

My mistake, the CM computer account has sysadmin rights to the SQL server, db_owner of the CM database and local admin to OS.

I've just upgraded from 1511 to 1610 and now I am getting the following error under Site Status / Management Point (and mpcontrol.log): MP Control Manager detected management point is not responding to HTTP requests. The HTTP status code and text is 500, Internal Server Error. I've checked / attempted the following: {EDIT} Made sure the the SQL database instance has the CM computer account set as *italics*sysadmin*italics*. The Windows firewall is off. Installed all Important and Recommended Updates / rebooted. Uninstalled the MP role, restarted and reinstalled the role. Mpsetup.log states the install was successful. Validated the CM service account (pwd's correct). Ran iisreset after most steps. Checked the CM server still has full access to the Systems Management OU in AD. Set "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmEval\NotifyOnly" to TRUE, uninstalled the MP role, restarted, reinstalled MP role, restarted. Tried the trick outlined here: https://www.anoopcnair.com/configmgr-sccm-2007-mpcontrol-log-shows-httpsendrequestsync-fails-with-status-code-500-internal-server-error/ We have a simple setup of 1x primary CM server and 1x SQL Server, both running on Server 2012 R2. Running out of ideas except to rebuild CCM. Any suggestions? Thanks. [EDIT]: Further steps tried: Performed 2x system resets through the builtin ConfigMgr Setup Wizard as mentioned here: http://vworld.nl/?p=2228 Installed .NET 4.6.1 as replacement of 4.5.2. Removed and added the default webpage binding of port 80 to *.

There must be around 100x mgmt packs installed on our SCOM server. Can I somehow detect the unused ones so I can remove them? SCOM 2012 R2 RTM.

I thought this would be a straight forward and obvious thing to execute but I couldn't find anything that worked from a web search. We had an infrastructure upset that was quickly rectified but it left ~50 servers in a false positive state of Critical . I need a method to perform a Reset Health on all the servers listed as critical. I thought having something like this in a loop would work but it made no difference: Get-SCOMMonitoringObject { $_.HostComputer.RecalculateMonitoringState() } Any ideas?

Having trouble finding this info. I'm designing a layout for an educational institution and have 2 primary ConfMgr servers on separate AD forests under a CAS, one to manage Staff/Admin and the other to manage student computers. As there will of course be both staff and student devices at each campus, can I use one distribution point for both primary servers or do I need to build 2 DP's? Thanks.

I have 4x ADR's for deploying updates to 4x respective server collections. I selected Add to an Existing Software Update Group and have it run every month, adding the previous month's updates; Date Released or Revised: Last 1 month This way I only need 1x SUG for 2015 per collection. However, it doesn't just add updates to the SUG, it deletes all the existing updates that were already in the SUG. I now only have updates from the last 30 days in each SUG. Is there something to prevent this and have it retain what's already there? Or is better to create a new SUG every month? That gets kind of messy that's all.

Because I live in Australia, we don't receive the monthly MS patches until sometime on Wednesday. So when creating ADR's for auto deployment of updates, I set the schedule to run every second Wednesday of the month. The problem is that the second Wednesday doesn't always follow the second Tuesday; (example of this is April 2015 when day 1 is a Wed.). It just means I have to log in every few months and run the ADR manually, no big deal. However we have a fairly complex update deployment procedure with ADRs for development, UAT and a few production server groups that will get a messed up schedule because of this. Just wondering if anyone has a working solution to overcome the 'Patch Wednesday' problem.

Seriously no one? Someone must has something that gives a clue as to why OSD would be throwing in extra applications?

I have a single site SCCM 2012 R2 server will all roles. When deploying Windows 7 OSD's, there are other applications being installed that aren't listed in the task sequence. Not only that, some apps listed in the TS are not installing and what does install is not in the order listed in the TS. I've created a new TS from scratch and added a few Apps, but a whole bunch of other applications are being installed. This is about as flakey as it's ever been and I can't get consistent results. Attached is a shot of my TS; Office/FIM/Quicktime/TRIM occasionally install and the Flash Player Plugin install 9th even though it's listed second. It's currently also installing Chrome and Lync, which are packaged and deployed to an All Windows 7 collection. Has anyone come across these kind of issues? I can't make any sense of it.

Thanks for this. I forget to mention that I have installed CU3 which I assume contains this update. Something possibly just needs to be uninstalled/reinstalled but I don't know what as I've tried several componet reinstalls already. The whole system screams of flakiness.

I just upgraded our SCCM 2012 SP1 to R2. All went smoothly except for the boot images which was to be expected. I've gone through dozens of forums and have run out of ideas to get PXE boot working again. Right now I get PXE-E51: No DHCP or proxyDHCP offers were received. This occurs from all distribution points. I've done the following: Deleted boot images and recreated using CopyPE.exe several times Removed "PXE support for clients" from a DP. After WDS uninstalls, I delete the RemoteInstalls folder. Reboot and add back PXE support for clients. Did the above but then removed the DP role. Reboot and reapply. Firewalls are fine and an IP is being offered from DHCP. Application deployment works fine but I can't get a PXE boot happening at all. I have a x64 and x86 boot image, both have the Deploy this boot image from the PXE-enabled DP" option ticked. Both are deployed to the DP's and the x64 boot image is used in a few task sequences that are deployed to the Unknown Computers and various site collections. Pretty sure I haven't missed any steps. One clue I have is in the SMSPXE.log which hasn't updated for the past 2 days and has a final entry of : ================= PXE Provider shutdown. ===================== Any ideas muchly appreciated. Single primary site, no CAS/ secondarys 4 DP's, all configured to support PXE clients.

Thanks for the reply, the existing server became a real mess when upgraded from RTM to SP1 (ie, EVERYTHING broke) so this makes a lot of sense. Thanks!

The existing SCCM server is problematic and some components / services (WSUS, WDS) are broken, which I can't get working again. It's also Svr 2008R2 and we want to move SCCM to Svr 2012 R2.

I need to perform a side-by-side migration of our existing CM12 SP1 system to CM12 R2. Which is preferable: Upgrade existing CM12 SP1 to R2 and then migrate to new CM12 R2 server; or Migrate to new CM12 SP1 build and then upgrade that to R2? The remote database will also be moved from a SQL 2008 box to SQL 2012 SP2. thanks

That's what I figured, set up SCUP for 3x Adobe products and everything else deploy through SCCM. There's a lot of app like Chrome, Firefox, VLC, QuickTime, Notepad++, 7-Zip, iTunes etc., that simply might not do well through SCUP.

I'm having trouble coming up with a third party application design. I configured SCUP to test deploying Java through SUP with flaky results. I was wondering, now that CM2012 uses Applications deployment with detection methods as well as supercedence, is SCUP really relevant anymore for patch management. There's no budget in our company for Secunia, Solarwinds or whatever and creating SCUP packages seems to take just as long as a CM2012 Application. Just wondering how everyone else is addressing third part app patching.

In our Environment, we have a list of third party applications that users can download through Software Centre, such as Chrome, Firefox, iTunes etc. They can then uninstall if they wish. I have a collection for each app that queries all users that have downloaded this respective app and want to now deploy an updated version. It's easy enough to deploy the latest .msi file and uninstall the outdated version. However this deployment will be a 'Required' install and the user won't be able to uninstall it if they so desire. If I use the 'Supersede' function, this will rely on the user performing the download of the updated app, which they shouldn't have to do. Is there a way to quietly auto-update these applications and still allow the user to uninstall completely if they no longer wish to use it? Or am I totally on the wrong track? Using SCCM 2012 SP1 CU3, all end users have Windows 7SP1. Thanks

Ahh why didn't I think of that?? Thanks for such a simple solution.

I need to deploy a package that runs a script using the current user's username. However, because SCCM uses the SYSTEM account, this changes the Windows environment variables (i.e., %username%, %userprofile%, etc.). I can't user the Run with user's rights because all user's are Standard Windows users and this needs Administrative rights. I've come up with a nasty Powershell script that grabs the logged in user's account name using WMIC, then truncates the domain name (first 5 characters) and the spaces from the end. This then goes into a Powershell variable. Is there an easier/better/more robust way of going about this? I thought this would be a rather common scenario; the need to push out a script that writes to the currently logged in user profile.

I wondered about that, just leaving the default paths in the data/transaction file paths. Thanks for letting me know, I'll give this a run. Cheers!

Thanks for the confirmation, better rewrite my strategy now. The existing server has been highly problematic since we upgraded from RTM to SP1_CU3. OSD task sequence, WSUS and WDS service aren't working and I can't fix them. Microsoft couldn't resolve the OSD TS and everything is strung together with work arounds. On top of that the server build wasn't designed very well and the folder structure is a mess. Mgmt also want CM12 on a Server 2012R2 platform.

Our existing SCCM 2012sp1 server is no longer fully functioning and needs to be migrated. I want to build a SCCM 2012 R2 server and migrate all content; however according to http://technet.microsoft.com/en-us/library/gg699364.aspx this migration strategy isn't supported. If that's the case, what would be the best way to go? Should I try upgrading my existing SCCM to R2 (really don't want to as the last upgraded destroyed a lot of components), or should I build another SCCM 2012sp1, migrate data and then upgrade this to R2. Or is there a better option that doesn't involve any upgrading?