Assigned Tasks Remain Pending and Computer Status is Incorrect

New Boundary Support — Thu, 29 Dec 2011 12:16:00 GMT

Abstract:

The information in this article applies to Prism Deploy, all versions.

Problem Summary: There is a scenario where the Prism client is not launched correctly when a user logs in. Because of this, the managed computer’s status in the Prism Deploy console appears as unattended even when a user is logged in. In addition, any of the computer’s assigned tasks that are not configured to run in unattended mode will stay pending and not run when a user is logged in.

Here are the conditions that cause the problem to occur:

· A Prism script is created that contains one or more /InstallPackage commands.

· The Prism package installed from the script is configured with the advanced (legacy) setting “unattended\all users.”

Contributing to the Prism Software Identification Database (PSID)

Applies to Prism Suite 7 and above, Asset Manager Component

Summary
This KB article describes how to enhance the Prism Software Identification Database (PSID) by sending information about unrecognized applications to New Boundary Technologies for possible inclusion in future releases of the PSID.

The Prism Software Identification Database

The PSID is used by Prism Asset Manager to identify applications (License Units) that are installed on the computers you manage with Prism Suite. The PSID contains over 12,000 identified applications, with more being added every month. If you know of applications and/or versions or applications that Prism Asset Manager does not yet recognize, you can easily contribute information to be added to a future update of the PSID by using the Emscanner utility. Note: Only commercially available applicatio

PwrSmart 3.x System Requirements

New Boundary Support — Wed, 13 Apr 2011 13:32:00 GMT

Abstract:

PwrSmart® 3.x System Requirements and Supported Platforms

Note: You must be an administrator-equivalent to install any PwrSmart component.

The information in this article applies to version 10 of Prism Deploy. It has been fixed in version 11.0.0.43

Using Prism Deploy in an environment with UAC enabled

Version 10 of Prism Deploy does not correctly handle an environment that has Windows User Account Control (UAC) enabled. This issue has been fixed in version 11.0.0.43 of Prism Deploy and you will not need any special setu

Deploying Office 2010

New Boundary Support — Fri, 18 Feb 2011 02:49:00 GMT

Abstract:

When deploying Office 2010 it is recommended to use a command line approach rather than packaging the application. There are two methods available for this approach, using the Office Customization Tool or creating a Config.xml file and using it as an answer file to help install Office 2010.

In Office 2010, the Office customization tool is only available to those who have the enterprise level edition of the product. To learn about the command lines you can use to launch the OCT, go to this site:

http://technet2.microsoft.com/Office/en-us/library/0f489f42-4c01-41d1-8b52-3a2a2da8f7311033.mspx?mfr=true

In brief, the Microsoft OCT creates an .msp file that configures the Office 2010 installation for your environment. Here are some of the tasks handled by the OCT: upgrading previous versions of Office, making general customizations, connecting to a Microsoft Exchange Server.

Once you have created the .msp file with the OCT, you can create a Prism Command Task to distribute that to your managed machines. Here is an example of the syntax to use:

\\server\office2010share\setup.exe /adminfile

MEMBER_OF Configuration Group Operator

New Boundary Support — Mon, 07 Feb 2011 10:37:00 GMT

Abstract:

The information in this article applies to:

Prism Suite
Policy Commander

The information in this article applies to Prism Suite versions 8 through 10 that will be upgraded to version 11.

Upgrading to Prism Suite 11

Upgrading the Console and Server

If you plan to upgrade your existing installation of Prism Suite on the same system where Prism is currently installed, follow the steps below. Version 11 supports upgrading from version 8 through 10. If you running pre-8 version of Prism and would like to upgrade to version 11, please contact New Boundary Technical Support (support@newboundary.com) for assista

SxS Assemby Error When Installing a Prism Package

New Boundary Support — Mon, 17 Jan 2011 08:54:00 GMT
Abstract:
When installing certain applications with a Prism package, an error similar to the one below may pop up near the end of the package installation:

Unable to install SXS assemblies. The manifest file contains one or more syntax errors. (X86_Microsoft.VC.90.ATL-ifceb3b9al18c36-9.0.21022.8X-ww-312cf0e9.manifest)

After the error is displayed, the Prism package is rolled back.

This error happens because 1) the side by side assemblies required by the application are not already installed on the target machine, and 2) the side by side assemblies required by the application cannot be installed by the Prism package, even though they are included in the package. The reason is that Windows doesn’t support the standard API used by the Prism client to install certain C++ side by side assemblies.

Here are some of the applications that may produce the error:
• Open Office 3
• Tortoise SVN 1.5.0
• Nokia PC Suite
• Design Review 2010 from AutoDesk
• CES educational software
• Adobe Reader 9.1

