Novell GroupWise SetupIP Client Installation Guide

  • 3730554
  • 01-Nov-2006
  • 16-Mar-2012

Situation

Novell GroupWise SetupIP Client Installation Guide

Resolution

To use SetupIP to install the GroupWise client files, perform the following steps:

1.Verify that GroupWise 6.x Administration and GroupWise 6.x agents have been installed, and that administration, agent, and client software have been updated in your defined software distribution directory. To verify that the SDD is defined and associated to your post office, go to Console One and then to the properties of the post office. Under the GroupWise Tab select the Post Office Settings and make sure that the correct SoftWare Distribution Directory is selected in the drop down menu. If you need to create one, go to the top tool bar select TOOLS,GroupWise System Operations,Software Directory Management. When that opens up click Create and fill in the information of where your SDD is located. There should be an SDD already created from the initial installation but if you need to change it, this is where you would do it.

2.Obtain the appropriate SETUPIP.FIL and SETUPIP.US files. With GroupWise 6, the SETUPIP files are not included in the support pack image because of its size (over 44 MB). These files must be downloaded separately from Novell Software Downloads https://download.novell.com and copied to\SETUPIP. With GroupWise 6.5 sp2, the required files are included in the support pack in the CLIENTCD directory under SETUPIP.

3.Create a directory on your webserver to hold the SETUPIP.FIL and SETUPIP.US files on your web server. In our example we will call this directory \CLIENT. Underneath the new Client directory create a new WIN32 directory.

·On a NetWare 6 server running the Apache Webserver for NetWare, create the directory in the document root directory, SYS:\APACHE\NWDOCS or SYS:\APACHE\HTDOCS. By default, NetWare 6 uses NWDOCS and NetWare 6.5 uses HTDOCS. Verify this by looking at *.CONF file that is initiated when you load Apache. By default this .is your ADMINSERV.CONF file.

NOTE: As a minimum you must have the SETUPIP.FIL and SETIPIP.US in the SYS:\APACHE\NWDOCS\CLIENT or SYS:\APACHE\HTDOCS\CLIENT directory or the SetupIP process will fail. You could see 2 %P characters rather than the word GroupWise in a Setup dialog and you will not see any product components to install. You could get an error "SetupIP could not copy the GroupWise setup files, Please contact your system administrator"

NOTE: The %P characters can be seen when the web server is IIS. This will happen if you just create the CLIENT directory manually from Explorer (WWWROOT\CLIENT) instead of creating it from the Internet Services Manager (Start > Settings > Control Panel > Administrative Tools > Internet Services Manager) as a Virtual Directory. For example, start Explorer and create a CLIENT directory under WWWROOT. Copy the SETUPIP.FIL and SETUPIP.US files to the CLIENT directory. (Optional: create a WIN32 directory and copy the SETUP.CFG to the WIN32 directory.) Start Internet Services Manager > select Default Web Site > click on Actions > New> Virtual Directory -give it an Alias such as CLIENT > click Next > browse and select the CLIENT directory you just created> click Next > the Defaults of Read and Run scripts will be checked, in addition check Browse > click Finish and thats it. IIS is configured to recognize the CLIENT directory.

oOn a NetWare 6 server running the Apache Webserver you must verify that "Fancy Indexing" is enabled. The simplest way to do this is to locate the *.CONF file that the Apache Webserver is using and add the following three lines to the end of the *.CONF file:

IndexOptions FancyIndexing

·On a NetWare 5.x or 6 server running the Netscape Enterprise Server for NetWare, create the directory in the SYS:\NOVONYX\SUITESPOT\DOCS directory.

·On a Windows NT/2000 server running the Microsoft Internet Information Server (IIS) for Windows, create the directory in the \INETPUB\WWWROOT directory.

·On a Solaris server running the Apache Webserver, create the directory in the/HTDOCSdirectory.

·On a Red Hat Linux server running the Apache Webserver, create the directory in the / HTDOCS directory.

4.Copy the appropriate SETUPIP.FIL and SETUPIP.US from \SETUPIP\ to the directory you created in step 3.

5.From the<name of SDD>\SETUPIP directory run WRITEIP.EXE.

·Specify the full path to the SETUPIP.FIL. For example, you can specify:

http://151.155.135.122/client

or

