Search the Community

Hi All, I am hoping someone can help. my SCCM knowledge is not very advanced still learning. The company SCCM expert left the company he was in the middle of providing a DP to an outside company to use as a PXE DP ( to build new desktops before being delivered.) He set it all up but it never worked, now its fallen in my hands to get it up and running. When the desktops try to pxe boot it fails. The pxe logs display these errors "Unsuccessful in getting MP key information. 80072ee2." PXE::MP_initializeTransport failed;0x80072ee2 PXE::MP_Lookupdevice faile; 0x80070490 Not in SSL Socket ' connect' failed 8007274c sending with winhttp failed 80072ee2 I tried the browser MP tests and both mplist and mpcert failed. I can ping the MP. windows firewall has been disabled. DP has been added to the boundary as subnet ID. Any help would be appreciated. Thanks C

Hello, We just installed the hotfix for SCCM 1810 (KB4486457). This hotfix implies a new version of the SCCM agent (5.00.8740.1024). We configured SCCM to deploy automatically this agents on workstations and servers but we are experiencing the following issue (ccmsetup.log) : I managed to install the client by using the ccmsetup.exe with the following parameters : SMSSITECODE=LOL SMSMP=HTTPS://SCCM-SUPMPDP2.DOMAIN.COM DNSSUFFIX=DOMAIN.COM CCMFIRSTCERT=1 CCMCERTSTORE=MY But the SCCM client is not able to find its management point. Actually it finds both MP but considers they are not "Compatible" Do you have an idea ?

We are having a very difficult time locating any posts, forum topics, or ms bulletins in regards to the attached distmgr.log file. If anybody of you knowledgeable helpful users on the forum can assist in ANY way, please feel free to offer any suggestions. We currently are unable to distribute any new data, sync dp's, etc... We have performed a site reset. We have removed MP role. We have removed and replaced the mentioned file. Kind of at a loss. Short of rebuilding the main site server, I'm not too sure as to our next step. Any assistance would be greatly appreciated. Thank you in advance for your time and assistance. distmgr.log mpcontrol.log

Hi!!! I have a problem with my sccm 2012 r2 on w2k12. When i try to install MP the option HTTP is greyd out!!! WHY!!!!!??????????????? Many thanks!!!

Our environment contains a CAS site and 3 Site servers. Currently each site server has 1 DP and 1 MP. Because of a firewall and various security limitations, we are setting up a new DP, MP and update point that reports to one of the existing site servers. We use SCCM for OS Deployments. We Use Site Based boot media today. I do not see the benefit of selecting dynamic Media option when creating a boot disk because I still have to enter in a DP. So in my existing setup, does it just make sense to still use Site base media but have 2 boot disks for my one sccm site that has 2 MP and DPs. All the computers that report to the 2nd MP/DP will in their own boundary I haven't investigated what I am going to do with DP groups. Currently we don't use them.

Hi, I need your advice about migrated sccm2007 AD entries(SMS-MP-SiteCode-SiteServerName, SMS-SLP-SiteCode-SiteServerName and sccm2007 sitecode) that still exists in system management container, sccm 2012 client installation on some machines failing because they are still contacting with old sccm2007 MP and assigned to sccm2007 site code "Name: 'MP.x.x.x.com' HTTPS: 'N' ForestTrust: 'N' LocationServices 4/25/2016 1:38:12 PM 3780 (0x0EC4)" log file attached. we are using GPO for site assignment. please help to answer following Qs: - is deleting migrated sccm2007 AD entries from system management container, will help on sccm2012 client installation? - what is best practice to delete sccm2007 MP and site code from system management container? thanks in advance. LocationServices.txt

I'm looking for information or documentation on client to management point communications start to finish. What reports go where? Where's the inbox for the mp? In short I'm trying to troubleshoot some reporting problems I have. The largest one is different reports aren't showing the latest information. Perhaps I'm doing something wrong with my procedures so I'm open for suggestions. Example - I distributed Acrobat 11 to a collection 2 days ago. The deployment monitor shows successful and the client definitely has Acrobat 11. I look at Report Manager (Software 02D) and it reports it still has Acrobat 8. I check out Resource Explorer and it says Acrobat 8. I run a query that looks for versions of Acrobat less than or equal to 11 and it reports the client has Acrobat 11. I've forced the Hardware Inventory Cycle on the client. The client agent is set to report every 7 days so I guess I shouldn't expect it to show in the 02D report yet but why does my query produce the most recent information? This is one of a series of questions I'm hoping I can get answered here. Thanks ahead of time for even reading this.

