InstantKB

Prism Suite System Requirements and Supported Platforms

New Boundary Support — Mon, 18 Jan 2021 15:11:08 GMT

The information in this article applies to Prism Suite®, Prism Deploy®, Prism Asset Manager®, Prism Deploy Packager, Prism Portal™, and Prism Mobile™

Current Release: 18.0	Prim Console (software deployment, asset management)*	Prism Deploy Packager**	New Boundary Channel Server	New Boundary Client**	Prism Portal and Prism Mobile web application
Operating System, 32 & 64 bit	Windows 10	Windows 10	Windows Server 2019	Windows 10	Windows Server 2019
	Windows 8, 8.1	Windows 8, 8.1	Windows Server 2016	Windows 8, 8.1	Windows Server 2016
	Windows Server 2016	Windows Server 2019	Windows Server 2012 R2	Windows Server 2019	Windows Server 2012 R2
	Windows Server 2012 R2	Windows Server 2016		Windows Server 2016
		Window Server 2012 R2		Windows Server 2012 R2

Database, 32 & 64 bit			MS SQL Server 2019		MS SQL Server 2019
			MS SQL Server 2017		MS SQL Server 2017
			MS SQL Server 2016		MS SQL Server 2016
			MS SQL Server 2014		MS SQL Server 2014
			MS SQL Server 2012		MS SQL Server 2012
Other Components	.Net Framework 4.0		.Net Framwork 4.0		.net Framerwork 4.5.1
					IIS 7, 7.5,8,8.5,10 with ASP.NET enabled
				PowerShell 2,3,4,5,6

