We are using Opus 10 (x64) on Windows Server 2008 R2 and have noticed that if we autolaunch Opus at logon then pretty much every time the network drives (some or all of them) are missing from the Folder Tree even though the contents of one of them is actually visible in the file list. If the user presses F5 then usually but not always one or more of the network drives will appear in the Folder Tree. However, if the user closes and reopens Opus then all the drives always appear and function fine. It's almost like Opus is autolaunching before the network drives are actually available. Opus 9 used to do this on the same server as well but it would throw an error at the user. I'm pleased to see that Opus 10 doesn't throw an error when this happens.
Are you familiar with this issue? Is there anything I can do about it? Unfortunately, we also publish Opus as a seamless XenApp application where the problem also happens as well. It's not possible for me to simply stop people autolaunching Opus. When it's published as a seamless XenApp application it's effectively autolaunching by definition.
It's likely that the network drives were not yet ready when Opus was launched. Windows typically does not wait for network drives to connect and start working before launching things at startup.
If you edit the Refresh/F5 command and set it to Go REFRESH=all then that may make F5 fix things. (There's also Go REFRESH=tree if you want to keep F5 doing its normal thing and have another button/key to force the tree to refresh.)
[quote="leo"]It's likely that the network drives were not yet ready when Opus was launched. Windows typically does not wait for network drives to connect and start working before launching things at startup.
If you edit the Refresh/F5 command and set it to Go REFRESH=all then that may make F5 fix things. (There's also Go REFRESH=tree if you want to keep F5 doing its normal thing and have another button/key to force the tree to refresh.)[/quote]
Leo,
Thanks, that's exactly the conclusion I came to as well. Does it make any sense to you that I'm only seeing this issue now after so many years using Opus on various systems I've been using Opus for more than 5 years on Windows XP, Windows 7, Windows Vista, Windows Server 2003 and I've never seen this until I tried to use Opus 9 and then 10 on Windows Server 2008 R2. I'm wondering if it's either something that might have changed in Windows Server 2008 R2 or else if I'm having a problem of the server being too fast (it's a Dell PE820 with 4 8-core CPUs and 64 GB of ram). The drive mappings come from a logon script....I wonder if there's something I could do with that via group policy or even introducing a delay into the script.
[quote="jproos"][quote="leo"]It's likely that the network drives were not yet ready when Opus was launched. Windows typically does not wait for network drives to connect and start working before launching things at startup.
If you edit the Refresh/F5 command and set it to Go REFRESH=all then that may make F5 fix things. (There's also Go REFRESH=tree if you want to keep F5 doing its normal thing and have another button/key to force the tree to refresh.)[/quote]
Leo,
Thanks, that's exactly the conclusion I came to as well. Does it make any sense to you that I'm only seeing this issue now after so many years using Opus on various systems I've been using Opus for more than 5 years on Windows XP, Windows 7, Windows Vista, Windows Server 2003 and I've never seen this until I tried to use Opus 9 and then 10 on Windows Server 2008 R2. I'm wondering if it's either something that might have changed in Windows Server 2008 R2 or else if I'm having a problem of the server being too fast (it's a Dell PE820 with 4 8-core CPUs and 64 GB of ram). The drive mappings come from a logon script....I wonder if there's something I could do with that via group policy or even introducing a delay into the script.
Thanks,
Jason[/quote]
Can you remind me how to edit the Refresh/F5 command?
It seems to be C:\ProgramData\GPSoftware\Directory Opus\Buttons\ListerMenu.dop (I'm using a Shared Configuration for my own profile). I realize that the users' file will be in C:\Users\username\AppData\Roaming\GPSoftware\Directory Opus\Buttons. Those paths are for Windows Server 2008 R2 and probably the same for Windows 7.