The Loadins displayed in the user guide are not part of the Faronics Core installation. Loadins are licensed and installed separately.
The Loadins have to be installed via Faronics Core Console. The Loadins are installed on the Faronics Core Server. Whenever Faronics Core Console connects to the Faronics Core Server, the version of the Loadin on the Faronics Core Server is updated on the Faronics Core Console.

System Requirements

The system requirements for Faronics Core and its components are described in the following section.
Faronics Core Server Requirements
System Requirements The following system requirements must be met to successfully install Faronics Core Server: 32- or 64-bit editions of Windows XP SP3, Windows Vista and Windows 7 32- or 64-bit editions of Windows Server 2003 and Windows Server 2008, Windows Server 2008 R2 The console requires Windows Installer (MSIEXEC) 4.5 and Microsoft MMC 3.0, which you must install separately (Faronics Core installer points to a download page if these components are missing). The console also requires Microsoft.NET 3.5 SP1 (which can be downloaded and installed by Faronics Core installer, if missing).
Faronics Core Console Requirements
System Requirements The following system requirements must be met to successfully install Faronics Core Console: 32- or 64-bit editions of Windows XP SP3, Windows Vista and Windows 7 32- or 64-bit editions of Windows Server 2003 and Windows Server 2008 The console requires Windows Installer (MSIEXEC) 4.5 and Microsoft MMC 3.0, which you must install separately (Faronics Core installer points to a download page if these components are missing). The console also requires Microsoft.NET 3.5 SP1 (which can be downloaded and installed by Faronics Core installer, if missing).
Hardware Requirements Minimum Pentium 4, 2.8 Ghz or equivalent 2 GB RAM 80 GB available hard disk space
Recommended Dual Core Pentium 2.4 Ghz or equivalent 3 GB RAM 80 GB available hard disk space
Faronics Core Database Requirements
System Requirements One of the following supported editions: Microsoft SQL Server 2005 SP4 or Microsoft SQL Server 2008 R2 (all editions) or Microsoft SQL Server 2008 Express or Microsoft SQL Server 2008 R2 Express
Microsoft SQL Server 2008 Express is included with Faronics Core Console and is perfectly acceptable for deployment sizes of 500 machines or less. Deployments of 500 to 1,000 machines can use the Express edition but may experience performance issues. For deployments over 1,000 computers it is highly recommended to use the Standard or Enterprise versions of SQL Server. The Microsoft SQL Server used by Faronics Core can be local to the Faronics Core Server machine (which will be the case if you install the 2008 R2 Express edition provided with the installer), though for larger deployments, of over 10,000 machines, it is highly recommended to connect to a remote SQL Server instance.

Click Next.

7. Create a new Administrator. An initial Administrator account must be created. Only authorized users can perform actions using Faronics Core. This initial Administrator account will allow you to create other user accounts.
This screen provides the following options: Faronics Core Administrator user Specify the user name. Password Specify a password. Passwords must be 8 to 15 alphanumeric. It must consist of upper case, lower case and numeric characters. Confirm password Re-enter the password. 8. The following screen displays the summary of all the settings. Click Save. to save the settings. Click Print. to print the settings. Select the Show passwords check box to display the hidden passwords.
9. Click Finish to exit Faronics Core Setup.
Configuring Faronics Core Console Manually
This chapter explains the Faronics Core Console Properties Dialog, its various tabs and configuration options.
Connecting to a Faronics Core Server Compatibility of Loadin versions on Faronics Core Server and Faronics Core Console Faronics Core Console Properties Dialog Console Tab About Tab
Connecting to a Faronics Core Server
During installation, you can install only the Faronics Core Console by selecting the option Install Faronics Core Console only. Once Faronics Core Console is installed, you can connect to multiple Core Servers. Complete the following steps to connect to a Faronics Core Server: 1. Launch Faronics Core Console. 2. Right-click Faronics Core Console in the Console Tree pane. 3. Select Connect to Server. The Connect to Faronics Core Server dialog is displayed.
4. Specify the values for the following fields: Name or IP the name of the Faronics Core Server or the IP address. Port the port through which Faronics Core Console connects to the Faronics Core Server. UserId the UserId for the Faronics Core Server. Password the password for the Faronics Core Server. Select the Save this connection check box to save the credentials.
5. Click Connect. Once the connection with the Faronics Core Server has been established, it is displayed in the Console Tree pane.

