Bumbi85

I checked compmon on the server now as well and i have the same: Checking components ... SMS_COMPONENT_MONITOR 2015-10-24 22:45:26 4276 (0x10B4) Can not get the current execution state for component Windows_Intune_Service since it is not installed or completed installing. SMS_COMPONENT_MONITOR 2015-10-24 22:45:26 4276 (0x10B4) But if i check the Microsoft Intune Connector under site status it's flagged as OK So thats why im wondering if Windows_Intune_Service is the same as the connector... As if i check the SCCM services there is a Windows_intune_Service and it's not running, i have checked 2 sccm servers and that services isnt active on any of them

Any news?

Sigh....

Ok, i am still getting error messages in statesys.log. Is it fixed for you?

Any one heard anythig from MS about a solution?

here is a technet link with people having the same issue: https://social.technet.microsoft.com/Forums/en-US/1177e0f0-0207-4252-a98a-22207181753f/statesysbox-corrupt-files-all-mobile-devices?referrer=http://social.technet.microsoft.com/Forums/en-US/1177e0f0-0207-4252-a98a-22207181753f/statesysbox-corrupt-files-all-mobile-devices?forum=configmanagergeneral

let me know how it goes, i will try and open a case with them to

Im thinking more in the line that the mobile units report via intune app to intune cloud services, which then relays the information to the SCCM:en. So if they made a update to the intune client or cloud service. On our server we have the iOS 9 Extension which we have enabled (you could require at hotfix for this if you enable it as we hade problem with Configuration Items after we enabled that, and we have the Conditional Access Extensions(which we dont use). The reason we dont have Windows Phone is that the customer doesnt use them so we havent enabled enrollment for that type of phone Conditional Access Extension has to do with exchange online (http://blogs.technet.com/b/configmgrteam/archive/2015/03/12/conditional-access-for-exchange-online.aspx) and it only adds 2 new features as the others are already implemented in r2 sp1: Minimum OS compliance rule Maximim OS compliance rule

From what i heard i a new CU will be released soon. I will most likely register a case with Microsoft to get this fixed. My personal opinion is that this isnt a problem with the upgrade to r2 sp1, but rather a problem with the intune service. As the phones all of a sudden are sending messages to the MP with a type that isnt recognised. We installed the server in june with r2 sp1, and in sepember applied CU1. So we have had the server running for a while(didnt add mobile devices until mid october), and the hotfix we installed after that was installed about 1 month ago. So i have a hard time seeing that there was a problem with any update, but more a problem with the Intune service sending a new type that the sccm doesnt know about Correct me if i am wrong in any way

Sadly i have no idea at the moment as i cant find any viable solution other then contacting microsoft and registering a case. They will most likely classify this as a bugg and then we dont have to pay for their time. The active phones we have on the server right now are android phones, and iphones. So it seem to affect all mobile devices. Do you use intune integration as well? We use Intune for mobile devices.

If you open the .smx file in notepad. Or make a copy of it and add xml at the end you can read it more easily in internet explorer. There is a section were the hostname is presented. Go to Microsoft Configuration Manager folder then inboxes\auth\statesys.box\corrupt You will see that it puts the files there. Take the latest message and copy it to another location and add xml then open it in IE or any other browser, otherwise you can open the .smx in notepad directly.

I can report that we have the same errors, it startade November 3rd 02:59, before that no problems what so ever. We have SCCM 2012 R2 SP1 CU1, we installed CU1 September 25 so we have had that installed for some time. And installed hotfix KB3081699 on Oktober 12 to fix a issue with IOS 9 Compliance. So my guess is that your update isnt the problem. If you check the .smx files is it your mobile devices that are sending the file? Or normal computers also?

Any one have any idea how to fix this? There must be someone else that have / had this issue with mandatory assignments for all clients that run during the OS Installation

Well the problem is when you reinstall computers that are already installed and reporting to the SCCM, have advertisment on them that are advertised to all computers the Customer have. Then this problem will occur. There wasnt a problem with cm07 as it didnt have this behavior. But CM12 installs programs during OSD

Hi. I was wondering if it's possible to stop mandatory advertisments during OSD in SCCM 2012. We can se in the logs on the server that it is running alot of advertisments outside of the OSD, and we Think that this cause trouble with a program outside the TS is "locking" the computer from installing the programs in the TS. So we are wondering if it's possible to block advertisments outside the TS from running during OSD? Best Regards Bumbi85

Hi. Have a question regarding driver packages in SCCM 2012. We have added driver packages for different computer modells, we can se that it access the packages but no drivers get installed. Then we read that you have to import the drivers as driver packages dont work as before. Is that correct? I think it seems strange that you have to import all drivers to get it to work, as in CM07 driver packages are enough. Do anyone have experience regarding driver packages in CM12? Thanks in advance

Fixed patching with an installed client in that collection, but when i try a build and capture on the client the problem persists. Continueing troubleshooting...

I seem to have found the issue, was looking in the WUAhandler.log on an installed client and found this: Group policy settings were overwritten by a higher authority (Domain Controller) to: Server http://XXXXXX:8530 and Policy ENABLED WUAHandler 2012-08-20 15:33:36 2728 (0x0AA8) Failed to Add Update Source for WUAgent of type (2) and id ({7C736AAF-FA9F-44F0-8E63-0E5D7A6AF2A3}). Error = 0x87d00692. WUAHandler 2012-08-20 15:33:36 2728 (0x0AA8) I remebered adding a policy to push the sccm klient to the computer using windows update, even thou it's the same server it bugged when trying to push patches using SCCM klient. After i removed the policy the patching started on the client. Will try build and capture next.

Saw this that refered to the update: FALSE, HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\installswupdate.cpp,1256) InstallSWUpdate 2012-08-13 13:37:35 2848 (0x0B20) Timedout waiting for updates refresh complete notification InstallSWUpdate 2012-08-13 13:37:35 2848 (0x0B20) WaitForRefreshUpdatesComplete(spInstall), HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\installswupdate.cpp,1314) InstallSWUpdate 2012-08-13 13:37:35 2848 (0x0B20) RefreshUpdates(), HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\installswupdate.cpp,906) InstallSWUpdate 2012-08-13 13:37:35 2848 (0x0B20) InstallUpdates(pInstallUpdate, tType, sJobID, sActiveRequestHandle), HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\main.cpp,248) InstallSWUpdate 2012-08-13 13:37:35 2848 (0x0B20) Setting TSEnv variable SMSTSInstallUpdateJobGUID= InstallSWUpdate 2012-08-13 13:37:35 2848 (0x0B20) Process(pInstallUpdate, tType), HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\main.cpp,304) InstallSWUpdate 2012-08-13 13:37:35 2848 (0x0B20) Process completed with exit code 2147943860 TSManager 2012-08-13 13:37:35 2904 (0x0B58) !--------------------------------------------------------------------------------------------! TSManager 2012-08-13 13:37:35 2904 (0x0B58) Failed to run the action: Install Updates. This operation returned because the timeout period expired. (Error: 800705B4; Source: Windows) TSManager 2012-08-13 13:37:35 2904 (0x0B58) MP server http://SCCM2012.labb.local. Ports 80,443. CRL=false. TSManager 2012-08-13 13:37:35 2904 (0x0B58)

