Prism Suite 8 Client Logging Changes (Where is Pictaker.log?)

New Boundary Support — Wed, 24 Sep 2008 08:35:00 GMT

Abstract:

The Prism Client version 8 logging has changed due to support for Fast User Switching available on Vista and where applicable on Windows XP systems. The log file is now being written in XML format and is located in a fixed location that cannot be changed.

Windows Vista:

C:\ProgramData\Prism Deploy\PrismXL\ClientLog.XML

Installing Prism Suite to a remote SQL Server 2005 or SQL Server 2008

New Boundary Support — Tue, 23 Sep 2008 10:51:00 GMT

Abstract:

The information in this article applies to:

Prism Suite 7.0.3 and newer

SUMMARY

If you wish to use a remote SQL Server 2005 or SQL Server 2008 as the database server for your Prism Channel (in other words, SQL 2005 or SQL 2008 is not installed on the same system as the Prism Server), then you first need to install the Microsoft’s SQL Server Backward Compatibility Components to the server where you are installing Prism Suite.&nb

Office Deployment Tips

New Boundary Support — Mon, 22 Sep 2008 11:29:00 GMT

Abstract:

When you are planning to deploy Office 2007, here are some questions to answer before you try to roll it out:

1. Are you upgrading from a previous version of Office?

2. Are you configuring Outlook to work with Exchange Server?

3. Are you delivering a vanilla installation of Office to a machine with no previous version installed, and you don’t need to configure Outlook for Microsoft Exchange Server?

If you answered “yes” to questions 1 or 2, New Boundary Support staff recommends that you do not create a Prism Package for Office 2007. Instead, use the Office Customization Tool (OCT

Prism Suite 9 System Requirements and Supported Platforms

New Boundary Support — Wed, 17 Sep 2008 04:44:00 GMT

Abstract:

Prism Suite 9 System Requirements and Supported Platforms

Note: You must be an administrator-equivalent user to install any Prism Suite component.

Upgrading to Prism Suite 9

Upgrading the Console and Server

If you plan to upgrade your existing installation of Prism Suite on the same system where it is currently installed, follow the steps below.

1. IMPORTANT: a) Check the System Requirements for Version 9 in the Related Articles section below. b) Make a backup copy of your existing Prism SQL database files before upgrading. Refer to t

