I just recently started a new Connections envoirnment including Docs.
After performing the default Connections installation I prepared the Windows envoirnment for the Docs 2.0.1. After all network path & mounts were set I started the installation....
After some time the Installation Manager cancelled the installation "can not create directory K:". K: is the shared data drive for Docs-Editor component. To workaround the issue I just started installing 2.0 CR3 instead. This installation was successfull.
Afterwards I tried to reproduce the issue in my testing envoirnment on Windows: Same issue here. 2.0 CR3 installation works fine - 2.0.1 installer fails with error message "can not create directory". I opened a case @HCL and after several months they came to the following conclusion:
We discussed this issue in team again and per our communication with L3/Dev, the current installer behavior is a more proper logic as most of customers has few knowledge about CIFS.
We embed checking steps to help them build once and success all the time. If you have security concerns, you can configured CIFS with SYSTEM before the Docs installation. After installation, you can try to change CIFS mount user to the one you'd prefer. But make sure the user you choose has privilege to allow the user that running Docs program access CIFS. The info center documentation will be updated and we will clearly state that customer must configure CIFS with SYSTEM user, as we already have notes in place that the procedure of mounting the shares must be done by SYSTEM user. From current documentation you are correct, I also didn't see it is a "must". It only says, if customer wants to start CIFS automatically, it is a must.
Lessons learned : always install Docs with Websphere running as "SYSTEM"
