TSE Commander is a powerful Windows® console (command-line) software solution for automating any Software Deployment to Windows NT/2000/2003 Terminal Servers. It is not limited to just OneWorld/EnterpriseOne® Package Deployment and, because it it not OneWorld release dependent, it will support any version of OneWorld.

In fact, to Deploy most of OneWorld/EnterpriseOne® software updates, without interrupting logged-in users at all, we have released a revolutionary Hot Deploy software utility, which replaces the legacy Update Package Deployment routine with a new state-of-the-art, absolutely transparent "hot" deployment process.

Consider this usual scenario:
You need to deploy a new OneWorld/EnterpriseOne® Package (or anything else) to your WTS/Citrix Server(s). The users are always connected (even if not, how can you tell from a script?) and you would normally have to:

• manually disable new connections;
• send the connected users messages, asking them to logoff;
• wait for a few minutes;
• check manually if there are still any connected users remaining and reset their sessions, if so;
• switch the Server into the Install Mode;
• run your Installation;
• switch the Server back into Execute Mode;
• re-enable new connections...

This exercise is manual, time-consuming (maybe up to about an hour per Server), error-prone and often requires the system administrator to stay late to perform it. It's particularly bad for larger sites, with a large number of WTServers running 24x7.

With TSE Commander, you can schedule all these tasks (provided you can run your Installation from a command-line) through the standard Windows® scheduler (or run it manually from either the Console or a Remote Session) as a very simple script. All you now need to run is a script like this (replace X: with the correct drive letter, and XXX with the correct release number):

TSECommander PREINSTALL 5 "Please, logout. Going down in 5 min."
"\\DEPSERVER\BXXX\OneWorld/EnterpriseOne Client Install\setup.exe" /s /d X:\B7 /p PDXXXFX
TSECommander POSTINSTALL

or, even better, like this (this is actually the entire script):

set PATHCODE=PD7333
set PACKAGE=PD7333FX
set DESTINATION=X:\B7
set DEPSHARE=\\DEPSERVER\B7XXXSHARE

if EXIST %DESTINATION%\%PATHCODE%.NEW\NUL rmdir /s /q %DESTINATION%\%PATHCODE%.NEW
mkdir %DESTINATION%\%PATHCODE%.NEW
mkdir %DESTINATION%\%PATHCODE%.NEW\BIN32
mkdir %DESTINATION%\%PATHCODE%.NEW\DATA
mkdir %DESTINATION%\%PATHCODE%.NEW\RES
mkdir %DESTINATION%\%PATHCODE%.NEW\SPEC

copy %DEPSHARE%\%PATHCODE%\PACKAGE\%PACKAGE%\BIN32\*.* %DESTINATION%\%PATHCODE%.NEW\BIN32
copy %DEPSHARE%\%PATHCODE%\PACKAGE\DATA\*.* %DESTINATION%\%PATHCODE%.NEW\DATA
xcopy /E %DEPSHARE%\%PATHCODE%\PACKAGE\%PACKAGE%\RES\*.* %DESTINATION%\%PATHCODE%.NEW\RES
copy %DEPSHARE%\%PATHCODE%\PACKAGE\%PACKAGE%\SPEC\*.* %DESTINATION%\%PATHCODE%.NEW\SPEC
copy %DEPSHARE%\FULL_DD_TAM\*.* %DESTINATION%\%PATHCODE%.NEW\SPEC

TSECommander PREINSTALL 1 "Please, logout. Going down in 1 min. for ~1 min."

if EXIST %DESTINATION%\%PATHCODE%.OLD\NUL rmdir /s /q %DESTINATION%\%PATHCODE%.OLD
if EXIST %DESTINATION%\%PATHCODE%\NUL rename %DESTINATION%\%PATHCODE% %PATHCODE%.OLD
if EXIST %DESTINATION%\%PATHCODE%.NEW\NUL rename %DESTINATION%\%PATHCODE%.NEW %PATHCODE%

TSECommander POSTINSTALL

which simulates installation by copying the files, instead of running the setup program, which brings the downtime down to seconds, plus retains all of the customized JDE.INI files in the users' profiles.

The commands in between the two calls to TSE Commander can be either calls to your Setup program, or simply any file copying commands - in either case you will need to make sure there's nobody using the system, so it's wise to use TSE Commander to ensure that.

Imagine the time savings! Minimal disruption and guaranteed results!

Here's a screenshot of the Help Screen, which you get, when you run TSE Commander without any parameters:

Trial Version is available - this version will only run 20 times, after which it must be removed from your system.
Do not forget to remove any schedules you may have created to test this Trial Version, because after the allowed 20 runs (which is 10 deployments, as the executable is run twice for each deployment), it will cease to operate.