Quantcast
Channel: VMware Communities : All Content - All Communities
Viewing all articles
Browse latest Browse all 179681

Horizon JMP config not accepting UEM credentials

$
0
0

Hi All,

 

Just a trap that I have spent a bit of time debugging while configuring UEM for JMP on horizon

 

Using Horizon 7.5.2 with JMP server 7.5.2 you try to add a user to manage UEM and it keeps failing with

"The UNC path appears to be invalid. Please modify and try again."

or

"Could not process your request. Please try again later"

 

Look in the JMP logs on the jmp server and you get

 

[2019-09-25 23:23:33 UTC]    P8960R124  INFO Started POST "/xms/file_shares" for 127.0.0.1 at 2019-09-26 09:23:33 +1000

[2019-09-25 23:23:33 UTC]    P8960R124  INFO Processing by Xms::FileSharesController#create as JSON

[2019-09-25 23:23:33 UTC]    P8960R124  INFO   Parameters: {"data"=>{"name"=>"\\\\share\\Share_folder", "virtual"=>"false", "physical"=>"false", "policies"=>"true", "images"=>"false", "auto_import"=>"true", "type"=>"FileShare", "status"=>"pending", "status_message"=>"", "username"=>"USERNAME", "password"=>"[FILTERED]", "domain"=>"DOMAIN", "path"=>"\\\\share\\Share_folde", "local_path"=>"", "node_id"=>"1", "last_sync"=>"2019-09-25T23:23:33.245Z"}}

[2019-09-25 23:23:33 UTC]    P8960R124  INFO  Referred by nothing using unknown browser

[2019-09-25 23:23:33 UTC]    P8960R124 DEBUG Requested XMS version (20160205.0) is acceptable, server version is (20160205.0)

[2019-09-25 23:23:33 UTC]    P8960R124 DEBUG Authorized tenant "1" (cached)

[2019-09-25 23:23:33 UTC]    P8960R124 DEBUG Checking if mount exists: "wmic netuse where RemoteName="\\\\share\\Share_folde" get RemoteName".

[2019-09-25 23:23:33 UTC]    P8960R124 ERROR Unable to mount file share: error 1

[2019-09-25 23:23:33 UTC]    P8960R124 ERROR Unable to create file share "//share/Share_folde"

[2019-09-25 23:23:33 UTC]    P8960R124 DEBUG Error creating file share: {:status=>:bad_request, :json=>{:error=>"Unable to create file share \"//share/Share_folde\""}}

 

This is because it can't handle complex passwords.

 

I changed the password for my service account to something that didn't have special characters and it worked.

 

Good luck all

Tom


Viewing all articles
Browse latest Browse all 179681

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>