When connection to Faronics Core Server is lost, the Reconnecting.message is displayed in the Console Tree Pane and Faronics Core Console attempts to connect every 10 seconds for 10 times. To stop reconnecting, right-click on the Faronics Core Server and select Stop Reconnecting.
Compatibility of Loadin versions on Faronics Core Server and Faronics Core Console
Once a connection with a Faronics Core Server is established, the compatibility between the Loadin version installed on the Faronics Core Server and Faronics Core Console is checked. It is recommended that the Loadins on all Core Servers are upgraded at the same time.
If the Loadin versions on the Faronics Core Console and the Faronics Core Server are different, the following dialog is displayed:
Complete the following steps to resolve the mismatch: 1. Click Clear Product Cache. The Loadins from the Faronics Core Console are cleared. (Click Clear Server Connections to clear all connections with Core Servers. The Faronics Core Server connections are removed permanently.) 2. Close Faronics Core Console. 3. Re-open Faronics Core Console. The Loadins on the Faronics Core Server are synced with Faronics Core Console.
If Faronics Core Server 1 and Faronics Core Sever 2 have different versions of the same Loadin installed, Faronics Core Console will not be able to connect to both Faronics Core Servers at the same time. For Faronics Core Console to connect to two Faronics Core Servers, the version of the Loadin on both the Faronics Core Servers must be the same.
Faronics Core Console Properties Dialog
The Faronics Core Console Properties dialog provides options to configure Faronics Core Console manually. In the Console Tree pane, right-click Faronics Core Console and select Properties. The Faronics Core Console Properties dialog is displayed:
The Faronics Core Console properties dialog contains two tabs that allow you to configure Faronics Core Console. The tabs are explained in detail in the following sections.

Console Tab

The Console tab provides the following configuration options:
Select the Connect to www.faronics.com to check for news and updates check box to ensure that Faronics Core Console connects to the Faronics web site. Select the Display name of connected user in the connection label to display the user currently logged in to Faronics Core Console. Select the Display server port number in the connection label to display the port for the Faronics Core Server on the Faronics Core Server node. Select the Show Faronics system tasks to display tasks that are created internally by Faronics Product Loadins in the task History. This information may be useful for administrators who manage workstations. The check box is selected by default.

Keep tasks active for - select this check box to keep the action active if the workstation is not communicating with the Faronics Core Server. If this option is selected, the tasks will remain in the Active node of the Console Tree pane until all the offline computers come back online or, until the Active Time expires (whichever is earlier). The following options are enabled when the Keep tasks active for check box is selected. Active Time: - Select the duration in minutes (minimum 0 and maximum 1140), hours (minimum 0 and maximum 168), or days (minimum 0 and maximum 365). Automatically attempt to wake up any offline workstations - select this check box to attempt to wake up any offline workstation(s) associated with the tasks.
Restore Defaults - select this option to restore to default settings.
5. Click OK to apply the settings.
Changes to the settings in the Edit Action Behavior dialog will be applied globally to all new and scheduled tasks of the type displayed in the dialog.

Database Tab

The Database tab allows you to configure the database. Complete the following steps to configure the database: 1. In the Console Tree pane, right-click [Core_Server] and select Properties. Select the Database tab.
2. Click Change Settings to change the database connection settings or to connect to a different database server. The following dialog is displayed:
3. Select the database server from the drop-down list. Alternatively, you can enter the name of the database manually. 4. Select Use Windows Authentication or Use SQL Server Authentication as required. 5. If you select Use SQL Server Authentication, enter the User name and the Password for the SQL Server. 6. You can also test the connection to the database server by clicking on Test. This step is optional. 7. Click Apply. Click OK to exit the dialog.

Web Services Tab

The Web Services tab allows you to create a Remote WOL Web Service. For more information on how WOL can be used on your network, refer to Wake-On-LAN. The Remote WOL Web Service allows users to wake up their workstations remotely. This allows remote users to establish a remote connection to workstations. The Remote WOL Web Service requires Internet Information Server (IIS) 7.0 to host the web page. IIS 7.0 runs only on Microsoft Windows Vista, Microsoft Windows Server 2008 and Windows 7. The Web Services tab is displayed only if you have installed the Faronics Core Console on Microsoft Windows Vista or Microsoft Windows Server 2008.

Configuring WOL Web Service
The Web Services Tab provides the following configuration options: 1. Select the Enable Remote WOL Web Service check box. 2. The Configure IIS screen is displayed.
3. Click Install. The packages necessary to run the web page will be installed and enabled on IIS. 4. The following screen is displayed during install. No action is necessary during this step. 5. Once the installation is complete, the following screen is displayed. 6. Click OK. The Web Service URL is automatically entered in WOL Web Services tab after IIS has been configured.
7. The Web Service URL is not editable. The default port number is 81. 8. Select the Allow user to select target from all managed workstations check box to allow the user to select the target from the managed workstations. This feature provides limited security by preventing users from waking up all workstations on the network without knowing the individual workstation IDs.
9. Select the Enable Wakeup API Web Service check box to allow third party applications to integrate with Faronics Core and access the Wake-On-LAN functionality. (If the Enable Remote WOL Web Service check box is not selected earlier, steps 2-5 are performed after selecting the Enable Wakeup API Web Service check box. The Wakeup API Web Service and the Remote WOL Web Service can be used independently). 10. Click OK to exit the dialog.
Sending an Email via the Remote WOL Email Generator
The Remote WOL Email Generator can be used to create and send a reminder email to the users of a particular workstation. The email will have a link to the web site that allows you to wake up the workstations remotely. To send an Email to users, complete the following steps: 1. Select workstation(s) from the list of managed workstations. 2. Right-click and select Create Remote WOL Reminder. The Remote WOL Email Generator dialog is displayed. Click Legend for a list of macros that can be used. Click Save Template to save the current Email as a template for future use. Templates can be saved only in.txt format. Click Load Template to browse and select an existing template.
3. The Email ID and workstation names are automatically entered in the appropriate fields. Enter the message and click Send Email.

