No matter how i've tried to install WinPE 4.0 as a pre-boot operating system it continually fails with 'Missing Operating System Files'.  I've tried using the adksetup.exe and i've also tried using the option for the pre-installed ADK and both give the same error.   Previously with 2.1, Altiris had their own exe's to install this.  Using the Windows adksetup seems to be buggy.  Anyone have a solution?

Thanks!

I currently run Altiris 6.8 Build 378 SP2 on a Windows Server 2003 OS - Everything works currently from pushing of jobs, to remoting into PCs ect... However I can't image for some reason, when I image a PC everything seems to work as per the norm from start to finish, Name selection, Job Selection then the 0-100% bar appears and images fine. However when the image hits 100% and is booting to production 1 of 2 things occur. It'll either boot just fine but all the existing components on the PC are still there as if it didn't in fact image despite it going through the process completely or the PC won't boot, and I'll be prompted to uninstall any new software/hardware I've put on the machine.

I feel I've searched around a bit and tried a few things however nothing I try seems to resolve this issue, any assistance would be grateful!

Thanks in advance,

Alex

Greetings,

So I followed the instructions to create and upload a NetBoot Image to Deployment 7.5. Now I keep getting Kernel Panics whenever I try NetBooting. It doesn't matter if I send "Boot to Automation" task or holding the N key while starting. The Panic also happens on the same machine it was used to create the NetBoot Image. Anyone else is having that issue? Or Am I missing something in the process of crating the NetBoot Image?

Many thanks in advance.

I was trying to create an offline package for SMP CMS 7.1 SP2 and I was able to create the package using the Symantect Installation Manager 7.5. When I click the exe file after the package is created, I am getting the following error: "Symantec_Install_Package_XXXXXXX is not a valid Win 32 application." 

I didnot get any errors while the package was created. I see the file on my desktop with a size of 6.28 GB.

I am using  Win 7 64 bit machine for this whole process. Is that the issue?

Can We set Altiris agent uninstallation password?

Some of the clients are removing altiris agents from their system.

Hi!