The workaround is to download the required Microsoft Visual C++ redistributable setup and deploy it as a Command Task in the Prism Console prior to installing the package that depends on it. The downloaded redistributable will install the required side by side assemblies, after which the Prism package installation will succeed. Use the syntax shown below in your Command Task to install the redistributable, and configure the properties of the Command Task to run as an admin-level user.

\\server\share\vcredist_x86.exe /q

Here’s how to find the correct V

Backing Up Prism SQL Databases

New Boundary Support — Thu, 13 Jan 2011 03:58:00 GMT
Abstract:
The information in this article applies to Prism Suite versions 6 and later, all versions of Policy Commander, all versions of PwrSmart.
Backing up Prism and Policy Commander SQL Databases
It is extremely important to regularly backup the databases associated with Prism Deploy and Prism Suite. This will allow you to recover from a hardware or software failure. Database backups should be done on a daily basis, and the resulting .bak files should be included in your nightly file backup.
The first section of this article shows how to back up SQL Server 2000 using SQL Enterprise Manager. The second section shows the command-line steps for backing up MSDE (SQL Desktop Engine).
For a much more complete discussion of database backups, please refer to Microsoft SQL “Books Online” in the Related External Links section at the end of this article.
The information in this article applies to:
PwrSmart Service
PwrSmart 3.0 and newer
Prism Suite 7.0.3 and newer

SUMMARY

This Article d

Updating Your Asset Management Database with the Latest Prism Software Identification Database (PSID)

New Boundary Support — Mon, 03 Jan 2011 10:52:00 GMT
Abstract:
Updating Your Asset Management Database with the Latest Prism Software Identification Database (PSID)

The information in this article applies to Prism Suite 7, Asset Management.

Obtain the PSID update installation from New Boundary Technologies, Inc. and launch it on your Prism Server machine. Customers who have purchased Asset Management licenses will receive notification of database updates via email. NOTE: The updates are available ONLY to customers who have purchased Asset Management licenses.
The update executable must be run on the machine that is running the Prism Server, not necessarily the same machine that is running MSDE or SQL Server.

Microsoft SQL Database Basics

New Boundary Support — Mon, 03 Jan 2011 10:36:00 GMT
Abstract:
Preserving Customizations to the Rules.INI File
When installing Prism Suite over an existing installation of Prism, the installation logic presumes that the existing Rules.INI file may have been customized by the administrator and that the customizations must be preserved. Therefore, the installation merges the new Rules.INI file changes into the existing customized Rules.INI. In order to use the new merged Rules.INI when upgrading your Clients, follow the prep steps below.

Background: Prism uses a Prism Package to install the Client, both when doing a Direct Install and when generating a Subscription executable. The Package “template” (ClientInstallTemp.exe) is part of the installation. When you initiate a Direct Install or when you generate a subscription file, the template is used as a starting point for creating a Package with your Channel’s unique information.

There are two prep steps that must be completed to ensure that your customizations are retained and that the Clients receive an updated, customized Rules.INI

“You have insufficient permissions on the target computer”

New Boundary Support — Mon, 03 Jan 2011 10:29:00 GMT
Abstract:
This error can occur during Direct Installation if the target computer does not have the Remote Registry Service enabled. To fix, start the Remote Registry Service on the target computer.
Also test to make sure your account has necsssary permissions to use the Remote Registry Service. This can be done by opening the Registry Editor (regedit.exe) on the Prism Server machine. From the Registry menu choose Connect Network Registry... and type in the name of the target computer. Make sure you can browse HKLM on the target machine. To fix, use an account that has permissions to HKLM on the target machine.

Securing Prism

New Boundary Support — Mon, 03 Jan 2011 10:28:00 GMT
Abstract:
Prism Deploy and Prism Pack ship with Group Policy template files that when enabled will prevent the unauthorized installation of Prism Packages (.pwc), Self-Installing Files (.exe) and the unauthorized running of Prism scripts (.pts) and subscription files (.pwsubs and .exe).

Steps to Secure Prism Installations
The following items are well known network security ”best practices”:
Do not give users local or domain administrative rights. Only those responsible for managing the network and who understand the implications of their actions should be given local or domain administrator rights.
Do not give users access to the registry.
Keep all systems (servers and workstations) patched with the latest security patches, service packs, hotfixes, etc.
Customers often want to include a subscription to a Prism Channel on new computers before they are given to employees. Their goal is to get the Prism Deploy Client installed and subscribed to their Channel so that the computers will appear in the Channel as soon as they are put on the network. Often this process involves "imaging" a system with an approved configuration (using a product such as Ghost), then using Microsoft's Sysprep to give the imaged systems unique security identifiers, computer names, domain membership, etc. Administrators want the new computers to appear in the Channel with their permanently-assigned name.
Here are the recommended steps for accomplishing this.
1. Add the approved "reference image" system to the desired Channel by doing a direct install over the network by browing either the Active Directory tree or Microsoft Windows Network tree within the Prism Console. Alternately, manually run a subscription file on the reference system. When you create the subscription file, you can choose whether the system should appear in the Channel using its NetBios name or its Active Directory name.
2. Once the Prism De