Prism Patch Manager Deployment Failure Codes (190A, 190C, 109D, 190E

New Boundary Support — Mon, 15 Sep 2008 07:26:00 GMT

Abstract:

Prism Patch Manager Deployment Failure Codes (190A, 190C, 190D, 190E)

Patch Deployments fail with Error 190D

New Boundary Support — Mon, 15 Sep 2008 07:23:00 GMT

Abstract:

Patch Deployments fail with 190D

Prism Suite 8.x Platform Requirements

New Boundary Server³:

(includes the New Boundary Channel Manager and New Boundary Channel Migration Tool applications)

OS Windows 2000, Windows XP, Windows Server 2003

Prism Suite 7.x Platform Requirements

New Boundary Server³:

(includes the New Boundary Channel Manager and New Boundary Channel Migration Tool applications)

OS Windows 2000, Windows XP, Windows Server 2003

Creating a Subscription File to Install the Prism Client

New Boundary Support — Fri, 08 Aug 2008 04:27:00 GMT

Abstract:

Creating a Subscription File to Install the Prism Client

For computers that are not on the corporate network or those that do not use Microsoft networking, use the Console to create a subscription file you can run on these computers. The subscription file installs the Client and sets the Client to subscribe to the Channel. If the default auto-populate and auto-license options are set for the Channel, the computers are automatically assigned Prism licenses when they contact the Channel Server.

Description: Service Pack 1 (SP1) for Prism Patch Manager Server 6.4 contains latest enhancements and fixes that increases server performance and manageability.

Applies To: Prism Patch Manager 6.4

Patch Name: Prism Patch Manager Server 6.4 Service Pack 1 (6.4.0.1378)

Impact: Critical

What's New

The information in this article applies to:

• Prism Deploy

• Prism Pack

Summary:

Creating Prism Packages for Windows 2000 and XP Service Packs and operating system updates is not recommended because of Windows File Protection (WFP).

When a service pack is installed, the installation program written by Microsoft examines the operating system for software components (applications, drivers, DLLs, etc.) that need to be updated. It then updates only those components that are already installed on the system. The updated components are captured in a Package. If you apply the resulting P

Prism Patch Manager 6.4 Documentation

New Boundary Support — Thu, 17 Jul 2008 12:03:00 GMT
Abstract:
Go to the Related External Links section below to see all New Boundary Technologies product documentation in PDF format. Scroll down to the Prism Patch Manager 6.4 section to find links to the User Guide, Server Installation Guide and Agent Installation Guide.

Prism Patch Manager 6.4 - Service Pack 1 for Update Agent

New Boundary Support — Fri, 27 Jun 2008 11:33:00 GMT
Abstract:
Description: Service Pack 1 (SP1) for the Update Agent for Windows contains the latest enhancements and defects fixes that stabilizes the Agent to increase performance and reliability.
Patch Details
Patch Name: PatchLink Update Agent 6.4 SP1 (Windows)
Impact: Critical

Description

This article discusses additional subscription servers to be added to support Prism Patch Manager’s subscription service and provides IP addresses for the new servers in the event that your organization uses outbound filtering rules to restrict outbound Internet traffic. Please review this information thoroughly and advise the appropriate technical resources at your organization about these changes.
Applies To: Prism Patch Manager Subscription Server
Update Agent Memory Leak when Running McAfee VirusScan 8.0i Patch 11 or higher
3^rd-Party Application Patches supported by Prism Patch Manager 6.4
Prism Patch Manager 6.4 currently supports the following application patches. Application support includes:
Update installers (no base installers)
How to Configure Exporting for Policy Commander Web Reports

Policy Commander Web Reports (PCWR) supports exporting data to two file types: Adobe Acrobat and Microsoft Excel. After installing PWCR, there is some additional configuration needed in order to support exporting data, detailed below.

Configuring PCWR for Acrobat PDF Export

The two main steps for configuring the PCWR export-to-Acrobat feature are:
Install Adobe Acrobat Reader on the IIS/PCWR computer.
Modify folder permissions for a PCWR website folder.
How to Install and Configure Policy Commander Web Reports

Policy Commander Web Reports (PCWR) is an optional add-on to Policy Commander 2.0.1. (Note: You cannot use PCWR with Policy Commander 2.0.) This document contains information to help guide a successful installation of PCWR.

PCWR requires the following software be installed and configured on the target computer.
Microsoft Windows Installer version 3.1 (or later)
International Users:

In order to display vulnerabilities for non-English locales, you will need to contact your local distributor or New Boundary Technologies so your assigned serial number can be linked to the desired locale (see the list below). Please include the serial number that was sent to you in the email from New Boundary Technologies.

Find your local technology partner:
http://www.newboundary.com/partners/

or

New Boundary Technologies
Email: support@newboundary.com
Phone: 612.379.1851

Prism Patch Manager Server 6.4 System Requirements

New Boundary Support — Thu, 27 Mar 2008 08:26:00 GMT
Abstract:

Requirements
Detail
Troubleshooting Deployment of Microsoft Office Patches

Speed Up Detection Scans by Excluding Drives and Paths

New Boundary Support — Thu, 27 Mar 2008 07:12:00 GMT
Abstract:
Speed Up Detection Scans by Excluding Drives and Paths

Description
This article details how to exclude any drive or path from agent-based detection scans in order to decrease scan time and discusses a known issue when scanning the virtual M:/ drive of Microsoft's Exchange Server.

Applies To
Prim Patch Manager’s Update Server 6.4, Microsoft Exchange Server

Default IIS Configuration for Server

New Boundary Support — Thu, 27 Mar 2008 07:00:00 GMT
Abstract:

Default IIS Configuration for Patch Manager Server

Description

This article provides the default Directory Security settings for the Patch Manager Server in Internet Information Services (IIS). If problems arise as a result of changes to these settings, use this article to revert the Patch Manager Server Website to its original configuration.

Applies To
Prism Patch Manager 6.4
Prism Patch Manager 6.4 Agent Supported Operating Systems

Version
Supported Operating Systems

Upgrade to Prism Suite 8

New Boundary Support — Mon, 03 Mar 2008 03:01:00 GMT
Abstract:
Upgrading to Prism Suite 8
Upgrading the Console and Server
If you plan to upgrade your existing installation of Prism Suite on the same system where it is currently installed, follow the steps below.
1. IMPORTANT: Make a backup copy of your existing Prism SQL database files before upgrading. Refer to the Database Backup

Resolving Variables in Non-INI Text Files

New Boundary Support — Fri, 22 Feb 2008 03:48:00 GMT
Abstract:
The information in this article applies to:
• Prism Deploy
• Prism Pack
• PictureTaker
Summary:
Occasionally, a software installation process creates a non-INI formatted text file containing critical, user-specific information that the software ne

Moving the Prism Deploy Channel Database from one SQL Server to Another SQL Server

New Boundary Support — Thu, 14 Feb 2008 08:36:00 GMT
Abstract:
The information in this article applies to the following products:
• Prism Deploy 6.x, Prism Suite 7.x, Prism Suite 8.x

Summary:
There may be situations that require you to move a Prism Channel database from one SQL server instance to a different one. For example, you may have started out using MSDE (Microsoft Database Engine) for your Prism Deploy Channel database. However, your compan

Installing Policy Commander 2 on an Existing Prism Server

New Boundary Support — Mon, 21 Jan 2008 03:02:00 GMT
Abstract:
Installing Policy Commander 2.0 on an Existing Prism Server

Unlike earlier versions of Policy Commander, version 2.0 can be installed on the same server as Prism 8. This has the advantage of allowing customers to use existing hardware resources and software licenses efficiently (for example, Windows 2003 server or SQL Server). In addition, Policy Commander 2 makes it possible for customers to use the same Channel database for Policy Commander that they currently use for Prism. In other words, the computers you currently manage in your Prism Console can also be managed in your Policy Commander Console.

IMPORTANT: We strongly recommend that you do not evaluate Policy Commander on your existing production Prism installation, because if you decide to uninstall it later, it could affect your Prism in

Configuring SQL Server to Send Policy Commander Non-Compliant Email Alerts

New Boundary Support — Thu, 17 Jan 2008 12:32:00 GMT
Abstract:
Configuring SQL Server to Send Policy Commander Non-Compliant Email Alerts

1. On your SQL Server 2005 machine, run Microsoft SQL Server Management Studio.

2. Connect to and expand the SQL instance that Policy Commander is using.

Exporting and Importing Configuration Groups
Configuration groups can be exported out of any version of Prism or Policy Commander, and Policy Commander can import these configuration groups. The export file format is XML.
Exporting Configuration Groups
Configuration groups can be exported out of a channel by running the export_config_groups.vbs script. This script can be used with any version of Prism or Policy Commander. The script extracts all of the configuration groups from the channel and stores them in an xml file called ChannelConfigGroups.xml in your TEMP folder (for example, C:\Documents and Settings\user\Local Settings\Temphttp://www.newboundary.com/pdf/Policy_Commander2_Tutorial.pdf

Policy Commander 1.0 Quick Start Guide

New Boundary Support — Thu, 17 Jan 2008 10:05:00 GMT
Abstract:
Browse here to view the Policy Commander Quick Start Guide.
http://www.newboundary.com/products/manuals/policycommander1/PolicyCommander_QSG.pdf

Policy Commander 2.0 System Requirements

New Boundary Support — Thu, 17 Jan 2008 09:57:00 GMT
Abstract:
System Requirements

Note: You must be an administrator-equivalent user to install any Policy Commander component.

Policy Commander Errors when Enforcing a Policy on Windows XP or 2000

New Boundary Support — Thu, 17 Jan 2008 09:46:00 GMT
Abstract:
PROBLEM:
There is a known issue with Policy Commander version 1.0.1 and earlier where Windows XP and 2000 have difficulty evaluating policies that contain changes to permissions on the registry branch “Machine\System\ControlSet001” and “Machine\System\CurrentControlSet\Control\WMI\Security”. This can result in an Error when enforcing one of these policies.

Strategies for Organizing Computers and Policies into Groups

New Boundary Support — Thu, 17 Jan 2008 09:45:00 GMT
Abstract:
Strategies for Organizing Computers and Policies into Groups

Policy Commander lets you organize computers into groups with similar requirements or having similar functions. Appropriate security polices are then assigned to the group and are enforced for computers within the group.

Likewise, you can organize related policies into groups. For example, you may have a group of policies designed to protect sensitive data. Computers where data privacy is of utmost importance would be added to the group and would have the data privacy policies enforced.

Automatic Groups
By default, Policy Commander recognizes and automatically creates groups that reflect a computer’s Active Directory OU membership. For example, if your Active Directory domain is called MyCompany.com, and computers in the Accounting, Sales, Marketing and Administration OUs are managed with Policy Commander, the Dashboard w

Computer does not appear in Policy Commander Dashboard

New Boundary Support — Thu, 17 Jan 2008 09:45:00 GMT
Abstract:
One reason a computer may not appear in the Policy Commander Dashboard even after the client has been installed is that the computer is not part of an Active Directory domain. By default, Policy Commander is configured to require computers to use their Active Directory name. If they are not part of an Active Directory structure, they don't appear until a configuration change is made.

Here are the steps to get non-AD computers to appear in the Dashboard:
Open the “Settings” link, go to the “Communications Settings” section. At the bottom of the section, there is a drop-down under “Use Active Directory Naming”; choose “no, use NetBIOS.” Save the change.
Go back to the Dashboard view, open the “Add Computers” link, and again download the client installation program and run it on the PC. The computer should now appear in the Dashboard view.
Policy Commander can be configured to send email alerts when a computer goes out of compliance with an assigned policy, and when a policy is enforced on a computer. This technote details the steps that must be completed after installing Policy Commander in order to activate email alerts. Please refer to the Policy Commander Quick Start Guide for enabling email alerts on individual policies.

The steps vary depending on which SQL instance Policy Commander uses. If it uses the local MSDE instance that was installed during setup, you must 1) modify the stored procedure Create_proc_SetPCommResults.PRC in the Policy Commander database, and 2) configure the SMTP email server to allow the Policy Commander database to send email.

