Microsoft KB Archive/229617

= CD: Cannot Deploy Nested CAB =

Article ID: 229617

Article Last Modified on 10/11/2002

-

APPLIES TO


 * Microsoft Site Server 3.0 Standard Edition

-



This article was previously published under Q229617



SYMPTOMS
Content Deployment (CD) can not deploy a CAB file, if the CAB file is nested. This means that the CAB file contains another CAB file within it.



WORKAROUND
It is possible to deploy un-nested CAB files serially using a CD script. If there are more than two CAB files that need to be deployed, the deployment process can be chained together so one CAB file will be deployed after another. This can be accomplished by executing a script at the end of the first deployment.


 * 1) Modify the CAB file so that it doesn't contain a CAB within it.


 * 1) Use the AfterSendScript to chain the two CAB files to be deployed.

You can only chain two CAB files since the script can only be executed once.

For additional information about running a Content Deployment script, please consult Site Server online documentation.



MORE INFORMATION
A component deployment disseminates compressed application files across a network where the files can be uncompressed and installed automatically on remote servers. Component deployment is one of Content Deployment's more powerful features. It enables you to replicate active content, including Java and COM applets, to all the Microsoft(r) Windows NT(r) servers at your site.

The earlier paragraph is extracted from Site Server online documentation.

Keywords: kbprb kbpending KB229617

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.