Phil Schwan has a new post up talking about how to raise the ASP buffer limit to show “large” reports.
As an FYI, another solution to this issue is to use SQL Reporting Services as the 10k row limit and the ASP buffer issue don’t apply when using SRS.
If you have more than a couple thousand clients in your SCCM 2007 site and have ever tried to run a large report (like “Hardware 01A – Summary of computers in a specific collection” against the All Systems collection, for example), you’ve probably encountered this HTTP 500 error:
This problem and resolution are pretty well documented for Windows Server 2003 and IIS6, but in this particular case we’re running Windows Server 2008 SP2, so we’re using IIS7. The underlying cause is the same (default ASP Buffering Limit is set too low to handle the size of the report) and the fix is the same (increase the limit), but the steps to fix are just a little different for IIS7
Aussie legend Cameron McBride and good friend Tony Sanchez from Citrix sent a heads up to me recently on some performance related hotfixes. They are specific to proc and SP1. Nevertheless they are definitely worth applying for the best performance.
Issue 1: Performance is not as awesome as it could be on Westmere or Sandybridge chipsets
- You have a Windows Server 2008 R2-based computer that has a large amount of physical memory and that has Intel Westmere or Sandy Bridge processors.
For example, you have a computer that has Intel Xeon 5600 series processors and that has 48 gigabytes (GB) physical memory.
- You install the Hyper-V role on the computer.
In this scenario, the performance of the computer may decrease.
For example, the following performance issues may be encountered:
- The CPU usage is high and the server responds slowly when you copy large files on the computer. For example, you copy a 10-GB file.
- The disk I/O performance of the virtual machines (VMs) is slow.
- Windows takes a long time to start.
Issue 2: Networking Performance is not as awesome as it could be under load and is lost in certain scenarios
You install the Hyper-V role on a computer that is running Windows Server 2008 R2 Service Pack 1 (SP1).
- You run a virtual machine on the computer.
- You use a network adapter on the virtual machine to access a network.
- You establish many concurrent network connections. Or, there is heavy outgoing network traffic.
In this scenario, the network connection on the virtual machine may be lost. Additionally, the network adapter may be disabled.
- You must restart the virtual machine to recover from this issue.
- This issue can also occur on versions of Windows Server 2008 R2 that do not have SP1 installed. To resolve the issue, apply the hotfix that is described in one of the following Microsoft Knowledge Base articles:
974909 (http://support.microsoft.com/kb/974909/ ) The network connection of a running Hyper-V virtual machine is lost under heavy outgoing network traffic on a Windows Server 2008 R2-based computer
2264080 (http://support.microsoft.com/kb/2264080/ ) An update rollup package for the Hyper-V role in Windows Server 2008 R2: August 24, 2010
So theres hotfixes for both of these. Thanks Cam and Tony for the heads up on this!
The RemoteFX documentation team has been hard at work creating topics that you can use to evaluate and deploy Microsoft RemoteFX within your environment. Following is a list of all the RemoteFX documents that were published to coincide with the Windows Server 2008 R2 with Service Pack 1 release.
The following documents were created for Microsoft RemoteFX:
The following existing Remote Desktop Services documents were updated to include Microsoft RemoteFX:
For information about the RemoteFX WMI provider documentation, see MSDN.
If you are interested in seeing more Remote Desktop Services documentation, see the Remote Desktop Services TechCenter.
Another colleague sent a link for this awhile back and I’ve been meaning to blog about it for quite some time.
We are pleased to announce the latest version of Core Configurator built and designed for Windows Server 2008 R2 x64 Core edition!
It is completely open source so it can be amended and change to fit your requirements, this version has been a year in the making and has been written in powershell with a reference to Winforms so that a GUI format is displayed.
The primary focus of this project is to try and get feedback and contributions back from the community to make this a tool the best/ free tool everyone will want in there toolkit, so if you have some code or features that you might want included then please leave a comment and we will get in touch.
Core Configuration tasks include:
- Product Licensing
- Networking Features
- DCPromo Tool
- ISCSI Settings
- Server Roles and Features
- User and Group Permissions
- Share Creation and Deletion
- Dynamic Firewall settings
- Display | Screensaver Settings
- Add & Remove Drivers
- Proxy settings
- Windows Updates (Including WSUS)
- Multipath I/O
- Hyper-V including virtual machine thumbnails
- JoinDomain and Computer rename
- Add/remove programs
- Complete logging of all commands executed
I recently had an issue with my hyper-v lab where my MP quit working. It’s a test lab so I’m making changes all the time. So no big surprise there. However, uninstalling the MP and even uninstalling/installing IIS didn’t resolve the issue. I kept getting a failed attempt when running the MP Troubleshooter and when trying to browse to the web page to verify the MP. Again, thanks to a colleague for pointing me in the right direction.
You can use these links to test your MP:
What ended up resolving the issue was running the following command and then restarting IIS.
cscript.exe %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0
Be sure to add the scripting tools in order for this command to work. I think it’s a good idea to add both the IIS 7 and the IIS 6 tools for your lab environment.
Error “The WebDAV server extension is either not installed or not configured properly” in Configuration Manager 2007
In addition the the following article:
It looks like if you see this in your logs:
401 WebDav Authorization OSD MDT GetDirectoryListing
Then the webdav_schema.xml is also the culprit. Use the fix below to resolve it.
The SMS Site Component Manager fails to install the SMS_MP_CONTROL_MANAGER component on a Windows Server 2008 based computer. The error is as follows:
The WebDAV server extension is either not installed or not configured properly.
Solution: Make sure WebDAV is installed and enabled. Make sure there is an authoring rule that allow “All users” read access to “All content”. Make sure the WebDAV settings “Allow anonymous property queries” and “Allow property queries with infinite depth” are set to “true” and “Allow Custom Properties” is set to false.
If you go to the IIS management console, connect to the local server and open the “WebDAV Authoring Rules” option you will find everything enabled but it still doesn’t seem to recognize it.
This can occur if the settings for the WebDAV Authoring Rules become out of sync with the WebDAV_schema.xml file.
We need to go the location of the configuration file of Webdav which isC:\Windows\System32\inetsrv\config\schema\WebDAV_schema.xml. After opening this file you may notice that the settings in this file were different from the settings that were configured in the IIS Manager. The settings were configured as:
<attribute name=”allowAnonymousPropfind” type=”bool” defaultValue=”false” />
<attribute name=”allowInfinitePropfindDepth” type=”bool” defaultValue=”false” />
<attribute name=”allowCustomProperties” type=”bool” defaultValue=”true” />
However they should be:
<attribute name=”allowAnonymousPropfind” type=”bool” defaultValue=”true” />
<attribute name=”allowInfinitePropfindDepth” type=”bool” defaultValue=”true” />
<attribute name=”allowCustomProperties” type=”bool” defaultValue=”false” />
After correcting these settings (remember we have to take ownership of the file to be able to change it) and restarting the World Wide Web Publishing Service and the SMS_SITE_COMPONENT_MANAGER the Management Point should install correctly. You can check if the installation is successful in the log fileMPSetup.log in your SCCM\Logs directory. If successful the log should have entries similar to this:
<04-01-2010 13:15:58> ======== Completed Installion of Pre Reqs for Role SMSMP ========
<04-01-2010 13:15:58> Installing the SMSMP
<04-01-2010 13:15:58> Passed OS version check.
<04-01-2010 13:15:58> IIS Service is installed.
<04-01-2010 13:15:58> checking WebDAV configuraitons
<04-01-2010 13:15:58> WebDAV is configured
<04-01-2010 13:15:58> No versions of SMSMP are installed. Installing new SMSMP.
<04-01-2010 13:15:58> Enabling MSI logging. mp.msi will log to E:\SCCM\logs\mpMSI.log
<04-01-2010 13:15:58> Installing E:\SCCM\bin\i386\mp.msi CCMINSTALLDIR=”E:\SMS_CCM” CCMSERVERDATAROOT=”E:\SCCM” USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<04-01-2010 13:16:32> mp.msi exited with return code: 0
<04-01-2010 13:16:32> Verifying CCM_CLIENT virtual directory.
<04-01-2010 13:16:32> Website path is IIS://LocalHost/W3SVC/1.
<04-01-2010 13:16:32> Connecting to IIS.
<04-01-2010 13:16:32> CCM_CLIENT is currently E:\SCCM\Client.
<04-01-2010 13:16:32> Installation was successful.
Note: As you do any time you modify an XML file, please make a backup of WebDAV_schema.xml before making changes to it.
As an alternative resolution you can also run the following commands:
C:\Windows\system32\inetsrv\appcmd.exe set config “Default Web Site/” /section:system.webServer/webdav/authoring /enabled:true /commit:apphost
C:\Windows\system32\inetsrv\appcmd.exe set config “Default Web Site/” /section:system.webServer/webdav/authoringRules /allowNonMimeMapFiles:true /commit:apphost
C:\Windows\system32\inetsrv\appcmd.exe set config “Default Web Site/” /section:system.webServer/webdav/authoringRules /+[users=’*’,path=’*’,access=’Read’] /commit:apphost
C:\Windows\system32\inetsrv\appcmd.exe set config “Default Web Site/” /section:system.webServer/webdav/authoring /fileSystem.allowHiddenFiles:true /properties.allowAnonymousPropfind:true /properties.allowInfinitePropfindDepth:true /properties.allowCustomProperties:false /commit:apphost
Then just restart the World Wide Web Publishing Service and the SMS_SITE_COMPONENT_MANAGER and the Management Point should install correctly.
Was working on setting up a new Central Site for a client today and noticed what appears to be a bug in the pre-req checker. This was building a new site server on Server 2008 R2 with SQL 2008 R2 from ConfigMgr SP2 media. I wanted to run the pre-req checker before launching the install and received the following error talking about the SQL Sysadmin rights.
I double-checked everything and was still sure I had everything correct. On a whim, I decided to launch the ConfigMgr install to see if I still received the same error. Lo and behold the error no longer surfaced on the box, without any changes having been made.
Hope this helps someone else from pulling their hair out!
Steve Rachui has another nice post on Direct Access over on his MSDN blog.
“Do you have internet based clients that you want to manage? Does the idea of switching to SCCM native mode to manage those client make you nervous? Do you have Windows 2008 R2 servers in your environment and are the internet systems you want to manage running Windows 7 (Enterprise or Ultimate) or Windows Server 2008 R2? If you said yes to all of these questions then you might just be interested in taking a look at Direct Access (DA).”