https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# citrix-app-layering
s
This message was deleted.
d
Upgrading to latest both agent and ELM did not work 😞
r
Applayering all-stars @Rob Zylowski @Nick Panaccio
r
is the bits service enabled
on the pvs server
have you rebooted the elm since changing its IP?
d
I have rebooted both
checking bits
r
d
all ports are open from ELM to PVS that I know
r
K
Pretty strange then
The reboot is the usual issue
I assume your account is ok
d
I tried both the AD integrated admin and local admin
r
Meaning the administrator account on the elm
d
It has to be something simple... I just dont know what. Both ELM and PVS are on the same subnet.
Yes administrator account on ELM
built in one and the one I added from AD
r
Yea thats the right acct
d
.net 4.8 is installed on PVS
r
Either should workout
I dont tjink powershell or fornet are used until you actually publish
So for the registration it more just ports and auth
Have you tried reinstalling the agent
I might uninstall and reinstall
d
yes several times
r
Ok weird i guess youll need to open a ticket
d
anything with defender maybe?
r
I have not heard of that
Being an issue
d
😞
r
Yea
d
was trying to not have to deal with support
r
✔️
I know
I assume you dont see the ovs server if uou try to add a connector
d
yea 😞
r
What os is the pvs server
d
Server2019
could that be an issue?
r
No
I haven’t used 2022 but it’s probably fine. But i do use 2019 no issues
Could be dome issue with dotnet
d
should I try to reinstall 4.8?
r
Do you have another pvs server you could try
You could try it
d
I have an old qa box that is running some old ver of PVS and server 2016
r
You could try it just asca test.
Not sure how helpful it would be
d
indeed thats why I was not in a hurry to go that route. I can build a new PVS server too. will take a bit.
r
Yea that’s probably more worthy it. It’s actually a good idea to use a dev server for the integration though very few customers do
Is this 2211
d
yea just updated last week
this is a kind of dev/new environment I am building out
r
K
d
figured I get everything latest and greatest 😄 and get layering going as well
r
Always a good idea
d
just installed agent on the old 2016 qa pvs box with zero issues. 🤔 something is messed up on that new 2019 server
r
That Sucks are they in different OU's wondering about GPO settings? Not sure if it got this far for you tere are agen logs in progiram files (x86)\citrix\agent
👍 1
d
Just moved to the same OU. rebooting
that worked. but... there are no other policies in that OU? 😄 wtf and the only policy I had in the old OU was for PVS specific fw settings
r
Inheritance?
d
They are in the same parent OU. Perhaps I need to take a closer look at pvs fw policies that are configured in the original OU. But I did add a policy to allow all from elm and that made no difference. Perhaps some other restriction. 🤷‍♂️🤦‍♂️
5 Views
Open in Slack
PreviousNext
Powered by