Today I installed WSUS role on Windows 2012 R2 Server in order to install Configuration Manager Software Update Point. After the WSUS has been successfully installed there was an issue with the WSUS service. The service wasn't running. By starting the service manually an error 192 0xc1 poped up. Also in event viewer there could be "Event ID 7000 : not a valid Win32 application" errors found. The cause of the problem was, as discribed here, a file named "program" on the system drive (c:\program). The solution was simply to delete/rename this file.
0 Comments
There is a new branchcache bug found by 2 Pint Software company. Changing settings of the branchcache enabled DP or even adding a new content to it will reset the BranchCache Server Secret what will delete the Hasch Cache on the DP.
For the known ADK 1703 issue there is now a hotfix from Microsoft. More infromation can be found here.
There has been up to now a workaround for this issue. Any time when distributing content of my software packages to one of my remote DPs the error 0x800706BA is generated. Also the status of the DP in the SCCM admin-console is set to error. The error 0x800706BA itself means "The RPC-Server is not available"
After Side-by-Side migration of an SCCM 2012 R2 SP1 (Standalone Primary Site Server) to a new SCCM CB 1610 (Standalone Primary Site Server) creating a task sequence didn't work any more. Any time when I tried to create a media the "Create Task Sequence Media" wizard ended with an error message (0x80070490). All Content requiered for the TS had been already distributed to the DP.
The error Messages recorded in the CreateTSMedia.log were: PROBLEM: Taks Sequence that has been working doesn't work any more. The task sequence hangs when installing updates. In the log files there are no error messages. In WUAHadler.log the Software update scan cycle has been initiated and completed successfully.
SOLUTION: Check the UpdatesDeployment.log file and find out the GUID of the latest Update. If you want to troubleshoot an PXE SCCM issue and want to understand how it works, you should read the Microsoft's "Troubleshooting PXE boot issues in Configuration Manager 2012" Gude. The Guide is available at: https://support.microsoft.com/en-us/help/10082/troubleshooting-pxe-boot-issues-in-configuration-manager-2012
Since 19.04.2016 there is a new tool in Beta Version from Microsoft for troubleshooting SCCM hybrid environments (SCCM with Intune). The Tools checks for several issues such as:
- is SMS Executive Service running - checks AAD synchronization - checks for known Status Messages The tool can be downloaded from here: http://aka.ms/SCCMHD The official announcement and further Information can be found here: https://blogs.technet.microsoft.com/configmgrteam/2016/04/19/announcement-system-center-configuration-manager-hybrid-diagnostics-tool-public-beta/ I few days ago I was asked to fix an Samsung Galaxy Note 10.1 tablet that has been infected with a malware/virus. I tried first to reset the tablet to factory Default. Unfortunately that didn't work. After several successful resets this wasn't possible anymore, because the tablet's touchpad stopped working a few seconds after I tried to configure it after the reset. And this would happen any time when the tablet was reseted. In order to resolve the issue I had to reinstall the Firmware. This was done by following These steps:
1. Download the Firmware file (e.g. from www.sammobile.com) 2. Download Odin v3.10.7 Tool on your PC 3. Start Odin Tool 4. Reboot the Tablet in "Download Mode" (press Power + Volume Down Buttons) 5. Connect the tablet via USB to your PC 6. Select AP Option in Odin and brows for the Firmware file 7. Make sure the "Repartition" Option is NOT ticked 8. Click the Start button and wait a few minutes When the message "Added!!" showed up I closed Odin and the tablet was agin up and running and malware free. Last week I noticed that my Configuration managerClients had not been reporting their Hardware inventory. By checking the inventoryagent.log on some of the Clients, I could see that this was not a Client related issue. Therefore I checked the IIS log file of the MP. There I could see many BITS related Errors - bits_error 0x800070005. Something was wrong with the "...CCM\Incoming" Folder on the Management Point.
|
Author
Write something about yourself. No need to be fancy, just an overview. Archives
November 2022
Categories
All
|