http://intranet.company.com/software/client

·You can also include proxy and port information, for example:

http://name.mycompany.com/software/client:proxy.
place.mycompany:1690

·You can specify up to five locations. During AutoUpdate, each location is checked, in order, until a connection is made. If you select Choose IP Address at Random, the order in which the locations are checked is selected randomly when AutoUpdate occurs. This will balance the load on the web server.

·Specify other options, such as the location for downloading the client installation files (SETUPIP.FIL or the CLIENT subdirectory files). You can have files downloaded to a temporary or specific directory. If you select Allow the User to Change the Download Directory, the user is prompted for the location of the download directory and can change the default location.

·Click OK. SETUPIP.EXE is created. WRITEIP.INI, which stores the options you selected in WRITEIP.EXE, is also created. The WRITEIP.INI does not need to be copied anywhere but may be helpful in troubleshooting issues. It contains the location of what you entered in step 5.

6.Copy SETUPIP.EXE to the \CLIENT\WIN32 directory. This should be the same software distribution directory that is associtated with the post office object. The WIN32 directory needs to be the same WIN32 directory that holds the full client. To verify the correct SDD is associtated, go to Console One and then to the properties of the post office. Under the GroupWise Tab select the Post Office Settings and make sure that the correct SoftWare Distribution Directory is selected in the drop down menu. You can also copy this same SETUPIP.EXE file to the new WIN32 directory on the webserver. Example: SYS:\APACHE\NWDOCS\CLIENT\WIN32 or SYS:\APACHE(2)\HTDOCS\CLIENT\WIN32 directory. The purpose of this is to allow your users to access the SETUPIP.EXE from the website. Having a SETUPIP.EXE in the WIN32 directory of the webserver does not play a crucial role in the AUTOUPDATE process. It does however, give you the option of having your users go to the website and running SETUPIP.EXE manually.

7.Make a backup copy of \CLIENT\SETUP.CFG.

8.Using an ASCII text editor, edit the following entries in the SETUP.CFG file.

·Under the [AutoUpdate] heading, specifyEnabled=Yes

·SpecifyForceUpdate=Yesif you want GroupWise to automatically update the users' client software

or

SpecifyForceUpdate=Noif you want users to be prompted to update their client software.

·Specify the number of grace logins you want to allow a user before forcing an AutoUpdate, for example:GraceLoginCount=2. This entry is ignored if ForceUpdate=No.

·AutoUpdate, specifySetupIPEnabled=Yes

9.Save the file as SETUP.CFG. Copy SETUP.CFG from

\CLIENT

to

\CLIENT\WIN32 and the SYS:\APACHE\NWDOCS\CLIENT\WIN32 or SYS:\APACHE(2)\HTDOCS\CLIENT\WIN32 directory. (NetWare 6.5 uses APACHE2 as the name of its directory).

See "Modifying the Configuration File" on page 1218 in theGroupWise 6 Admin Guidefor more information regarding the SETUP.CFG file. It is recommended to run the SETUP.EXE with the modified SETTUP.CFG to test the behavior of the install before deploying the client to your users.

12.If necessary, modify ADDON.CFG files with the values you want. See"Modifying ADDON.CFG" on page 1229 in theGroupWise 6 Admin Guidefor more information.

13.Log in to ConsoleOne as an Admin equivalent.

·Click Tools > GroupWise System Operations.

·Double-click Software Directory Management.

·HIghLight the defined software distribution directory and select Update. Again, this should be the same software distribution directory that is associated with the post office. To verify go to Console One and then to the properties of the post office. Under the GroupWise Tab select the Post Office Settings and make sure that the correct SoftWare Distribution Directory is selected in the drop down menu. You can have multiple software distribution directories defined and it is recommended that each post office have its own SDD.

·Select ForceAuto-Update Check by GroupWise Components. This increases the BUMP number off the SDD.

Each time the client loads, it asks for the bump number associated with the SDD of the post office. The bump number that is associated to the SDD comes from the WPHOST.db file. There is not an easy way to look at what this is. The client then compares the bump number of the SDD with the bump number that is held in the registry of the workstation. The registry key is held here: HKEY_LOCALMACHINE\SOFTWARE\Novell\GroupWisw\Client\5.0, under the value called the NewSoftWareBump.

