The functionality of this Fling has been integrated into Horizon View 6.1 and due to this, this Fling has been retired. This means that this Fling will not be updated in the future and comments will not be responded to. However, you can still download this Fling if you are using earlier versions of Horizon View.
May 13, 2015

I keep receiving Java errors on windows 2012 when I run --scanMachines

Can anyone advist

Sep 29, 2015

I kept getting Java errors too while running these commands on Server 2012 R2. Open command prompt and run as admin and the commands worked flawlessly in Server 2012.

Oct 01, 2015

Hi Braxton,

Can you post the error text here in as much detail as possible.
Also, what version of View are you using? Later versions of View come with this tool included in the install.

thanks

Oct 01, 2015

Connection Server = Server 2012 R2
VMware View version = 6.1.1 build-2769403
Using the viewdbchk.cmd that is included in the connection server install located at C:\Program Files\VMware\VMware View\Server\tools\bin

I was able to get the command to run when running command prompt as administrator and the tool worked great.

Below is the error that it returns when running --scanMachines

javax.naming.AuthenticationException: GSS-SPNEGO [Root exception is javax.securi
ty.sasl.SaslException: Failed to initiate authentication: com.vmware.vdi.common.
winauth.WinAuthCodifiedException: Failed to start authentication negotiation: Un
known error [Caused by com.vmware.vdi.common.winauth.WinAuthCodifiedException: F
ailed to start authentication negotiation: Unknown error]]
at com.sun.jndi.ldap.sasl.LdapSasl.saslBind(LdapSasl.java:168)
at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:235)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2740)
at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:316)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193)

at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211
)
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.ja
va:154)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.jav
a:84)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
84)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307
)
at javax.naming.InitialContext.init(InitialContext.java:242)
at javax.naming.ldap.InitialLdapContext.(InitialLdapContext.java:1
53)
at com.vmware.vdi.ldapcontextpool.LdapContextManager$LdapContextPool.new
LdapContext(LdapContextManager.java:826)
at com.vmware.vdi.ldapcontextpool.LdapContextManager$LdapContextPool.get
LdapContext(LdapContextManager.java:729)
at com.vmware.vdi.ldapcontextpool.LdapContextManager$LdapContextPool.get
LdapContext(LdapContextManager.java:748)
at com.vmware.vdi.ldapcontextpool.LdapContextManager.getLdapContextForPo
ol(LdapContextManager.java:185)
at com.vmware.vdi.ldapcontextpool.LdapContextManager.getLdapContext(Ldap
ContextManager.java:142)
at com.vmware.vdi.viewdbchk.desktop.MiniDesktopTracker.initialize(MiniDe
sktopTracker.java:293)
at com.vmware.vdi.viewdbchk.desktop.MiniDesktopTracker.getInstance(MiniD
esktopTracker.java:305)
at com.vmware.vdi.viewdbchk.command.ScanMachines.execute(ScanMachines.ja
va:79)
at com.vmware.vdi.viewdbchk.command.ViewDbCmd.execute(ViewDbCmd.java:409
)
at com.vmware.vdi.viewdbchk.ViewDbChk.go(ViewDbChk.java:129)
at com.vmware.vdi.viewdbchk.ViewDbChk.main(ViewDbChk.java:62)
Caused by: javax.security.sasl.SaslException: Failed to initiate authentication:
com.vmware.vdi.common.winauth.WinAuthCodifiedException: Failed to start authent
ication negotiation: Unknown error [Caused by com.vmware.vdi.common.winauth.WinA
uthCodifiedException: Failed to start authentication negotiation: Unknown error]

at com.vmware.vdi.common.winauth.sasl.WinAuthSASLClient.prepareSASLCtx(W
inAuthSASLClient.java:118)
at com.vmware.vdi.common.winauth.sasl.WinAuthSASLClient.evaluateChalleng
e(WinAuthSASLClient.java:146)
at com.sun.jndi.ldap.sasl.LdapSasl.saslBind(LdapSasl.java:123)
... 22 more
Caused by: com.vmware.vdi.common.winauth.WinAuthCodifiedException: Failed to sta
rt authentication negotiation: Unknown error
at com.vmware.vdi.common.winauth.WinAuthCodifiedException.fromResponse(W
inAuthCodifiedException.java:103)
at com.vmware.vdi.common.winauth.UserContext.initiateSASLAuthentication(
UserContext.java:399)
at com.vmware.vdi.common.winauth.UserContext.initiateSASLAuthentication(
UserContext.java:367)
at com.vmware.vdi.common.winauth.UserContext.initiateSASLAuthentication(
UserContext.java:351)
at com.vmware.vdi.common.winauth.sasl.WinAuthSASLClient.prepareSASLCtx(W
inAuthSASLClient.java:114)
... 24 more

Oct 01, 2015

So everything is ok when running as an administrator? but if you use a regular user you get the error?

If this is the case the behaviour is expected. The tool asks the connection server process to perform some work for it. The transport used for this has a security check that insists that the ViewDbChk process is run as an administrator.

Oct 01, 2015

That is correct. Right clicking and running command prompt as admin works without issue. I was posting the comment because often times I forget to run things as admin and thought it may help others in the future.

Oct 01, 2015

Hi Braxton,

Thanks for confirming.

The security check has to insist on the user being an administrator in order to run any commands - because they are pretty powerful....

Thanks

Griff

May 14, 2015

Hi Declan,

Can you provide a few more details on the
- version of View you are using the fling with
- details of the error you are seeing

Thanks

Mar 12, 2015

Thank you very much.
Very very very good game :)

Feb 14, 2015

Does this scan against missing/orphan VMs not in ADAM as well, or do we need to prompt which pools to scan?

Feb 15, 2015

Hi Anton,

No, ViewDbChk won't detect VMs that are missing from ADAM. If the entry for a VM has been removed from ADAM, View will attempt to re-provision the VM and re-create the ADAM entry before failing because the VM already exists.

Griff

Feb 12, 2015

This is awesome!!!