What’s new, and what to do:
Moving from File System Factory 3.1.1 to Senergy 4.0
Obviously, there is a name change. Senergy has all the same (existing) features that File System Factory has. It is the next version of FSF for AD. More details on this can be discovered here.
Other than the name, the biggest change is the back-end database. Previously, FSF used SQLite. Senergy uses Microsoft SQL 2012, or 2014. If you don’t have this product, you can use Microsoft SQL Express which is free. Either version will provide the full functionality that Senergy needs.
Other new features in Senergy include
- Search fields – Now you can search for or go directly to an object without having to browse to an object. This is especially helpful when you don’t know the FDN, or when you have large numbers of objects in one container.
- Redrive management actions – When you run a management action or consistency check, you can select items from the results list, and add them back to the “Take Action – Target List.” This facilitates performing actions on a sub-set of objects when it is not necessary to act on the full list.
- No-identity file migration – You can use this option to move or copy a folder with all its rights and trustees, but without it having to be associated to a directory object.
In addition to these features, Senergy has a framework for data management across platform types. The first of these new supported platforms is SharePoint Online in Office 365. The separately-purchased Senergy Pak for Education uses the Senergy Engine, Event Monitor, and Agents to automatically provision SharePoint Online class sites according to group membership in Active Directory.
Pre-requisites for moving to Senergy from File System Factory
- The Engine will need to be installed on Server 2008 R2 or newer. If upgrading from FSF 3.1.1, you can install Senergy on the same engine server, or on a different server.
- 32-bit Agents are no-longer included. Data stored on 32-bit systems can be managed by setting up proxy agents for those systems.
- All components (Engine, Agent, Event and Admin) require .Net 4.5.1 which can be downloaded from Microsoft here. (This installation often requires a reboot.)
- One of the following Microsoft SQL Server platforms is required:
- SQL Express 2012 or 2014 on same server as FSF 3.1.1 engine.
- SQL Express 2012 or 2014 on a separate server.
- SQL Server 2012 or 2014 on same server as FSF 3.1.1 engine (this is not recommended for performance reasons.)
- SQL Server 2012 or 2014 on a separate server.
What to do next
Videos and documentation are available to help you with the move from File System Factory to Senergy. Or, if you prefer, Condrey Corporation Technical Support is happy to set up a session with you to walk through the process. We recommend a two-hour time allotment for this.
You can get started with any or all of the following steps:
Make an appointment with Condrey Corporation Support if you would like us to walk through the process with you. You can email us at email@example.com, or call us at (864) 329-8528 x 1.
Decide where you engine will be – either on the same box as your current installation of FSF or on a new server.
Decide if you are using an existing MS SQL or installing MS SQL Express. We do not recommend you have the engine on the same server as your MS SQL. If you are using Express, you can run it on the same box as your engine, but you may experience better performance if they are separate. You can download Express from Microsoft (SQL Express 2012), (SQL Express 2014) . (We recommend SQLEXPRWT_x64_ENU.exe as that package includes Management tools.)
Install your SQL choice. Documentation for installing SQL to meet Senergy requirements is here.
Request a license for Senergy. Current FSF customers, if you are close to your renewal, we may have one ready for you.
Download the Senergy software. We try to have the latest software available here, but feel free to check with us.
You can get a jump on the process by installing the event monitor. Run the configuration and start the service, and it will begin the process of building partial replicas that it needs to be able to act on events as they come in. This is sometimes a long process (depending on how many objects are in your AD and how long it has been around) and installing it in advance can allow it to be ready when you install the other pieces.