For installations using a SQL instance that was not installed by Policy Commander, one additional step is necessary. You must register the extended stored procedure XPSMTP in the master database of the SQL instance used by Policy Commander.

Note: This technote assumes you have a properly-configured SMTP em

Policy Commander 1.x System Requirements

New Boundary Support — Thu, 17 Jan 2008 09:16:00 GMT
Abstract:
Policy Commander 1.x System Requirements

Note: You must be an administrator-equivalent user to install any Policy Commander component.

Web Server
Operating System Windows® 2000 Server, Windows® XP Professional, or Windows Server® 2003
Application Services Unattended/All Users Explanation
When Prism installs a Package, the Package is broken up into two different portions; a user portion and a machine portion. The user portion contains all the shortcuts and user settings, while the machine portion contains the application files and machine settings. The machine portion of the Package is only installed once. The user portion is installed once for each user of the machine. This is all handled by Prism under the covers and is the behavior of all Package Tasks deployed through the Console.
When a Package is installed outside of the Console or via a Script (such as a Script Task in the Console), this behavior can be duplicated by setting the "Unattended/All Users" value in the Advanced settings of the Package's Properties. When an "Unattended/All Users" Package is installed, the file PTPNDFLS.EXE and a user only portion of the Package are created in the PTPNDFLS folder. A shortcut called "Install Pending Files" is added to the Startup folder of the All Users Start Menu. This shortcut points to PTPNDFLS.EXE with an /ApplyPending switch. PTPNDFLS.EXE is a fully functioning copy of PTCLI

