Configuration. Cortado Corporate Server in a Novell environment. Version 4.0

Transcription

1 Cortado Corporate Server in a Novell environment Version 4.0 Configuration Cortado. A Division of ThinPrint ThinPrint AG Alt-Moabit 91 a/b Berlin Germany/ Alemania ThinPrint Pty. Ltd. L 10, 275 Alfred Street North Sydney/ NSW/ 2060 Australia ThinPrint, Inc Detroit Road, Suite 303 Cleveland, OH USA/EEUU ThinPrint, Inc Grandview Avenue, Suite 200 Denver, Colorado USA/EEUU info@cortado.com Web: Issued: July 3, 2009 (v09)

2 Notes Copyright This document is the intellectual property of ThinPrint AG. This document may be copied in whole or in part, provided this Copyright notice is included in every copy. Registered trade marks All hardware and software names mentioned in this document are the registered trademarks of their respective companies or should be regarded as such. Safety warning All ThinPrint products are pure software solutions. Please note the safety warnings in the technical documentation from your hardware vendor and from the manufacturer of each device and component. Before beginning installation, we recommend closing all windows and applications and deactivating any virus scanner. How to use this manual The following conventions are used throughout this manual to represent recurring actions and text types. Conventions Note! SMALL CAPS Italic Name Courier Example Page 5 Important tip, explanation, exception Menu, command, dialog panel, option Proper name, emphasis, variable Keyboard input Consecutive menu or command Enumeration, head note Example Procedural steps Links 2 Configuration Cortado Corporate Server + Novell

3 Contents Novell network structure with Cortado... 4 Integrating a Novell file server... 4 Objective... 4 Scenario... 4 Requirements... 5 Setting up the CIFS share... 5 Integrating a Novell print server (iprint) Objective Scenario Procedure Integrating GroupWise Objective Scenario Procedure Using the Novell Identity Manager Objective Scenario Procedure Cortado Corporate Server + Novell Configuration 3

4 Novell network structure with Cortado Novell network structure with Cortado This document will help you configure the systems when you want to integrate a Cortado Corporate Server into an environment with Novell servers. It presents plausible situations in separate scenarios in succession. These can also be combined in practice. Illus. 1 Illus. 1 Overview Integrating a Novell file server Objective The Cortado Explorer is to be able to access a Novell file server within a Windows-based BlackBerry environment (DFS on the Cortado Corporate Server). Scenario Illus. 2 Illus. 2 Cortado and Novell file server 4 Configuration Cortado Corporate Server + Novell

5 Integrating a Novell file server Requirements 1. The Cortado Corporate Server requires the following entries in the Active Directory (AD): Display name, address, User Principle Name (UPN), password 2. The users from the Novell e-directory must be created identically in the AD; only the domain may differ. 3. For each relevant user, the exact same password must be entered under the login method Simple Password in both the e-directory and the Windows AD. 4. The CIFS file protocol has been enabled on the Novell file server. The manual set-up of the CIFS share on the Novell file server is described below. Setting up the CIFS share Specify server Launch the imanager. Under the menu item FILE PROTOCOLS, open NETWARE CIFS (Illus. 3, left arrow). Use the magnifying glass icon to select the server (and the organization unit, if applicable) where the CIFS share should be set up (Illus. 3, right arrow). Confirm with APPLY. Illus. 3 Illus. 3 Create NetWare CIFS file protocol Cortado Corporate Server + Novell Configuration 5

6 Integrating a Novell file server Setting up the pool Now create a new pool, if no existing pool is going to be used. To set up a new pool, open the POOLS item under the menu item STORAGE (Illus. 4, left arrow). Select NEW in the window that opens (Illus. 4, right arrow). Illus. 4 Illus. 4 Creating pool Another window opens. Assign a name to the pool you just created and click NEXT to confirm. Now specify the storage space for the home drives of the users and then click FINISH (Illus. 5). Illus. 5 Illus. 5 Specifying storage space 6 Configuration Cortado Corporate Server + Novell

