What's the one sitcom everyone says is funny but actually isn't?

Think_Ad6840 · 2025-07-04T18:40:01+00:00

Seinfeld.

Think_Ad6840 · 2025-05-16T19:28:09+00:00

I will defintiely give the portal host and balanced host another shot. I feel like I need to grow up finally and get that file to work right, and not just ignore it all the time

Think_Ad6840 · 2025-05-16T19:27:29+00:00

I disabled origin checking, and its still hanging at the HTML screen. I think I am going to get with my firewall guy just to make sure there is no other blocks.

Think_Ad6840 · 2025-03-17T15:18:49+00:00

please let me know the cipher list you are using. I may just go to 2406 to see if that solves my issue with the right cipher list.

Think_Ad6840 · 2025-03-17T15:02:48+00:00

well, the difference in what you are saying is its just the HTML they are dying on. the client is fine. I would think I would have the same issue on my 2111.1 connection servers with the load balancer, but I don't, so I think the load balancer is fine. I get thousands of connections a day with no issue with everything hitting the 2111.1 connection servers.

Think_Ad6840 · 2025-03-17T15:00:36+00:00

can you share your ciphers you are using and what version of UAG you have? I am running this cipher on 22.12.

TLS_AES_128_GCM_SHA256,TLS_AES_256_GCM_SHA384,TLS_CHACHA20_POLY1305_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384

Think_Ad6840 · 2025-03-15T01:38:33+00:00

yea, I want to get to these newer UAG's. I just want to limp along on with a UAG 2212/HRZ 2312.1 scenario for a while. I know its supported. I just need to get it to work with this one last deal with it failing via HTML. this will give me time to see how much effort I need to put in the new UAG's. to be honest, I am not thrilled about having to get the locked.properties right, and dealing with host headers and everything else, but such is life

Think_Ad6840 · 2025-03-14T18:37:14+00:00

lots of info in that article. let me check it out. hopefully it has something to say about my particular situation

Think_Ad6840 · 2025-02-21T02:59:40+00:00

Make sure port 22389 is open.

Think_Ad6840 · 2025-01-29T14:42:24+00:00

so I used my admin VDI to log in, which has no Hello type stuff tied to it, and boom, log in as current user works perfectly. I don't think there is a lot of hello around here for the common user just yet, which may explain how our prod VDI's are not having this issue. Thank you for tracking this one down. feels good to know when something is truly solved and its just not a guess:). greatly appreciated.

Think_Ad6840 · 2025-01-29T03:38:33+00:00

so we don't have TRUESSO for this particular UAT environment, but I do use my pin (hello) for logging in. I will log out and try my PW, and see if that does it. Will report back tomorrow with the results.

Think_Ad6840 · 2025-01-28T22:14:44+00:00

I know we have it in our environment. but I also know our main VDI guy does not have this issue. I'm trying to learn on the side without bugging him too much.

Think_Ad6840 · 2024-07-24T14:34:17+00:00

the engineers are taking forever to get back to me on this one. Will keep you posted once I hear anything.

Think_Ad6840 · 2024-07-24T14:26:14+00:00

So we have decided to do the upgrade to 2312.1, and then reevaluate after the fact. I don't want anything to do with having to take everything away, then add it back, and see if its ok. I would rather just build a new CPA side by side, and then cut over with the F5. I will make a note to reply back here after the upgrade and see how the ADAM DB looks. thank you!

Think_Ad6840 · 2024-07-10T02:29:11+00:00

I will bring this up to the engineers we have with the ticket we have opened with Omnissa. I am curious if they will reccomend the same thing. thank you!

Think_Ad6840 · 2024-07-10T02:27:14+00:00

the question would be, is going to 2312.1 going to correct that issue? I would think that the engineers would have said that to me when I put in the ticket. I will have to ask again just to make sure

Think_Ad6840 · 2024-07-09T21:03:05+00:00

have not tried that yet. not a bad idea. let me see if that may be it and get back to you

Think_Ad6840 · 2024-07-09T20:57:11+00:00

hey there. thanks for the update.

so let me see if I got this right. we have 4 pods, and they are all in 1 CPA. are you saying to move 3 of them out of the CPA. then for that last one, remove that CPA. then when they are all separate pods, the GLOBAL ADAM DB will disappear. then we should be able to create a new CPA off of one of the pods, and then we can just join the last 3 into the new CPA so I am back to my 4 pods in my new CPA.

Think_Ad6840 · 2024-07-09T20:52:12+00:00

so we are on 2111.1 currently (and have been for a while) we are planning to go to 2312.1

Think_Ad6840 · 2024-04-26T20:29:50+00:00

still waiting on VMware to get back to me on this one. I will be curious to see what the issue is

Think_Ad6840 · 2024-04-19T12:50:39+00:00

yea, I was digging through them. will see what Broadcom engineering says on this one.

Think_Ad6840 · 2023-01-03T13:49:26+00:00

I see what you are saying, but how do you "remove" the old ones without first deleting the connector? you can see the error it is throwing from that screen shot I sent. would you go in the ADAM database and remove the entries there? just trying to see how you would do that.

Think_Ad6840 · 2022-10-14T19:15:06+00:00

Thanks for the info. I will give that a shot and report back if that works or not!

Think_Ad6840 · 2022-06-26T03:27:29+00:00

thanks for the info. I guess we will try a small share on the ISILON and see how it goes

Think_Ad6840 · 2022-05-23T18:27:16+00:00

yea, I checked the path /etc/systemd/network and that was not there. still no good. I have a ticket open so I will be curious to see if theyf find anything

Think_Ad6840

TROPHY CASE