“Access is denied” error while login to a Windows Server 2008 R2 SP1 with Citrix VDA7.15 CU installed

To fix this Access is denied error, add following registry and restart the server.

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal Server

Name: IgnoreRegUserConfigErrors

Type: REG_DWORD

Value: 1

HKLMSystemCurrentControlSetControlLsaKerberosParameters

Name: MaxTokenSize

Type: REG_DWORD

Value: 48000 (Decimal)

Related:

Desktop Studio Error: “Can't Get License Info”

The license server can be registered with XenDesktop either when XenDesktop is configured, or through the Change license server action on the Licensing node in Desktop Studio.

When the administrator specifies the address of the license server, Desktop Studio attempts to discover the License Configuration Service to allow more reading of license usage.

The error “Can’t get license info” appears if Desktop Studio cannot detect the License Configuration Service. The error does not signify that XenDesktop is not functioning as expected or that the users cannot connect to their desktops and applications.

For administrator authentication issues, only full administrators can connect to the License Configuration Service. Local administrators of the license server machine are implicitly full administrators of the License Configuration Service installed on that machine. Other full administrators can add the new administrators to the License Configuration service.

Some administrators setup on the License Configuration service might still experience problems when connecting to the service. This is generally because of the domain setup issues. The License Configuration Service uses Active Directory (AD) authentication to approve which users are allowed to retrieve license information. For this authentication process to work, either the license server must be in the same domain as the XenDesktop site, or there must be a two-way trust between both domains. Refer to Microsoft documentation for details on configuring trust relationships.

Related:

Migrating DLP from Windows Svr 2008 R2 to Windows Svr 2016

I do not need a solution (just sharing information)

Hi,

We currently have DLP version 15.0 running on Windows Server 2008. We need to migrate our servers to a new set of Windows Server 2016. However, since we can’t upgrade our Oracle database, we must keep the current version at 15.0.

Can you provide suggestions and documentations on the proper method to perform this migration? Again, we need to bring up Enforce Server and all supporting servers on newly stood up Windows Server 2016 servers.

0

Related:

Proactive Threat Protection doesn’t get installed

I need a solution

Hello all,

I’m running a trial of SEP 15 on Windows Server 2016.

The package used to install the client on Server 2016 is the same as on a Windows 10 client.

The Windows 10 installation shows that ‘Proactive Threat Protection’ and ‘Network and Host Exploit Mitigation’ are installed along with the ”Virus and Spyware Protection’.

The same package only installs ‘Virus and Spyware Protection’ on the 2016 Server.

Both windows 10 and 2016 server are showing ‘No problems deteted’ however the security cloud console is showing status of ‘Not Computed’ and status reason of 

‘Not Found (SONAR) + 8 others’.

any help appreciated, 

kind regrds, NC

0

Related:

Single 2008R2 SEP v14 upgrade to 2016 SEP 14.2

I need a solution

Hi,

We have a single Endpoint Protection Server version 14.0.1904 running on Windows 2008R2 Server. I am looking to upgrade the version of SEP to 14.2 and install on to a new Windows 2016 Server. 

The SEP database is on the SEP Server.

There is documentation around performing an in place upgrade on the same server but I’ve not seen anything about upgrading and migrating to a new server.

Is there documentation that discusses this approach or is there a recommended approach to take for this?

There is the option to Export Server Properties. Would this enable a full server export and then import to a version 14.2 server or would it only work on a server running the same version? There is also the Server Private Key Backup. What would the approach be around this?

Many thanks

Ben

0

Related:

  • No Related Posts