Waking up Workstations via the Remote Workstation Wake up Web Interface
Once users receive the email, they can click on the hyperlink to launch the Remote Workstation Wake up Web interface and wake up the workstations remotely. For more information on the URL, refer to step 6 in Configuring WOL Web Service. To wake up the workstations remotely, complete the following steps: 1. Click the hyperlink in the Email. 2. The Remote Workstation Wake up screen is displayed. 3. Select Users Workstations to wake up selected workstations and select the check box for the particular workstation(s). Alternatively, you can select All Managed Workstations to wake up all managed workstations. 4. Click Wake up Selected to wake up the workstations. Click Refresh Event to refresh the web page.
The Remote Workstation Wake up Web interface is displayed only after you have logged on to your corporate Virtual Private Network (VPN) (if a VPN has been set up). The Web Server is installed on the Faronics Core Server and users have to log on to your corporate VPN to wake up the workstations.
The About tab displays the version of Faronics Core installed on your computer. This tab also displays the Loadins installed on the Faronics Core Server.
The Loadins displayed are not part of the Faronics Core installation. Loadins are licensed and installed separately.
Faronics Core Agent Installer
The Faronics Core Agent Installer is used to install the Faronics Core Agent on the workstation. The Faronics Core Agent is used to establish communication between the Faronics Core Console, Faronics Core Server and the Faronics Core Database. This installer must be deployed to the workstations to be managed using Faronics Core Console.
Creating a Faronics Core Agent Installer
To create the Faronics Core Agent installer, complete the following steps: 1. Right-click on the Faronics Core Server connection node and select Create Faronics Core Agent Installer. 2. The Create Faronics Core Agent Installer dialog is displayed with the following options:

Event Reporting Connection This field displays the server to which the workstation communicates. This field cannot be edited. Faronics Core Server Connection This field displays the port on which the Faronics Core Agent listens. The default port is 7751. Wake-on LAN Across Subnets Select this check box if the workstation will act as a Wake-on-LAN (WOL) Relay. Network Traffic Management Select the Max frequency of reports: in minutes and seconds. This is the number of times managed workstations report to the Faronics Core Server. Faronics Core Agent Local Uninstallation Password specify the password that will be required when uninstalling the Faronics Core Agent locally. Specify the values for Password and Confirm Password. This prevents unauthorized removal of Faronics Core Agent from the workstation. StorageSpace (new installs only) Select the drive to be used as the Faronics StorageSpace drive. The Faronics StorageSpace drive cannot be changed once the Faronics Core Agent has been installed. Upgrades to the Faronics Core Agent will automatically use the existing Faronics StorageSpace drive. The default drive letter is V:. Select Automatically select the next available drive letter to automatically select the next available drive, if the drive selected from the drop-down is in use. Reboot after installation Select the Do not reboot the workstation after installing Faronics Core Agent check box to avoid a workstation reboot after installing the Faronics Core Agent. If you select the check box, ensure the workstation is rebooted later. The
reboot is required before the new/updated Faronics Core Agent can take effect on the workstation.
3. Click OK. Browse to select a location for the file.

4. Click Save.

If Deep Freeze is installed on the workstation, the Loadin data is retained in the StorageSpace even after a reboot (when the workstation is Frozen). For more information about DeepFreeze, refer to Deep Freeze Enterprise User Guide available at www.faronics.com/library.

Using Advanced Options

This chapter explains advanced features of Faronics Core.
Faronics Core Security Ports used by Faronics Core Wake-On-LAN

Faronics Core Security

Faronics Core uses Security Certificates to ensure secure communication between the Faronics Core Console, Faronics Core Server and Faronics Core Agent. The Security Certificate consists of the following: Public Key used to Encrypt the communication. Private Key used to Decrypt the communication.
A Public Key and Private Key are always paired. For every Public Key, there is one and only one Private Key. The Faronics Core components have the following: Faronics Core Server Public Key and Private Key Faronics Core Console Public Key Faronics Core Agent Public Key

Displaying Workstations in Faronics Core Console
Once Faronics Core Agent has been installed on a workstation (either via the Faronics Core Console or attended install) it reports to the Faronics Core Server and the workstations list columns are populated with the information in Faronics Core Console.
Changing the Faronics Core Server
Once workstations are managed by a Faronics Core Server, they can be changed to report to a different Faronics Core Server. Conversely, a Faronics Core Server can take over workstations known to be managed by a different Faronics Core Server.

Change Ownership

The ownership of the workstation(s) can be changed from the current Faronics Core Server to a different Faronics Core Server. For example, if the workstations are being managed by Faronics Core Server 1, and the ownership of the workstations need to be changed to Faronics Core Server 2, it can be done as follows: 1. Click Managed Workstations in the Console Tree Pane. 2. Right-click on one or more workstations and select Faronics Core > Change Ownership. 3. In the Change Ownership screen, specify the Name or IP and Port. Select Force ownership change even if the new server cannot be reached if required. (In this case, specify the Name or IP for Faronics Core Server 2). 4. Click Change Ownership. The ownership of the workstation(s) is changed to Faronics Core Server 2.

Take Ownership

