Brüel & Kjær Pulse 20.0 Product Support Changes Please note: PULSE 18 was the last release to support mixed-mode operation (LAN-XI and IDAe) PULSE 18 was the last release to support Windows® XP From PULSE 19, IDAe Module Types 3030, 3032-A, 3032-B, 7533-001 and 7533-003 are no longer supported PULSE 20 will be the last version to support Windows® 7 (x32) Back to top Installation Installing PULSE This will install a 32-bit version of PULSE LabShop and applications. If you already have a PULSE version installed, you must uninstall it first. Uninstallation of the software does not uninstall any auto-installed databases or servers. Installing from the installation USB key: Note that with node-locked licenses, the license is automatically installed after software installation. Floating licenses are not automatically installed. See Installing Licenses below for more information. To install PULSE: If your license is node-locked to the dongle, insert the dongle to another USB port. Click Install to start installation. Follow the on-screen instructions. During installation you have the option to install one or more database engines. To use PULSE Data Manager (PDM) databases, this is required. Ensure that at least the SQL Server 2012 Express is selected. After server installation, a reboot prompt may appear. To ensure smooth handling of licenses, we recommend to wait to reboot. During installation with custom settings, there is an option to change the location of the databases and the filefarms. When making changes to these settings, please keep the following in mind: When relocating PULSE File Farm to another folder, the newly specified folder must be named "BKFileFarms" in order to make it work Backup and remove existing databases before changing locations. Never use mixed locations for databases and filefarms. If databases are already present on the PC, make a backup of every database and then disconnect or delete the databases using PDMTools. Backups can be restored after the custom installation is completed and will be automatically updated with the new database and filefarm location upon restoring. Click Finish. You will see this installer window again. Look through the Readme file for information on new features, tips, troubleshooting and latest fixes. Click Exit to close the installer. If you have installed a new database, you may want to restart your PC before opening PULSE. Installing from a downloaded PULSE: If your license is node-locked to a dongle, the dongle should be disconnected during installation. After installing PULSE Reflex, insert the dongle. The dongle will blink for up to 30 seconds while it is updated. Once updated the dongle should light continuously. See the troubleshooting section if the dongle does not update correctly or stop blinking. To install PULSE Reflex: Extract the zip file. Run "Setup.exe" from the folder to which the data was extracted. Select PULSE Reflex and click Install to start installation. Follow the on-screen instructions. During installation you have the option to install one or more database engines. To use PULSE Data Manager (PDM) databases, this is required. Ensure that at least the SQL Server 2012 Express is selected. After server installation, a reboot prompt may appear. During installation with custom settings, there is an option to change the location of the databases and the filefarms. When making changes to these settings, please keep the following in mind: When relocating PULSE File Farm to another folder, the newly specified folder must be named "BKFileFarms" in order to make it work Backup and remove existing databases before changing locations. Never use mixed locations for databases and filefarms. If databases are already present on the PC, make a backup of every database and then disconnect or delete the databases using PDMTools. Backups can be restored after the custom installation is completed and will be automatically updated with the new database and filefarm location upon restoring. Click Finish. You will see this installer window again. Look through the Readme file for information on new features, tips, troubleshooting and latest fixes. Click Exit to close the installer. If you have installed a new database, you may want to restart your PC before opening PULSE. Installing Databases During installation, the Database Engine Installer tool helps you install Microsoft® SQL Server® and set it up for use with PULSE Data Manager (PDM). This is required with PDM. You can use either SQL Server Express or SQL Server Standard edition If you have SQL Server Standard Edition or SQL Server Express already installed, the tool can simply set these up for use with PDM and/or PULSE Reflex. If your current SQL Server Express is an older version, the tool can upgrade it to the latest supported version. Installation of SQL Server 2012 Express (SP2) SQL Server 2012 Express (SP2) is included in the installation. In some cases, however, you may not have the required privileges, or a reboot may be required. If a reboot is required, you will see the message: Reboot required If you do not have the required privileges, you will see a message stating: Privilege "xxxx" missing. where xxxx is one of the following: seSecurityPrivilege seBackupPrivilege seDebugPrivilege In these cases, the install user executing the SQL Server installation must be assigned the required user rights before running the installation. If the PC is a member of a domain, you should ask your IT administrator if the required user rights should be defined by group policies, or if you should define the user rights using the Local Group Policy Editor: Enter gpedit.msc in a command prompt to open the Local Group Policy Editor. Navigate to Local Computer Policy > Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment. Check that the install user or a group including the install user is included in the Security Setting for these policies: Manage auditing and security log - seSecurityPrivilege Back up files and directories - seBackupPrivilege Debug programs - seDebugPrivilege If you can, double-click on the item to bring up its Properties and correct the setting. Otherwise, contact your IT administrator to obtain the necessary privileges. Group policies overwrite local policies.