Can someone help me, i cannot install Management Point on my server, here is my logs. I configures all parameters correctly but every time i get same error. i reinstaled server 7 times someone help me please <10-19-2012 18:07:12> SMSMP Setup Started.... <10-19-2012 18:07:12> Parameters: C:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:SCCM SMSMP 0 <10-19-2012 18:07:12> Installing Pre Reqs for SMSMP <10-19-2012 18:07:12> ======== Installing Pre Reqs for Role SMSMP ======== <10-19-2012 18:07:12> Found 2 Pre Reqs for Role SMSMP <10-19-2012 18:07:12> Pre Req MSXML60 found. <10-19-2012 18:07:12> No versions of MSXML60 are installed. Would install new MSXML60. <10-19-2012 18:07:12> Enabling MSI logging. msxml6_x64.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\msxml6_x64MSI.log <10-19-2012 18:07:12> Installing C:\Program Files\Microsoft Configuration Manager\bin\x64\00000409\msxml6_x64.msi <10-19-2012 18:07:13> msxml6_x64.msi exited with return code: 0 <10-19-2012 18:07:13> msxml6_x64.msi Installation was successful. <10-19-2012 18:07:13> Pre Req SqlNativeClient found. <10-19-2012 18:07:13> SqlNativeClient already installed (Product Code: {C79A7EAB-9D6F-4072-8A6D-F8F54957CD93}). Would not install again. <10-19-2012 18:07:13> Pre Req SqlNativeClient is already installed. Skipping it. <10-19-2012 18:07:13> ======== Completed Installation of Pre Reqs for Role SMSMP ======== <10-19-2012 18:07:13> Installing the SMSMP <10-19-2012 18:07:13> Passed OS version check. <10-19-2012 18:07:13> IIS Service is installed. <10-19-2012 18:07:13> No versions of SMSMP are installed. Installing new SMSMP. <10-19-2012 18:07:13> Enabling MSI logging. mp.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log <10-19-2012 18:07:13> Installing C:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi CCMINSTALLDIR="C:\Program Files\SMS_CCM" CCMSERVERDATAROOT="C:\Program Files\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1 <10-19-2012 18:07:41> mp.msi exited with return code: 1603 <10-19-2012 18:07:41> Backing up C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError <10-19-2012 18:07:41> Fatal MSI Error - mp.msi could not be installed. <10-19-2012 18:07:41> ~RoleSetup(). __________________________ Property(S): FilesInUse_Info = Setup has detected that it needs to update some files that are currently in use by other processes. To prevent having to reboot the machine, please close the following applications: Property(S): DefaultUIFont = DefaultDlgFont Property(S): DialogBox_Title = ConfigMgr Management Point Setup Property(S): WelcomeDialog_Info = This will install the ConfigMgr Management Point. Property(S): InstallDialog_Title = Install Property(S): InstallDialog_SubTitle = The product is now ready to install Property(S): InstallDialog_Info = Click Next to proceed. Property(S): ProgressDialog_Title = Please Wait Property(S): ProgressDialog_SubTitle = Setup is configuring your system. Property(S): CompleteDialog_Title = Setup Complete Property(S): CompleteDialog_SubTitle = Setup has finished updating your system. Property(S): CompleteDialog_Info = Setup was successful. Property(S): UserExitDialog_Title = Setup Aborted Property(S): UserExitDialog_SubTitle = Setup was cancelled Property(S): UserExitDialog_Info = The ConfigMgr Management Point setup was cancelled. Property(S): InstallErrorDialog_Title = Setup Aborted Property(S): InstallErrorDialog_SubTitle = Setup failed Property(S): InstallErrorDialog_Info = Setup encountered an error and could not continue. Property(S): PolReqStagingDir.1114972D_590D_4AB6_BA2E_779928CEDCC2 = C:\Program Files\SMS_CCM\PolReqStaging\ Property(S): SystemFolder.1114972D_590D_4AB6_BA2E_779928CEDCC2 = C:\Windows\SysWOW64\ Property(S): System64Folder.1114972D_590D_4AB6_BA2E_779928CEDCC2 = C:\Windows\system32\ Property(S): CcmDefaultPolicyAuthority = SMS:MP:Default:{26ED0430-F99D-4A6B-89B6-90BC56EC40EE} Property(S): MPVDirRoot.67022EC1_A401_46E9_91FC_2DF2ED04CF15 = C:\Program Files\SMS_CCM\SMS_MP\ Property(S): Res1033.0EACD2EE_412B_4985_9727_96BC217AABD8 = C:\Program Files\SMS_CCM\1033\ Property(S): Res1033.4CB41E5B_59DE_4D09_98C5_332377961F73 = C:\Program Files\SMS_CCM\1033\ Property(S): MsiLogFileLocation = C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log Property(S): ProductState = -1 Property(S): PackagecodeChanging = 1 Property(S): USESMSPORTS = TRUE Property(S): SMSPORTS = 80 Property(S): USESMSSSLPORTS = TRUE Property(S): SMSSSLPORTS = 443 Property(S): USESMSSSL = TRUE Property(S): SMSSSLSTATE = 0 Property(S): CCMENABLELOGGING = TRUE Property(S): CCMLOGLEVEL = 1 Property(S): CCMLOGMAXSIZE = 1000000 Property(S): CCMLOGMAXHISTORY = 1 Property(S): CURRENTDIRECTORY = C:\Program Files\Microsoft Configuration Manager\bin\x64 Property(S): CLIENTUILEVEL = 3 Property(S): MSICLIENTUSESEXTERNALUI = 1 Property(S): CLIENTPROCESSID = 3904 Property(S): MsiSystemRebootPending = 1 Property(S): VersionDatabase = 200 Property(S): VersionMsi = 5.00 Property(S): VersionNT = 601 Property(S): WindowsBuild = 7601 Property(S): ServicePackLevel = 1 Property(S): ServicePackLevelMinor = 0 Property(S): MsiNTProductType = 3 Property(S): WindowsFolder = C:\Windows\ Property(S): WindowsVolume = C:\ Property(S): System64Folder = C:\Windows\system32\ Property(S): SystemFolder = C:\Windows\SysWOW64\ Property(S): RemoteAdminTS = 1 Property(S): TempFolder = C:\Windows\TEMP\ Property(S): ProgramFilesFolder = C:\Program Files (x86)\ Property(S): CommonFilesFolder = C:\Program Files (x86)\Common Files\ Property(S): ProgramFiles64Folder = C:\Program Files\ Property(S): CommonFiles64Folder = C:\Program Files\Common Files\ Property(S): AppDataFolder = C:\Windows\system32\config\systemprofile\AppData\Roaming\ Property(S): FavoritesFolder = C:\Windows\system32\config\systemprofile\Favorites\ Property(S): NetHoodFolder = C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Network Shortcuts\ Property(S): PersonalFolder = C:\Windows\system32\config\systemprofile\Documents\ Property(S): PrintHoodFolder = C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Printer Shortcuts\ Property(S): RecentFolder = C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Recent\ Property(S): SendToFolder = C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\SendTo\ Property(S): TemplateFolder = C:\ProgramData\Microsoft\Windows\Templates\ Property(S): CommonAppDataFolder = C:\ProgramData\