The current Faronics Core Server can take ownership of workstations from another Faronics Core Server. For example, if some workstation(s) are currently managed by Faronics Core Server 2, Faronics Core Server 1 can take ownership of the workstations from Faronics Core Server 2. Complete the following steps to take ownership of the workstations: 1. Click Console Tree Pane > Discovered Workstations > Network Workstations> [Network Name]. 2. Right-click on one or more workstations and select Take Ownership. 3. In the Take Ownership screen, specify the Name/IP and Port. (In this case, specify the Name or IP for Faronics Core Server 1). The Name or IP can only be selected from a pre-populated list (one IP address is displayed for each network card on the server). Specify the Port on which the workstations are listening. 4. Click Take Ownership.

Reports under the root node. Faronics Core Console displays reports created by Product Loadins. If no Loadins are installed, no reports can be generated.
Checking For Updates To check for updates, click on the Faronics Core Console node. The Connect to www.faronics.com and check for news and updates must be selected in the Console Tab in the Faronics Core Console properties dialog for a check to succeed. If this box is not selected, clicking on the Faronics Core Console node only displays the current version installed and does not connect to www.faronics.com to check for a newer version. LDAP Groups It is possible to use groups of workstations that already have been defined on a directory server. Once the Faronics Core Agent has been installed on workstations discovered through LDAP, those workstations can be managed directly through the LDAP groups node. These workstations can also be added to custom groups. Custom Workstation Groups Workstations can be added to a custom group by standard Windows clipboard functionality. Cut, copy, or paste (along with drag-and-drop) a workstation into a group. To create a group, right-click on the Custom Workstation Groups icon and select Create Subgroup. You can also add or edit Dynamic Filters via the context menu or Actions pane.
The Workstation List and Tasks are stored on the Faronics Core Server, whereas the Reports are stored locally on the computer where Faronics Core Console is installed.
Faronics Core Console Action Pane
The commands and features available in the right side of Faronics Core Console are also available via a right-click on one or more selected workstations. The Action pane can be removed via View > Customize View. The actions available are based on the privileges of the connected user.
The Faronics Core Console specific tasks are as follows: Shutdown Select one or more workstations to shutdown immediately or later. Restart Select one or more workstations to restart immediately or later. Wake up Select one or more workstations to perform an immediate Wake-On-LAN or later.
Faronics Core Select one or more workstations and select Faronics Core menu. The following options are available: Install Faronics Core Agent to install Faronics Core Agent immediately or later. Upgrade Faronics Core Agent to upgrade Faronics Core Agent immediately or later. Uninstall Faronics Core Agent to uninstall Faronics Core Agent immediately or later.

Generate Report Select one or more workstations and select the appropriate report for the Product Loadin. View Add or Remove columns and Customize View. Refresh Refresh the workstation list. Export List Export the list of workstations in.csv or.txt format. Remove from Database One or more workstations can be removed from the list. The workstation will reappear in the list if it is restarted or if it is trying to send information to the console computer. If the Faronics Core Agent is uninstalled from the workstation, it will not appear in the list. Once the workstation is removed from the database, the workstations data and settings are removed permanently. If the workstation connects to Faronics Core Console, and a new report is generated, it will not contain the details of the workstation before it was removed from the database.
Copy Copy a workstation to paste to a custom workstation group or subgroup.

Manage Users and Roles

Faronics Core Console allows you to configure and manage multiple users. The users can be assigned to different groups depending upon different roles.

Create a User

Complete the following steps to create and manage users: 1. Right-click the Faronics Core Server and select Manage Users and Roles. 2. The User Management dialog is displayed. Click Create User.
3. The Create User dialog is displayed.
Specify values for the following fields: User ID specify a User ID for the user. Password specify a password (the password must be alphanumeric, between 8 to 15 characters, with upper case, lower case and numbers). Re-enter password re-enter the password. Email address enter the email address for the user. User Role for Faronics Core Console select if the user is an Administrator, Power User, User or Guest.
4. Click Create. The user is created.
Permissions for User Roles
The User Roles for Faronics Core Console drop-down in the Create User or Edit User dialogs allow assigning users to users. The following actions are allowed for User Roles Administrator, Power User, User, and Guest: User Role Administrator Permission Power User Manage Users Manage Database Connection Export Private Key at the Server All other actions available to Power Users. Schedule Actions Install/Upgrade/Uninstall Agent All other actions available to members of the User role.

User Role User

Permission Execute Basic Tasks (shutdown/restart) Schedule Actions Wake-up workstation Generate Reports All other actions available to members of the Guest role. View all workstations Generate Reports for the Loadins (if Loadins are installed)

The users in the User role can only edit or delete the Scheduled Tasks created by them. The Administrators and Power Users can edit or delete all tasks.
If a user is downgraded from a higher role (for example, Power User) to a lower role (for example, User), the Scheduled Tasks created by the user will not be executed. If a user is deactivated, the Scheduled Tasks created by the user will not be executed.
When Loadins are installed, existing users must be assigned to new Loadin-specific roles.

Edit a User

