• Replies 2 replies
  • Subscribers 336 subscribers
  • Views 33 views
  • Users 0 members are here
Related

Mapped drives & running Tess locally instead

Former Member
Former Member $organization

Hi everyone,

We have been having some issues lately with our mapped drives which has meant that even though Tessitura is up and functioning, anyone who tries to log in can’t access it due to their T:\ being ‘down’.

Is there an alternate way that Tessitura can be set up on the local stations so they don’t require the mapped drives to be operational in order to use Tess? Of course having the mapped drives just work (always) is ideal….but when they don’t, it would be great if this didn't make Tess unavailable to our users.

The reports library is the only thing I can think of as being a potential problem to having everything  run locally. Is there a way around this?

Could you have LOCAL_LIBRARY_LIST in T_DEFAULTS reference the local machine somehow? Then have the local library sync via a group policy with the T:\ on a schedule? What about all the other network paths in T_DEFAULTS, they would still work, wouldn't they?

In the long run, it looks like Terminal Services is the way to go (from reading other forum threads) but at this stage, running locally is where we are at. Is this possible?

Thanks as always for any advice,

Tash 

Parents
  • $organization

    Hi Tash

    how is the T: drive getting mapped? Is it via windows logon script or do you manually map the drive?  If it is this, you can check to see if the users are closing their logon script by adding:


    time /t > %temp%\logon.log
    date /t >> %temp%\logon.log
    ipconfig /all >> %temp%\logon.log

    to the top of their logon script and

    time /t >> %temp%\logon.log
    date /t >> %temp%\logon.log
    dir t:\ >> %temp%\logon.log

    to the bottom.  If you check the %temp%\logon.log file on their machine, if there aren't two time and date stamps in there, the user has closed their logon script and you can ignore the rest of this post.

     

    Depending on how you start Tessitura, you could add to that process to check for the existence of a file on your T: drive.

    The logic behind the code below is

     

    • it checks for the existence of a file on your t: drive
    • if it can't find it, it remaps the drive, 
    • puts a 4 second delay in (the ping command) 
    • then start Tessitura.  

     

    If you use a batch file to start tessitura, you could add similar to this (probably not exactly this):

    @cls
    if not exist t:\Installation\ini\LIVE.ini (
    net use t: /delete
    net use t: \\servername\foldername
    )
    ping 127.0.0.1 
    c:\program files\impresario\tessitura.exe t:\installation\ini\live.ini 

     

    You can, on your own head be it, have a local T: drive mapped by using the subst command:

    subst T: C:\LocalTDriveFolder

    I don't suggest using this method - or use it as a last resort

     

    Hope this helps pointing you in the right direction for a fix.

    Thanks

    Wayne

Reply
  • $organization

    Hi Tash

    how is the T: drive getting mapped? Is it via windows logon script or do you manually map the drive?  If it is this, you can check to see if the users are closing their logon script by adding:


    time /t > %temp%\logon.log
    date /t >> %temp%\logon.log
    ipconfig /all >> %temp%\logon.log

    to the top of their logon script and

    time /t >> %temp%\logon.log
    date /t >> %temp%\logon.log
    dir t:\ >> %temp%\logon.log

    to the bottom.  If you check the %temp%\logon.log file on their machine, if there aren't two time and date stamps in there, the user has closed their logon script and you can ignore the rest of this post.

     

    Depending on how you start Tessitura, you could add to that process to check for the existence of a file on your T: drive.

    The logic behind the code below is

     

    • it checks for the existence of a file on your t: drive
    • if it can't find it, it remaps the drive, 
    • puts a 4 second delay in (the ping command) 
    • then start Tessitura.  

     

    If you use a batch file to start tessitura, you could add similar to this (probably not exactly this):

    @cls
    if not exist t:\Installation\ini\LIVE.ini (
    net use t: /delete
    net use t: \\servername\foldername
    )
    ping 127.0.0.1 
    c:\program files\impresario\tessitura.exe t:\installation\ini\live.ini 

     

    You can, on your own head be it, have a local T: drive mapped by using the subst command:

    subst T: C:\LocalTDriveFolder

    I don't suggest using this method - or use it as a last resort

     

    Hope this helps pointing you in the right direction for a fix.

    Thanks

    Wayne

Children