7 Integrating a Novell file server The pool created using this method now appears in the pool list (example pool Data in Illus. 6). Illus. 6 Illus. 6 Pool set up Creating volumes Now create a new volume if this has not already been done. If a volume already exists, adjust the settings corresponding to the present version. To create a new volume, open the VOLUMES item under the STORAGE menu item. Select NEW in the window that opens. Assign a volume name and confirm with NEXT. Select the pool previously set up and click NEXT (Illus. 7). Illus. 7 Illus. 7 Select the pool where the volume should be created Cortado Corporate Server + Novell Configuration 7

8 Integrating a Novell file server The settings in the next window (ATTRIBUTE INFORMATION) can be carried over. Click FINISH. The volume created using this method now appears in the list of volumes (Illus. 8). Illus. 8 Illus. 8 Volume set up Setting up CIFS share Under the menu item FILE PROTOCOLS, select the NETWARE CIFS item (see Illus. 3, left arrow). Select SHARE NEW in the window that opens. In the next window you are prompted to enter a share name, path, and optional comment (Illus. 9). In order to be able to specify a path, you must have previously created a folder to be used for the share of home drives (in the example with the name Novell123 ), if applicable, on the selected server. Confirm your entries with OK. Illus. 9 Illus. 9 Setting up CIFS share 8 Configuration Cortado Corporate Server + Novell

9 Integrating a Novell file server The share created using this method is now displayed under SHARES (Illus. 10). Illus. 10 Illus. 10 CIFS share set up Under SERVER, click PROPERTIES (Illus. 10). In the window that opens, make sure that DISTRIBUTED FILE SERVICES (DFS) SUP- PORT is disabled (Illus. 11). Then click APPLY. Illus. 11 Illus. 11 DFS support disabled Adjusting the configuration file cifsctxs.cfg Tell the CIFS protocol where the user accounts are located. To do this, adjust the configuration file cifsctxs.cfg in the path SERVERNAME\SYS\ETC (see example entry in Illus. 12). The path entered in the configuration file must lead to the server (organization unit, if applicable) that you set up the share on (see Illus. 3). Illus. 12 Illus. 12 CIFS configuration file Cortado Corporate Server + Novell Configuration 9

10 Integrating a Novell file server Lastly, stop the CIFS service at the command line with cifsstop and restart it with cifsstrt. Note! You can use the command cifs share to test if the share is available. Setting user properties For authentication via CIFS on the share you created to occur, the users must be set up appropriately. Switch to the ConsoleOne and make the appropriate settings to the account of every user 1 already created there who will have access to the share. On the LOGIN METHODS tab, select SIMPLE PASSWORD and assign a password (Illus. 13) identical to this user s password in the Windows AD. Illus. 13 Illus. 13 Select login method Use the RIGHTS TO FILE AND FOLDERS tab to assign the appropriate file rights if they have not already been set. These also apply when accessed using the Cortado Explorer. Click ADD here and then select the CIFS share you created (in the example Data ) (Illus. 14). Confirm with OK and close the ConsoleOne. 1 Creating a user group reduces work outlay. 10 Configuration Cortado Corporate Server + Novell

11 Integrating a Novell print server (iprint) Illus. 14 Illus. 14 Assigning access rights to the CIFS share Finished! Now the CIFS share can be added onto the Cortado Corporate Server. Use the User Network Folders component for this. Note! Please note that Novell appends a -w to the server name for shares via CIFS. A share on a print server named FS01 would be called \\FS01-w\share. You can change this name if you want in the CIFS configuration. Integrating a Novell print server (iprint) Objective Printing via a Novell print server from BlackBerry devices using the Cortado Corporate Server is to be enabled within a Windows-based BlackBerry environment. To do this, the printers are manually set up as network printers by the administrator and made available to the BlackBerry users at the Cortado Server. Restriction Printing has only been tested via the LPD protocol between the Cortado Corporate Server and the iprint Server. Cortado Corporate Server + Novell Configuration 11