Once a user has been created, the credentials can be edited as required. Complete the following steps to edit a user: 1. Right-click the Faronics Core Server and select Manage Users and Roles. 2. The User Management dialog is displayed. Select the user to edit and click Edit User.
3. The Edit User dialog is displayed.
Edit the values for the following fields as required: User ID specify a User ID for the user. Password specify a password (the password must be alphanumeric, between 8 to 15 characters, with upper case, lower case and numbers). Re-enter password re-enter the password. Email address enter the email address for the user. User Role for Faronics Core Console select if the user is an Administrator, Power User, User or Guest.
4. Click OK. The user is edited. Click Close.
Activate or Deactivate a User
Users can be activated or deactivated via Faronics Core Console. Users deactivated will not be able to perform any actions on Faronics Core Console. Deactivated users can be activated as required. Complete the following steps to edit a user: 1. Right-click the Faronics Core Server and select Manage Users and Roles. 2. The User Management dialog is displayed. Select the user. Activate select the Active check box to activate the user. Deactivate clear the Active check box to deactivate the user.
If a user is deactivated, the Scheduled Tasks created by the user will not be executed.
Custom Workstation Groups
Faronics Core Console allows you to create Dynamic Custom Workstation Groups, Static Custom Workstation Groups and Mixed Custom Workstation Groups. Installing certain Product Loadins may automatically create Dynamic Custom Workstation Groups under the Product Loadin in the Console Tree pane. These groups are specific to the particular Product Loadin. Some groups created by the loadin can be edited and some are read-only depending on the Product Loadin that has created the group. Refer to the user guide for the Product Loadin for more information.

Multiple Core Agents report to the Faronics Core Server they are configured for. The Core Severs are managed via Faronics Core Console 1 and Faronics Core Console 2. Faronics Core Console 1 and Faronics Core Console 2 can manage Faronics Core Sever 1 and Faronics Core Server 2. The Faronics Core Server 1 and Faronics Core Server 2 store the information about workstations in the database.
104 Appendix B Single Subnet Multiple Core Servers

Appendix C

Multiple Subnet Multiple Core Servers
The following diagram shows the architecture of Faronics Core running on a Single Subnet and with multiple Faronics Core Servers.
The above architecture has the following components: Faronics Core Server There are two Core Servers in this setup, Faronics Core Server 1 and Faronics Core Server 2. Faronics Core Console Multiple Core Consoles connect to the both Core Servers. Faronics Core Console 1, Faronics Core Console 2 and Faronics Core Console 3. Database There are two databases, one for each subnet. Faronics Core Agent There are multiple workstations with the Faronics Core Agent installed.
Subnet 1: Multiple Core Agents report to Faronics Core Server 1. The Core Sever is managed via Faronics Core Console 1. Faronics Core Server 1 stores the information about workstations in Database 1. Subnet 2: Multiple Core Agents report to Faronics Core Server 2. The Core Sever is managed via Faronics Core Console 2. Faronics Core Server 2 stores the information about workstations in Database 2. Faronics Core Console 3 can connect to both Faronics Core Server 1 and Faronics Core Server 2 and manage the workstations on Subnet 1 and Subnet 2.

Faronics Core Migration Guide
Last modified: November, - 2009 Faronics Corporation. All rights reserved. Faronics, Deep Freeze, Faronics Core Console, Faronics Anti-Executable, Faronics Device Filter, Faronics Power Save, Faronics Insight, Faronics System Profiler, and WINSelect are trademarks and/or registered trademarks of Faronics Corporation. All other company and product names are trademarks of their respective owners.

Contents

Preface. 5
Important Information. 6 About Faronics. 6 Product Documentation. 6 Technical Support. 7 Contact Information. 7 Definition of Terms. 8

Introduction. 9

Migration Overview. 10 Faronics Core Console 2.x. 10 Faronics Core 3.x (FC3). 10 Migration Steps. 11 Migration Tool. 12

Migration. 13

Faronics Core Installation. Installing Faronics Core 3.x. Configuring the Core Database. Installing the updated product loadin on Faronics Core 3.x. Installing updated Core Agent and Product Agents Push from Core Console (FC3). Manual Deployment. Push using 3rd Party Tools. 19 19
Database Event Migration. 20 Event Migration Using the Migration Tool. 20 Manual Migration of Database Events. 21 Migrate the Core Console Tasks, Reports, Groups, and Filters. 22
Appendix A Creating the Core Agent. 23 Appendix B Moving the Core Console 2.4 database. 25
Backing up Faronics Core Console 2.x Database. 26 Restoring the Faronics Core Console 2.x database into Faronics Core 3.x (Core Database). 29
Faronics Core Migration User Guide

Preface

This document explains the process of migrating the data from Faronics Core Console 2.x to Faronics Core 3.x.

Topics

Important Information Technical Support Definition of Terms

Important Information

This section contains important information about your Faronics Product.

About Faronics

Faronics delivers market-leading solutions that help manage, simplify, and secure complex IT environments. Our products ensure 100% machine availability, and have dramatically impacted the day-to-day lives of thousands of information technology professionals. Fueled by a market-centric focus, Faronics technology innovations benefit educational institutions, health care facilities, libraries, government organizations, and corporations.

Product Documentation

