Large Files, Sharepoint, and Windows 2008

I ran across this problem and thought I’d share.  After much troubleshooting, I found that Sharepoint 3.0 on Windows 2008 is limited to 28MB file uploads – this includes multiple file uploads that, combined, equate to a total of 28MB.

There’s a fix or workaround for it, but you have to modify web.config file in the Sharepoint virtual directory.

To work around this problem, follow these steps:

  1. Use Notepad to open the Web application Web.config file. By default, this file is in the following folder:

    Microsoft Windows SharePoint Services 3.0
    C:\Inetpub\Wwwroot\Wss\VirtualDirectories\ VirtualDirectoryFolder

  2. Navigate all the way down to the bottom of the web.config file, and right before the </configuration> tag, add the following code:
<system.webServer>
<security>
 
<requestFiltering>
<requestLimits maxAllowedContentLength="52428800"/>
</requestFiltering>
</security>
</system.webServer>

 

3. Save the file and upload larger files.

 

NOTE:  you can modify the maxAllowedContentLength value to the limit of the file(s) size(s) you want to be allowable.

The Configuration Manager Support Team Blog : Renaming the Configuration Manager 2007 database

 

You may find that at some point you need to change the name of the SCCM 2007 database and the steps to do so are below.  I worked on a case just like this a few days back and during that time I got the opportunity to confirm that this procedure works and is supported in the lab.

The Configuration Manager Support Team Blog : Renaming the Configuration Manager 2007 database

What’s New in the Configuration Manager Documentation Library for October 2009?

 

The following information lists the topics that contain significant changes since the August 2009 update.

Configuration Manager 2007 SP1 Supported Configurations

– Updated to include Windows Server 2008 R2 and Windows 7.

Supported Operating Systems and Hard Disk Configurations for Operating System Deployment

– Updated with information about the operating systems that are not supported and those which can be deployed only by first capturing a Windows installation image (.wim) file using an image capture task sequence.

Supported Mobile Devices

– Updated to remove information about supported mobile device client operating systems so that it is now exclusively in supported configuration topics (Configuration Manager 2007 Supported Configurations). This means that customers have a consistent place to find supported version information and it reduces the risk of inconsistent information between topics.

About Heartbeat Discovery

– Updated to remove the incorrect information "Although you can configure Heartbeat Discovery to update client DDRs as frequently as you want, if you configure it to run less than once every 25 hours (the default client refresh cycle) the updated DDR will be reported no less than once every 25 hours". This restriction applied to an earlier version of the product and does not apply to Configuration Manager.

About the Site Repair Wizard and How to Back Up a Secondary Site

– Updated with the information that the Site Repair Wizard should not be used to recover a secondary site. The Product Group has confirmed that the recovery procedure doesn't work for secondary sites and will not be supported. If you need to recover a secondary site, reinstall it and secondary site configuration from the primary site will be replicated to it automatically when installation is complete. Because restoring a secondary site is not supported with the product, there is no point in backing up a secondary site by using the Backup Secondary Site Server maintenance task. To help avoid confusion, we have removed the procedural information in How to Back Up a Secondary Site.

System Center Configuration Manager Team Blog : Announcement: Configuration Manager Documentation Library Update for October 2009

Monitoring Windows 7 with Operations Manager

 

The Windows Client Monitoring Management Pack is built to detects, diagnose, and resolve hardware and software problems pertaining to Client 2000, XP, and Vista operating systems. Information and analysis on the issues that the system detected are collected by the MPs through an agent on the client machine, and sent to OpsMgr where this data is converted into health state, alerts (if need be) and processed for business critical and aggregate reports. The MP gives a clear picture of catastrophic failures in your mission critical machines, trend-based alerts of significant changes to computer groups, in-depth views of health of individual machines, and reports that provide a landscape view of the health of all monitored clients.

Windows Client 2000/XP/Vista/Windows 7 Operating System Management Pack for Operations Manager 2007 – myITforum.com

Live Maps V4.1 for SCOM R2 Released

 

We are proud to announce the release of Live Maps 4.1 for Operations Manager R2. This update contains, besides some fixes and performance improvements, a number of new features that have been added based on customer feedback. Some of the new features are highlighted in this article, a complete overview can be found in the release notes.

Live Maps V4.1 for SCOM R2 Released

Introducing the F5 PRO-Enabled Management Pack for Microsoft Virtual Machine Manager 2008

 

I am proud to announce we have just released our latest addition to the F5 Management Pack, the F5 PRO-Enabled Management Pack for Microsoft Virtual Machine Manager 2008 (MS VMM). If you haven’t heard MS VMM is a member of the Microsoft System Center family that enables a host of different technologies and scenarios including Hyper-V management, VMWare instance integration, optimization of virtualized resources (PRO), and monitoring integration with System Center Operations Manager.

Introducing the F5 PRO-Enabled Management Pack for Microsoft Virtual Machine Manager 2008

Xtreme Deployment: Litetouch Folder Permissions

 

I was looking the other day at the permissions of my MDT deployment share, wondering if I had the optimal settings for security and flexibility (typically security and flexibility to *not* go together… ). So I did some digging, and came up with a solution that works well for my Litetouch deployment, and thought I’d share.

Xtreme Deployment