Automatic Client Deployment on Windows – deployclient.bat has Incorrect EOL

[javinofs2]

Trying to set up automatic client deployment for Windows X64 clients. The install files get stored on client but the batch file "deployclient.bat" fails to run and update the client. When I open the file in an editor I notice that it has *nix style line endings (LF) instead of the CRLF that Windows requires.

The package imported on the server is "7.1.4.0-TIV-TSMBAC-WinX64.exp"
Server is v. 7.1.5.100 on Linux

As far as I can tell the server is not supposed to modify the files in the package when they are imported, this leads me to suspect that the files included in the package did not have the correct line endings when exported by IBM.

Have anyone else come across this?

Any suggestions on how to fix it? Is it possible to update the files in the storage pool on the server?
Does it work correctly if the import is done on a windows server.

Appreciate any help or suggestions.

-jv

 

[javinofs2]

Found the solution to this myself:

The *bat files seem to work even if they do not have windows line endings (although hard to read in an editor that does not support it). My problem turned out to be that I had forgotten to set the HLaddress of the server (SET SERVERHLADDRESS x.x.x.x).

Hope this post can be of help to anyone else coming across this.

-jv