Guillaume,
I had similar problem where by backups were aborting with the error
filename too long. NT has 256 characters limitation with filenames.
If you are do not have macintosh support on your NT server, make sure you
have you have USEUNICODEFILES NO in your dsm.opt. This should solve
t
Change the password expiration on the tsm server to max value of days. This has helped us resolve password expiration problem on our NT environment
Cheers
Kelil
>From: "Selva, Perpetua" <[EMAIL PROTECTED]>
>Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>
HKEY_LOCAL_Machine\IBM\ADSM\NODES
Kelil
>From: Patricia LeBlanc <[EMAIL PROTECTED]>
>Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: TSM Client on W2K
>Date: Tue, 18 Sep 2001 11:20:58 -0400
>
>For a TSM Client on W2K..when you have "passwordaccess
We recently upgrade NT client from version 3.1.7 to 4.1.3. Since the upgrade we have had problems backing up some of our clients. Scheduled backups abort with the error of long filenames. However, the same files that we are having problems backing up with the new client used to be backuped with
HI,
We are running TSM 3.7.4 on an AIX 4.3.3 Server. Recently we upgraded the NT clients from 3.1.7 to 4.1.3. After the upgrade most of the clients were unable to log into the server.
We kept on getting password expiration problem. As a result, we reset the passwords for all nodes that expired
I have a batch file on al the domain controllers that i run centrally to stop and start all the TSM scheduler service for the servers in that domainFor example,NETSVC TivoliCentralScheduler /stop \\SERVER1sleep 5NETSVC TivoliCentralScheduler /start \\SERVER1
Cheers
Kelil
>From: "Chan, Kien