Preconfigure desktop client

Is there a way to customize the desktop client for windows, that the user only has to type in his Username and password?
I tried to edit the conf file, but when i deleted the username, the client only asked about an password, and there were no way to type in an username.
Furthermore i’d like to define the url as standard and the sync folder.

Thanks for your help.


This is currently not possible. There was some ticket on ownCloud client, but I think this is out of scope for the moment :grin:



I would like to see an automatic installer for a rollout in an enterprise, too. Some parameters, e.g. a silent switch or the setting of a default path for syncing would help a lot. Cheers, Hans

1 Like

@Hansi Silent switch is present – try /S :slight_smile:

Default path and others you can find at C:\Users\user_name\AppData\Local\Nextcloud\nextcloud.cfg. You can edit it before or after silent installation. I tries this with some success :slight_smile:

I also tested some installations with Scalable Discovery with some success. I will try to ask our devs for look if they could prepare new exe with cfg file or more switches. But it may takes some weeks.


Thank you for the Information. Cheers, Hans

I found out something very bogus, but it works.

if you paste https://[username]:[password]@[nextcloudurl] into the URL Box, the nextcloud Installer
will paste all the needed information to the correct boxes on the Username and Password entry Step.

all you have to do here is click next.

1 Like

Yes, but the login/password windows still exist at the configuration wizard but it fills with data.

Hi Therion7777.

Could you please share info about preconfig/unattended?
Probably was developed a new execution keys which will allow to set server address and local path during install ?

Unfortunately not.
We decide to push the client configuration to users hands.

We simply drop clients from AD with this .bat:

@echo off

if EXIST “C:\Program Files (x86)\Nextcloud\nextcloud.exe” GOTO :End
if EXIST “C:\Program Files\Nextcloud\nextcloud.exe” GOTO :End


copy \\SysVol\\scripts\Nextcloud\nextcloud2242.exe %windir%\Temp

%windir%\Temp\nextcloud2242.exe /S



thnx for reply.

i know how to deploy software…
the biggest issue for me - client configuration. but now i create “man” for that.
i hope that end users will not crash system :slight_smile:

do you have any plan for end users autoconfig?

1 Like

Nope. Not know. We don’t have free resources to do it… :slight_smile:

I managed to install the client with PDQ deploy (using the /S option, not /s!!!) but had to create manually a nextcloud.cfg file

I used an existing .cfg file, broke it up into three pieces and created a batch file for the user to execute (wih PDQ deploy you can automate this):

if not exist %LOCALAPPDATA%\Nextcloud*.* md %LOCALAPPDATA%\Nextcloud
type “\iag.local\data\software\algemeen software\Nextcloud\nextcloud.1.cfg.txt” > %LOCALAPPDATA%\Nextcloud\nextcloud.cfg
echo C:/users/%USERNAME%/Appdata/Local/Nextcloud >> %LOCALAPPDATA%\Nextcloud\nextcloud.cfg
type “\iag.local\data\software\algemeen software\Nextcloud\nextcloud.2.cfg.txt” >> %LOCALAPPDATA%\Nextcloud\nextcloud.cfg
echo %USERNAME% >> %LOCALAPPDATA%\Nextcloud\nextcloud.cfg
type “\iag.local\data\software\algemeen software\Nextcloud\nextcloud.3.cfg.txt” >> %LOCALAPPDATA%\Nextcloud\nextcloud.cfg
echo %USERNAME% >> %LOCALAPPDATA%\Nextcloud\nextcloud.cfg

This is currently not possible. There was some ticket on ownCloud client, but I think this is out of scope for the moment

Well it was in the scope of a paid feature:


You’re aware that you quoted a post from December 2016? :roll_eyes:

It’s still relevant. Why no MSI other than for paid subscribers? Seems like a bait and switch from the free and open source Nextcloud I signed up for.

Me ? The article is dated November 13, 2019

IMHO: If your enterprise is big enough to rely on sth like this you should buy an enterprise subscription. Nextcloud (the company) has to pay their bills anyway too.

Sorry for the off topic.

Not related to Nextcloud (the company) anyway.

The quoted post (with the grey background) is from December 2016.