12 Integrating a Novell print server (iprint) Scenario Illus. 15 Illus. 15 Cortado with Novell file server Procedure 1. Share the desired printers on the Novell iprint Server as IPP printers with LPD support: To do this, enter a name for LPR at the desired printer (Illus. 16). Illus. 16 Illus. 16 Setting up IPP printer 2. Install the Unix print support on the Cortado Corporate Server via adding additional Windows components. 3. Now the printers can be set up on the Cortado Server as local printers. An LPR port is selected as the connection for each, at which the LPR name selected under Novell is entered as queue name next to the IP address of the iprint Server. A corresponding printer driver must also be selected, in which the desired print settings can then be entered. Beyond that, the printers need to be shared and then assigned to users with help of the Cortado Corporate component, User Network Printers. 12 Configuration Cortado Corporate Server + Novell

13 Integrating GroupWise Result When the user initiates a print job on the BlackBerry, it is rendered on the Cortado Server and sent as RAW data to the selected printer queue on the Novell iprint Server using the LPD protocol. From there it is then sent to the printing device designated on the iprint Server. Integrating GroupWise Objective Printing of attachments from the mailboxes of the Groupwise Server is to be enabled. It is also possible to allow forwarding of documents via from the Cortado Explorer. The two scenarios (Novell file and print server) described in the previous chapters also work with mail servers other than Groupwise. Scenario Illus. 17 Illus. 17 Cortado with mail server Groupwise Procedure Only a few settings on the Novell Groupwise Server are required to use this function. It is not necessary to set up the user accounts on the Groupwise Server and in the AD identically. However, for every account on the Groupwise Server, an account must be set up on the Windows AD that can be allocated. Only if file servers and/or print servers are to be accessed as well must the accounts and passwords be set up identically as described in the previous chapters. Otherwise it is sufficient to generate or edit the configuration file route.cfg (= text file) in the home directory of the Internet agent on the Groupwise Server (\\server\data\grpwise\domain\wpgate\gwia where server is to be replaced with the IP address or host name of the computer and domain with the Groupwise domain). Here you enter the real non-existing domain that you already previously set up on the Cortado Corporate Server. s to be printed can be forwarded via this to the Cortado Corporate Server. Details on this can also be found in the Cortado Corporate Server installation manual. Cortado Corporate Server + Novell Configuration 13

14 Files can be sent from the Cortado Explorer via as long as SMTP receipt for the Cortado Corporate Server is possible and allowed on the Groupwise Server, which usually must be set up there separately. Using the Novell Identity Manager Objective The Novell Identity Manager (IDM) should automatically synchronize the Active Directory and e-directory for the scenarios described in the preceding chapters. The Novell Identity Manager executes tasks like password management and user provision across systems (AD and e-directory). Particularly if the Novell e-directory is the source, it must be ensured that the data required for the Cortado Corporate Server, like the username, the UPN (User Principal Name) and the address in the AD, if applicable, are entered correctly and that the password under Novell for simple login and the Windows password in the Active Directory agree. This is achieved by creating a suitable driver. If the IDM is already used with a driver, this can be adjusted accordingly. Scenario Illus. 18 Illus. 18 Cortado and Novell Identity Manager Procedure Following the Novell manuals, the IDM must be installed on the Novell Server with the e-directory and the Windows domain controller (DC) with the AD (here as a connected system, for example) including the Remote Loader (on the DC) and the plug-in for the imanager. It is essential that a password policy be created on the Novell side, if one does not already exist. Certain functions of the IDM are only usable if this condition is met. The values of the policy can be freely set within reasonable limits as long as it concerns integration of the Cortado Corporate Server. 14 Configuration Cortado Corporate Server + Novell

15 To set this up, open the Novell imanager (Web site) and select PASSWORD POL- ICIES under PASSWORDS (Illus. 19). End the process with FINISH. Illus. 19 Illus. 19 Setting up a password policy Afterwards, configure the Remote Loader appropriate to the desired settings in your environment. This is also required in order to test the access option when creating drivers. The assigned passwords (Illus. 20) must be entered identically in the later driver. Illus. 20 Illus. 20 Remote driver configuration Cortado Corporate Server + Novell Configuration 15

16 Next create the driver using the imanager. In the overview, first create a new driver set if one does not already exist. This must be done in order to create a driver. At the same time, create a new partition and assign it a name (Illus. 21). Illus. 21 Illus. 21 Creating a driver set Now the actual create of a driver can occur. Call up the corresponding assistant via ADD DRIVER (Illus. 22 and 23). Illus. 22 Illus. 22 Adding a driver 16 Configuration Cortado Corporate Server + Novell