Moving the Prism Deploy Channel Server to a Different Machine

New Boundary Support — Mon, 03 Jan 2011 10:26:00 GMT
Abstract:
The information in this article applies to the following products:
• Prism Deploy and Prism Suite versions 6 and

"Cannot copy files to target computer" during Direct Install

New Boundary Support — Mon, 03 Jan 2011 10:10:00 GMT
Abstract:
Symptoms
You get the error "Cannot copy file to target computer" while attempting a Direct Install.
Cause
This error occurs if the Console (using the rights of the user running the Console) cannot access the C$ administrative share on the target machine.
Resolutions
1. Launch the Console as a domain administrator.
2. Enable the C$ administrative share for the C drive. In order to do so, it may be necessary to turn off Simple file sharing. This can be done by launching Windows Explorer on the target machine, going to the Tools menu, and choosing Folder Options... Select the View tab and in the Advanced settings portion, scroll down and uncheck "Use simple file sharing"

Search files by file type and remove them

New Boundary Support — Wed, 29 Dec 2010 10:52:00 GMT
Abstract:
The information in this article applies to Prism Deploy v.10 and newer.

This article describes how to create a Prism script task that scans a computer for all files of a specific type and removes them. This can be useful when you need to scan your network for offensive or unwanted files such as torrents, mp3s, etc.
The computer will search for all files of a certain file type in a location that you specify and then create a package to remove them. After creating the package, it will run that package to remove those specific files. In my step by step instructions, I will be using the example of removing all .mp3 files from the C drive.

The information in the article applies to Prism Deploy Packager 10.5.0.x. The Prism Deploy Packager is included in Prism Deploy, Prism Suite and Policy Commander.
_________________________________________________________________________________________________________________________________________________________________
Problem: Incorrect syntax of some of the entries in the rules.ini file could cause the Package Editor to capture more information than is necessary when building a package.

Resolution: Make corrections to the rules.ini file on the system where the Prism Editor is installed (wherever you create packages). This should be done every time you install the Prism Package Editor on to a new machine for package building purposes.

In the [Ignore Folders] section of Rules.ini locate the following four incorrect statements:

Key=%WINDIR%System32\CONFIG
Key=%WINDIR%System32\NtmsData
Key=%WINDIR%System32\WBEM\Logs
Key=%WINDIR%System32\CATROOT2
These four

Files Without an Extension are Sometimes Missed by Prism Package Editor

New Boundary Support — Mon, 04 Oct 2010 12:02:00 GMT
Abstract:
The information in the article applies to Prism Deploy Packager 10.5.0.x. The Prism Deploy Packager is included in Prism Deploy, Prism Suite and Policy Commander.

Problem: Files that do not have an extension (for example, hosts file, some Java app files) are not captured by the Prism Editor when taking a picture or finding changes.

Resolution: Make a correction in the rules.ini file on the system where the Prism Editor is installed (wherever you create packages). A section of the Ignored Files section is incorrectly duplicated, and one of the entries is missing a period. The RulesINI_Correction.rtf file in the Article Attachments section below contains both the incorrect syntax and the corrected syntax. The corrections are not posted in this article because of formatting and scrolling issues that may occur in some browsers.

You must close and reopen the Editor after making the change to rules.ini in order for the change to be recognized. This issue will be corrected in the next release of Prism Suite, Prism Deploy and Prism Packager.

Upgrade to Prism Patch Manager 7.0 - Switch to new hardware

New Boundary Support — Tue, 06 Jul 2010 12:23:00 GMT
Abstract:
Upgrade to Prism Patch Manager 7.0 - Switch to new hardware

This scenario is preferred if:
· You want to use new hardware for the Prism Patch Manager server and/or for the SQL server and instance.
The information in this article applies to:
Prism Suite
SUMMARY
The Externals Tools menu options are separated into two categories, the general Tools category and the specific Single Computer Apps category. The Tools category is where you would add general applications for launching from the menu bar within the Prism Console. The Single Computer Apps category is where you would add computer specific commands for launching from a right-click menu within the Prism Console.
METHOD
Launch the Prism Console and choose Tools | Edit Tools Menu

Prism Patch Manager 7.0 SP1 Remote SQL Configuration Changes that may affect other applications using the Remote SQL Server

New Boundary Support — Tue, 15 Jun 2010 09:39:00 GMT
Abstract:
Prism Patch Manager 7.0 and higher Remote SQL Configuration Changes that may affect other applications using the Remote SQL Server
Description: This article explains Remote SQL Server configuration changes made during Prism Patch Manager 7.0 and higher Installa

