I am worried about space used by resources put into MCMS and then deleted particularly about attachments. When you put some attachments into a posting, and then delete the attachments (or the whole posting), the URLs of the attachments are still valid.
When are the resources used by attachments (either on disk or in the DB) freed up?
Answer
MCMS Background processing deletes unused resources. This process is configurable in the SCA.
[Back to Top]
Topic: How to create a Posting in the root of a Web site
Is it possible to create postings in the root of a Web site? Currently I'm using an ASPX page in the root of my website and do a redirect to http://servername/Channels.
Answer
Yes this is possible by using the "map channel names to host header names" feature. For details check out this article:
326783 - HOWTO: Enable the Map Channel Names to Host Header Names Feature
Note: this feature is not available in CMS 2002 Standard Edition
[Back to Top]
Topic: Identifying MCMS patch level
Is there a way to verify the patch level of a MCMS server? This should include checking of service packs and the most updated security hotfixes.
Answer
This check is now included in the Microsoft Baseline Security Analyzer v1.2.
If you would like to do a manualy quick check you could check the registry to determine which patches have been applied. In the registry check the following keys:
"HKLM\Software\NCompass\Resolution Content Server\VersionInfo" "Patches"
Example:
(for MCMS 2001)
MCMS 2001 + SP1: Patches = MCMS 2001 SP1
MCMS 2001 + SP1+SRP1: Patches = 2001 SP1+SRP1
MCMS 2001 + SP1+SRP2: Patches = MCMS 2001 SP1+SRP2
MCMS 2001 + SP1+SRP1+SRP2: Patches = MCMS 2001 SP1+SRP1+SRP2
(for MCMS 2002)
MCMS 2002 + SP1: Patches = SP1
MCMS 2002 + SP1a: Patches = SP1a
[Back to Top]
Topic: Mapping two different host-header names to the same channel
How can I map two different host-header names (e.g. www.mysite.com and mysite.com) to the same channel?
Answer
This cannot be achieved out of the box. But here are two possible workarounds for this problem:
- Create a custom error page that examines the domain and redirects the user to the correct page with the correct domain. This will change the URL for the user. The error page can be dynamic (i.e. only requested when the wrong domain used), and can be edited and saved without difficulty.
- Add an ISAPI filter or HTTP Module to the site that will preprocess the requested URL (e.g. changing www.mysite.com to mysite.com). This can happen transparent to the user, the down side is it executes every time and should not be a dynamic list otherwise overall performance is affected. The list would be static and need to be recompiled as new entries are added.
A ready-to-use ISAPI filter that can do this can be found here: http://www.isapirewrite.com/.
Below is an example for how to configure the httpd.ini file for this ISAPI filter.
[ISAPI_Rewrite]
# Canonicalize Host-Headers
RewriteCond Host: www\.mysite\.com
RewriteHeader Host: .* mysite\.com
In order to get this method working you need to ensure that the following hotfix is installed to ensure that MCMS does not return absolute URLs including the host name:
824597 - Absolute URL Is Returned When You Use the Channel.Url Method of the PAPI and Host Headers Are Enabled
[Back to Top]
Topic: Script error in Revision History when using HTTP compression in IIS 6
In Internet Information Server (IIS) 6.0 with HTTP Compression turned on, the Revision History dialog throws some Javascript errors when comparing differences between 2 pages. (With HTTP compression turned off it works as expected without errors)
Is there a fix for this?
Answer
There is an hotfix to resolve this:
867755 - Content in Web pages does not appear as expected, or you receive script error messages, after you turn on dynamic HTTP compression for Web sites that use ISAPI filters in Internet Information Services 6.0
[Back to Top]
The information contained in this document represents the current view of
Microsoft Corporation on the issues discussed as of the date of publication.
Because Microsoft must respond to changing market conditions, it should not be
interpreted to be a commitment on the part of Microsoft, and Microsoft cannot
guarantee the accuracy of any information presented after the date of
publication.
This White Paper is for informational purposes only. MICROSOFT MAKES NO
WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS
DOCUMENT.
Complying with all applicable copyright laws is the responsibility of the user.
Without limiting the rights under copyright, no part of this document may be
reproduced, stored in or introduced into a retrieval system, or transmitted in
any form or by any means (electronic, mechanical, photocopying, recording, or
otherwise), or for any purpose, without the express written permission of
Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or
other intellectual property rights covering subject matter in this document.
Except as expressly provided in any written license agreement from Microsoft,
the furnishing of this document does not give you any license to these patents,
trademarks, copyrights, or other intellectual property.
© 2004 Microsoft Corporation. All rights reserved.
Microsoft, ActiveX, Visual Studio, Windows, and Windows Server are either
registered trademarks or trademarks of Microsoft Corporation in the United
States and/or other countries.
The names of actual companies and products mentioned herein may be the
trademarks of their respective owners.
| © 2004 Microsoft Corporation. All rights
reserved. |
