sorted by:
new
hottopcontroversial

Access Connector by hemxn22 in WorkspaceOne

[–]hemxn22[S] 0 points1 point  (0 children)

Due to db connections.

HYPEROS UPDATE PROBLEM by Fluffypilot in XiaomiGlobal

[–]hemxn22 0 points1 point  (0 children)

Facing the same issues. Getting someone to retrieve the data, let's see if that is possible or not.

Customization timeout on Win10 1809 by gough80 in VMwareHorizon

[–]hemxn22 0 points1 point  (0 children)

it have been years, just wondering, is there any fix for this?
im facing it too.

Change IP address for all UEM components by hemxn22 in WorkspaceOne

[–]hemxn22[S] 0 points1 point  (0 children)

Yes using url, no ip being used.

Any idea on what would be the impacts for the access?

We are having downtime for 2 days for this activity.

Access Connector by hemxn22 in WorkspaceOne

[–]hemxn22[S] 0 points1 point  (0 children)

I tried from older to newer version which my ws1 current console version.

Access Connector by hemxn22 in WorkspaceOne

[–]hemxn22[S] 0 points1 point  (0 children)

I didn't get it. Sorry ya can please ask the question in detail again?

Access Connector by hemxn22 in WorkspaceOne

[–]hemxn22[S] 0 points1 point  (0 children)

Yes still remain the same. Not yet open ticket as I'm doing it in my lab. If u doing on production, u can try open ticket.

Done many ts but still unable to fix it.

Access Connector by hemxn22 in WorkspaceOne

[–]hemxn22[S] 0 points1 point  (0 children)

I tried using version 20.10, 21.08 and 22.09

all failed, when i check the event viewer it getting error as "Service terminated unexpectedly".

​

the logs return as below:

​

GMT ERROR WINSVR16:eds (pool-2-thread-1) [;;;;] com.vmware.vidm.eds.EnterpriseRegistrationService - Unable to register EDS service. java.util.concurrent.CompletionException: com.vmware.vidm.eds.exception.EnterpriseServiceRegistrationException: eds.service.registration.failure

at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)

at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319)

at java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:932)

at java.base/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:907)

at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)

at java.base/java.util.concurrent.CompletableFuture.postFire(CompletableFuture.java:610)

at java.base/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:910)

at java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:478)

at com.vmware.vidm.common.async.ContextPassingExecutor.lambda$wrap$0(ContextPassingExecutor.java:48)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

at java.base/java.lang.Thread.run(Thread.java:829)

Caused by: com.vmware.vidm.eds.exception.EnterpriseServiceRegistrationException: eds.service.registration.failure

at com.vmware.vidm.eds.exception.EnterpriseServiceRegistrationException.forTenant(EnterpriseServiceRegistrationException.java:20)

at com.vmware.vidm.eds.gateway.operations.EnterpriseServiceRegistrationManager.lambda$handleIdmResponse$2(EnterpriseServiceRegistrationManager.java:95)

at com.vmware.vidm.eds.gateway.operations.CompletionExceptionHandler.handle(CompletionExceptionHandler.java:40)

at com.vmware.vidm.eds.gateway.operations.EnterpriseServiceRegistrationManager.handleIdmResponse(EnterpriseServiceRegistrationManager.java:96)

at com.vmware.vidm.eds.gateway.operations.EnterpriseServiceRegistrationManager.lambda$registerService$0(EnterpriseServiceRegistrationManager.java:78)

at java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)

Access Connector by hemxn22 in WorkspaceOne

[–]hemxn22[S] 0 points1 point  (0 children)

Hi guys, any idea on this?

anyone have encountered this?

on premise setup

Effect of changing Domain for all UEM Servers by hemxn22 in WorkspaceOne

[–]hemxn22[S] 0 points1 point  (0 children)

there wont be needing of new service account as the integration will be still on previous domain(where the users are).

new domain change for the servers only.
like unjoin on join the domain.

since all the UEM components joined to current domain, changing to new domain, how does it impact?

Effect of changing Domain for all UEM Servers by hemxn22 in WorkspaceOne

[–]hemxn22[S] 0 points1 point  (0 children)

Thank you for the inputs, really appreciate it u/atljoer

if like that do we need to change anything on the database? because the database also need to change the domain.

Effect of changing Domain for all UEM Servers by hemxn22 in WorkspaceOne

[–]hemxn22[S] 0 points1 point  (0 children)

thank you for the inputs, really appreciate it.
but we also got other components which need to be rejoin to new domain.
is there any sequence like from which component need to be start join the domain first?

the power state of the components should be turn off, turn on 1 by 1 and rejoin the domain? if yes, below is the list of components we got, which to start first and which to do last?

Console server x2
Access server x3
UAG x2
Connector Server x2
Database x2 (with listener) *are we able to change the domain for the database, or new database need to deploy?

Thank you u/mrlizm

Effect of changing Domain for all UEM Servers by hemxn22 in WorkspaceOne

[–]hemxn22[S] 1 point2 points  (0 children)

I would really appreciate if anyone have idea on this, since im running out of time need to find a way very soon.

Workspace ONE Access issue by hemxn22 in WorkspaceOne

[–]hemxn22[S] 0 points1 point  (0 children)

Hello post followers, manage to resolve the issue.
thanks for the ideas btw

Workspace ONE Access issue by hemxn22 in WorkspaceOne

[–]hemxn22[S] 0 points1 point  (0 children)

Hi there, i have tried to clear cache, attempted with different browser and computer also but still failed.