Hello Windows-Noob users, Need your Help one more time. Please check the error and please advice. thank you

In our last post, we finished configuring computers and devices to be managed by SCOM. So at this point we have SCOM setup and running, along with a few agents installed on other systems in our environment. Technically, you could say that we are monitoring our environment, however, this isn’t entirely accurate. In actual reality, SCOM is only monitoring the state of the Agent that is installed on the systems. Right now, SCOM has no insight into the Operating System, or any middleware platforms (i.e. SQL, IIS, AD, etc.). We are going to correct that by importing Management Packs. Download Management Packs To start, we need to download the Management Packs (MPs) we want to install. Open a browser and navigate to the System Center Marketplace (URL: http://systemcenter.pinpoint.microsoft.com/en-US/home). From here, enter your search term, and click Search. For our example we will enter “Windows Server” (I will explain why shortly). Currently there are 539 results, though this may change depending on when you perform your search. In reference to SCOM, we are specifically looking for ‘Monitoring Management Pack’ as this marketplace will also contain other packs for use with SCCM, Orchestrator, etc. In our example of “Windows Server”, look for “Windows Server Operating System Monitoring Management Pack”, and click the title (which will be a hyperlink). This will bring you to that specific Management Packs page. From this page you can read information about it (i.e. which OS’s it supports), reviews, release date, etc. You will need to determine if this Management Pack is applicable to your environment. This one is applicable to my lab environment I am using, because I have Windows Server 2012. Click the orange ‘Download’ button in the top left area of the page. This will bring you to the Microsoft Download Center. From here you can read further information about system requirements, installation instructions, etc. When you are ready, click the red ‘Download’ button. You will be prompted with a dialog, asking you which files you want to download. The MSI file contains the Management Pack, and the DOCX provides more in depth information. I would recommend downloading both files. From my personal experience, I would read the entire Management Pack documentation twice (and I have done so for each/every Management Pack that I have implemented). This serves 2 purposes. First, I highlight points that are applicable to the environment that I am implementing it in. Second, I review it a second time focusing on the points I’ve highlighted. Select the file(s) that you want to download, and click the Next button. Download the files to your either your workstation or your SCOM server. I mention your workstation, only because you probably don’t have Microsoft Word installed on your server, and you need to be able to read the documentation. At this point to move forward, I will assume that you have downloaded or copied the MSI file (in this specific example ‘System Center Monitoring Pack-Windows Server Operating System.msi’) to your SCOM server. Install Management Packs On your SCOM server, run the MSI to install it. Read and accept the License Agreement and click Next. Next select the folder you want to install to. There are a few things to take note of at this point. First, remember the directory that the Management Pack is installed to, as this will be used in a later step. Second, it is recommended that you select the option to install the Management Pack for ‘Everyone’ to avoid any access related issues. Third, and the most important, is that this is actually NOT installing the Management Pack. I disagree with the wording used in this dialog, since in fact this is not installing anything, but rather is extracting the files required for installation (you’ll see what I mean shortly). But I digress. Click Next. Finally, click the Install button. The installation will be quick. Once it is complete, click Close. When you close the installation dialog, the directory that you installed the Management Pack to MAY open in File Explorer. I stress “may” because I haven’t noticed every Management Pack that I have installed behave this way. If File Explorer does open, you can close it, as we will work with these files in another step. Now that we have “installed” the Management Pack so that the .MP files are extracted, we can now move onto the final step, importing. Import Management Pack At this point, we have downloaded the Management Packs we are interested in (in our example the Windows Server OS), installed it on the SCOM server so that the .MP files are extracted and available for use. Now we have to import the Management Packs so that SCOM will have the information required to identify and monitor the technology platform. Start by opening the SCOM console, and navigating to the Administration space. From the Administration space, you can either click on the link ‘Required: Import Management Packs’, or you can right-click on the Management Pack item in the left navigation pane. I am going to demonstrate using the navigation pane option, since the link may not always be present after you import a few Management Packs. So, right-click on the Management Pack item in the navigation pane, and choose ‘Import Management Packs’. This will cause the Import Management Packs wizard to launch. From the first and really only dialog screen, click the Add button. You will be presented with 2 options, ‘Add From Catalog’ and ‘Add From Disk’. The ‘Add From Catalog’ option will enable you to search the catalog directly, however, most Production systems don’t have an Internet connection, which this option requires. \ Therefore, we will demonstrate and choose the ‘Add From Disk’ option. When you select this option, you will immediately receive the following prompt. Since, in Production, your server probably will not have Internet access, we will choose ‘No’. Now, you will see the File Explorer dialog. From here you need to navigate to the location that you installed the Management Pack (in our example it is: C:\Program Files (x86)\System Center Management Packs\System Center Monitoring Pack-Windows Server Operating System\). When you navigate to the location that the Management Pack is installed, you will then see several .MP files. You can select more than one MP file at a time. Since our lab example is running on Windows Server 2012, we will select the ‘Microsoft.Windows.Server.2012.Discovery.mp’ and ‘Microsoft.Windows.Server.2012.Monitoring.mp’ files, then click Open. The system will add the .MP files to the import list. However, you will notice that there are a few errors! Why is that? As you can see in the Status Details this is because some Management Packs have dependencies. To see which dependencies you are missing, click the Error link. You can see from the following 2 examples, that some Management Packs have more than one dependency. So, to be able to import the Windows Server 2012 Operating System Management Pack(s), we need to also import 3 additional Management Packs. Thankfully, we can import all of these Management Packs at the same time. So, click Cancel on the Import Management Pack Error dialog, and go back to the Import Management Packs dialog and click Add > From Disk, and select the other dependant Management Packs. Your Select Management Packs dialog should then look similar to this: Now all you have to do is click the Install button. The import will begin, and may take some time depending on the number of Management Packs you are importing. Once the import has completed, click Close. You can confirm that the Management Packs have been successfully imported, but looking for them in the Management Pack list. Additionally, when a new Management Pack is imported, there may be new/updated Reports included. As well, if you navigate to the Monitoring space, you will see new folders/views for the technology platform that the Management Pack relates to. In our example, we now see the Microsoft Windows Server folder, and within there it has a Windows Server State view that shows the status of the server(s). With this new Management Pack imported into SCOM (specifically the ‘Discovery’ Management Pack), SCOM is now able to identify systems that are running this technology platform. This is how it works for all Management Packs (i.e. SQL, IIS, WSUS, AD, etc.). SCOM will now start Alerting to issues that pertain to the technologies that it can detect and monitor. Congratulations, your SCOM environment is now able to monitor your Windows Server 2012 Operating System and report/alert on any issues. For any other technologies, repeat the same steps described. Now that we have SCOM monitoring and alerting to issues in our environment, we need a way to easily be notified when there is an issue. That’s why we need to Enable Notification Channels. Stay tuned for the next post.

Preface: Running SCCM 2012 on physical hardware, with MS Windows Server 2012 and SQL Server 2012. I know it isn't officially supported, but thus far most everything is working splendidly! So, I know I post more questions than answers here, but I'm still getting my feet under me with SCCM 2012. I need some brilliant minds to help me unravel an issue I've been having for some time now. My site statuses are all great except for my Management Point status. I keep getting a recurring critical error (Message ID 5436). I discovered that if I remove the MP role and re-add it, the MP status resets and works fine...for a while. But if I come in the next morning the error has reappeared overnight. I've spent a lot of time trying to resolve the issue on my own but can't seem to track down the cause. The logs are mildly unhelpful, given I don't know what I'm looking for. I have a hunch it could be related to IIS (which I know very little about) and the web has yet to be helpful in regards to setting up IIS to play nice with SCCM. I resolved an issue related to WebDav that seemed to clear up a smaller MP issue, but this one still persists. Is there any help someone can provide me outside of what is listed in the error message? I have attached a screenshot of my mpcontrol.log in an effort to be helpful. If there is any other info I can provide I would gladly give it to try and work through this problem. Thanks in advance for the help!

Hello, We have a site with two MP's, one used for a DMZ (behind fire wall) and one for the production environment. When installing the SCCM client for the production computers they connect to the correct MP but then quickly change to the wrong MP behind the firewall. MS explained that all MP's for a site are listed and the SCCM client choose one of them and then tries to connect. Then it tries another. Our problem is that it takes hours before the client changes MP again and it doesn't stay connected to the correct more than a couple of minutes. This causes the client not to register ok with the site and it doesnt receive the policy ok. Boundaries are ok and boundarie groups points to the correct MP. What could cause this issue and how could we solve it? Would a secondary site setup for our DMZ MP behind the fire wall solve this or would our production clients still try to connect to the DMZ MP? Any help would be appreciated! /Sam A.