Performing an In Place Upgrade from Prism Patch Manager 6.4 to 7.0

New Boundary Support — Thu, 10 Jun 2010 10:08:00 GMT
Abstract:
Performing an In Place Upgrade of Prism Patch Manager Server from 6.4 SP2a to 7.0 SP1
This document will cover performing an “in place” upgrade of Prism Patch Manager 6.4 SP2a (build 6.4.6.1573) to Prism Patch Manager 7.0 SP1. Note: The SP1 version is New Boundary Technologies’ first release of Prism Patch Manager 7.0.
Important: New Boundary Technologies strongly recommends that you identify and use a dedicated server for Prism Patch Manager 7.0 SP1, and that the server not run any other mission-critical applications or websites.
Recommended Minimum Hardware Requirements: Your Prism Patch Manager 7.0 SP1 server must meet or exceed the specified hardware requirements, the requirements indicated are the recommended minimum needed to run Prism Patch Manager 7.0 SP1. Depending on your environment you should consider using hardware that meets your organizational needs.
2+ GHz multi-core processor
2 GB Ram
72 GB of available disk space (4 GB for application, 68 GB for storage cache)
Installing Prerequisite Items: The installati

Moving the Virtual Storage directory in Prism Patch Manager 6.3 - 6.4

New Boundary Support — Tue, 27 Apr 2010 05:27:00 GMT
Abstract:
Moving the Virtual Storage Directory in Prism Patch Manager Server v6.3 and v6.4

Description
The information in this article applies to Numara Deploy, all versions.

Companies that are using Numara Deploy can easily migrate to Prism Deploy. Prism Deploy provides the same user interface and is 100% compatible with Numara Deploy. This means that all information contained in the database and all packages created by Numara Deploy work without modification in Prism Deploy. New Boundary Technologies provides top-notch technical support and Prism Deploy fully supports Windows 7 and 64-bit operating systems. The product also contains significant enhancements not available in Numara Deploy. See the Related External Links section below for a link to the Version History page for Prism Deploy.
<

Unattended, Recurring Package Tasks Can Cause Excessive Growth in Size of Prism Channel Database

New Boundary Support — Mon, 29 Mar 2010 10:44:00 GMT
Abstract:
The information in this article applies to Prism Client versions 10.0.0.x and 10.3.0.x.
Problem:
You may notice that your Prism channel database is growing rapidly. Also, you may see a large number of repeating unexpected "success" events in the Deployment Log report related to certain Package tasks. In addition, the Unapply folder where Package rollback files (.pwr) are stored may have a very large number of rollback files per package.

New Boundary Technologies Support Knowledge Base

How to Configure Full SQL Server to Send Email Alerts Using SQL Database Mail

Assigned Tasks Remain Pending and Computer Status is Incorrect

How to use Remote Wake™ in PwrSmart Service

Enabling Wake on LAN

Installing PPM 7.0 SP1

Updating Prism Patch Manager 7.0 SP1 client

Updating Prism Patch Manager 7.0 SP1 to latest version

Upgrading from PPM 6.4 to 7.0 SP1

Prism Patch Manager Server 7.0 Components and Configuration

Prism Patch Manager 7.0 COMPONENTS

Upgrading to Prism Suite 12

Upgrading from MSDE (SQL2000) to SQL Express 2005 SP4 (minimum supported version) to support Prism Deploy 12

Prism Patch Manager 7.0 System Requirements

Adding Right-Click "Browse" functionality to Items on the Assets Tab

Obtaining the Latest Manufacturer Information for Scanned Assets

Prism Suite System Requirements and Supported Platforms

Moving the Prism Deploy Server and Channel Database from one Machine to Another Machine

PwrSmart 3.x System Requirements

Deploying Office 2010

MEMBER_OF Configuration Group Operator

SxS Assemby Error When Installing a Prism Package

Backing Up Prism SQL Databases

Updating Your Asset Management Database with the Latest Prism Software Identification Database (PSID)

Microsoft SQL Database Basics

“You have insufficient permissions on the target computer”

Securing Prism

Moving the Prism Deploy Channel Server to a Different Machine

"Cannot copy files to target computer" during Direct Install

Search files by file type and remove them

Files Without an Extension are Sometimes Missed by Prism Package Editor

Upgrade to Prism Patch Manager 7.0 - Switch to new hardware

Prism Patch Manager 7.0 SP1 Remote SQL Configuration Changes that may affect other applications using the Remote SQL Server

Performing an In Place Upgrade from Prism Patch Manager 6.4 to 7.0

Moving the Virtual Storage directory in Prism Patch Manager 6.3 - 6.4

Unattended, Recurring Package Tasks Can Cause Excessive Growth in Size of Prism Channel Database