FM 4.1.6

OS 10.4.11

MC 2.8.3

I have posted about this before, but have new info...

When mounting drives in the FM software, the software acts like the drives mounted, but nothing shows up on the desktop.  In the monitor tool, the client will be connected, but the "last seen" date is from the previous day.  After disconnecting the client in the monitor tool, and restarting the client, FM will load the drives on the desktop (this isn't a consistent fix, but it worked on the last client that had this problem).  This is happening with multiple clients randomly.  Anyone seen this?

Yes!  The workspace names must not have any spaces or underscores.  MACs have issues mounting workspaces to the desktop when this happens.  This is not an issue on PC's.

Really?  If a workspace has an underscore, does it never mount, or is its mounting random?  We have 7 clients and it is only happening randomly to 3 of them.

I just checked this with Avid--you are supposed to replace spaces with underscores.  Underscores are allowed.

Do the workspaces show up on the desktop now that the spaces have been removed?

I never had spaces.  I have underscores, which are fine.  All workspaces show up eventually.  It just gets into a weird cycle.

hi all, im having the same problem.

file manager 4.1.6, sr2200 server, dual atto 3300, dual qlogic 5602 switches (5.0.10 firmware), 8 eurologic 2 gig chassis, 98 ea 146gig drives. drivers and firmware on all the computers are the  ones that came with the respective installers. 

12 clients running 5.1 (need 5.1 for interoperability with unity 4.2.4) but the problem exist on the 4.1.6 client also.

12 clients are G5's, atto 41xs fiber cards, 10.4.11.

it began with 1 system having the problem, now its up to 4. there is no consistency, most of the time in the morning the workspaces will not mount on 4 of the 12, sometimes they all mount. usually rebooting once or twice will fix the problem. the good news is that once the workspaces are mounted, they are good for the rest of the day, or until a reboot.

the problems did not begin until the update from 4.1.5 to the 4.1.6, and the replacement of atto 3300 to celerity 41xs's on the clients.

any help or insights would be appreciated.

pete

Hey Pete, it seems as if our problems happened when the editors would login to their Macs and immediately open Fiber Manager.  Now, they login, what a minute or so, and open Fiber Manager--we have had no problems since they started doing that.  I know that sounds like fiber manager voodoo, but it seems to have solved the problem.

Hi all, just wanted to post this link to the Knowledge Base article on this. I had to deal with this and my MCA's and our LanShare a while back.  MAC clients are at the bottom.

http://tinyurl.com/56wm7u

Unity MediaNetwork Workspace Auto-Mount Issues

Microsoft Windows XP was enhanced to create the impression that the Operating System starts up faster.  The Desktop and User Login Window comes up much faster than it did on previous OS's: Win2K and NT 4.0.  However, many Services have not yet fully started before the Login Window comes up.  If one "Logs In" immediately----the Unity Connection Manager Service may not have yet fully initialized and the Auto Mount at Login feature will consequently fail.

Workarounds include:

1.) Delay Logging in by at least 5 seconds once the Windows login window pops up---so the Unity Service on the client can complete initialization first.

2.) Disable XP Logon Optimization via one of the methods listed below:

__________________

Found at http://www.kixtart.org/ubbthreads/showflat.php?Cat=0&Number=111153&an=0&page=0

Microsoft has optimized Windows XP to enhance the user experience by creating the impression that the operating system starts up faster. This is achieved by having the login prompt show up before the network is fully initialized. Additionally, existing users are logged in with cached credentials.

Drawbacks in a domain or corporate environment are that login scripts might not run, drives and printers might not be mapped, policies might not get applied, account expiration warnings might not get displayed, and GPO software distribution might fail.

The logon optimization can be disabled in the following ways:

• Local PO via "Computer Configuration\Administrative Templates\System\Logon\Always wait for the network at computer startup and logon"
• Global PO via "Computer Configuration\Administrative Templates\System\Logon\Always wait for the network at computer startup and logon"
• Per-machine registry hack as a policy via "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\Winlogon" with registry value "SyncForegroundPolicy"=dword:00000001
• Per-machine registry hack via "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" with registry value "SyncForegroundPolicy"=dword:00000001
• Per-user registry hack as a policy via "HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\Winlogon" with registry value "SyncForegroundPolicy"=dword:00000001
• Per-user registry hack via "HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" with registry value "SyncForegroundPolicy"=dword:00000001

__________________ 

Additonally; Avid Unity MediaNetwork ReadMe's recommend disabling "Windows Auto Login" which can have the same effect on the Unity Workspace Auto Mount Feature.

From the Unity - MediaNetwork 5.0 Read Me p. 17:

Windows Autologin

Avid recommends that you turn off the Windows 2000 Professional or Windows XP
Autologin feature that takes you directly to a desktop when you boot the system rather than displaying a login window. Autologin prevents some necessary Avid files from initializing properly and this prevents the Connection Manager from mounting workspaces on the desktop. For information about turning off Autologin, see your Windows documentation or Help.

___________________

Additionally p. 18 of the MN 5.0 ReadMe recommends that Mac AutoLogin be disabled for similar reasons:

Mac OS X Autologin 

Avid recommends that you turn off the Mac OS X Autologin feature that takes you directly to a desktop when you boot the system rather than displaying a login window. Autologin prevents some necessary Avid files from initializing properly and this prevents the Connection Manager or media engine from mounting workspaces on the desktop. For information about turning off Autologin, see your Apple documentation or Help.