I will be upgrading approx. 2500 Windows 95b workstations to NetWare Client 3.31e. The PC's are currently running a mix of client versions anywhere from 2.x to 3.3.
I have prepared an "unattend.txt" file using nciman.exe to include all the proper client settings. I will be installing only the NetWare Client and Workstation Manager components.
I launch the setup via login script as follows: #<path>\setup.exe /acu /u
The client installation completes as expected. However, being that this will be an enterprise rollout of the client I have two concerns:
1. Winsock is updated to Winsock2 and upon completion of this update, a message box appears saying "These files were updated... you must restart..." and prompts the user to hit OK. The client upgrade process then continues.
2. During the file copy process of the installation the user has the ability to click cancel. The result is that the client installation fails and when the workstation is rebooted many error messages are displayed and there is no functional NetWare client on the machine.
Has anyone run into these issues in the past? Any know workarounds? Input on how to remedy these issues is greatly appreciated.
JL
I have prepared an "unattend.txt" file using nciman.exe to include all the proper client settings. I will be installing only the NetWare Client and Workstation Manager components.
I launch the setup via login script as follows: #<path>\setup.exe /acu /u
The client installation completes as expected. However, being that this will be an enterprise rollout of the client I have two concerns:
1. Winsock is updated to Winsock2 and upon completion of this update, a message box appears saying "These files were updated... you must restart..." and prompts the user to hit OK. The client upgrade process then continues.
2. During the file copy process of the installation the user has the ability to click cancel. The result is that the client installation fails and when the workstation is rebooted many error messages are displayed and there is no functional NetWare client on the machine.
Has anyone run into these issues in the past? Any know workarounds? Input on how to remedy these issues is greatly appreciated.
JL