I created script to update notes.ini, silent install, etc… Well… it is not so silent in the begiining thanks to the ECL warnings. Once it gets started, it works great with the /qb!+ option. The issues… the SetEnvironmentVar, Execute, RunAgent all bark. The template is signed by the “new” admin server. In most cases, this server is not in the user’s ECL. You get 3 ECL screens… just doing its job, right? Any thoughts? I thought about getting creative with a transform file to handle ini change… that does not solve the upgrade execution. The servers are R7 and security profiles have been updated to include admin server. The R5 clients are not dynamic like the R7 clients… requires a manual refresh. Possible to automate this? I thought about @RefreshECL… problem is the ECLSetup=3… keeps it from working. A manual “click the refresh” button under user prefs works. Any thoughts?
Subject: R5 Client Upgrades → 7.0.2 & ECL Woes
This might be better than 3 separate ECL warnings. I used it a number of years ago. You can drop the last command, if preferred. Either adjust the @Prompt or eliminate it altogether. Test it with a few users. It may be that you get no warnings and it is truly silent.
@Prompt( [OK]; “Information”; “This button will … something.” + @Char(10) + @Char(10) + “Click TRUST SIGNER if prompted with an Execution Security Alert.”);
@PostedCommand( [FileCloseWindow] );
@RefreshECL( “server/ou/o” : “names.nsf”; “” );
@PostedCommand( [WindowWorkspace] );
Subject: RE: R5 Client Upgrades → 7.0.2 & ECL Woes
Thanks… the @postedcommand would process after the @RefreshACL, right? I’ll try the refresh ECL… though there was a problem with he ECLSetup=3 on 5.x clients when using the @RefreshACL. It would be great if the RefreshACL would work prior to any of the @Commands. Will post results…