Processor	Pentium or higher	Pentium or higher	Intel Core Duo or higher	Pentium or higher	Intel Core Duo or higher
Ram	2 GB	512 MB	2 GB	512 MB	2 GB
Disk space for installed Components	100MB	40MB	65MB	12MB	Web app: 15BM (Mobile)37MB(Portal
			Database: 4GB	;	Database: 40 MB (Mobile) 60 MB (Portal)

Microsoft Supplemental Installations

Other installations that may be needed include: SQL Server, MDAC 2.8, .Net Framework

These third-party items will be included in the standard installations as noted for the individual components above.

^* DEVEXPRESS and INFRAGISTICS DLLs are required to support reporting functions.

** CAPICOM.DLL is required to support Package authentication.

^***Microsoft IIS 7, 7.5, 8, 8.5, or 10 must be installed on a Web server if you intend to use the NBTProxy Service to enable HTTP/HTTPS communication from the Prism Console or New Boundary client outside the network perimeter, to a New Boundary Channel Server inside the network perimeter. IIS installation and configuration is not part of the Prism Suite installation. Note: If you choose to install IIS 7, you must also install the IIS 6.0 management tools in order to install the NBTProxy Service. (Installing the IIS 6 management tools is a choice during installation of IIS 7.)

^****The following Microsoft components are prerequisites to installing SQL Server 2008 R2 Express. They will NOT be downloaded during installation. If you plan to install SQL 2008 R2 Express as part of the Prism Suite installation (instead of using an existing SQL server), please install the prerequisites before starting the installation.

Customizable Console User Interface

New Boundary Support — Mon, 18 Jan 2021 14:03:23 GMT

Administrators can now configure the Console UI to hide or make visible features such as multiple report icons, the toolbar or the status bar for easier navigation.

The status bar is now hidden by default but can be enabled again in the View menu.

The Reports Icons are also hidden by default. If you would like to enable them please contact support and we can walk you through configuring the client to show them again.

Low Bandwidth Operation

New Boundary Support — Mon, 18 Jan 2021 13:49:25 GMT

Computers with low bandwidth connections to the server can now be targeted for special treatment.

Once a group of computers are identified for special low bandwidth treatment, the administrator sets a value for the number of simultaneous connections back to the server.

Computers temporarily denied access for receiving the tasks will poll again later to receive the task.

The number of simultaneous low bandwidth connections is configured in the Channel Properties dialog box under the Server tab.

You can flag any computer as low bandwidth in the Computer Properties dialog box.

Task “Snooze” Option

New Boundary Support — Mon, 18 Jan 2021 13:43:33 GMT

Tasks now have the ability to be “snoozed” by end-users so they can be executed at a more convenient time.

Administrators have the option to configure tasks with custom messaging that prompts end-users to delay, if desired, the execution of a task.

The End User is enabled by first selecting the "Show Task Delay Settings" box on the first page of the "Schedule Task" dialog box.

This will now add a third page for you to configure your user interaction.

Allow Task Delay

With this option checked, users will be presented with the "snooze" prompt before the task installs.

Task Delay

With this option unchecked, the task will install without user interaction.

Task Delay ("Snooze") Interval

Use this option to select how long the task is delayed if the user chooses to "snooze" it. The drop-down list offers several different time intervals.

Custom Message

Use the Caption and Message options to customize the text the user sees in the "snooze" prompt dialog. If one or both fields are left blank, a default message will appear in the dialog.
One can include a special insertion point, <SnoozeTime>, in the Message text. The chosen task delay ("snooze") interval is substituted when the message is displayed.

Message text: "Click OK or click Snooze to delay for <SnoozeTime>."

User sees: "Click OK or click Snooze to delay for 1 hour."

Randomized Task Execution

New Boundary Support — Mon, 18 Jan 2021 13:30:33 GMT

Administrators can now flag a task to be executed at a random time within the scheduled time window.

Enabling this new feature will help balance server load and reduce peak bandwidth needs.

In previous versions, tasks would execute on all computers upon receiving the task assignment or at the scheduled start time.

This feature can be enabled on the second page of the "Schedule Task" dialog box.

To enable assign a time window and make sure that "Randomize start time within window" is checked.

Task “Time Window” Scheduling

New Boundary Support — Mon, 18 Jan 2021 13:22:26 GMT

Administrators can now schedule a specific time of day window for a task to be installed.

Computers will receive assignments at any time of day as with previous versions, but will only execute the task when it is within that specified time of day window.

Setting for this can be found on the second page of the Schedule Task Dialog box.

To enable: Select "Schedule processing to start at a specified time" and set a time window then select "Only between specific times"

The option "Randomize start time within window" allows for a more staggered deployment.

You can also allow it to install on a schedule during that time window by using the "Repeat Deployment" option.

Channel Data Import/Export

Travis — Wed, 02 May 2018 14:25:40 GMT

The information in this article applies to Prism Deploy 17 or higher.

The Prism Console’s new Import Channel Data and Export Channel Data menu options provide a rich set of options for moving data between channels. This data can include: Organization Groups, Configuration Groups, Distribution Groups, Users and Roles, Tasks and Task Groups, and Task Assignments. The feature is found on the File -> Import/Export menu: Import Channel Data and Export Channel Data. These menu options open a wizard that allows you to choose the source or destination, the specific data, and how it should be handled (e.g., overwrite/do not overwrite).

For example, using Export Channel Data, you could select 10 tasks and 5 configuration groups, and export them to 2 other channels (and or to a file). You would have the option of including the assignments of those tasks to those groups (if any assignments existed).

For more information, please refer to the context sensitive help available within the wizard.

Active Directory User Authentication for Prism Console

Travis — Mon, 30 Apr 2018 16:38:57 GMT

The information in this article pertains to Prism Deploy 17.0 and above.

Prism Deploy has always been able to have a Prism Channel secured so that users of Prism are required to enter credentials before using the console. This requires that each user have separate Prism credentials, since Prism performs the authentication. Now a channel administrator can allow users to login using their Windows credentials instead of requiring them to use (and maintain) separate Prism credentials.

To enable Active Directory Authentication within your Prism Channel, you first need to secure the Prism Channel. Then, login to the Prism Console as a user who has Channel Admin rights, select the Security Menu option, and choose Configure Security. Check "Allow Windows authentication against" to allow users to use their AD username and password to log into the Prism Console. Note that the AD domain that will be used is shown to the right. To access Prism, they must have been added as a Prism user, and their Prism username must match their AD username. Therefore, if your Prism User is jjohnson, as long as their AD user name is jjohnson they will now be able to log into the Prism Console using Windows credentials. Prism does not store the Windows password. Prism queries Active Directory to see if the user exists and if the password they entered is correct. If the query is successful, the user is able to log in as if they were using "Prism Authentication".

This Configure Security dialog shows two Prism users. Assuming user “travis” is also “travis” in Active Directory, “travis” can login using Windows credentials.

Prism Package Size Limit Increase (64bit only)

Travis — Mon, 30 Apr 2018 15:22:16 GMT

The information in this article applies to Prism Deploy Packager, Prism Deploy 17, Prism Suite 17, and above.

With the Prism Deploy Packager, you can now build a Prism Package that can be larger than the previous size limitation of 4.3 GB. When building packages that will be large, please give ample time to the capture process. In addition, it is important to not preform secondary actions on the computer you are building a package during the capture process. This reduces the possibility of capturing objects not related to what was intended to be captured.

You should always review the contents of a Prism Package upon completion, to remove objects that are not associated with what was intended to be captured. The larger the package the more extraneous objects one might need to remove. Keep a copy of the original package captured to use as a reference, especially with larger packages.

Task Priority not compatible with mismatched scheduled Task assignments

Travis — Mon, 27 Feb 2017 16:02:16 GMT

The information in this article applies to the Task Priority feature in Prism Deploy versions 11.0 and later.

The Task Priority feature in Prism Deploy allows you to assign more than one task to a PC or group of PCs and to set a specific order for the Tasks to run (1, 2, 3..). However, the priority order may not work as expected if you choose to prioritize Tasks that have already been assigned using various scheduling options for Install or Reinstall, such as "Install after", "Reinstall after", "Reinstall on first logon after...", etc.

Let's look at a screen shot of various task schedule assignments properties.

As you can see, there are eight tasks, all with various task schedule assignment properties. Because all of the tasks have previously been deployed with schedules, the prioritized tasks won't install this time in their intended priority order. For Tasks to install in the priority order you want, all the Tasks must have the same installation schedule (such as Install or Reinstall). All other Task execution properties such as "Allow unattended installation" and "Run as" need to match as well.

Here is an example of task scheduling assignment properties matching;

As you can see, the Task scheduling assignment on the prioritized is now identical, and the Tasks will run in the proper priority order

Web Package Tasks - Tips & Tricks

Pam — Mon, 20 Feb 2017 10:45:12 GMT

The information in this article applies to Prism Deploy 16.0 and above.

Prism Deploy has always been able to deploy Packages from a web address. With Prism 16.0, we’ve improved this capability in two ways:

There is now a Web Package Task wizard to help you create the correct syntax for the Task.
The credentials you specify to access the Web Package (if necessary) are more secure. Once the Task is created, the password is hidden in the Console and encrypted in the channel database. It is not exposed in the client log file.

One of the most common ways that Prism Deploy customers use Package Tasks is to stage the payload for subsequent Tasks locally on the target PCs. For example, when installing large and/or complex software, Prism administrators manually create a Package that contains the scripts, setup files, folders and other source files necessary for the software installation. They deploy the staging Package and then follow up with a separate Task (MSI, Command or Script Task) to kick off the installation using the locally-staged files. With Web Package Tasks, Prism administrators have another option for supporting off-network PCs.

Here are some tips for getting the right URL syntax for Prism's Web Package Tasks.

Internet-facing web server: The syntax would look like this https://server.domain.com/WebPackages/SomePackage.pwc (or http://).

When deploying from cloud storage sites such as Dropbox or OneDrive, there are some extra steps for getting a correctly formatted URL to use in the Web Package Task.

Dropbox: By default, files shared through Dropbox URLs are for viewing, not for download. A typical Dropbox URL looks like this: https://www.dropbox.com/s/lpbb6enj3jzp38p/Small.PWC?dl=0. To convert the URL to a downloadable one, simply replace the 0 at the end to 1 (…dl=1).

OneDrive: OneDrive URLs also need to be changed before being used for Web Package Tasks. By default, OneDrive URLs are shortened. They first need to be expanded, then converted into a direct download URL. To illustrate, here’s an original (shortened) OneDrive URL to a Prism Package:

https://1drv.ms/u/s!AtUhQlsHZZrxi2DHgs8jhmaQyFHe
If it was deployed as a Web Package Task in it’s shortened format, it would fail with error 4400, “unexpected Internet error.”

To expand the URL, use one of these free sites:
www.wheredoesthislinkgo.com
www.linkexpander.com

Here’s the expanded URL:
https://onedrive.live.com/redir?resid=F19A65075B4221D5!1504&authkey=!AMeCzyOGZpDIUd4
This URL isn’t ready to use for a Web Package Task because it needs to be converted to a direct download link.

To get the direct download URL, use one of these direct link generators:
www.syncwithtech.org/p/direct-download-link-generator.html
www.technorange.com/cloudlinker-direct-link-generator-for-dropboxgoogle-driveone-drive-copy-com/

You now have a direct download link that works for the Web Package Task. Here’s the final URL:

https://onedrive.live.com/download?resid=F19A65075B4221D5!1504&authkey=!AMeCzyOGZpDIUd4

Google Drive: Shared URLs from Google Drive are not supported at this time.

The Running Tasks Window - Finding "Stuck" Tasks

Pam — Tue, 14 Feb 2017 11:23:10 GMT

The information in this article applies to Prism Deploy 16.0 and above.

The Running Tasks feature make it easier to know which Task deployments are in process and to troubleshoot ones that may be hung up.

It’s possible for the Prism Client to get stuck on a particular Task, causing other assigned Tasks that are behind it in the queue to remain pending. Here are the two most common ways that happens:

A Task is configured to “allow unattended installation.” If the Task starts running when no user is logged into the target computer, it launches in the context of the unattended user. If the Task launches some type of prompt that needs a response, it’s impossible to respond to the prompt because no user is logged in. Even if a user logs in during this time, the unanswered prompt does not switch to the logged in user’s environment. The Task remains running.
A Task is configured to run in Hidden mode so the end user won't see any activity. However, just like in #1 above, the Task launches some type of prompt. Since the Task was set to run in Hidden mode, the prompt can’t be answered because it is hidden from the logged in user.

This is what you'd see in the Running Tasks window:

If the Task had become stuck on multiple computers, there would be one entry for every computer where it was stuck. Assigned Tasks that are behind the stuck task in the queue do not appear in the Running Tasks window because they are still pending. Only those that have launched appear here.

Resolution to both scenarios:

To clear a Task that is stuck, either disable or unassign it within the Prism Console. Then reboot the client. To avoid this situation, always test any Tasks that you allow to run unattended or run in Hidden mode. Verify they don’t produce prompts that users must answer or open windows that users must close.

PowerShell Version Information for Prism PowerShell Tasks

Pam — Mon, 13 Feb 2017 14:45:22 GMT

The information in this article applies to PowerShell tasks, which were introduced in Prism Deploy 16.0.

When creating a PowerShell Task in Prism Deploy, you have the option to choose the minimum version of PowerShell that's required to run the Task. If you use this option, the version you choose becomes a prerequisite on the Task. If the target system doesn't meet the prerequisite, the Task won't attempt to run.

The latest version of the PowerShell core (as of 2/1/2017) is version 5. Each Windows operating system has a default version of the PowerShell core installed. The default versions per operating system are shown below. Note: Powershell 1.0 is not supported for Prism's PowerShell Tasks.

PowerShell version 5 can be installed side by side with version 2. PowerShell versions 3 and 4 can be upgraded to version 5.

Each version of the PowerShell core is forward-compatible. This means any script or cmdlet that worked in an earlier version should still work in later versions. However, the PowerShell core and the Windows operating system interact to determine what commands and cmdlets will work. For example, cmdlets that are available on Windows 10 are not available on Windows 7. Likewise, server operating systems have many cmdlets that workstation operating systems don’t. So even if you update the PowerShell core, you won’t get the cmdlets from newer operating systems.

More information about PowerShell versions and related topics is available on Microsoft's Hey! Scripting Guy blog.

Symantec Endpoint Protection Produces False Positive

New Boundary Support — Wed, 17 Feb 2016 10:48:48 GMT

The information in this article applies to:

Prism Deploy
Prism Suite

Summary

This article is to assist users of Prism products that have experienced false positives with anti-virus solutions such as Symantec Endpoint Protection (SEP). Occasionally, Heuristic Scanning from Symantec Endpoint Protection will identify Prism Packages (.pwc), Prism Rollback (.pwr), or Self-Installing Files (.exe) (executable wrapped Prism Package) as Suspicious.emit.

New Boundary Technologies has performed rigorous malware scanning and testing against all of our product files and package files and have not found any anomalies. Symantec’s identification is therefore a false positive.

New Boundary Technologies is working with Symantec to find a resolution to this issue, until then we recommend that you follow this article.

Recommendations to minimize false positives with Symantec Endpoint Protection and other similar anti-virus applications

New Boundary Technologies recommends that you create an Exception Policy or add to an existing Exception Policy within Symantec Endpoint Protection for Prism Suite, Prism Deploy or Prism Deploy Packager executable and service files, as well as folder structures related to Prism Suite or Prism Deploy.

Folder structures that should have exceptions created for them are:
32-bit:
C:\program files\New Boundary
C:\program files\common files\New Boundary
C:\ProgramData\Prism Deploy

64-bit:
C:\Program Files (x86)\New Boundary
C:\Program Files (x86)\Common Files\New Boundary
C:\ProgramData\Prism Deploy

The following application and service files for Prism products (along with their paths) should have exceptions made for them:
32-bit:
C:\Program Files\New Boundary\Client\PTClient.exe (32-bit)
C:\Program Files\Common Files\New Boundary\PrismXL\PrismXL.sys (32-bit)

64-bit:
C:\Program Files (x86)\New Boundary\Client\PTClient.exe (64-bit)
C:\Program Files (x86)\Common Files\New Boundary\PrismXL\PrismXL.sys (64-bit)

Optional: The following proprietary file types created by Prism products can also be exempted in Symantec:
.PWC (software deployment package file)
.PWR (software deployment rollback file)
.PWI (package “snapshot” definition file)
.PWF (package “snapshot” file)
.PWSUBS (Prism client subscription file)
.PTS (Prism script file

After creating or modifying your Exception Policy (Symantec Endpoint Protection) to include Prism-related information, ensure that the policy is then applied to all workstations or servers where Prism (product) files may exist.

Policy Commander System Requirements and Supported Platforms

New Boundary Support — Fri, 09 Jan 2015 16:29:00 GMT

The information in this article applies to Policy Commander version 3.2.

	Installed disk space requirements	Install file size
SQL Server 2008 R2 Express⁴	350 MB	37 MB
MDAC 2.8	40 MB	5.5 MB
.NET Framework 2.0	150 MB	24 MB

These third-party items will be included in the standard installations as noted for the individual components above.

¹ devexpress and infragistics dlls are required to support reporting functions.

² capicom.dll is required to support Package authentication.

³Microsoft IIS 6 or IIS 7 must be installed on a Web server if you intend to use the NBTProxy Service to enable HTTP/HTTPS communication from the Policy Commander Console or client outside the network perimeter, to a Policy Commander Server inside the network perimeter. IIS installation and configuration is not part of the Policy Commander installation. Note: If you choose to install IIS 7, you must also install the IIS 6.0 management tools in order to install the NBTProxy Service. (Installing the IIS 6 management tools is a choice during installation of IIS 7.)

⁴The following Microsoft components are prerequisites to installing SQL Server 2008 R2 Express. They will NOT be downloaded during installation. If you plan to install SQL 2008 R2 Express as part of the Policy Commander installation (instead of using an existing SQL server), please install the prerequisites before starting the installation.

	Installed disk space requirements	Installer file size
Windows Installer 4.5	3 to 4.5 MB	70 to 125 MB
.NET Framework 3.5 SP1	500 MB	197 MB

PwrSmart System Requirements and Supported Platforms

Travis — Thu, 31 Jul 2014 14:33:00 GMT

PwrSmart® 4.2 System Requirements and Supported Platforms

Important note: Power schemes are not enforced on Windows Server operating systems. However, a client can be installed on servers in order to allow that server to act as an agent for wake-up events.

Microsoft Supplemental Installations

These components will be installed separately if needed. They are downloaded from the New Boundary web site during installation.

	Installed disk space requirements	Installer file size
SQL Server 2008 R2 Express³	350 MB	37 MB
MDAC 2.8	40 MB	5.5 MB
.NET Framework 2.0	150 MB	24 MB

These third-party items will be included in the standard installations as noted for the individual components above.

¹ DEVEXPRESS and INFRAGISTICS DLLs are required to support reporting functions.

²Microsoft IIS 6, 7 or 8 must be installed on a Web server if you intend to use the NBTProxy Service. The NBTProxy Service enables HTTP/HTTPS communication from New Boundary clients that are outside the network perimeter to a New Boundary Channel Server inside the network perimeter. IIS installation and configuration is not part of the PwrSmart installation. Note: If you choose to install IIS 7 or 8, you must also install the IIS 6.0 management tools before installing the NBTProxy Service. Installing IIS 6 management tools is a choice during installation of IIS 7 and 8.

³The following Microsoft components are prerequisites to installing SQL Server 2008 R2 Express. They will NOT be downloaded during installation. If you plan to install SQL 2008 R2 Express as part of the PwrSmart installation (instead of using an existing SQL server), please install the prerequisites before starting the installation.

	Installed disk space requirements	Installer file size
Windows Installer 4.5	3 to 4.5 MB	70 to 125 MB
.NET Framework 3.5 SP1	500 MB	197 MB

Prism Suite System Requirements and Supported Platforms

Travis — Wed, 23 Apr 2014 13:19:00 GMT

The information in this article applies to Prism Suite®, Prism Deploy®, Prism Asset Manager®, Prism Deploy Packager, Prism Portal™, and Prism Mobile™

Microsoft Supplemental Installations

These components will be installed separately if needed. They are downloaded from the New Boundary web site during installation.

These third-party items will be included in the standard installations as noted for the individual components above.

¹ DEVEXPRESS and INFRAGISTICS DLLs are required to support reporting functions.

² CAPICOM.DLL is required to support Package authentication.

³Microsoft IIS 7, 7.5, 8, 8.5, or 10 must be installed on a Web server if you intend to use the NBTProxy Service to enable HTTP/HTTPS communication from the Prism Console or New Boundary client outside the network perimeter, to a New Boundary Channel Server inside the network perimeter. IIS installation and configuration is not part of the Prism Suite installation. Note: If you choose to install IIS 7, you must also install the IIS 6.0 management tools in order to install the NBTProxy Service. (Installing the IIS 6 management tools is a choice during installation of IIS 7.)

⁴The following Microsoft components are prerequisites to installing SQL Server 2008 R2 Express. They will NOT be downloaded during installation. If you plan to install SQL 2008 R2 Express as part of the Prism Suite installation (instead of using an existing SQL server), please install the prerequisites before starting the installation.

Prism Mobile Architecture

New Boundary Support — Mon, 11 Mar 2013 15:39:00 GMT

Prism Mobile^TM Architecture

Prism Mobile consists of three components that work together to give you the ability to manage your Prism Deploy channels from your mobile device.

Prism Mobile app for iOS and Android -now available on the App Store and Google Play. Search for it either by Prism Mobile or New Boundary Technologies.
Prism Mobile Web Service, which is installed on your company's intranet (Microsoft IIS server with ASP.NET enabled). Download setup file by clicking here. IMPORTANT: The communication between the mobile devices and the Prism Mobile Web Service is secured using industry-standard SSL. The IIS server must use an SSL certificate from a valid certificate authority (CA), not a self-signed certificate.
Prism Deploy installation (minimum version 13.1) consisting of the Prism Deploy server, console, channel database(s) and managed PCs running the Prism Deploy client. Download the latest version here.

Here's a graphic of how the pieces work together:

Prism Mobile FAQs and Tips

New Boundary Support — Tue, 18 Dec 2012 17:51:00 GMT

Prism Mobile^TMFAQs and Tips

FAQs

Who can use Prism Mobile?

Any Prism Suite or Prism Deploy customer using version 13.1 or later. The Prism Mobile web service needs to be installed and activated on your company's intranet IIS server. Contact prismmobile@newboundary.com if you need an activation code, or contact your company’s Prism Suite/Prism Mobile administrator for details.

How do I get started using Prism Mobile?

After launching the app, register as a new user of Prism Mobile with your email address and password. Your Prism Mobile administrator will give you the Server name to enter for your site’s installation. Once registered, log into Prism Mobile. You’ll be presented with a list of at least one channel that your Prism administrator has made available. Log in using the credentials you would normally use when logging into the Prism Console.

Is Prism Mobile Secure?

Yes! All communication between the app and the Prism Mobile service on your IIS server occurs over industry-standard SSL (Secure Sockets Layer). This is the same standard used for internet banking and online purchasing at sites such as Amazon.com.

Prism Mobile app users log in once to the app (using the email address and password they used when registering their device), and once to the channel they want to manage. The channel login is the same one used when logging into the Prism Console on Windows. This means Prism Mobile app users have the same roles and the same permissions they have when using Prism on their Windows PCs.

Prism channel data is not stored on the device.

How do the counts in Recent Activity work?

The count shown on “New since last check” is the number of failed deployments since the last time you viewed that information. Every time you view the new items, the count is reset.

Counts of failed deployments in the past week appear when you click on the “By task” and “By computer” buttons. You’ll be able to see at a glance if a particular task or computer is experiencing a large number of failures. These counts are continually updated.

Tips

Shortcut back to Home

iOS: Simply swipe 2 fingers to the right. Android: use the Prism Mobile icon in the Action Bar.

Viewing long computer, group or task names

Just switch to landscape mode.

Viewing all task results (not just failures) older than one week

From the Home screen, find the task whose results you’d like to see. Alternately, look at task results for a particular computer or group.

How to Update Existing Non-Scannable Assets via Importing

New Boundary Support — Wed, 27 Jun 2012 15:27:00 GMT

The information in this article applies to Prism Asset Manager (part of Prism Suite) version 13.0 and newer.

When importing non-scannable asset data to the Assets tab, you now have the choice to update existing (not just add new) non-scannable assets. For example, let’s say your non-scannables already include 5 mobile broadband cards that can be loaned to users as needed. Your non-scannable items on the Assets tab might look something like this:

You’re planning to order some new mobile data cards, and the existing ones will be phased out soon. In addition, you want to add a field that shows who the data cards are loaned out to. Your import spreadsheet might look something like this:

You're now ready to being the process of importing updated information about your non-scannable assets.

Steps for Updating Non-scannables

1. In order to enable non-scannable updating (instead of only adding new records when importing), you need to add the following registry value to the system where you are running the Prism console: HKEY_CURRENT_USER\Software\Lanovation\Prism Deploy\Preferences; value name (Reg_SZ) = AssetImportOverride; value data=”choice”. (Other data options are “update” or “new”.) If the Prism console is already open when you make this registry change, close and reopen the console.

2. Verify that your asset import spreadsheet has the new information you want to import.

3. Before you begin your import, create any new User Defined fields (UDFs) in the Prism Console by opening the Asset Management|User-defined Fields|Assets menu.

4. Now you’re ready to import. On the Assets tab, right-click on non-scannable and choose Import Data. Walk through the import wizard, being sure to check the option Update the existing Asset, otherwise new rows (duplicates) will be created when you import.

5. Specify the columns to import, matching them up with the asset fields used in the Prism Console.

6. Press the Import Now button to complete the import of updated non-scannable information. After the import, your non-scannable data might look something like this:

New Boundary Technologies, Prism Suite and Prism Asset Manager are registered trademarks of New Boundary Technologies, Inc. All other brands and product names are trademarks or registered trademarks of their respective companies.

Installing Office 2010 via a Distributed Task

New Boundary Support — Fri, 27 Apr 2012 10:56:00 GMT

The information in this article applies to the following products:

• Prism Suite 10.x and above

Summary:

In order to deploy Office 2010 to remote offices taking advantage of Prism Suite's Distribution locations there are some specific settings that need to be set to insure that deployment goes smoothly.

Notes:

It is beyond the scope of this document to explain all the options available for customizing the installation of Office 2010. This article is intended for users that have already determined what customizations to make and how to make them using methods support by Microsoft. *See the related articles section for information about how to customize the installation of Office 2010
Please be aware that the way that the task talked about in this article will only work for machines that are installing this task from a Distribution location. If you have machines that are not members of any distribution location then you will need to create a second task for them. *See the related articles section for information about how to create a task to install Office 2010 that are not members of a distribution location.

Method:

1. Extract the contents of the .ISO file to a server

2. Create a command task like so;

*Check the option for Distributed

3. Add the files and folders that were extracted from the .ISO

4. Finish creating the task and wait as Prism copies them to an internalized location that the Distribution Agent for the Distribution location can copy them from.

*Note: You might need to edit the properties of this task after this phase and add a “runas” user for this task to run as due to UAC being turned or if your users don’t have local admin privileges.

5. Give your distribution location(s) enough time to copy the “content” of the distributed task from the Prism server to itself or its local network storage location. This time will change depending on what the speed of the connection between your offices is, as well as if you’ve set any settings to restrict the hours at which “replication” can happen.

Policy Commander 3.0 Tutorial

New Boundary Support — Tue, 03 Apr 2012 10:13:00 GMT

Policy Commander 3.0 Tutorial

User Guide - Prism Patch Manager 7.0 SP1

New Boundary Support — Fri, 30 Mar 2012 11:39:00 GMT

User Guide - Prism Patch Manager 7.0 SP1

Server Install Guide - Prism Patch Manager 7.0 SP1

New Boundary Support — Fri, 30 Mar 2012 11:36:00 GMT

Server Install Guide - Prism Patch Manager 7.0 SP1

Agent Install Guide - Prism Patch Manager 7.0 SP1

New Boundary Support — Fri, 30 Mar 2012 11:34:00 GMT

Agent Install Guide - Prism Patch Manager 7.0 SP1