The following documents form the Faronics Core documentation set: Faronics Core User Guide This document guides you how to use the product. Faronics Core Release Notes This document lists the new features and known issues and closed issues. Faronics Core readme.txt This document will guide you through the installation process. Faronics Core Migration Guide This document will guide you through the migration process.

Technical Support

Every effort has been made to design this software for ease of use and to be problem free. If problems are encountered, contact Technical Support: Email: support@faronics.com Phone: 800-943-6422 or 604-637-3333 Hours: 7:00am to 5:00pm (Pacific Time)

Contact Information

Web: www.faronics.com Email: sales@faronics.com Phone: 800-943-6422 or 604-637-3333 Fax: 800-943-6488 or 604-637-8188 Hours: 7:00am to 5:00pm (Pacific Time) Address: Faronics Technologies USA Inc. 2411 Old Crow Canyon Road, Suite 170 San Ramon, CA 94583 USA Faronics Corporation 609 Granville Street, Suite 620 Vancouver, BC V7Y 1G5 Canada

Definition of Terms

Term Core Console Core Database Core Agent Core Server Faronics Core 3.x (FC3) Loadin MAC
Definition The user interface used to manage and monitor Core Servers and workstations. The database stores the workstation list. The Core Agent, that is installed on the workstation, enables communication between the workstation and the Core Server. The management of workstations, processing of tasks and communication between Core Console and workstations is done by the Core Server. Faronics Core consists of the Core Server, Core Console, Core Database and the Core Agent. A Product Loadin is a software library that adds new product-specific functionality to Faronics Core. A Media Access Control address (MAC address) or Ethernet Hardware Address (EHA), hardware address, adapter address or physical address is a quasi-unique identifier assigned to most network adapters or network interface cards (NICs) by the manufacturer for identification. If assigned by the manufacturer, a MAC address usually encodes the manufacturer's registered identification number. User Account Control (UAC) is a technology and security infrastructure introduced with Microsoft's Windows Vista operating system. It aims to improve the security of Microsoft Windows by limiting application software to standard user privileges until an administrator authorizes an increase in privilege level. Wake-on-LAN (WOL) is an Ethernet computer networking standard that allows a computer to be turned on or woken up remotely by a network message.

Wake-on-LAN

Introduction
This chapter introduces the migration process and the Migration Tool.
Migration Overview Migration Steps Migration Tool

Migration Overview

Faronics Core Console 2.x and Faronics Core 3.x have different architectural designs. Therefore, installing Faronics Core 3.x will not upgrade Faronics Core Console 2.x installation on your system. Faronics Core 3.x will be installed separately on the same system. Faronics Core 3.x can also be installed on a different system. Following are the components of Faronics Core Console 2.x and Faronics Core 3.x.
Faronics Core Console 2.x
Faronics Core Console 2.x has the following components: Faronics Core Console The user interface used to manage and monitor workstations. The management of workstations, processing of tasks and communication with workstations is done by Faronics Core Console. Database The database stores the workstation list and information about the workstation. Core Agent The Core Agent, that is installed on the workstation, enables communication between Faronics Core Console and workstations.

Faronics Core 3.x (FC3)

Faronics Core has the following components: Core Console (UI Tier) The user interface used to manage and monitor Core Servers and workstations. A single instance of Core Console can connect to multiple Core Servers. Core Server (Logic Tier) The management of workstations, processing of tasks and communication between Core Console and workstations is done by the Core Server. Core Database (Data Tier) The database stores the workstation list and information about the workstation. Core Agent The Core Agent, that is installed on the workstation, enables communication between the workstation and the Core Server.

Migration Steps

Faronics Core 3.x is a significant architectural improvement of the existing Faronics Core Console 2.x platform to deliver enhanced security and greater scalability. Due to the improvements which now leverage a multi-tier architecture, upgrading to the Faronics Core 3.x will require a migration process that follows the basic steps outlined below: 1. Install Faronics Core 3.x. Refer to the Faronics Core User Guide available at http://www.faronics.com/library for more information. 2. Install the updated product loadins to Faronics Core 3.x. Refer to the specific product loadins available at http://www.faronics.com/library for more information. 3. Install or upgrade the updated Core Agent to the client workstations. Refer to the Faronics Core User Guide available at http://www.faronics.com/library for more information. 4. Install the updated product agents to the client workstations. Refer to the specific product loadins available at http://www.faronics.com/library for more information. 5. Migrate the Faronics Core Console 2.x tasks to Faronics Core 3.x. This is explained in this document. This step is optional. 6. Migrate the workstation event data from Faronics Core Console 2.x database to the Faronics Core 3.0 database (Core Database). This is explained in this document. This step is optional. The above process remains the same regardless of if the Faronics Core Console 2.x data is being migrated on an existing server or being setup on an entirely new hardware. In the event that Faronics Core 3.x is being configured on new hardware, either the Core Database (FC3) must be configured on the same SQL instance as the existing Faronics Core Console 2.x database, or the Faronics Core Console 2.x database must be moved to the new SQL instance where Core Database (FC3) will be installed.

Migration Tool

