Search results for query: *

Hi, I would create a batch file like this: --- @echo off net use f: \\TNGserver\office start /wait f:\path\to\setup.exe /qb- if %ERRORLEVEL% NEQ 0 echo Installation error (EC %ERRORLEVEL%) > %1 --- Name it to whatever.CMD and put it into the volume of the package you create. Don't forget to...

Adrian, we are running the Engine service under the local system account. That's why we needed to define the share name of the sector (AMsector$ by default) to the system registry (HKLM/SYSTEM/CurrentControlSet/Services/lanmanserver/parameters/NullSessionShares - AMSECTOR$) on the sector...

Adrian, so this error is present on the second engine only ? If you keep getting the problems with both the engines, you can have a problem with the sector. Anyway, check: 1. basically - access to the sector computer from the engine (RW permissions, etc.) 2. the sector has a network share...

What TNG version are you using ? What OS, Service Pack ? We used to have Unicenter 2.2 running on our NT4.0 SP6a servers. Experiencing the same problems, including some Dr. Watsons on caoprdmn.exe the problem was solved by upgrading to TNG 2.4. Regards, Ondra

Hello, SDO uses WOL by default. Note that it works only on LAN as it uses a broadcasts. To reboot a workstation remotely you can use shutdown.exe from NT Resource Kit. Cheers, Ondra