For the most part you can REM that out... It's been a while, but I think the cause is the PATH variable is too long. Joe On 3/27/07, StGeorge <wcsconnect@xxxxxxxxx> wrote:
Hello Jeremy, We have this occasionally... If you put pauses in your usrlogon.cmd you will find it fails when it calls the setpaths.cmd ( first 3 lines of usrlogon.cmd) We have researched this but never found a full solution. It might help you though. Regards Rob On 3/28/07, Jeremy Saunders <jeremy.saunders@xxxxxxxxxxx > wrote: > > Would anyone know of a situation when usrlogon.cmd would not run? I've > been > asked to lock down a terminal server, built by a 3rd party, and I > noticed > that usrlogon.cmd is not running. It's in the AppSetup key, but just > doesn't run. A bit bizare. > > Cheers. > > Kind regards, > > Jeremy Saunders > Senior Technical Specialist > > Infrastructure Technology Services > (ITS) & Cerulean > Global Technology Services (GTS) > IBM Australia > Level 1, 1060 Hay Street > West Perth WA 6005 > > Postal: PO Box 525, West Perth WA > 6872 > > Visit us at > http://www.ibm.com/services/au/its > > P: +61 8 9261 8412 F: +61 8 9261 8486 > P: (Reception) +61 8 9261 8420 E-mail: > M: TBA jeremy.saunders@xxxxxxxxxxx > > > > > > > > > > SBC SITES ONLY GOOGLE SEARCH: http://www.F1U.com > ************************************************ > For Archives, RSS, to Unsubscribe, Subscribe or > set Digest or Vacation mode use the below link: > //www.freelists.org/list/thin > ************************************************ >