Getting "Package is invalid" in the package list of the Package Server for many Deployment related packages (DeployAnywhere, Bootwiz, Images).

Article:TECH122379  |  Created: 2010-03-19  |  Updated: 2013-05-22  |  Article URL http://www.symantec.com/docs/TECH122379
Article Type
Technical Solution


Issue



All Package Servers show an invalid package called "Drivers" after installing Deployment Solution 7.1.  This is the DeployAnywhere drivers package.

The same applies to all of the DS packages, like the BootWiz driver packages.  It will also happen to all the images that are captured in DS.

 


Environment



Symantec Management Platform 7.0 to 7.1 all SP levels

Deployment Solution 7.0 to 7.1 all SP levels


Cause



The packages mentioned are built to be replicated to the "Deployment" share on the package server which doesn't exist on any package server that does not have the DS Site components on them.  The DS Site components only get sent to Site Servers that have package and Task on them.  Because some companies do not install Task on all their Package servers, this error can occur.


Solution



 

This is working as designed.  Deployment Solution recommends that each Package Server also have Task and the DS Site components on them for modular access to images on all package and task servers.  It is not a bug. 

NOTE: Symantec recognizes that the above expectation is not realistic for some customers and has redesigned the product to allow for Package servers to not be Task servers in the next major release.

Best Solution:

Ignore the errors.  They will not cause problems, other than confusion in the console about whether the package server is in sync or not.  A Package Server that is not also a Task Server will not, at this time, ever service any Deployment jobs, so not having the packages on those servers is not a problem.

Additionally, IF per chance you manually installed PXE services on said Package Server that does not have Task, this is unsupported and not recommended.  At this point, you'll have to go to the Unsupported workaround below and best of luck in making things work.  The target of the DS Site Components policy should never be modified.

Next Best Solution:

Per the design of DS, to resolve these errors, ensure that all your Package servers are also Task Servers.  This will allow the DS site policy to target the package servers currently getting these errors, create the share point on the package servers, and elliminate these errors.

Possible Manual Solution (very difficult):

 

To manually resolve this issue, you can modify each package to only replicate to those servers that have the Deployment share on them.  This is how you change the Drivers package.  All 5 of the packages in the same folder will also need to be modified the same way:

  • Open the Symantec Management Platform console;
  • Navigate to: Settings > Deployment and Migration > Drivers > Drivers
  • Click on the Package Servers tab
  • Modify the Assign package to and set it to Package Server individually
  • Select the Package Servers that also have the DS Site components on them
    • by rule, this is generally any Task / Package combination on a Site Server
    • The DS Site Components install PXE but you don't have to use PXE on them, so even if you're not using PXE, the servers can accept the packages.
  • Click Save Changes.

 

 

 

NOTE:  All of the images that you capture also will suffer this issue and create these errors.  They can be modified the same way if desired.

Unsupported Workaround:

You can also create a Deployment share on the other package servers if you simply want to get rid of the errors.  However, we recommend against this because a lot of relatively useless information will be replicated to that share, including images!  Unless you stop the images from being replicated, creating these shares on all your package servers could cause serious disk space issues.

IF you want to script your tasks to go to package servers instead of using our default methods, you could use a manually created share point, but again, it's not supported.



Legacy ID



52050


Article URL http://www.symantec.com/docs/TECH122379


Terms of use for this information are found in Legal Notices