Jump to content


Established Members
  • Posts

  • Joined

  • Last visited

mikedisd's Achievements


Newbie (1/14)



  1. When disabling performance monitoring, is it best to override the Parent aggregate rollup or each individual monitor underneath it?
  2. One year on, found that putting all unhealthy servers into maintenance mode for 10 minutes sorted them out.
  3. My mistake, the CM computer account has sysadmin rights to the SQL server, db_owner of the CM database and local admin to OS.
  4. 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 *.
  5. 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.
  6. 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?
  7. 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.
  8. 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.
  9. 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.
  10. Seriously no one? Someone must has something that gives a clue as to why OSD would be throwing in extra applications?
  11. 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.
  12. 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.
  13. 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.
  14. 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!
  • Create New...