Recently at a site we had machines starting using high CPU of the SVCHost process, this process is used by lots of services to access the network , however, as soon as stopping the Windows Update Service CPU came back down to normal

I had seen this before at another site and the issue was due to not enough CPU ( only one was flatlining the CPU )  , however increasing the CPU and memory still did not fix this

Then after some recent updates, the servers would no Windows Update anymore , they would just sit on “Checking for Windows Updates”. I couldn’t install updates Via powershell 

A server running Windows Server 2012 R2 on the same network updated fine!

I tried the normal fix of Wiping these : 

C:\Windows\SoftwareDistribution

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate

However to no avail.

 

I checked the Windows Update Log : C:\Windows\WindowsUpdate.log

2019-04-23 14:09:51:839 5080 ab8 CltUI FATAL: CNetworkCostChangeHandler::RegisterForCostChangeNotifications: CoCreateInstance failed with error 80004002
2019-04-23 14:09:51:839 5080 ab8 CltUI WARNING: RegisterNetworkCostChangeNotification: Error 80004002

 

I then found an article to Remove the Desktop Experience Feature ( which had been installed to Disk Cleanup the servers ) 


After this I did this again and could windows update again

C:\Windows\SoftwareDistribution

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently installing iManage Desksite , and upon loading the Applicaiton a .net error displayed with 

“WinDatapicker”

Reinstalling the App didn’t help , in the end , I had to change the data format of windows to dd/mm/yyyy for it to work!

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently had an issue where Worksite 10 Filesite was remembering a credential even though we had wiped it from the client. Turns out there is some heavy credential Caching in FileSite/Desksite and this is the way you need to clear old credentials : 

  1. Stop the iwsingleton.exe process in taskmanager
  2. Clear C:\Users\%username%\AppData\Roaming\Interwoven
  3. Delete the following Windows Credential in Windows 10

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

The Web uses port 443 ( SSL ) TCP

The client uses port 1090 TCP

The client Auth used 1091 TCP

These all need to be open on the router for iManage URL connection to work externally. Also the below registry items need to be set for it to force the client to use a dedicated port instead or the normal client default

 

64bit

[HKEY_LOCAL_MACHINE\SOFTWARE\Interwoven\Worksite\8.0\Common\Options]

"Use Hosted DM"="Y"

"Hosted DM ServicePort"=dword:00000442 ( Decimal 1090 )

"Enable Hosted DM SSL"="Y"


32bit

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Interwoven\Worksite\8.0\Common\Options]

"Use Hosted DM"="Y"

"Hosted DM ServicePort"=dword:00000442

"Enable Hosted DM SSL"="Y"
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

How to save existing Document library as Template

Login to Sharepoint then navigate to the Document Library

Go to Library Settings

Save template ( with or without the content ) 

Next go to the Site where you want to create the new Library and create a new App ( NOT Document library )

Search for your new Template

And Add this with the new Name

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently a client had the following come up on their StoreFront Event Viewer

Failed to launch the resource ‘WTCITRIX.XenApp Desktop $S1-1’, unable to obtain a ticket from the configured Secure Ticket Authorities.

 

This is usually mimicked with an Error on the reciver end

Connection to “Desktop” Failed with Status (Unknown client error 0)

Make sure your Citrix StoreFront is configured with the STA details in the NetScaler Gateway section (remember you only need to use the STA in case of remote users, for which you would have to configure a NetScaler Gateway). They need to be the same also clear DNS cache if you have recently updated a DNS Record

Similarly the NetScaler itself is configured with the STA details. 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: -1 (from 1 vote)

Trying to add a secondary Storefront server came up with an error during propagation of settings : 

 

Failed to get the end status of the sever configuration update.
System.ServiceModel.FaultException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Access to the path ‘C:\Program Files\Citrix\Receiver StoreFront\Receiver Clients\Windows\CitrixReceiver.exe’ is denied.
at Citrix.DeliveryServices.ConfigurationReplication.WCF.ConfigurationReplication.EndUpdateConfiguration(IAsyncResult asyncResult)

 

Looks like the same issue as https://pariswells.com/blog/research/import-stfconfiguration-an-error-occurred-configuring-storefront-diagnostics-method-invocation-failed-because

Deleting : C:\Program Files\Citrix\Receiver StoreFront\Receiver Clients\Windows and \Mac Fixed this issue

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently trying to install VDA on a server 2016 server and it comes up with the below error trying to install Remote Desktop Session Host

Error Id: XDMI:334CF235

Exception:
Citrix.MetaInstaller.MetaInstallerException ‘dism’ component failed to install with error 0x800f080c.
at Citrix.MetaInstaller.Prerequisite.RdsComponents.Install(InstallationContext context)

at Citrix.MetaInstaller.InstallationManager.InstallComponent(InstallableComponent component, InstallationContext installContext)

 

Looking in the logs it’s failing when running this :

dism /quiet /norestart /english /online /enable-feature /featurename:Remote-Desktop-Services /featurename:ServerMediaFoundation /featurename:AppServer /featurename:InkAndHandwritingServices /featurename:DesktopExperience

When I run this manually I get  : 

Feature name DesktopExperience is unknown. 
Feature name InkAndHandwritingServices is unknown.

This is actually already bundled in 2016 , you will need to install VDA 7.11 ( the minimum version that supports Server 2016 ) 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)