Hi!
O2K13 C2R. Using for setup ODT and everything is ok, starting with download and ending deploying. Unattended way on hundreds of devices. No problem. But with update ... not so good. Using C2R Client update option ... much faster than setup, good to have. But, there is a "but". In our environment I can't expose setup source files to the world. During initial setup I used login credentials for accessing network share where setup files is placed. And, as I wrote, no problem at all. But, seems to, officec2rclient.exe handling things differently (btw, I could be wrong, I hope, this is why I'm here!). Keeping in mind – I can't expose setup source files. So, update (as far I find out) must be done with interactive user present and user must have at least read permissions to share. I couldn't user dynamic admin user I could use with setup wo interactive user present with permissions to share (where setup files present), I couldn't use system account at all as ... no "user" present. I can't run update that way on hundreds of devices, can I! Please advise! I certainly hope I missed something. But keep in mind, I can't expose setup source files to the "world". Is there a way to use update (which is much faster as I noted comparing to full setup) and not exposing setup source files? (Well, I haven't chance to try does this "public" read-only option for source files work, bit probably it does.)
Luckily I can still use ODT setup over older Office version to update, but – as stated – this is much slower than update option.
More thanks, Alar.
And maybe, just maybe, officec2rclient.exe for O2K16 has better design on this one. If I'm correct.