Yeah i did that, i uppdated the DP's now. And so far command line seems to work now. I will try and get a hold of the smsts.log

Hi, ive followd the RTM Guide along with the guide for Build and Capture. The VMWare client boots fine with pxe, and OS installation works fine and it captures the media without any problem. But it wont install the patches. I have downloaded and deployed all avaible windows 7 patches except a few and deployed it towards my Build&Capture collection and added the following in the "setup configmgr" step: smsmp=sccm2012.labb.local I have also check the "Enabled Command line support" option on the bootimg, but it dont want to appear when i hit F8. Any ideas? //Bumbi85

Tried with a 32-bit os now, and it works fine. Have you guys had any problem with build and capture of a 64-bit Win7 in a vmware enviroment? Forgot to mention that my test enviroment is on a vmware server. Got a tips from about a possible solution: http://scug.be/blogs/sccm/archive/2010/02/03/sccm-deploying-windows-7-on-a-vmware-esx-environment-howto.aspx

Hi. I have a problem with Build and Capture of Windows 7. It goes threw the steps ok, until it comes to Prepare OS. Then i get the following error: "sysprep.exe is not present on this machine" The SCCM enviroment is uppgraded to SP2 recently. the x64 boot image is taken from the OS CD. And i have added the CD to the "Operating System Install Packages" OS: Win 7 x64 Enterprise I have check the install.wim file, and sysprep folder + content is present. Log: sysprep.txt Any ideas? Haven't tried with a 32 bit-os, but the filestructure in windows catalog should be the same as the 64-bit os.