If the bump numbers are different the client will compare the build numbers in your registry and in the SOFTWARE.INF in the SDD. The Build number is really just the GroupWise version number. The SOFTWARE.INF is located in the SDD\CLIENT directory. The build number in your registry is held in HKEY_LOCAL_MACHINE\SOFTWARE\Novell\GroupWise

If the Build number in your registry is lower than than the build number in the SOFTWARE.INF the client will then look in the SETUP.CFG file to see if the AutoUpdate is enabled. We will also want SetupIPEnabled to say yes. The SETUP.CFG is in the SDD/CLIENT directory. Here is an example of the SETUP.CFG:

e.g.

[AutoUpdate]

Enabled=Yes

SetupIPEnabled=Yes

Make sure the POA has read and write rights to the SDD. If the POA is on the same server nothing needs to be done. If it is on a separate server add the /user and /password switch to the POA startup file or add a user name in the post office settings in the properties of the post office object using console one.

Once the upgrade kicks off, the POA will grab the SETUPIP.EXE from the SDD/CLIENT/WIN32 and execute it locally at the client. If your users have rights to the SDD, SETUPIP.EXE will not be used. Instead the SETUP.EXE will execute and you will be upgrading the client from the software distribution directory on the client rather than the web server. If you are testing and are logged in to the tree with admin rights make sure and disconnect from the tree first and launch the GroupWise client using a normal user.

Remember, the SETUPIP.EXE file was created by running the WRITEIP utility. This is how the client knows what web server(s) to go to in order to install using the SETUPIP.FIL

**Do not get the SDD confused with what is out on the webserver. To recap, on the webserver you have a client directory that contains the SETUPIP.FIL the SETUP.US and another directory called WIN32 under the CLIENT directory. This WIN32 directory contains the SETUPIP.EXE and the SETUP.CFG. The same SETUPIP.EXE and the SETUP.CFG is copied to the full SDD in the CLIENT/WIN32 directory. If you get the message that says there is new software available however you do not have rights to access it, go to the properties of the post office object/ under the groupwise tab / post office settings, and make sure that the correct sdd is selected in the drop down menu.

In the event that no connection to the SDD can be made, the file SETUPIP.ERR is created in C:\WINDOWS of the user's workstation. This file explains why none of the connections could be made.

.

Formerly known as TID# 10079869

Additional Information

Note: To use SetupIP to install the GroupWise client files, perform the following steps:

1. Verify that GroupWise 6.x Administration and GroupWise 6.x agents have been installed, and that administration, agent, and client software have been updated in your defined software distribution directory. Verify the SDD is defined and associated to your post office. Go to Console One and then to the properties of the post office. Under the GroupWise Tab select the Post Office Settings and make sure that the correct Software Distribution Directory is selected in the drop down menu. If you need to create one, go to the top tool bar select TOOLS, GroupWise System Operations, Software Directory Management. When that opens up click Create and fill in the information of where the SDD is located. There should be an SDD already created from the initial installation but if you need to change it, this is where you would do it.

2. Obtain the appropriate SETUPIP.FIL and SETUPIP.US files. With GroupWise 6, the SETUPIP files are not included in the support pack image because of its size (over 44 MB). These files must be downloaded separately from Novell Software Downloads https://download.novell.com and copied to\SETUPIP. With GroupWise 6.5 sp2, the required files are included in the support pack in the CLIENTCD directory under SETUPIP.

3. Create a directory on your web server to hold the SETUPIP.FIL and SETUPIP.US files on your web server. In our example we will call this directory \CLIENT. Underneath the new Client directory create a new WIN32 directory. Create the CLIENT directory in the document root directory of your web server. By default, NetWare 6 uses SYS:\APACHE\NWDOCS and NetWare 6.5 uses SYS:\APACHE2\HTDOCS. Verify this by looking at *.CONF file that is initiated when you load Apache. By default this is your ADMINSERV.CONF file. Note* On NetWare 6.0 if you load APACHE by running NVXADMUP.NCF then you are using ADMINSERV.CONF. If you load apache with GWWEBUP.NCF then look in GWAPACHE.CONF for the document root.

