I sent your question on to Andy who maintains the ADC script.

Webster

I forwarded your comment to Andy, the script maintainer. Let me know if you don’t hear from him.

Webster

Thanks for the reply! I did some more testing and confirmed that 443 TcpTestSucceeded : True. I did the same test for port 80 and TcpTestSucceeded: False. It appears that I am needing to run the script with SSL parameters.

For SSL do I change the below parameter to $true?
## EXPERIMENTAL: Require SSL/TLS, e.g. https://. This requires the client to trust to the NetScaler’s certificate.
[parameter(Mandatory=$false )]
[System.Management.Automation.SwitchParameter] $UseNSSSL,

Also do you think that this setting on the NSIP would block the script? “Allow access only to management applications”

Hi Mark,

If you’re having issues connecting to the IP address then the DNS name may not help too much as it will just resolve to the same IP I would assume?

Best bet is to check the basic connectivity – e.g. can you telnet to tcp/443 on the device? if there’s a proxy server in path that may be intercepting traffic, try putting an exclusion in for the IP/dns and see if that helps.

If you want to check from powershell you can use “test-netconnection -computername -port 443″ which would use the same stack as the methods the script is using.

Let me know how you get on.

Thanks,

Andy

For the “Citrix Application Delivery Controller Documentation Script Version 4.52” can I use the DNS name of ADC Management SNIP instead of the IP?

I am getting cannot connect when I use the IP address within the script parameter.

Thank You!

Have you tried the Export and Import options. Those are what I use when I don’t have access to Word at the customer’s site. When Andrew does his next update to that script, I will add HTML output.

Thanks

Webster

Unfortunately a full Office repair isn’t an option, as the only place where I have access to both Office and the Netscalers are from a non-persistent VDI.
I tried running the script with the suggested parameters, but it didn’t make much difference, there was no output. The only thing that happens is that Word starts running in the background, and has to be killed manually. This happens everytime, regardsless of what arguments I use when running the script.

I’ll have a look around and see if I can find another machine to run the script, maybe that will help.

Keep up to good work, and stay safe.

G

Issues with Word or the #1 most FAQ. I recommend doing a full online repair of Office. That has solved all but one reported issue.

If you could rerun the script with -Dev -ScriptInfo -Log and email me those three text files, that would help.

webster@carlwebster.com

Thanks

Webster

We’re running Office 365, 16.0.13426.20270, 32 bit.

Regards,
Geir