Jump to content


Leon1983

Established Members
  • Posts

    44
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Leon1983

  1. I have had a bug confirmed related to Android for Work enrolled devices and Exchange Conditional access. Please see my blog post here for the workaround I have been provided at this stage https://leonashtonleatherland.blogspot.co.uk/2017/08/intune-android-for-work-exchange_9.html
  2. 0 Hi, We are experiencing multiple instances of the above event ID on both of our SCOM management servers. On the RMS the below workflows are being referenced; Microsoft.SystemCenter.CollectSignatureData Microsoft.SystemCenter.CollectPublishedEntityState Microsoft.SystemCenter.CollectEventData Microsoft.SystemCenter.CollectAlerts Microsoft.SystemCenter.CollectPerformanceData Microsoft.SystemCenter.CollectDiscoveryData On the second Management server on the below is being referenced; Microsoft.SystemCenter.CollectDiscoveryData I am led to believe this is indicating performance issues specifically with the operational Database and have followed this article to the best of my ability https://support.microsoft.com/en-us/help/2681388/how-to-troubleshoot-event-id-2115-related-performance-problems-in-operations-manager . I can also confirm that the most recent changes in our SCOM Infrastructure that may be affecting this are; 1.New Management server was added to the environment 2.SCOM Action Account had to have its password changed, which I followed the procedure as per this article http://thoughtsonopsmgr.blogspot.co.uk/2015/01/om12x-changing-passwords-om12x-service.html 3.Both the Operational and Data Warehouse Databases which almost full and only auto growing by 10MB at a time, so I have removed auto grow and sized both databases correctly, removing autogrow. I also believe that excessive configuration churn is not taking place due to the presence of event ID's 21024 being promptly followed by 21025 or 21026 in the event logs as per the following article https://support.microsoft.com/en-us/help/2603913/how-to-detect-and-troubleshoot-frequent-configuration-changes-in-operations-manager Is there anything else that I can check for on this? Regards Leon
  3. Failed to get SDM CI for update (Site_1AAA8919-CE7D-43A2-8BAF-D95647C0D2B9/SUM_62a927af-8bc2-4ede-b504-d638e1e0c066) from type store, error = 0x80070002 Failed to get SDM CI for update (Site_1AAA8919-CE7D-43A2-8BAF-D95647C0D2B9/SUM_593ada2f-ccdd-4c31-abc2-045386837346) from type store, error = 0x80070002 My understanding is that the SUM_ guid can be matched to an actual update?
  4. Hi Niall, I am just trying to work out how to match the SUM guid to the update itself.. any advice on this? Did you see the recent comments on the Technet post I mentioned or do you think this is an unrelated issue? Regards Leon
  5. I cannot seem to make any headway with this, I have seen another post on Technet, with similar characteristics to this issue here https://social.technet.microsoft.com/Forums/en-US/e5a3a864-2d0c-40be-b7c7-d27b48bee17c/failed-to-get-sdm-ci-for-update-from-type-store-error-0x80070002?forum=ConfigMgrCompliance&prof=required which seem to inidicated that the SUP and WSUS components should be removed and then re added again.. I have carried out a client scan while monitoring ScanAgent.log, UpdatesDeployment.log, UpdatesHandler.log and UpdatesStore.log in the same merged view within CMTrace, and the process seems to end producing multiple errors like the below Failed to get SDM CI for update (Site_1AAA8919-CE7D-43A2-8BAF-D95647C0D2B9/SUM_e7e45f84-3523-4cd3-ab9e-685437758ebf) from type store, error = 0x80070002 Failed to GetSupersededUpdatesFromDigest for the update
  6. I am having this same issue, with UpdatesDeployment.log reporting error 0x87d00215 - "Item not found" for all updates All of my clients are on version 5.00.8458.1005 Did you have a resolution for this in the end? I am investigating further now...
  7. So, it would appear that this issue was related to the fact that the global admin account of which I was trying to add the subscription needed to be assigned an EMS license.
  8. Anyone? Has anyone seen this before? I have just spoken to "Tech Support" and to be honest not getting anywhere.
  9. I have encountered an issue where we do not appear to be able to specify SCCM as the Mobile Device Management Authority. After attempting to add the Intune subscription via the SCCM console I receive the error message "An unexpected error has occurred" I have confirmed that no MDM authority has indeed already been set, and believe that all of the network infrastructure requirements as per https://docs.microsoft.com/en-us/intune/get-started/network-infrastructure-requirements-for-microsoft-intune have be satisfied. I have can also see that the URL's attempting to be accessed are being permitted by the Firewall and passing through successfully. SCCM version is 1606 with the two hotfixes installed (I haven't installed Update Rollup 1 yet as it was released while I have been on leave for the past week or so)
  10. Many thanks for this, exactly what we are doing and seems to work well
  11. Please see above in bold the full command I have just realised it was incorrect. Have now used this for Surface Pro 3, 4 and Books
  12. Anyone share their thoughts on this? I am with the mind of just keeping the base install driver package only in the system for each device and then create separate Applications for the different versions of the MSI's...
  13. I do not knowingly do this. Also FYI I ran the prerequsities checks prior to attempting the upgrade which passed. I will email you the log file
  14. As per the log file I believe the errors seem to be related to SQL and during my daily checks noted some WSUS errors in the event log id's 6700 and 6703 relating to an "Unspecified SQL error". On running the Disk usage report on the database I noticed that the data files only showing 7.44 % of free space. The data files are also not limited to a specific size. We have limited the log files due to the fact that these were constantly filling up disk space, so was wondering if there was a recommendation to do this for data also?
  15. Yes I did see that post, many thanks. Please see below - if this is not enough info should I just attach the full log file? INFO: Configuring SQL Server CLR assemblies... CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C) INFO: SQL Server CLR assembly ServiceBrokerInterface from file ServiceBrokerInterface.dll already exist in database, skip it. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C) INFO: SQL Server CLR assembly MessageHandlerService from file MessageHandlerService.dll already exist in database, skip it. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C) INFO: SQL Server CLR assembly DcmObjectModel_SQLCLR from file DcmObjectModel_SQLCLR.dll already exist in database, skip it. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C) INFO: SQL Server CLR assembly CryptoUtility from file CryptoUtility.dll already exist in database, skip it. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C) INFO: SQL Server CLR assembly ModelFactory from file ModelFactory.dll already exist in database, skip it. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C) INFO: SQL Server CLR assembly SMSSQLCLR from file smssqlclr.dll already exist in database, skip it. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C) sql object StateSysSqlClr with hash SHA256:D3EC1B62BE7429D29850E4BA4EEFAD9BA7E6B7782ACBB2BED1318EF3AA660AED is not found. It will be created. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C) *** SELECT HashMatch = COUNT(*), ClrExists = (SELECT COUNT(*) FROM sys.assemblies WHERE name = N'StateSysSqlClr') FROM DBSchema WHERE ObjectName=N'StateSysSqlClr' AND ObjectHashAlg=N'SHA256' AND ObjectHash=0xD3EC1B62BE7429D29850E4BA4EEFAD9BA7E6B7782ACBB2BED1318EF3AA660AED AND SiteNumber = dbo.fnGetSiteNumber() CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C) *** [42000][6270][Microsoft] [sql Server]ALTER ASSEMBLY failed because the required method "ParseiOSVPPSyncRow" in type "Microsoft.SystemsManagementServer.SQLCLR.StateSys.VPPMessageParsing" was not found with the same signature in the updated assembly. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C) ERROR: Failed to create assembly StateSysSqlClr. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C) ERROR: Failed to UPDATE CLR assemblies. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C) Failed to update database. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C) Successfully reverted SQL function fnCurrentSiteVersion. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C) Successfully reverted SQL function fnCurrentSiteVersion_INT. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C) Successfully reverted SQL function fnCurrentSiteVersion_INT_TABLE. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C)
  16. I have just attempted to upgrade from 1511 to 1606, after the prerequisite checks passed. The error message I am receiving is "failed to apply update changes 0x87d20b15" however I believe the error "ALTER ASSEMBLY failed because the required method "ParseiOSVPPSyncRow" in type "Microsoft.SystemsManagementServer.SQLCLR.StateSys.VPPMessageParsing" was not found with the same signature in the updated assembly" is more specific to the issue. Has anyone else experienced this, also can anyone assist?
  17. Peter, Also would I be correct in saying that different client OS's may only show up to a certain version of the SCEP client itself?
  18. Many thanks for the advice on this, but in the end I migrated to a new environment where the offline servicing feature seems to work a treat. MS Support even advised to do this if possible. I am currently running version 1511
  19. I was just wondering what everyone's standard practice was when importing the different updated versions of MSI's and Driver packages for all of the Surface Devices? We are currently using Surface Pro 3, 4 and Books within the organisation and was wondering if I should import the separate versions them into SCCM as their own application (in the case of the MSI) or Driver package (self explanatory) with the version number specified for each?. Or should I be removing old versions once they have been tested in production, maybe having 2 for each device available in the system at one time?
  20. pvr02, In case you were interested, I have the command required for this here https://www.windows-noob.com/forums/topic/13839-surface-pro-3-windows-81-msi/ which is now working for all of my Surface Pro 3 devices
  21. Just a quick update on this I have added REBOOT=REALLYSUPPRESS /norestart at the end of the above command, now I am able to effectively suppress the restart from the command line using PSExec emulating running as SYSTEM. So it would appear that the complete command is msiexec /i SurfacePro3_Win8x_160128_3.msi /qn /l*v "%windir%\Logs\SurfaceProDrivers.log" REBOOT=REALLYSUPPRESS /norestart
×
×
  • Create New...