Saturday, March 10, 2012 4:54 PM
I have InTune installed on about 5 computers at a local business that I support. All have been working fine up until this past week. Only one has been giving me an error when attempting to install Windows Intune Monitoring Agent (x64) (Error Code: 0x80070643). Up until this past week I was getting no error messages from any of the clients. The client in question is running Windows 7 Pro x64.
I have looked up the error code and tried all the methods on: http://support.microsoft.com/kb/976982 (both the FixIt and .Net 4 repair)
I have also tried other suggestions that I've found when searching up the error code on Google and Bing. No luck.
When I tried to manually remove all the InTune software using either the automatic scripts or manually uninstalling each as specified on http://onlinehelp.microsoft.com/en-au/windowsintune/hh127721.aspx only the InTune Monitoring Agent is left behind.
If I try to uninstall the Windows InTune Monitoring Agent, I eventually receive the error message: A network error occurred while attempting to read from the file: C:\Windows\Installer\MonitoringSetup.msi
I click OK and the uninstaller exits. I've ran chkdsk on the C: drive and there was no file system corruption. I cannot find the MonitoringSetup.msi file on another Windows 7 system to try to place it in the location it is looking for.
I have tried to uninstall all the other InTune software and reinstall it, but no luck with this either.
What can I do to resolve this issue?
Sunday, March 11, 2012 7:14 AMModerator
Because troubleshooting this issue usually requires reviewing logs I recommend opening a support case.
The Support Engineer will gather logs and troubleshoot the failure with you.
You can open a support case here:
- Marked As Answer by Jon LynnMicrosoft Employee, Moderator Friday, March 16, 2012 3:48 AM
Monday, April 16, 2012 5:02 PMI've got the same issue - tried lots of things to fix this and have not come up with a solution :/
Monday, March 25, 2013 3:42 AM
I have exactly the same issue, was a fix ever found for this?