Windows 2000 or XP as a standalone server (Active Directory for Users and Groups not installed) / Windows NT.
1. Log on as administrator.
2. Install U/BL
3. Run U/BL Admin 2000 > select Win NT style authenticator.*
* Note: To set the authentication setting, run the U/BL Administrator. The first time you do this, you will get a warning box that says “No Authenticator is specified”. This is what it should do the first time you run the U/BL Administrator. To set this, click the “Options” button, check the “Windows NT Style” check box, and enter the Windows Computer Name (NOT the IP Address and not the Domain Name) of the server as noted in step #4. Depending on the O/S, the machine name is usually located in the Network Properties.
4. Enter the name of the machine in the authentication box.
5. Add users (only one user needs to be added at this stage - additional users can be added later)
6. Install a full banner.
7. Start the U/BL server.
*NOTE: If installing on a Windows NT Domain Controller (Primary or Backup), it may be necessary to do the following:
Run the User Manager for Domains (located in the Administrative Tools Group). In the menu bar, select Policies, then User Rights. Add the UBL_USERS group to the Users Rights. This step may only be necessary if you are having trouble logging into U/BL.
Windows 2000 Domain controller (Active Directory for Users and Groups is installed).
You must ensure that the domain controller on which U/BL is installed has access to the Global Catalogue. Without correct access the U/BL installation will not be able to create the UBL_USERS group. For more information please refer to the Microsoft Active Directory documentation and on line help.
1. Log on as administrator.
2. Install U/BL
3. Run U/BL Admin 2000 > select Win NT style authenticator.
4. Enter the Domain Name in the authentication box.
5. Add/create required users.
6. Run Administrative tools > Domain security policy > local policies > user rights.
** Note: If the ‘log on locally’ policy is not defined then DO NOT edit that policy and move on to step #8.
7. Select 'log on locally' right and add the UBL_USERS group to the right.
8. Run Administrative tools > Domain controller security policy > local policies > user rights.
9. Select 'log on locally' right and add the UBL_USERS group to the right.
10. Run Administrative tools > local security policy > local policies > user rights.
** Note: If the ‘log on locally’ policy is not defined then DO NOT edit that policy and move on to step #12.
11. Select 'log on locally' right and add the UBL_USERS group to the right.
12. Install full banner.
13. Start U/BL
Important Install Notes:
- ** THIS IS CRITICAL! After you install U/BL, make sure that users on the network are able to log off of their computers and log back on. If they are not, then try the following. First, reboot the workstation (It is sometimes necessary to reboot after a policy change). If they are still not able to login then the problem could be with one of the policies that you edited. If one of the policies that you added the U/BL users group to was empty or not defined then go back and remove the U/BL users group from that policy only. Reboot the workstation and try to login again. If this resolves the problem, then make sure that you are still able to login to U/BL.
- If you are prompted to have U/BL start automatically, you should choose "Yes". After doing this, an "Information" window is displayed alerting you to read the "ReadMe" file, you can just hit "OK". The next "Information" window explains that the installation is complete; you must again hit "OK".
- If this is a Win95/98/ME installation, the shortcut that runs UBLMON.EXE must have a "-t" and a "-s" switch in the command line. The "-t" forces ublmon to run in the Windows system Tray (Tray-Mode), and the "-s" allows you to start the runtime with ublmon. The command line for the U/BL Monitor should be similar to: "C:\ubl\bin\UBLMon.exe -t -s". If you say 'yes' to start U/BL automatically, this command will be added to the Windows Startup directory.
3. Install MCMS/VanS.
** WARNING !: If you are doing an update, you may want make sure that all files in the PROGS and UTIL directories do not have READ-ONLY attribute set. If you do not check this, files that are set to Read-only may not get updated by the installation process. This also applies if you copy any files directly off the CD. Any files copied from a CD will always have the READ-ONLY attribute set and should be changed.
From the main menu, click on either the MCMS or VanS logo for install menus.
** WARNING ! ** - The MCMS Install and VanS Install options will overwrite ALL files including data and modified programs, so if there are existing live data or modified files/programs, you must rename those directories so they are not lost. The MCMS Update and VanS Update options will ONLY update files in the PROGS and UTIL directories.
The Install Compusource Utilities Update option may be used to update ONLY the UTIL directory.
Application
|
Installation File/Path
|
Password
|
Install MCMS
|
D:\MCMS\WINDOWS\Install.exe
|
2521045
|
Install MCMS Update
|
D:\MCMS\WINDOWS\Update.exe
|
N/A
|
Install MCMS Pre Update
|
D:\MCMS\WINDOWS\Presetup.exe
|
N/A
|
*Install MCFILE
|
D:\MCFILE\MCUg5.00.exe
|
N/A
|
*Install MSDE for MCFILE
|
D:\MCFILE\MSDESetup.exe
|
N/A
|
*Install MCMS Visual Suite
|
D:\MCMSVS\setup.exe
|
mcmsvs9034
|
|
|
|
Install VanS
|
D:\VANS\WINDOWS\Install.exe
|
2521045
|
Install VanS Update
|
D:\VANS\WINDOWS\Update.exe
|
N/A
|
* Install VanS Visual Suite
|
D:\VanSVS\setup.exe
|
N/A
|
|
|
|
Install Compusource Utilities Update
|
D:\UTIL\WINDOWS\UTIL.exe
|
N/A
|
* Please refer to individual installation documents before attempting to install these applications.
4. Setup the U/BL Environment file.
VanS: Run the Command Prompt. At the “C:\” prompt, change directories to the \Compu\PROGS directory, and look for the BBENVNT.DEF file. Copy BBENVNT.DEF to Compu\BBENVNT.
The BBENVNT.DEF file is setup to have paths all relative to the /compu directory, there are no references to drive letters. If VanS and U/BL are not installed on the same drive then: You must edit the BBENV file and change the following lines
From:
BBERM=\ubl\misc\BASIC.ER
BBUBBERM=\UBL\misc\ublerm
To:
BBERM=C:\ubl\misc\BASIC.ER
BBUBBERM=C:\UBL\misc\ublerm
(You just need to insert the drive letter where U/BL is installed in these two lines.)
5. Create U/BL Banner.
Run the U/BL Secure program: Start--> Programs--> UBL 2.0--> Secure. Use the "Create a new banner" option and fill out the banner form exactly as it appears except for the Banner File Name. The name of the banner file can be anything. Click the Generate button to create the banner.
** Note: If you get an "Invalid Checksum" error, DO NOT CLICK "OK". Instead, click somewhere on the banner form window, and correct any errors. (If you click OK at the error message, the banner form will be erased, and you will need to type all of the banner details in a second time.)
After generating the banner, use the Transoft website – www.transoft.com and go to the On-Line Orderering section to register the banner and request an activation code. To activate the banner, run Secure once more, and use the Activate option.
6. U/BL Environment Setup.
Run the U/BL Server program: Start--> Settings--> Control Panel--> UBL Server. There are three pages (tabs) of settings. On the Server tab, you need to define the Banner and the Environment files. To do this, click the browse button next to the option labeled "...". For the Banner navigate to the /UBL/Banner directory and select the banner file that you created. For the Environment, navigate to the Compu directory, and select the BBENVNT file.
Switch to the Environment tab and add the following variables:
UBLNTEXE value: C:\UBL\bin\UBL.exe **May be on a different drive letter.
UBLNTPROG value: CCLOGON
CCFPROG value: MCMENU or VANSMENU
CCDIR value: DATA1 **This may also be set by User.
BBBYE value: Y
UBLNTGUI value: N ** This is important, turns GUI mode Off.
NOTE: For UBL version 5.30 please add the following:
BBMONSWAPSTACK=Y
UBLNTREALINODES=Y
BBSECUREKEY=N
Remove OSExclusion=1 in the registry. This can just be deleted.
Also in the Environment Tab, click the box labeled "Allow users to override these settings" Make sure that the box next to this is checked.
There are no changes to the Obituary and Logging tab.
7. U/BL User Setup.
Run the U/BL Administrator program: Start--> Programs--> Transoft UBL 5.00--> UBL Administrator. Add the users by clicking the Add button. If this is an NT system, after you hit Add, another window will be displayed titled "Dialog" which will have three options. You can type in the ‘User Name’, ‘Choose from list’ or ‘Create new user’. If you are adding new user, then you must Use the Create new user option (to create the user in Windows) then you must use the Choose from list’ option to add that user to U/BL. Before adding a new user, always use the Choose from list option to verify that they do not already exist.
After selecting/creating a user, select the user again at the U/BL Administrator screen and click the EDIT button. You will need to define the Home directory as C:\COMPU or the correct path for the compu directory. You should also add the following Environment variables:
BBUSER value: Login name (first 5 characters being unique)
CCDIR value: Data directory for this user if not DATA1
For the DATA user, add the following variables:
BBABORT value: Y
BBUSER value: DATA
BBBYE value: N
CCFPROG value: (The value should be blank)
*** Windows Password: After any new users are added to Windows, you should check the password expiration flag. When a user is added, the login default is set to expire ever 30 days. To change this, you must have administrator privileges. The methods vary, but any time a user is added, you should always make sure that the Password Never Expires box is checked.
** If you decide to setup a TEST user, you will need to add BBPATH as a variable for the TEST user, and redefine the path to be: \compu\MODS;\compu\PROGS;\compu\UTIL.
8. Edit the Registry. *** Note, this is now done automatically as part of the MCMS and VanS Installation Install.exe program. Just verify that the key was added.
Run the REGEDIT program to fix the U/BL registry settings: Start--> Run. Type REGEDIT as the name of the program to run. Navigate to the following directory: Hkey_Local_machine/Software/Transoft/UBL/2.0/Settings. Position the cursor anywhere inside the right half of the window, and RIGHT-CLICK. A box will appear that says New. Highlight New and another box will appear. Highlight the option that says DWORD_VALUE. Name the new value "OSExclusion" and set the value to "1". To set the value, RIGHT-CLICK on the new value, and select the MODIFY option and set it to 1.
9. Install U/Gi
From the CD main menu, click the U/GI icon. This will get you to the U/Gi installation menu, there will be only one option, Install U/Gi (D:\UGI\UGi 5.0\UGi501Setup.exe). You should choose the Typical Installation option. You will be prompted to enter the IP address of the server.
After installing U/GI, there will be a U/Gi shortcut on the desktop. This shortcut will default to a connection called “compu”. Run U/Gi, uncheck the tool tips box then go to the Choose a Connection Window. Use the Import .UGI option and select “compu.ugi” and call the new connection “compu”. The next time you use the desktop icon for U/Gi, it will default to the compu connection and no other changes will be necessary.
At this point, you should be able to start the U/BL run time bye either clicking the Start button in the U/BL server program (If NT) or by starting the U/BL monitor (If Win9x).
You should create a shortcuts on the desktop for U/BL Monitor.
.
Troubleshooting
If you are trying to login to U/BL and receiving a message that says that your login is not in the necessary group then the problem could be one of the following:
If adding a user, verify that the user was NOT a member of the UBL USERS group prior to adding them to U/BL. If so, remove them from U/BL, then remove them from the U/BL USERS group and read them into U/BL.
The Authentication method may not be defined or has been defined incorrectly. Try using just the domain name or just the computer name as the Authentication name. If that seems correct, then make sure that you have followed the instructions on adding the U/BL Users group to the Windows Policies as stated above.
If this is still an issue, try the following; try to restart the U/BL service; try to log off and back on; try to run the U/BL Administrator, click on options, and just hit OK in the options screen to reset the Authentication Method and then restart the U/BL service and try to login, try removing the data user from U/BL and from Windows and recreate it.
-------------------------------------------------------------------------------------------------------------------------
If when logging on with the data user, you are NOT getting to the DATA1 directory (and are just in “:”, this is usually a symptom of the CCLOGON program not running or erring out. Make sure that the U/BL Environment settings in the U/BL Server program have the UBLNTPROG variable set to CCLOGON. If this is already set correctly, run CCLOGON from the "*" prompt, and see if you get any errors.
-------------------------------------------------------------------------------------------------------------------------
File Write Protected Errors
Error -131 at 10505 File in use in CCLOGON
Error -8 at 9955 in CCLOGON
Error 44 at 5860 File unopened in CCSECURE
File does not exist at 8345 in UPDATE or Cannot create new file /compu/BBENVDATA
These are all symptoms of a problem with file or directory permissions. This error indicates that you do not have write permission to one or more directories in or including the /compu directory. Right click on a folder such as the MODS folder and make sure that the Read Only box is not checked. Repeat for all folders (individually) in and including compu. See below for more details/ solutions.
1) Make sure that all of the files under the Compu directory and it's subdirectories do not have the Read-Only attribute set. To check this for a file or range of files, RIGHT-CLICK on the file or the selected group of files, and select the Properties option. There will be a Read Only box, this box should not be checked. If you are checking on a group of files, and the box is checked, but is DIM, this means that some of the files in the selected group are set this way, but not all. In any case, clear the Read Only selection box, and hi OK or Apply.
2) Make sure that all of the users are members of a group that has Full control of the compu directory and all of the subdirectories. Check the permissions on the Compu directory first. Open the My Computer folder in the desktop. Navigate to the Compu folder, and RIGHT-CLICK on it once, and select Properties. Click the Security tab, and then click the Permissions button located within the Security tab. A window titled "Directory Permissions" will appear, and it will list all groups that have specific permission to access the Compu directory. One or more of the groups should be set to "Full Control", such as the Domain Users group. Make sure that the U/BL user is a member of a group that has Full Control Access over the Compu directory.
If you do need to change the type of Access for a group to allow Full Control, be sure to check the "Replace Permissions on Subdirectories" box so that the Full Control Access gets applies to Compu and all the subdirectories under it.
To verify what groups a user is a member of in NT, go to Start--> Programs--> Administrative Tools--> User Manager for Domains.
Double-click one of the users to view the properties, and then click the Groups button to see what groups this user is a member of. Add any necessary groups except for the UBL Users. DO NOT ADD UBL USERS group from here. Users will be added to the UBL Users group when you add them as a U/BL User through the U/BL administrator.
3) If you are still having problems with errors such as "File Does Not Exist" or "Unable to open file" or any other error that seems like a write error then there still may be a problem with the file permissions in the /compu directory. To check this, use the My Computer or Explorer to view files in the compu directory. To do this, navigate to the /compu directory, and then into one of the subdirectories (such as DATA or DATA1), and select all of the files in that directory. RIGHT-CLICK on the selected files and select properties, and look at the READ-ONLY option. If this is checked, it means that some or all files in that directory do not have write permission. You must clear that box, and click the OK or the APPLY button. You must repeat this for every subdirectory of compu.
4) If you are having problems with logins not working, or giving you "file does not exist" errors, there is a possibility that pcANYWHERE is causing this. If you are running pcANYWHERE at the time, run the file transfer facility, and check to see what directory the host window defaults to. If it defaults to any subdirectory under compu, then it is possible that pcANYWHERE is causing a sharing violation with that directory. Change the host directory to some other directory, maybe just /compu, and exit the file manager by going to file and to exit (don't just "X" the window), and see it the problems get resolved.
-------------------------------------------------------------------------------------------------------------------------
** Error 31 @ 11910 - Subscript in CCLOGON
This error is happens if running U/Gi 4.02.00 and not in GUI mode. To fix, just install U/Gi 4.25. If you can not install 4.25, then run in GUI mode until then. To run in GUI mode, take the UBLNTGUI statement out of the environment settings or set it to "Y". This can only be temporary, because running in GUI mode causes other problems.
-------------------------------------------------------------------------------------------------------------------------
*** Arithmetic Errors ***
If you are getting Arithmetic errors in any program it is most likely caused by a missing U/BL environment variable. This will happen if the client is running U/BL 2.40 or higher. In this case, you must make sure that the client is using the current package environment file, /compu/PROGS/BBENVNT.DEF (refer to step 5 in the VanS Installation procedures). The variable that is missing is BBWRITECHK=N, but rather then add this variable, you use the package BBENV file in case anything else is missing.
-------------------------------------------------------------------------------------------------------------------------
Can not get a login prompt with U/Gi OR
Server allows NTLM authentication only
Server has closed connection
If you are not getting a login prompt when running U/Gi, and/or are getting the errors listed above, verify that the IP address is correct. If so, then verify that the Server running U/BL does not have the “Telnet” service started. If so, stop and disable it.
Also, verify that the U/BL Server service is ‘started’ and is set to start automatically.
-------------------------------------------------------------------------------------------------------------------------
** U/BL UNIX Installation Note:
If installing or updating U/BL to 5.01 on a UNIX server, you will need to execute the following command as root: ln /usr/lib/libsocket.so /usr/lib/libsocket.so.2
If you do not do this, U/BL will error with a file not found error.
www.compusource.com/FTP/MISC/INSTALLATION_GUIDE.doc Last updated 12/26/2019 -cjh
|
