The below post explains the end to end process of software updates management in SCCM 2012 Pre-requisites: 1. WSUS Server (WSUS 3.0 SP2 ) should be installed on the SCCM site server or if you want to install WSUS on another server, it is important that you install WSUS administration console as the SCCM Server uses API. This link explains the step by step procedure to install WSUS 3.0 SP2 2. Install SUP-Software Update Point on the SCCM Server . 3. Reporting Services Point: Install reporting services point role as described in this link . 4. Client agent: The software update client agent should be enabled(will be enabled by default) and the settings have to specified as per the requirement. On SCCM console, go to Administration>Site Configuration>Client settings>Right click on Default client settings> Click on Properties. If required, we can create custom client settings and then enable client settings for that settings. Unde
HTTP 400 Bad Requests in SCCM Reporting
You can configure reporting in SCCM with the help of the below TechNet article.
After the configuration is done, I ensured that the reporting was working fine on the
system where the Reporting Point role was installed.
But I faced issues while accessing the reporting URL from other machines.
I got HTTP 400 bad requests from all the other machines.
I came across a quick solution for this ,hope it will be useful to you too..
There are two ways to resolve this issue :
1. Use the IP address of the site server rather than the server name.
2. Add registry DWord values to HKLM\System\CurrentControlSet\Services\HTTP\Parameterson the Site server where the Reporting Point role is installed.
The Dword values are
MaxFieldLength 65534
MaxRequestBytes 500000
Comments
Post a Comment