To aid in the migration process, Faronics has provided a migration tool that can be used to migrate the workstation event data and other non-event based user data to Faronics Core 3.x. This tool is not localized and will display all output in English. The tool is located in the following location: C:\Program Files\Faronics\Faronics Core 3\Console\Faronics Core Migration Tool or C:\Program Files (x86)\Faronics\Faronics Core 3\Console\Faronics Core Migration Tool The Migration tool can move the following data: Non-event user data: Scheduled Tasks (Faronics Core Console 2.x tasks as well as Product Loadin tasks) Custom Workstation Groups Reports Workstation Event Data for all products. Prior to launching the tool, all instances of Core Console and the Core Server must be shut down. Instructions on using the utility can be found in the Database Event Migration and Migrate the Core Console Tasks, Reports, Groups, and Filters sections of this document.
If migration tool is used on a computer with only Core Console installed, only the Reports are migrated.
LDAP connections and tasks in the History are not migrated.

Migration

This chapter describes the migration process.
Faronics Core Installation Installing updated Core Agent and Product Agents Database Event Migration Event Migration Using the Migration Tool
Faronics Core Installation
Installing Faronics Core 3.x
Faronics Core 3.x can be installed on either a new server or on the existing Faronics Core Console 2.x system. For larger deployments it is recommended to use a new server to deploy Faronics Core 3.x as this will provide the most flexibility. (Refer to the Faronics Core User Guide available at http://www.faronics.com/library for more information.)
Configuring the Core Database
After installation, it is recommended that the following changes be implemented on the database used by the Core Server: 1. Launch the SQL Server Management Studio. 2. Select the Database Properties of the database to be altered. 3. Click the Files node on the left side of the properties dialog.
4. Edit the following settings: Set the database (FaronicsCore.mdf) to grow in 100mb increments as required. Do not alter the Autogrowth settings for the log file (FaronicsCore.ldf).
Change the initial size of the database to 100mb larger than the existing FaronicsEnterpriseDatabase used for Faronics Core Console 2.x.
Installing the updated product loadin on Faronics Core 3.x.
A Product Loadin should be installed and updated as per the instructions in the Loadin user guide. Once installed, further steps may be required to complete the update process and enable full control of the products in Faronics Core 3.x. (Refer to the specific Product Loadins available at http://www.faronics.com/library for more information.)
Installing updated Core Agent and Product Agents

Push from Core Console (FC3)
To perform a push to a client workstation from the Core Console (FC3) follows the procedure below: 1. Browse and select the workstation listed in the Discovered Workstations node of the Core Console (FC3).
2. Select the workstation to push the installation to and right-click to select Install Faronics Core Agent.
3. Configure the options listed in the Configure Agent dialog box as shown and click Next.
4. Enter the credentials that will be used to perform the remote installation. It is recommended to use domain credentials. Click OK to begin the installation.
5. During installation, the task progress will be displayed in the Tasks node of the Core Console (FC3). When installation is complete, check task history to determine if the installation was successful.

Manual Deployment

The Core Agent can be deployed manually by copying the installation package to the local system and executing the MSI installer package following the prompts provided on screen. The process of creating the Core Agent is described in Appendix A, Creating the Core Agent.
Push using 3rd Party Tools
The Faronics Core Agent is packaged as a standard MSI file that can be pushed using any 3rd party management utility. The process of creating the core agent for deployment is detailed in Appendix A, Creating the Core Agent.

Database Event Migration

In most cases, administrators will not need to move the database between Faronics Core Console 2.x and Faronics Core 3.x. The majority of the database is made up of status tables that reflect the current state of the workstations and these are rebuilt as workstations report into the new Faronics Core 3.x installation. In the event that there is a need to preserve the historical event data between the Faronics Core Console 2.x and Faronics Core 3.x installations the process below will allow administrators to do so. The process is as follows: 1. Backup the Faronics Core Console 2.x database. This is explained in Backing up Faronics Core Console 2.x Database. 2. Restore the Faronics Core Console 2.4 database into the instance of SQL in use by the Core Database (FC3). This is explained in Restoring the Faronics Core Console 2.x database into Faronics Core 3.x (Core Database). 3. Migration of the historical event data to the new database. This step is explained in this section. There are two methods for the migration of the data; either using the Faronics Core Migration Tool, or manually by using the SQL command.

Event Migration Using the Migration Tool
To migrate the data using the Migration tool run the following commands: NET STOP FaronicsCoreEventReceiver NET STOP FaronicsCoreService NET STOP "Faronics Core 3 Event Receiver" C:\Program Files\Faronics\Faronics Core3\Console\Faronics Core Migration tool\FaronicsCoreMigrationTool.exe /t NET START FaronicsCoreEventReceiver NET START FaronicsCoreService NET START "Faronics Core 3 Event Receiver" This command will transfer the event data for all workstations between the Core Console 2.4 database and the Faronics Core 3.0 database. If required, you can select to only move the data for the workstations that are currently managed by Faronics Core 3.0 by specifying the /m switch at runtime as below: NET STOP FaronicsCoreEventReceiver NET STOP FaronicsCoreService NET STOP "Faronics Core 3 Event Receiver" C:\Program Files\Faronics\Faronics Core3\Console\Faronics Core Migration tool\FaronicsCoreMigrationTool.exe /t /m NET START FaronicsCoreEventReceiver NET START FaronicsCoreService NET START "Faronics Core 3 Event Receiver" This utility assumes that both databases are in the same instance. If they are not, the Faronics Core Console 2.x database must be moved to the same SQL instance as the Core Database (FC3).
Manual Migration of Database Events
Once the database is restored, the following SQL statement can be used to move the historic log event data from one database to the other (if you do not want to move the data using the Faronics Core Migration Tool). This command assumes both databases exist in the same instance of SQL and that the appropriate rights exist to move the data between both databases. insert into FaronicsCore.dbo.tbl_LogEvents (MachineId, ActionEventId, ProductId, LogTime, ExtraDataGuid) (select MachineId, ActionEventId, ProductId, LogTime, ExtraDataGuid from FaronicsEnterpriseDatabase.dbo.tbl_LogEvents) DBCC DBREINDEX(tbl_logEvents) insert into FaronicsCore.dbo.tbl_LogExtraData (ExtraDataGuid, XMLData) (select ExtraDataGuid, XMLData from FaronicsEnterpriseDatabase.dbo.tbl_LogExtraData) DBCC DBREINDEX(tbl_logExtraData)
Migrate the Core Console Tasks, Reports, Groups, and Filters
Faronics Migration Tool has the ability to export the existing groups, tasks, reports, and filters from Faronics Core Console 2.x. When run on the Faronics Core Console 2.x, it will generate a ZIP file that can be transferred to the Core Server (FC3) and imported. To Export the data run the following commands on the Core Console 2.4 Server: NET STOP FaronicsCoreEventReceiver NET STOP FaronicsCoreService NET STOP "Faronics Core 3 Event Receiver" C:\Program Files\Faronics\Faronics Core3\Console\Faronics Core Migration tool\FaronicsCoreMigrationTool.exe /e data.zip NET START FaronicsCoreEventReceiver NET START FaronicsCoreService NET START "Faronics Core 3 Event Receiver"

To import the data copy the file created during the export into the C:\Program Files\Faronics\Faronics Core3\Console\Faronics Core Migration tool folder and run the following commands: NET STOP FaronicsCoreEventReceiver NET STOP FaronicsCoreService NET STOP "Faronics Core 3 Event Receiver" C:\Program Files\Faronics\Faronics Core3\Console\Faronics Core Migration tool\FaronicsCoreMigrationTool.exe /i data.zip NET START FaronicsCoreEventReceiver NET START FaronicsCoreService NET START "Faronics Core 3 Event Receiver" It is recommended that the computer running the Core Server (FC3) be rebooted once the import is complete.

Appendix A

Creating the Core Agent
Creating an updated Core Agent MSI installer is only required in the event that the software is deployed using a 3rd party utility. In the event that the software is deployed using a 3rd party tool, follow the steps listed below to generate an updated install package. 1. Right-click on the server node in the Core Console (FC3) and select Create Core Agent Installer.
Appendix A Creating the Core Agent
2. In the dialog displayed, ensure that the name of the Core Server (FC3) is correct and the appropriate port is listed. If the workstation is to be a Wake-On-LAN Relay ensure that the Workstation will act as a Wake-on-LAN (WOL) Relay option is selected.
3. Click OK. 4. Save the Core Agent installer package in an accessible location on the hard disk.
Once the Core Agent is saved, it is ready for deployment on the client workstations.

Appendix B

Moving the Core Console 2.4 database
There are two steps involved in moving the Faronics Core Console 2.x database to Faronics Core 3.x (Core Database): 1. Backing up Faronics Core Console 2.x Database 2. Restoring the Faronics Core Console 2.x database into Faronics Core 3.x (Core Database)
Appendix B Moving the Core Console 2.4 database
Backing up Faronics Core Console 2.x Database
Before beginning the update process, it is recommended that the database be backed up for recovery purposes. The following process details the process of backing up the database using the Microsoft SQL Server Management studio. 1. Launch the SQL Server Management Studio 2. Expand the databases node to show the Faronics Enterprise Database.
3. Right-click on the Faronics Enterprise Database and select Tasks> Back Up.
4. In the Wizard that appears, ensure that the database is correct and that the backup type is listed as FULL. In the Destination field, make note of the path and file name being used to back up the database.

5. Click on OK to begin the backup.
6. When the backup is successful, click OK in the notification dialog.
7. Close the SQL Server Management studio. 8. Browse to the location where the backup was saved.
9. Copy the backup file to a safe location on another system or on removable media.
Restoring the Faronics Core Console 2.x database into Faronics Core 3.x (Core Database)
Complete the following steps to restore the database backed up in the previous section: 1. Launch the SQL Server Management Studio. 2. On the Databases node, right-click and select Restore Database.
3. In the Restore Database wizard, select the option to restore From Device and then click on the selection button.
4. In the file selection dialog, select the backup of the Faronics Enterprise Database (backup that was taken as explained in the previous section) by clicking the Add button.
5. Browse to the backup file and click on OK, and then click OK again.
6. Once you are back to the Restore Database wizard click on the To Database option in the destination for restore and select FaronicsEnterpriseDatabase.
7. Click on the restore button under the Backup sets to restore pane and click OK.
8. Once the restore is complete the database will be displayed in the Management Studio along with the existing databases for Faronics Core 3.x.