![]() ![]() ![]() If "Edit Limits" is grayed out, then the setting is configured at the Domain Level via Group Policy. Launch and Activation Permissions: Edit Limits > Make sure the "ANONYMOUS LOGON" / ThinServer account user is allowed both Local and Remote Access.Under Access Permissions: Edit Limits > Make sure the "ANONYMOUS LOGON" / ThinServer account user is allowed both Local and Remote Access.To enable Anonymous Login / ThinServer account on the machine where the ThinManager user interface is installed: If DCOM on the ThinManager machine is not setup to allow connections from the account ThinServer is running under, then the ThinServer service cannot communicate its status with to ThinManager. If the Windows users running ThinManager is not allowed to access DCOM on the ThinManager server, then the user interface will not be able to communicate with the ThinServer service.ġ. If DCOM on the ThinManager machine is not setup to allow Anonymous Logon, then the ThinServer service cannot communicate its status with to ThinManager.Ģ. The ThinManager User Interface uses DCOM to connect to ThinManager Servers.ġ. Terminal Servers are showing a red bar.Smart Session cannot get server information.ThinManager asking for password where none is required.Unable to connect to ThinManager Server from a Workstation and/or Server.I have also attempted searching on the server for dcomc*.* without success.Īs indicated in my original post, I have resorted to a dcomperm utility, however there seems to be something still missing. However this is a server core machine which does not have a start button. This security permission can be modified using the Component Services administrative tool. To the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID The APPID/CSLID relates to a HP VSS Hardware Provider which is working on a 2008 R2 server core (non-DC). I have resorted to the process outlined here using the DCOMPERM tool however the issue still appears suggesting there is somethingĮlse I am missing perhaps in the dcomcnfg or component services tools. Which does not appear to make these options available. Unfortunately the server in question is running Windows 2008 R2 Server Core SP1 I am experiencing EventID 10016 (see below) when attempting to perform a VSS backup suggesting I need to access component services or dcomcnfg to adjust the permissions. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |