kpelt's Posts

We recently lost power in our lab and had a hard shutdown on our identity manager cluster.  When powering up, both ID manager servers get stuck during POST at rabbitmq starting.  Any ideas how to... See more...
We recently lost power in our lab and had a hard shutdown on our identity manager cluster.  When powering up, both ID manager servers get stuck during POST at rabbitmq starting.  Any ideas how to fix this?
Has anyone come up for the reason this happens?  I am in the exact situation and it looks like it is trying to reference a VM that no longer exists.
I have redeployed the vApp in an effort to check something.  I think it is possible the integration with View might be causing the issue.  Currently still syncing and will report back after furth... See more...
I have redeployed the vApp in an effort to check something.  I think it is possible the integration with View might be causing the issue.  Currently still syncing and will report back after further testing.
Ok, more information.  Apparently folders are not using the SSL handshake when created so no error on that.  Files on the other hand require this and I guess I am going to have to create some cer... See more...
Ok, more information.  Apparently folders are not using the SSL handshake when created so no error on that.  Files on the other hand require this and I guess I am going to have to create some certificates.
That says to me that it is still looking for your old Workspace vApp because you shut it down and it says "no route to host".
Not a time issue.  What is even more odd about these file sync errors is it does not occur with folders.  Only files.
I possibly could be mistaken on the "whole domain" as I am seeing it supposedly will not work with that setup.  I have not had issues with this setup but I did change my bind DN to an OU that had... See more...
I possibly could be mistaken on the "whole domain" as I am seeing it supposedly will not work with that setup.  I have not had issues with this setup but I did change my bind DN to an OU that had my users and horizon admin account within that so it could search the entire OU.
I only say this because you didn't mention doing it and that is enabling the pools for HTML access.  You need to go into each pool settings and checkmark "enable html access". If so you might ... See more...
I only say this because you didn't mention doing it and that is enabling the pools for HTML access.  You need to go into each pool settings and checkmark "enable html access". If so you might also need to go into the connector-va (port 8443) and under User Attributes you need to checkmark the userPrincipalName required box.  Without this, you will not be able to get to the desktops through workspace.
Change your Bind DN to the whole domain.  If the service account you are using is not with all of your users it will not be able to find the users outside that OU.  I have seen this documented in... See more...
Change your Bind DN to the whole domain.  If the service account you are using is not with all of your users it will not be able to find the users outside that OU.  I have seen this documented incorrectly around the interwebs by some.
Is this on a Windows machine?  Is UAC enabled?
Without knowing your exact DNS set up, it seems to me that the setup wizard is still trying to tie back to your original installation of Workspace.  If the only thing you have changed is the fqdn... See more...
Without knowing your exact DNS set up, it seems to me that the setup wizard is still trying to tie back to your original installation of Workspace.  If the only thing you have changed is the fqdn of your external and all of your other xxxx-va machines all end in your local.domain then that is for sure what is happening.  I also am assuming you have all of your forward and reverse lookups set up in DNS.  Workspace is extremely picky about DNS.
Do you have the first installation tied to a .local domain as opposed to this new one?  You said the different dns suffix for each installation.  How were you able to  get different dns suffixes ... See more...
Do you have the first installation tied to a .local domain as opposed to this new one?  You said the different dns suffix for each installation.  How were you able to  get different dns suffixes for all the vms in the vApp.  Each piece should be named as xxxx-va.whateveryourlocaldomain is no matter if you named the external fqdn a domain.com on the new installation.
I think this is a time sync issue.  I didn't think that was it in the beginning but my data-va is slowly losing time compared to the rest of the vApp.
So let me get this straight.  You currently have a working Workspace install in your environment which is up and running? And you are trying to add another or did you tear down the other one ... See more...
So let me get this straight.  You currently have a working Workspace install in your environment which is up and running? And you are trying to add another or did you tear down the other one already?
./wizardssl.hzn --makesslcert gateway-va horizon.xxxx.com then run ./wizardssl.hzn
On configurator-va, as root cd /usr/local/horizon/lib/menu/secure ./wizardssl.hzn --makesslcert gateway-va  <FQDN> ./wizardssl.hzn
Constantly having issues with files syncing when added to Horizon folder.  Very vague error that states "Network error" with a red exclamation point over the cloud icon on the toolbar up top (Mac... See more...
Constantly having issues with files syncing when added to Horizon folder.  Very vague error that states "Network error" with a red exclamation point over the cloud icon on the toolbar up top (Macbook client).  I have tried to comb through the logs but don't see anything that is giving me any clue.
I am currently out of the office, Monday, February 24th and will return on Friday, March 1st. I will be replying to emails throughout the day on a delayed basis. Kevin Pelt Systems Enginee... See more...
I am currently out of the office, Monday, February 24th and will return on Friday, March 1st. I will be replying to emails throughout the day on a delayed basis. Kevin Pelt Systems Engineer - EchoStor Technologies 45 South Street Hopkinton, MA 01748 Office: 508-544-1313 ext. 2428 Mobile: 603-842-9686 Email: kpelt@echostor.com Website: www.echostor.com
Was the package 32-bit or did you use the 64-bit?  64-bit applications are not supported.
Some users are reporting that Visio is holding current user as author but Projects does not.  Both packaged same way except Visio was activated before post scan.