Blog

NTFS Circular Reference

Tuesday, February 5th, 2013

Redirected to http://kb.acronis.com/content/39356

Microsoft NTFS Circular Reference Hotfix

Wednesday, January 30th, 2013

Redirected to http://kb.acronis.com/content/39356

Configuring Kerberos for ExtremeZ-IP Network Reshare

Wednesday, November 7th, 2012

Redirected to http://www.acronis.com/en-us/support/documentation/ExtremeZ-IP/index.html#30099.html

mobilEcho supports iOS 6; iPhone 5 screen enhancement coming soon

Tuesday, October 16th, 2012

The current mobileEcho 4.0.1 release in the App Store is compatible with Apple’s new iOS 6 operating system for iPad and iPhone. Our upcoming mobliEcho 4.1 release will also be updated to take advantage of the extra vertical space on the iPhone 5 so there’s more room for secure mobile file management, previewing and annotation.

We’ll be submitting mobilEcho 4.1 to the App Store in a few weeks and expect it to be available in November.

Configuring Network Reshare support in ExtremeZ-IP

Wednesday, June 6th, 2012

After Downloading A File From The Server, The Client Repeatedly Uploads The Same File

Monday, June 4th, 2012

Symptom: After a file is downloaded to the activeEcho client on a Windows XP or Windows 2003 computer it is uploaded again, in some cases multiple times, creating a new revision each time.

Reproduction steps:

  1. Connect to a Windows XP or Windows 2003 activEcho client to the activEcho server.
  2. Log in to your activEcho server and upload a file to the server using the web interface.
  3. Wait until the file is downloaded to the Windows XP or Windows 2003 computer running the client.

Cause: This is caused by Windows Security Essentials.  On Windows XP and Windows 2003, the Windows Defender component of Windows Security Essentials scans files in the system and overwrites data in the file.  The activEcho client and other tools can’t differentiate this change from legitimate data updates in the file system monitoring service.

Solution: This only occurs on Windows XP and Windows 2003.  Excluding the activEcho folder from the real-time download scanning in Windows Defender should eliminate or at least alleviate this problem.

Backup and restore of iOS devices running mobilEcho 3.5, 3.5.1, and 3.5.2

Monday, March 19th, 2012

Versions 3.5, 3.5.1, and 3.5.2 of the mobilEcho iOS app use an encrypted database to manage the files stored within the mobilEcho app’s on-device storage. The information required to access this database is stored in the iOS keychain. For security reasons, mobilEcho’s keychain items are not restored to the new device during the backup and restore process.

When this method of backup and restore to a new device is performed with a device that has mobilEcho 3.5, 3.5.1, or 3.5.2 installed and configured, the keychain item required to open the encrypted file database is not restored to the new device. This causes mobilEcho to be unable to access the restored file database and the on-device files it manages.

A workaround for this limitation of the ‘backup and restore to new device’ process will be included in mobilEcho 3.5.3, and all future versions of mobilEcho.

To work around this mobilEcho / iOS backup and restore situation:

1. Backup any needed local files to a server-based location before moving to your new device.

  • If you have already restored to a new device using a standard iTunes backup and restore process, mobilEcho will not function properly on the new device and will not include the on-device files from your old device. If you still have your old device, you will need to use that device to save your files to a server-based location, so they can be downloaded to mobilEcho on your new device.

2. Remove mobilEcho from the new device, reinstall, and reconfigure.

  • Tap and hold the mobilEcho app icon. Once it appears, tap the “X” in the corner of the app icon to remove the app.
  • Visit the App Store and install mobilEcho again: http://itunes.apple.com/us/app/mobilecho/id429704844?mt=8
  • Add your mobilEcho server(s) within the app, or if you are using a managed mobilEcho client, request a new enrollment invitation from your IT administrator and follow the included instructions to reenroll your mobilEcho client app. This enrollment process will reconfigure all the servers and folders that you previously had access to.
  • You can now copy the files you backed up to the server back down to the new device using the mobilEcho app.

mobilEcho compatibility with the new iPad (updated)

Friday, March 16th, 2012

To use mobilEcho on the new iPad (third generation), please update to the latest version through the App Store. We added support for the new iPad in version 3.5.2 on March 17, 2012.

If you have any questions or find any issues, please open a support case at http://support.grouplogic.com/request.

How can I set mobilEcho and activEcho to listen on the same port (multi-homing)?

Tuesday, March 13th, 2012

Question:

How can I set mobilEcho and activEcho to listen on the same port on one computer?

Answer:

If activEcho and mobilEcho are installed on one computer, they can both listen on the same port (e.g. 443) only if they are bound to different IP addresses (multi-homing).

Follow the steps below:

  1. Open a Command Prompt and type the following line for each IP address that will be used. Replace the <ip address> part with the corresponding IP address.
    • on Windows Server 2008:
      netsh http add iplisten <ip address>
    • on Windows Server 2003:
      httpcfg.exe set iplisten -i <ip address>
  2. Open the Registry Editor (Start -> Run -> regedit) and navigate to the following path:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\mobilEcho\Parameters4\NonRefreshable
  3. Double click on IPAdress. An Edit Multi-String window opens.
  4. In the Value Data field type the IP address that will be used for connections to mobilEcho.
  5. Click OK.
  6. Close the Registry Editor and navigate to C:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\conf
  7. Open the server.xml file with Notepad.
  8. Find the following line:

    <Connector port=”443″ maxHttpHeaderSize=”8192″

    Note: If you have already changed activEcho’s port, the new port number will be written instead of 443.
  9. Add the red text as in the example below. Replace the <IP address> part with the IP address that will be used for connections to activEcho.

    <Connector port=”443″ address=”<IP address>” maxHttpHeaderSize=”8192″

    Note: If you want to use a port other than 443, replace the port number now. 443 is the default HTTPS port, so if you change it, the new port will have to be appended to the server URL when accessing the servers.

    mobilEcho’s port can be changed from mobilEcho Administrator -> Settings

  10. Save and close the server.xml file.
  11. Stop the mobilEcho service.
  12. Restart Tomcat.
  13. Start the mobilEcho service.

For additional technical notes, please check our online documentation.

How can I change the location of activEcho’s FileStore?

Tuesday, March 13th, 2012

Question:

How can I move the FileStore to a non-default location?

Answer:

To change the location of activEcho’s FileStore, follow the steps below:

  1. Stop the “activEcho Repository” service.
  2. Stop the “Apache Tomcat” service.
  3. You will find the current FileStore here:
    C:\Program Files (x86)\Group Logic\activEcho Server\FileStore”
  4. You can copy or move the entire FileStore folder with all its contents to the target point, like:
    E:\MyCustom Folder\FileStore
  5. Open a Command Prompt window.
  6. Change Directory to the activEcho Server directory, like:
    cd “C:\Program Files (x86)\Group Logic\activEcho Server”
  7. At the Command Prompt, run the following command:
  8. aE_Config.bat "D:\MyCustom Folder\FileStore" 5787

    Note: There is a SPACE between the closing double quote and 5787
    Note:
    You can check which port is the FileStore currently using. Open the webUI, go the Settings tab and find the FileStore repository service setting (e.g. http://127.0.0.1:5787) from which you can verify the current port number (e.g. 5787).
  9. Wait for the command to complete. It takes 2 or 3 seconds.
  10. Start “activEcho Repository” service.
  11. Start “Apache Tomcat” service.
  12. Done.

For additional technical notes, please check our online documentation.