NOTE: As a minimum you must have the SETUPIP.FIL and SETIPIP.US in the SYS:\APACHE\NWDOCS\CLIENT or SYS:\APACHE2\HTDOCS\CLIENT directory or the SetupIP process will fail. You could see 2 %P characters rather than the word GroupWise in a Setup dialog and you will not see any product components to install. You could get an error "SetupIP could not copy the GroupWise setup files, Please contact your system administrator"

NOTE: The %P characters can also be seen when the web server is IIS. This will happen if you just create the CLIENT directory manually from Explorer (WWWROOT\CLIENT) instead of creating it from the Internet Services Manager (Start > Settings > Control Panel > Administrative Tools > Internet Services Manager) as a Virtual Directory. For example, start Explorer and create a CLIENT directory under WWWROOT. Copy the SETUPIP.FIL and SETUPIP.US files to the CLIENT directory. (Optional: create a WIN32 directory and copy the SETUP.CFG to the WIN32 directory.) Start Internet Services Manager > select Default Web Site > click on Actions> New > Virtual Directory -give it an Alias such as CLIENT> click Next > browse and select the CLIENT directory you just created > click Next > the Defaults of Read and Run scripts will be checked, in addition check Browse > click Finish and thats it. IIS is configured to recognize the CLIENT directory.

On a NetWare 6 server running the Apache Webserver you must verify that "Fancy Indexing" is enabled. The simplest way to do this is to locate the *.CONF file that the Apache Webserver is using and add the following three lines to the end of the *.CONF file: IndexOptions FancyIndexing On a NetWare 5.x or 6 server running the Netscape Enterprise Server for NetWare, create the directory in the SYS:\NOVONYX\SUITESPOT\DOCS directory. On a Windows NT/2000 server running the Microsoft Internet Information Server (IIS) for Windows, create the directory in the \INETPUB\WWWROOT directory. On a Solaris server running the Apache Webserver, create the directory in the /HTDOCS directory. On a Red Hat Linux server running the Apache Webserver, create the directory in the / HTDOCS directory.

4. Copy the appropriate SETUPIP.FIL and SETUPIP.US from \SETUPIP\ to the directory you created in step 3.

5. From the \SETUPIP directory run WRITEIP.EXE. Specify the full path to the SETUPIP.FIL. For example, you can specify: http://151.155.135.122/client or http://intranet.company.com/software/client You can also include proxy and port information, for example: http://name.mycompany.com/software/client:proxy.
place.mycompany:1690 You can specify up to five locations. During AutoUpdate, each location is checked, in order, until a connection is made. If you select Choose IP Address at Random, the order in which the locations are checked is selected randomly when AutoUpdate occurs. This will balance the load on the web server. „h Specify other options, such as the location for downloading the client installation files (SETUPIP.FIL or the CLIENT subdirectory files). You can have files downloaded to a temporary or specific directory. If you select Allow the User to Change the Download Directory, the user is prompted for the location of the download directory and can change the default location. „h Click OK. SETUPIP.EXE is created. WRITEIP.INI, which stores the options you selected in WRITEIP.EXE, is also created. The WRITEIP.INI does not need to be copied anywhere but may be helpful in troubleshooting issues. It contains the location of what you entered in step 5.

6. Copy SETUPIP.EXE to the \CLIENT\WIN32 directory. This should be the same software distribution directory that is associated with the post office object. The WIN32 directory needs to be the same WIN32 directory that holds the full client. To verify the correct SDD is associated, go to Console One and then to the properties of the post office. Under the GroupWise Tab select the Post Office Settings and make sure that the correct Software Distribution Directory is selected in the drop down menu. You can also copy this same SETUPIP.EXE file to the new WIN32 directory on the webserver. Example: SYS:\APACHE\NWDOCS\CLIENT\WIN32 or SYS:\APACHE(2)\HTDOCS\CLIENT\WIN32 directory. The purpose of this is to allow your users to access the SETUPIP.EXE from the website. Having a SETUPIP.EXE in the WIN32 directory of the webserver does not play a crucial role in the AUTOUPDATE process. It does however give you the option of having your users go to the website and running SETUPIP.EXE manually.

7. Make a backup copy of \CLIENT\SETUP.CFG.

