| Installation
Server
Components
Client
Communications
MSDE
Licensing
Diagnostics
Registry
Why
do I get the DB Configuration dialog twice?
On a standard installation the DB configuration dialog is
displayed first for the Enterprise server and again for
the Standard Server. This allows maximum flexibility for
data storage options.
Back
to Top
What
gets installed?
For
a default (full) installation the following are installed:
Default
home directory is %PROGRAM FILES%\Wyse\Alcatraz\
- File:Alcatraz
Function Reference.pdf
The reference guide for setting shipped with the release.
- File:Alcatraz
User Manual.pdf
The administrator’s user guide for Alcatraz.
- File:Readme.rtf
The readme file displayed during installation
- Dir:
AlcatrazAdmin
All files required for the MMC Administrator console.
- Dir:
AlcatrazEnterprise
The Alcatraz Enterprise Server service & supporting
files.
- Dir:
AlcatrazServer
The Alcatraz Standard Server service & supporting
files.
- Dir:
ClientDeploy
Deployment files for standard client installation
- Dir:
Pre-Requisite
Setup.exe for MSXML3 update.
- Dir:
WebDeploy
One click installs for client, versions included with
and without MSXML3
Back
to Top
Can
the Server Components be installed on Windows Server 2003?
No, the installer version currently in use does not support
Windows 2003, this will be addressed very shortly as there
is nothing stopping the software from running on this platform.
What
are the pre-requisites for a Server / Enterprise Server?
The
minimum requirements for servers are:
- NT4
service pack 6
-
Windows 2000 service pack 1
-
Windows XP
Server
& Workstation OS’s are supported.
Over
and above this the three “golden rules’ must
be adhered to…
1.
The host PC must have be on a TCP network
2. The host PC must have a static IP Address
3. Only one Enterprise server can be installed in an environment.
Back
to Top
What
is the optimal loading for a server?
This
varies depending on usage and the host hardware,
A
Server on standard PC hardware (P4 - 2GHZ, 512MB) can handle
up to 10,000 clients. The MMC can handle large volumes of
clients but may not be responsive if all clients are being
used in a single view.
We
recommend that, because server licenses are included in
the client license, servers should be segregated by department.
Do
I really need to reboot after installing Server Components?
Yes,
in some instances, the Server or Enterprise server will
not accept connections from each other, from clients or
the Administrator console until a reboot has been applied.
Back
to Top
What
is an “Orphan” client?
An Orphan client is a client that has not been assigned
to a server. In an Enterprise environment clients are “homed”
to a specific server. Homed clients can only be managed
from this server.
If
a clients homed server is not available the client will
connect to any other server, but will not be directly manageable
until it reconnects to its homed server.
Back
to Top
How
do I home a client?
There are two ways to home a client:
From
the MMC Administrator console:
- Right
click the Orphans Node under the Enterprise node in the
MMC and select Manage Orphans
-
Logon to the Enterprise Server
- Select
the Server to be homed from the drop-down list.
- Select
the Clients to home from the list
- Click
the Assign Selected button
- All
selected clients will now disappear from the Orphans list,
and will appear in the Client Management View for the
selected server.
By
editing the setup.ini file in the ClientDeploy\Installfiles
directory (Easiest option)….
Before
installing the client:
- Open
the Setup.ini file
- Under
the IP Discovery section set the values for DefaultServer
& ServerList to the IP Address of the homed server
(if multiple IP addresses are need then separate them
with a semicolon with a semicolon at the end, thus.
[IP
Discovery]
DefaultServer=192.168.0.1;192.168.0.2;
ServerList=192.168.0.1;192.168.0.2;
- Run
the InstallAlcatraz.exe on the client, this will pre-populate
the registry with the clients homed server, the client
will then connect to its homed server and show in the
Client Management View ready to be managed..
Back
to Top
How
can I simplify the Installation process?
You
can use Parameters to alter how the installation interacts
with the user.
UNATTENDED (must be uppercase)
This does not require the user to close the installer when
finished, the installer runs without any interaction.
REBOOT
(must be uppercase)
At the end of the install process the client will be rebooted.
NOTE: The Alcatraz shutdown (and reboot) forces the PC to
shutdown and any open applications will be closed. The user
will not be prompted to save files.
Back
to Top
How
can I roll out the client to NT platforms where the user
does not have administrative rights?
The
Alcatraz Installer can impersonate an Administrators account
to support this situation. A few steps must be taken in
order to do this.
1.
Set the privileges of the Administrator account and the
user accounts that will be impersonating the Administrator,
the privileges required are:
·
Increase Quota’s
· Replace a Process Level Token
· Act as part of the Operating System
A
reboot of the Server will be required for these settings
to take effect.
The above privileges must be assigned to users, assigning
the rights to groups does not have the required affect.
2.
Specify the Administrator account that will be impersonated
during the installation:
· In the MMC right click the server node & select
Set Administrator Logon from the menu
· In the dialog that appears set the Administrator
account name and password then click Ok. If a domain is
not used then use “.” as the domain i.e. .\Administrator
NOTE; these details are stored encrypted in the Registry
on the server and are only transmitted over the network
encrypted.
When
the client installer is run it will connect to the server,
retrieve the account details and execute the second stage
of the install under the administrator account.
Back
to Top
I
get an error when I run the ClientInstaller.exe
To
install a client, you must use the InstallAlcatraz executable.
I
get an error when I run the InstallAlcatraz executable
This
is because you have not got IE5 or above installed on the
target PC. IE5 or above is required for Alcatraz Client
installation.
I am
trying to Browse the registry on a remote client and nothing
is happening, its online and connected, I can run applications
etc. What’s wrong? Some
functions on the client require Microsoft XML 3 or above
to be installed (this ships with IE6). The client can operate
with out XML 3 but the following functionality will not
be available:
· Remote File Explorer
· Remote File Search
· Remote Registry Editor
· Remote Registry Search
· Remote Command Prompt
To access this functionality run the Setup.exe from the
Pre-Requisite folder or copy the Setup.exe file to the Installfiles
directory and reinstall the client.
Back
to Top
I
have an out of date client. How can I update it?
The
easiest way is to upgrade multiple clients remotely from
within the MMC console.
·
Copy the ClientDeploy to a network share accessible by the
clients to be upgraded
· In the MMC select the clients to be Upgraded and
select Run Remote Application from the Client Management
menu.
· Specify the path to the InstallAlcatraz.exe file
on the share, and add parameters as required.
· If any NT clients are included then specify the
Administrator account to be used for impersonation (see
above).
· Click Ok, the clients will copy the install files
locally and upgrade themselves.
Back
to Top
I
have lots of clients and want to remove the product because
my trial period is about to expire…
This can be done remotely against multiple clients very
easily:
·
Restore all PC’s to their original state (using Uninstall
Profiles)
· Select the clients to be uninstalled in the Client
Management view and select Run Remote Application from the
Client Management menu.
· Specify c:\AlcatrazClient\ClientInstaller.exe as
the application and UNINSTALL as the parameter (you can
add REBOOT as a parameter also if you wish).
· Click OK in the dialog the client will remove itself
from the database and remove all trace of itself from the
client, a reboot is required to do tidy up.
Back
to Top
I
have just upgraded my NT client and cannot run a remote
application, Why?
The
watchdog application used by NT clients to run applications
is not restarted after an install the client needs to be
rebooted following installation.
MMC
I
am trying to run the Administrator console and am getting
a error message that the Snap-in is not registered, what is
wrong? For
some reason the MMC snap in has lost its registration.
To
reregister the snap-in:
1.
Open a command prompt window and type
Regsvr32
<Path to AlcatrazMMC.dll>
2.
In explorer select the AlcatrazMMC.dll and select open with,
then browse for the Regsvr32.exe application (normally found
in WINDOWS\System32)
Back
to Top
I
am running the MMC console and don’t have a Enterprise
node, whats happened to it?
This
is caused by the Server being administered not having established
communications to the Enterprise server, see communications
below.
Back
to Top
My server is not connecting to the Enterprise
Server, or my client is not connecting to the server. What
is causing this?
This is normally because there is a router or firewall between
the Server & Enterprise server (or client & server)
that is blocking UDP broadcasts (the default method of connection)
and no alternative connection methods are specified.
To correct
this you can:
1. Force
connection to the Enterprise / Server:
Using
Registry Editor
Server – Enterprise Server
Create a string value called ALCMAST under the AlcatrazGeneric
Key
Set the value to the IP address(es) of the Enterprise server
followed by a semicolon.
Stop and restart the Alcatraz Server service.
Client –Server
Create a string value called ALCSERV under the AlcatrazGeneric
Key
Set the value to the IP address(es) of the Server followed
by a semicolon.
Stop and restart the Alcatraz Client service. (9x systems
should be rebooted)
2. Open
the required ports in the firewall (see Comms Ports below)
3. Setup
alternative connection methods DHCP option tags or IPWalking
(see User documentation)
Back
to Top
I
have followed the steps above and still cannot get a connection,
or the connection is very slow, what causes this?
Check
network connectivity, i.e. ping the server from the client,
if this succeeds then check DNS, if DNS is configured incorrectly
this can have a detrimental effect on communications efficacy.
I am using MSDE how can I view the data?
You will need a tool that will support this as MSDE does
not come with any user interface.
For the connection you will need the following information:
The
MSDE server is called <HOST PC NAME>\ALCATRAZ
The username is sa
The password is thisissecure
Back
to Top
I have moved my Enterprise Server and Alcatraz says that
it is unlicensed, Why?
The Alcatraz license is linked to the MAC address of the
active network card, if the Enterprise server is moved the
license will be invalid. Contact Wyse for a replacement
license.
My
license says that it is invalid, Why?
In a
system with multiple network cards the Alcatraz license
gets the unique identifier from the primary network card
at the point of registration, if that network card is disabled
or removed then the license will become invalid. Contact
Wyse for a replacement license.
My
version of the product is not working properly, is there any
way to tell what the problem is?
Alcatraz logs faults in one of two places.
·
If the faulting application is a Service application then
the fault will be log to the Application event log.
· If the faulting application is a standard executable
the fault will be written to the application directory in
a file called <MACHINENAME>_ERROR.log
Back
to Top
Where
does Alcatraz store configuration data?
All
application configuration options are stored in the registry.
If required
these values can be altered remotely using the Custom Settings
feature of Profiles:
HKEY_LOCAL_MACHINE\SOFTWARE\WYSE\
| AlcatrazAdmin |
|
|
|
HelpFile: |
|
|
Contains
the path to the Administrator Helpfile |
| AlcatrazClient |
|
|
|
CurrentProfile: |
|
|
Default
profile assigned to client |
DomainName: |
|
|
Client
domain name |
ServerName: |
|
|
Name
of the last server connection |
| AlcatrazEnterprise |
|
|
|
LicenseKey: |
|
|
License
key for the Enterprise server |
SQLMode: |
|
|
Either
MSDE or SQL |
SQLSvr: |
|
|
Servername
for SQL connection |
SQLUsr: |
|
|
Username
for SQL connection |
SQLPwd: |
|
|
Password
for SQL connection |
| AlcatrazGeneric |
|
|
|
ALCSERV: |
|
|
Standard
Server list |
ALCSERV_HOME: |
|
|
Default
Server for client |
ALCMAST: |
|
|
Enterprise
Server list |
137: |
|
|
Custom
Server DHCP Option tag |
138: |
|
|
Custom
Client DHCP Option tag |
| AlcatrazServer |
|
|
|
AdminA: |
|
|
Administrator
account username (encrypted) |
AdminP: |
|
|
Administrator
account password (encrypted) |
LicenseKey: |
|
|
License
key for server (from Enterprise Server) |
Master: |
|
|
Enterprise
Server exists(1 = yes) |
MasterIP: |
|
|
IP
address of enterprise server |
SQLMode: |
|
|
Either
MSDE or SQL |
SQLSvr: |
|
|
Servername
for SQL connection |
SQLUsr: |
|
|
Username
for SQL connection |
SQLPwd: |
|
|
Password
for SQL connection. |
Comms
Ports
The
following ports are required for communication between applications
of the Alcatraz suite.
| Usage |
Port |
TCP |
UDP |
| Client
To Server – Connection Ports |
3588 |
• |
• |
| Server
To Enterprise – Connection Ports |
3712 |
• |
• |
| Client
Service to Client UI(Local Only) |
55000 |
• |
|
| MMC
to Server |
54999 |
• |
|
| Client
Service to Watchdog((Local Only) |
54998 |
• |
|
| MMC
to Enterprise (Fixed Ports) |
60021
to 60023 |
• |
|
| Server
To Enterprise (Fixed Ports) |
60050
to 60060 |
• |
|
| Client
To Server (Fixed Ports)** |
55001
to 55005 |
• |
|
** These
ports can be changed by the user. Table shows default port
ranges.
Back
to Top
|