17 Illus. 23 Illus. 23 Configuration assistant launched In the driver set, create the new driver under a fitting name, whereby the information from your own environment must be used for domains, host names, accounts, etc. Unless otherwise noted, the assistant adopts the suggested preset values. Otherwise, go through the subsequent configurations step by step. At the end of each page, click NEXT to advance to the next step. It is assumed that synchronization will only occur from the e-directory in the direction of the AD and Groupwise will be used as the server and that no Exchange Server is present. Otherwise the driver would have to be adjusted accordingly. Illus. 24 Illus. 24 Import configuration Cortado Corporate Server + Novell Configuration 17

18 Clicking NEXT will take you to the next page (Illus. 25). Illus. 25 Illus. 25 Driver set-up (1) Clicking NEXT will take you to the next page (Illus. 26). 18 Configuration Cortado Corporate Server + Novell

19 Illus. 26 Illus. 26 Driver set-up (2) Clicking NEXT will take you to the next page (Illus. 27). Cortado Corporate Server + Novell Configuration 19

20 Illus. 27 Illus. 27 Driver set-up (3) 20 Configuration Cortado Corporate Server + Novell

21 Under CONFIGURE ENTITLEMENTS, select YES (Illus. 27, bottom) and click NEXT to continue. Illus. 28 Illus. 28 Driver set-up (4) Clicking NEXT will take you to the next page (Illus. 29). Cortado Corporate Server + Novell Configuration 21

22 Illus. 29 Illus. 29 Driver set-up (5) Clicking NEXT will take you to the next page (Illus. 30). 22 Configuration Cortado Corporate Server + Novell

23 Illus. 30 Illus. 30 Driver set-up (6) Clicking NEXT will take you to the next page (Illus. 31). Cortado Corporate Server + Novell Configuration 23

24 Illus. 31 Illus. 31 Driver set-up (7) When mapping principle names (Illus. 31, bottom), we recommend selecting FOL- LOW IDENTITY VAULT NAME, because there can be problems with the domain mapping otherwise. But then you must insert, as we will see later, an appropriate policy (adjusting XML driver set) so that this value can also be correctly set for the Cortado Corporate Server. Clicking NEXT takes you to the next page. There are then still more options that you can configure as needed. This concludes the driver creation process. Lastly, you must still enable the driver. 24 Configuration Cortado Corporate Server + Novell

25 Illus. 32 Illus. 32 Driver set overview For password synchronization to occur, this must also be enabled in the imanager under the menu item PASSWORDS and with the selection of the driver just created (Illus. 33). Illus. 33 Illus. 33 Enable password synchronization Furthermore, the settings from the following illustration must be opened (Illus. 34). Cortado Corporate Server + Novell Configuration 25

26 Illus. 34 Illus. 34 Editing drivers In order for the UPN to be set correctly, you should have selected FOLLOW IDENTITY VAULT NAME as described above (see Illus. 31) and adjusted the XML driver set in the manner described below: [Follow identity vault name] This option is useful if userprincipal-name is to be generated from the login name of the user and a character string defined in the policy. Here, the domain.local is to be replaced with the respective domains. <rule> <description>assign usernames to the Windows logon names</description> <comment>windows logon name mapping: When userprincipalname is configured to follow the edirectory user name, set userprincipalname to the edirectory object name plus the name of the Active Directory domain.</comment> <conditions> <and> <if-global-variable name= UpnMap op= equal >edir-name-auth</if-global-variable> <if-class-name op= equal >User</if-class-name> </and> </conditions> <actions> <do-set-dest-attr-value class-name= User name= userprincipalname > <arg-value type= string > <token-src-name/> <token-text xml:space= preserve >@</token-text> <token-text xml:space= preserve >domain.local</token-text> </arg-value> </do-set-dest-attr-value> </actions> </rule> 26 Configuration Cortado Corporate Server + Novell

27 To test the driver s function, you should lastly set up test users and check if they are properly synchronized, that is, do they appear in the AD. You should do the same with the password synchronization and check if login is successful with the new password. Cortado Corporate Server + Novell Configuration 27