Prism Deploy Configuration for a WAN Environment

New Boundary Support — Fri, 26 Oct 2007 08:13:00 GMT
Abstract:
The information in this article applies to:
• Prism Deploy
Summary:
This tech note discusses some options and scenarios for configuring Prism Deploy in a WAN environment.
Assumptions:
The example below illustrates a network environment consisting of three regions. One assumption is that all Prism Channel administration is done from the central server. The satellite offices within each region are connected via T1 to a regional server. The three regional servers are connected via Frame Relay to a central server at headquarters. This could be an Active Directory environment with an OU for each region, although Prism’s Channel configuration does not have to mirror the Active Directory structure. Below is simple sketch of the environment. Given this environment, what are the

Client Stopped Status reported in the Console

New Boundary Support — Tue, 02 Oct 2007 10:55:00 GMT
Abstract:
The information in this article applies to:
Prism Suite 8.0

The New Boundary Technologies team is currently investigating an issue where the Client Status reported in the Console is "Client Stopped". We believe that the status “Client Stopped” actually means “Offline (Known)” meaning that the computer has been shut down or is rebooting.

Upgrading to Version 8 of the Prism Deploy Packager

Prism Pack has now been upgraded to the Prism Deploy Packager. Here are some of the new features of the version 8 Packager:

· Prism Deploy Packager (named pictaker.exe instead of paedit.exe) supports Windows Vista (32-bit).
· New Boundary Client (named ptclient.exe instead of paclient.exe) supports Windows Vista (32-bit).
Prism Suite 8 now supports Windows Vista (32-bit). This means that you may add Vista clients to your Channel, build Packages, deploy Tasks, run Asset Management inventories, etc. All the same tasks you currently do with Windows 2003, XP and 2000 systems.
Direct Install requirements
You may have Vista PCs already in your environment, but when you try to Direct Install the client you’re getting the error “Install Failed (Service Failed)”.
In order to successfully Direct Install the client to Vista, File Sharing must be enabled. This setting is Off by default.
To enable – open the Start Menu, right-click on “Network” and select “Properties”. Click on the down arrow next to File Sharing and select the option to “Turn on File Sharing”. Answer any prompts. The setting should change to “On” and have a green icon.
Direct Client Installs s

Upgrading Prism Packages and Self-Installing Files to Version 8

New Boundary Support — Wed, 05 Sep 2007 11:31:00 GMT
Abstract:
The Prism Package Editor has been greatly enhanced with the Version 8 release. In addition to supporting Windows Vista, the number of “Special” or “Known” folders supported by Prism Packages has increased. This means that Prism automatically substitutes variables for known folders so that they will be installed to the appropriate path on target OS’s.
How does this affect your current library of Packages and Self-Installing Files?
Packages
- Do not need to be upgraded to be installed by the version 8 Prism client.

MEMBER_OF Configuration Group Operator

New Boundary Support — Wed, 05 Sep 2007 11:18:00 GMT
Abstract:

The information in this article applies to:

Prism Suite 7.0.3 and above
Policy Commander 1.5 and above

New Boundary Technologies Support Knowledge Base

Contributing to the Prism Software Identification Database

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

FAQs – Prism Suite Version 9 Distributed Tasks

Prism Suite 8 Client Logging Changes (Where is Pictaker.log?)

Installing Prism Suite to a remote SQL Server 2005 or SQL Server 2008

Office Deployment Tips

Prism Suite 9 System Requirements and Supported Platforms

Prism Patch Manager Deployment Failure Codes (190A, 190C, 109D, 190E

Patch Deployments fail with Error 190D

Creating a Subscription File to Install the Prism Client

Prism Patch Manager 6.4 Documentation

Prism Patch Manager 6.4 - Service Pack 1 for Update Agent

Prism Patch Manager Server 6.4 System Requirements

Speed Up Detection Scans by Excluding Drives and Paths

Default IIS Configuration for Server

Upgrade to Prism Suite 8

Resolving Variables in Non-INI Text Files

Moving the Prism Deploy Channel Database from one SQL Server to Another SQL Server

Installing Policy Commander 2 on an Existing Prism Server

Configuring SQL Server to Send Policy Commander Non-Compliant Email Alerts

Exporting Configuration Groups

Policy Commander 1.0 Quick Start Guide

Policy Commander 2.0 System Requirements

Policy Commander Errors when Enforcing a Policy on Windows XP or 2000

Strategies for Organizing Computers and Policies into Groups

Computer does not appear in Policy Commander Dashboard

Policy Commander 1.x System Requirements

Prism Deploy Configuration for a WAN Environment

Client Stopped Status reported in the Console

Upgrading Prism Packages and Self-Installing Files to Version 8

MEMBER_OF Configuration Group Operator