We`re having a problem with deployment. After booting with PXE command line appears with following line:

After that command line is minimalizing and nothing happens:

Initial Deployment is set for unknow and managed computers.

This problem also occurs then we are trying to capture image.

I have a software package to deploy that is an InstallAnwhere package. I can get it to install / uninstall silently but it always reboots at the end so clearly isn't much good for deployment to users. I know it doesn't need a reboot for the software to work. I can't find a switch that prevents it rebooting, so;

- Does anyone know if there is a switch that prevents reboot for InstallAnywhere packages? I have an answer file generated too but can't find the parameter to stop it.

- Is there any way to tell the SWD policy to *prevent* a reboot?

Hi,

I've a little question.

In the Altiris v6 version, it was possible to send a Wake on LAN directly on the computer with a right click / power management / wake on lan.

Today, with the v7, I have a Remote Management / manage power state and redirection option, but it visibly uses RTSM and profiles (WMI, AMT, ASH, ...)

Does this WOL feature disappear in the right click menu on a computer ? It was very useful.

The only way is to create a Power Control task, and Schedule Task in the right click menu on the computer targeted ?

Is it possible to create a custom menu/action (via the right click on the computer) that can directly launch a power control task on a computer ?

This is for a customer that migrate from v6 and uses WOL.

Thanks for your help.

Hi all,

I got surprised with this info so I would like to share and check if i've missed something:

I've found in DS 7.5 documentation (http://www.symantec.com/docs/DOC5678) page 29:

I need to export my Asset Management data from a 7.1 database into a new 7.5 database.  When I run the NSUpgradewizard.exe file on my 7.1 SMP it only produces a file at is 13MB in size.  When I look at the exporter for the Asset Management Solution it only lists License Certificate Exporter.  Does this tool work on exporting against a 7.1 database?  I used this on my NS 6 database and got a 19GB file which is what I was expecting from my 7.1 database.

Hi All, 

I am getting ready to implement patching to our workstations in the enterprise.  What is your current Reboot Notification configuration that works for best for your environment? we are currently using the out of the box Windows update. 

Please share your configuration or strategy.

Thanks

Enjoy a consistent endpoint management experience from console to iPad.  The ITMS Admin app is a mobile extension of the Symantec Management Console.  It lets you monitor client computers, check Patch, Inventory and Software data.  The app supports Symantec IT Management Suite 7.5 or higher.

The English version is now available for download from AppStore in the US, UK, SIngapore, India, Australia, Canada, and New Zealand.

For more information regarding description, installation, usage, and more, click on the following link:

http://www.symantec.com/business/support/index?pag...

When I have a pc that is not in the console and it boots to PXE I then pick an initial deployment job.  It will do all the stuff up until I tell it to boot to production, but then once its in windows 7 the agent never gets the rest of the job.  the job doesn't fail in the console but when I try and get the status it tell me I do not have permission anymore.  I was able to view the status all the way up until it booted into prod and the production agent started to communicate vs the PXE agent.  

It's almost as if it thinks it is a different pc and thus doesn't continue.  in the console I can only find one instance of the computer and strange enough it doesn't show the job in the history at all.

If I have the machine in windows and tell it to boot to PXE then assign the same exact job it works ok

Any thoughts, anyone seen this?

I've attached the error I get in the console when trying to bring up properties

Hello everyone,

Someone know how could add a template between incident resolved and incident closed?

Any idea to solve this requeriments?

I have installed ServiceDesk 7.1 SP2 with SMP integrated.

Thank you in advance!

Hello Symantec,

can you please check the bulletins in Title and add there missing parameters in their command lines for PMImport 7.0? We discovered that /quiet /norestart is missing there and it fails during the installation - no interactive session...

Thanks

Dear Symantec,

I have been creating Windows Service Workflows in SMP 7.1 and the installation process was to generate an installer, then run the installer and then run the install.bat in the \bin directory which essentially includes:

InstallUtil.exe -i MonitoringAgentService.exe
sc config "Workflow Windows Service" depend= "SWFSVR" obj= "NT AUTHORITY\NETWORK SERVICE" password= ""
net start "Workflow Windows Service"

When removing, it was quite simple as the installer placed an entry in the Add & Remove Programs Control Panel, so all I needed to do was to run the Uninstaller in there and all was well.

Now that WF 7.5 is fully released, there is no installer for Windows Service Workflows and you just generate the directory and just run the install.bat in the \bin directory (which seems not to have changed). All is good... ...until you want to uninstall the workflow. There is no uninstaller and the "InstallUtil.exe" does not  include an overt argument in the command line. I have trying -r and -d, etc, but to no avail.

I do not really know what the InstallUtil.exe does, so I am loath to just run a:

sc delete "Workflow Windows Service"

and then delete the folder, as I do not know what else the InstallUtil.exe does!

So, can we please have a corresponding uninstaller or a parameter for the InstallUtil.exe?

Kindest regards,

QuietLeni

I recently had to reformat my machine and I lost all the merge modules.  I Installed Wise Installation Studio SP2 (help about shows version 7.4.0.214).  I then found http://www.symantec.com/business/support/index?page=content&id=TECH38334 and downloaded/ran the WPSModules.exe that the articule references.  No issues during any of this.

When I compile a new project from scratch for testing, no issues (all this does is install a DLL in a folder).

When I compile a project that existed and worked fine prior to my reformatting, I get a message towards the end that says, "The runtime files required for this installation must be downloaded from the Internet for this installation to be compiled.  Do you want to download the runtime installation files?"  I click Yes, pick either Wise Web Site or Other Vendors' Web Sites, (doesn't matter which) and then I get the error, "An error occured while downloading information files necessary to continue the process".  I assume because this is a legacy product that's mentioned in the above articule, this feature will never work again.

There are no merge modules listed under Feature Details>Merge Modules.

How can I tell which merge module it's missing?

Thanks,

Bond

Symantec Management Platform 7.5 Red Hat Patching

1.      Configuration

2.      Initial Setup

3.      Policy Creation

4.      Agent Commands for Linux

Configuration

Assumptions:  SMP is configured properly, resides on domain, and sites are setup.

1.      Create an administrator account with Red Hat.  www.redhat.com

2.      In the Symantec Management Console select Home, Patch Management, Red Hat Linux. Under Settings select Remediation.

3.      Go to the Red Hat Network tab and type in the credentials from step 1.

4.      Use your company standards for the Software Update Options, Policy and PackageSettings and Programs tabs.

5.      Under Settings select Installation and Notification. (This is a default policy. If you have Development, QA, Test and Production Linux systems you may want to create a policy for each.)  Set the policy per your company standards.

6.      Under Settings select MetaData Import Task.

Note: Base channel for the first import must be selected for all required major updates. (You don’t have to select all child channels, also dependency resolving will not work without a base channel.)

Save changes and Select Import channels.

7.      Setting a schedule to import MetaData from Red Hat.  Under Task Status select New Schedule and create the schedule.

Initial Setup

1.      Log into Red Hat website to ensure you see the SMP reporting to Red Hat.

Select Customer Portal, Subscriptions, RHN Classic, Registered Systems.

For each Channel you selected in step 6 there will be a separate entry.

2.     Select each system. Than select Alter Channel Subscriptions.

3.    Ensure all channels are checked

Policy Creation

1.       In the Symantec Management Console select Home, Patch Management, Red Hat Linux. Under Software Updates select Errata.

2.      Select the Bulletin and right click.  Select Distribute Packages. 

The bulletin will be applied to the default filter discussed in Configuration step 5.   Select the appropriate filter and select Next.  Select the advertisements and select Distribute software updates. 

Agent Commands for Linux

Solution   http://www.symantec.com/business/support/index?page=content&id=TECH29115

# ./aex-bootstrap -h
aex-bootstrap - Usage:

        aex-bootstrap [options]

   Version 2.0.

This program will get all files at a URL/NS Package into the specified directory. It can also be used to download a file from a URL (see -onefile option). When started with no NS/URL argument, configuration must be provided in an XML file present in the same directory, or (in the case of a automatic reschedule) at one of the standard locations.

Generic options:

·         --help, -h -   Display this usage information and exit immediately.

·         -v -               Display Agent's full version and name.

·         --version -    Display version of the application.

Specific options:

·         <NS|URL> - arg 1 = name of Notification Server, URL of a package or file. If the Notification Server is configured to work with the non-default port, it is desirable to provide the full URL info. Example: https://www.altiris.com:3476 -test - output version

·          

·         -dir <dir> - specify Agent installation directory

·         -speedlimit <N> - limit download to n KB/sec

·         -onefile - URL is for a single file, download to current directory, no other action.

# ./aex-configure -h
Altiris Agent for UNIX and Linux Configuration utility.

Usage:

·         aex-configure [options]

·         aex-configure <command> [command-options]

Options:

·         --help, -h -   Display this usage information and exit immediately.

·         -v -              Display Agent's full version and name.

·         --version -   Display version of the application.

Commands:

·         -clean         Remove aex-configure created files prior to uninstall.

·         -configure  Automatically configure/upgrade an installation from an XML config file.

·         -iconfigure  Interactively configure/reconfigure an installation ignoring any XML file.

·         help           Display help on the specified command

Run 'aex-configure help <command>' to learn more information on how to use certain commands.

# aex-diagnostics -h
Agent diagnostics tool - Usage:

        aex-diagnostics [options]

Collect diagnostics information from the agent and its plug-ins

Generic options:

·         --help, -h -   Display this usage information and exit immediately.

·         -v -              Display Agent's full version and name.

·         --version -   Display version of the application.

Specific options:

·         -com -           Diagnose the default set of plugins

·         -com <ids> - Diagnose the specified components

·         -log -             Dump the contents of the log file

#./aex-env

No parameters

#./aex-filesurveyor -h
FileSurveyor Utility

  Usage: ./aex-filesurveyor [options]

  Options:
       --help, -h, -? : Display this usage information and exit immediately.
       -v : Display full version and name information.
       --version : Display version of the FileSurveyor Utility.
       -c <config file> : A user-specified cfg file name
       -f : Set file mode
       -m : Enables scanning of the mounted partitions (by default disabled) - NOTE: This option has not been implemented.
       -p : A user-specified product file
       -x <dir1>...<dirN>] : Specify a list of directories to be excluded during the scan
 

# aex-helper -h
Usage:

·         aex-helper [options]

·         aex-helper <command> [command-options]

Command line utility for working with Altiris Agent for UNIX and Linux.

Options:

·         --help, -h -   Display this usage information and exit immediately.

·         -v -               Display Agent's full version and name.

·         --version -    Display version of the application.

Commands:

·         adddep      Register dependencies between solutions.

·         agent         Perform various tasks with the UNIX Agent.

·         changerc   Change properties of registered RC services.

·         check        Check whether the Altiris Agent for UNIX and Linux is running.

·         clean         Clean items from the XML registry.

·         help          Display help on the specified command.

·         info          Query agent for various information.

·         installrc     Install and register RC scripts.

·         link           Create wrapper scripts and links for libraries and executables.

·         list            List objects in the Agent's registry.

·         query       Query agent for various information.

·         rc             Start, stop and list registered RC services.

·         register     Add an object to the Agent's registry.

·         uninstall     Uninstall solutions.

·         uninstallrc  Uninstall RC scripts.

·         unlink        Remove wrapper scripts and links for libraries and executables.

·         unregister  Remove object from the Agent's registry.

·         upgrade    Upgrade Notification Server Agent Plugin.

Run 'aex-helper help <command>' to learn more information on how to use certain commands.

# aex-mkmanifest -h
Manifest File utility - Usage:

        aex-mkmanifest [options]

Create an SWD manifest file for a directory.

Generic options:

·         --help, -h - Display this usage information and exit immediately.

·         -v - Display Agent's full version and name.

·         --version - Display version of the applications.

Specific options:

·         -o <file> - Write output to <file> (defaults to ./aex-manifest.xml)

·         -s <dir> - Base directory for scanning (defaults to the current dir)

# aex-pluginmanager -h

Altiris Agent for UNIX and Linux Core

Usage:

·        aex-pluginmanager [options]

Manages plug-ins, which do all the job.

Generic options:

·        --help, -h - Display this usage information and exit immediately.

·        -v - Display Agent's full version and name.

·        --version - Display version of the application.

Specific options:

·        -F - Work in the foreground mode

·        -D - Work in the background mode (default)

·        -nm - Do not start the monitor

·        -nc - Do not check if the agent is already running

# aex-refreshpolicies -h

Refresh policies from the Notification Server.

Usage:

·         aex-refreshpolicies

·         aex-refreshpolicies [options]

Options:

·         --help, -h -  Display this usage information and exit immediately.

·         -v -             Display full version and name information about Agent.

·         --version -   Display full version of the Agent.

# aex-sendbasicinv -h

Send the basic inventory to Notification Server.

Usage:

·         aex-sendbasicinv

·         aex-sendbasicinv [options]

Options:

·         --help, -h -   Display this usage information and exit immediately.

·         -v -               Display full version and name information about Agent.

·         --version -    Display full version of the Agent.

# aex-swdapm -h
Software Delivery Advertised Package Manager - Usage:

·         aex-swdapm [options]

Manual execution of Notification Server tasks and installation of packages.

Generic options:

·         --help, -h -    Display this usage information and exit immediately.

·         -v -               Display Agent's full version and name.

·         --version -    Display version of the application.

Specific options:

·         -np - Do not use paging mode, list all tasks at once.

# ./aex-uninstall -h

aex-uninstall": usage: aex-uninstall" [-f]
        -f force remove, do not ask to continue

# ./rcscript -h
rcscript: usage: rcscript: [start|stop|restart|status]

Whenever I try to start my pcAnywhere I get  this

:

I have tried numerous time to uninstall and reinstall the software. Ive tried running as administrator. Ive tried replacing DLL files and nothing seems to work. 

My main concern is that it may have corrupted some hardware in my machine and I will experience some issues down the road, not to mention the fact that I cant use this software. If anyone has any advice or has experienced this issue before please advise.

Thanks, 

-cachemem0

I'm trying to setup my patches to use two different maintenance windows so my clinics take patches at night and the rest take patches any time. I have been reading some of the documentation and I have my test filter assigned to my new maintenance window but the patches still show as set to run at the main time.

Can anyone help me out.

Thanks

Jen