8. Using an ASCII text editor, edit the following entries in the SETUP.CFG file. Under the [AutoUpdate] heading, specify Enabled=Yes Specify ForceUpdate.=Yes if you want GroupWise to automatically update the users' client software or Specify ForceUpdate=No if you want users to be prompted to update their client software. Specify the number of grace logins you want to allow a user before forcing an AutoUpdate, for example: GraceLoginCount=2. This entry is ignored if ForceUpdate=No. AutoUpdate, specify SetupIPEnabled=Yes

9.Save the file as SETUP.CFG. Copy SETUP.CFG from \CLIENT to \CLIENT\WIN32 and the SYS:\APACHE\NWDOCS\CLIENT\WIN32 or SYS:\APACHE2\HTDOCS\CLIENT\WIN32 directory. (NetWare 6.5 uses APACHE2 as the name of its directory). See "Modifying the Configuration File" on page 1218 in the GroupWise 6 Admin Guide for more information regarding the SETUP.CFG file. It is recommended to run the SETUP.EXE with the modified SETTUP.CFG to test the behavior of the install before deploying the client to your users.

10. If necessary, modify ADDON.CFG files with the values you want. See "Modifying ADDON.CFG" on page 1229 in the GroupWise 6 Admin Guide for more information.

11. Log in to ConsoleOne as an Admin equivalent. Click Tools > GroupWise System Operations. Double-click Software Directory Management. HIghLight the defined software distribution directory and select Update. Again, this should be the same software distribution directory that is associated with the post office. To verify go to Console One and then to the properties of the post office. Under the GroupWise Tab select the Post Office Settings and make sure that the correct SoftWare Distribution Directory is selected in the drop down menu. You can have multiple software distribution directories defined and it is recommended that each post office have its own SDD. Select Force Auto-Update Check by GroupWise Components. This increases the BUMP number off the SDD. Each time the client loads, it asks for the bump number associated with the SDD of the post office. The bump number that is associated to the SDD comes from the WPHOST.db file. There is not an easy way to look at what this is. The client then compares the bump number of the SDD with the bump number that is held in the registry of the workstation. The registry key is held here: HKEY_LOCALMACHINE\SOFTWARE\Novell\GroupWise\Client\5.0, under the value called the NewSoftWareBump. If the bump numbers are different the client will compare the build numbers in your registry and in the SOFTWARE.INF in the SDD. The Build number is really just the GroupWise version number. The SOFTWARE.INF is located in the SDD\CLIENT directory. The build number in your registry is held in HKEY_LOCAL_MACHINE\SOFTWARE\Novell\GroupWise If the Build number in your registry is lower than the build number in the SOFTWARE.INF the client will then look in the SETUP.CFG file to see if the AutoUpdate is enabled. We will also want SetupIPEnabled to say yes. The SETUP.CFG is in the SDD/CLIENT directory. Here is an example of the SETUP.CFG: Make sure the POA has read and write rights to the SDD. If the POA is on the same server nothing needs to be done. If it is on a separate server add the /user and /password switch to the POA startup file or add a user name in the post office settings in the properties of the post office object using console one. Once the upgrade kicks off, the POA will grab the SETUPIP.EXE from the SDD/CLIENT/WIN32 and execute it locally at the client. If your users have rights to the SDD, SETUPIP.EXE will not be used. Instead the SETUP.EXE will execute and you will be upgrading the client from the software distribution directory on the client rather than the web server. If you are testing and are logged in to the tree with admin rights make sure and disconnect from the tree first and launch the GroupWise client using a normal user. Remember, the SETUPIP.EXE file was created by running the WRITEIP utility. This is how the client knows what web server(s) to go to in order to install using the SETUPIP.FIL **Do not get the SDD confused with what is out on the webserver. To recap, on the webserver you have a client directory that contains the SETUPIP.FIL the SETUP.US and another directory called WIN32 under the CLIENT directory. This WIN32 directory contains the SETUPIP.EXE and the SETUP.CFG. The same SETUPIP.EXE and the SETUP.CFG is copied to the full SDD in the CLIENT/WIN32 directory. If you get the message that says there is new software available however you do not have rights to access it, go to the properties of the post office object/ under the GroupWise tab / post office settings, and make sure that the correct SDD is selected in the drop down menu. In the event that no connection to the SDD can be made, the file SETUPIP.ERR is created in C:\WINDOWS of the user's workstation. This file explains why none of the connections could be made.