Skip to main content
Content Starts Here Search Solutions

Solution Detail

 
Solution TitleWhat's new in Switch 12 update 1?
Solution Number00000442
Solution Details

Changed behavior

The Heartbleed leak is fixed. To still give older clients (including connection via Connect) the possibility to connect to Switch 12 update 1, we added a new preference to Switch. Before you use this setting, please read this article in our knowledge base.

If you set the new preference "Allow older client applications to connect (less secure)" to “Yes,” Switch uses the older SSL certifications for HTTPS communication with Switch Client and Switch Designer. 

This type of connection is less secure, but required if you want to connect Switch Server to Switch Client versions older than Switch 12 update 1. If this preference is set to “No” (default), Switch is only able to connect to Switch 12, update 1 Clients and higher, and uses the latest SSL certifications for HTTPS communication with Switch Client and Switch Designer.


Issues solved

Problems while using the User Pane

  • When adding/removing/editing users in the User Pane and/or switching to the User Pane.
  • When running large flows (each containing over 25 configurators/scripted tools) in combination with a large amount of jobs being processed at the same time.


Problems with Script Executors

  • The problem is related to sub flows caching in ScriptExecutors. When the cache reaches its limit and is cleared, Switch may crash.


Problems when updating Configurators via PackManager

  • Some older configurators were only shown if you enabled ‘show packs for non-installed applications.’ These configurators did not have the option to be updated when new versions were available.


Bug Fixes

Number Description
30760Crashes in User pane
30865Crashes in Switch 12 Script Executors
30126Not possible to update some configurators via Pack Manager with Switch 12
31207Certain setups trigger a crash in case of extended encrypted communication. Userpane passwords, ODBC, LDAP preferences.
31237Heartbleed vulnerability


Known issue

Network communication issues when using Switch 12 on Windows

When using Switch 12 on Windows (Windows Server 2008 R2 or Windows 7), you may encounter problems with the network communication, resulting in a ‘Switch Designer can’t connect to the Switch Service’ message in Switch and errors from other applications installed on the system. This problem is due to changes made in Switch 12, which trigger a known issue in Windows.

If you’re facing this problem, please check this article in our knowledge base on how to solve it. There you can also find the link to the hotfix from Microsoft.


System requirements

Switch

  • Mac: Intel processor only
  • Dual Core processor (Quad Core recommended)
  • Minimum 2GB of RAM (4GB recommended)
  • 1024x768 screen resolution

SwitchClient

  • Minimum 256MB of RAM (512MB recommended)
  • 1024x768 screen resolution (1280 x 1024 recommended)

SwitchProxy

  • Minimum Dual Core processor
  • Minimum 2GB of RAM
  • Needs to be the same version as Switch Server

Supported operating systems

  • Microsoft® Windows® 7, Home Premium, Business or Ultimate Edition
  • (32-bit and 64-bit, running in 32-bit mode)
  • Microsoft® Windows® 8 + 8.1 Standard or Enterprise Edition (32-bit and 64-bit,
  • running in 32-bit mode)
  • Microsoft® Windows® 2008 Server R2 Standard or Enterprise Edition (64-bit, running
  • in 32-bit mode)
  • Microsoft® Windows® 2012 Server (64-bit, running in 32-bit mode)
  • Microsoft® Windows® 2012 Server R2 (64-bit, running in 32-bit mode)
  • Mac OS® X 10.7
  • Mac OS® X 10.8
  • Mac OS® X 10.9
  • Including Virtual Machines
 
Does this solution help you answer your question?