Skip to main content

2 Messages

 • 

80 Points

Wed, Aug 30, 2017 8:45 AM

0

Add option to disable prov.exe, prov.dpk, etc.

There is no way to disable prov.exe, prov.dpk etc and use only manual connection method with dpsk? Registering devices with the device itself generates so many empty MAC addresses, that I have disabled the Onboarding portal but I would also like to disable prov.exe. Then I could tell users to open browser, go to controlleraddress.domain.com/activate, log in with AD credentials, copy the network key and use it to join their phones and tablets to our guest network. No certificate errors, no hassle, just plain and simple WPA2 key.

Responses

824 Messages

 • 

13.2K Points

3 years ago

try cloud path
 
or

create a batch DPSK and give them to users either via email and make a note to whom it was given...

5 Messages

 • 

110 Points

3 years ago

Use a radius server for auth. No need for a key. Radius -> AD

34 Messages

 • 

920 Points

3 years ago

Can you advise about your SZ model and release version? We do not support those automated onboarding functions in 3.4+. We are supporting Cloudpath for any automated onboarding (as Monnat Systems suggests). For DPSK implementations, we do have the ability to generate DPSKs within SZ without going through onboarding portals.  

2 Messages

 • 

80 Points

3 years ago

My bad, at the moment we are still using ZD and I thought that SZ works the same way. So if we are not using Cloudpath can users still generate DPSK themselves with SZ or do I have to generate it for them? And if they can, what is the address they have to browse to, is it controlleraddress/activate like in ZD or something else?

34 Messages

 • 

920 Points

3 years ago

Hi Mikko,
Ok, I understand. In SZ, we do not support the Zero-IT onboarding utility since Cloudpath does that more capably. So there is no portal page like on ZD for DPSK generation.

However, if you want to allow end-users to generate DPSKs on their own, we do have APIs within the SZ architecture by which you can accomplish this. It will require a development effort to make use of the APIs and expose the portal to your users, but the tools are there if you want to make use of native SZ functionality. Otherwise, the admin is responsible to generate DPSKs for the users from within the SZ UI.