Error validating current user and server

30 Nov

--------------------------------------------------------------------------------------------------- 1) Configuring COM A. Specify credentials for the LANDesk COM objects by clicking on Start, going to Administrative Tools, choose Component Services, click the plus sign next to Component Services, click the plus sign next to Computers, click the plus sign next to My Computer, COM Applications, right click on LANDesk (you will also perform this task on LANDesk1), click on the Advanced Tab, place the Radial button in “Leave running when idle”, click on the Identity tab, specify a Domain Administrator and password in this user.

(This will replace LANDesk Com Plus, the new username must be in the domain\username format.) B. Create a local account on the core server Add it to the landesk management group, ensure this user has web console rights by modifying the user in the console. Specify which user to log into the web console: In IE specify other user credentials by going to Tools Internet Options, choose the Security Tab, click on Custom Level, scroll to the bottom and place the radial button in “Prompt for user name and password”.

Ensure IIS_WPG and IUSER_CORENAME users exist and permissions match a working core for these folders: wwwroot and its subfolder remote, both found in :\inetpub.

If they do NOT match, proceed to Troubleshooting NTFS Permissions If none of the above troubleshooting steps helped pinpoint the problem, proceed with each of the in depth sections below.

NET\Framework\v1.1.4322\/codebase /tlb "drive:\path\LANDesk\Management Suite\file.dll"Note: For the purpose of the error being discussed the LANDesk. Versions previous to 8.7 require later versions of . For web sites pay special attention to the directory security tab found in the web site’s properties. IIS settings can also be compared by exporting the website to an XML and checked using the XML Comparison Tool, contact LANDesk support to have this done. If when Browsing to the result is: Page Cannot be displayed1- Ensure the Default Web Site has a certificate assigned found in the Directory security section.

Expand the Default Website then expand landesk-Management Suite-Core-SSL, Left Click on Information. https://localhost/landesk/managementsuite/core/ssl/information/Database If you receive the correct result: The page must be viewed over a secure channel.If not, enable them and propagate to dependents when prompted. If when Browsing to the result is: The browser attempts to download instead of browsing it. Go to Properties of the Default Website, HTTP Headers Tab, and choose MIME Types. When receiving these determine if the application pool is being overwhelmed or if it is just dropping connections.2- Make sure or .as* are not listed and then remove .*. E- If getting a 404 when browsing remote or database information it could mean that the aspnet extension being used by that site is prohibited.If these steps do not resolve the problem, you can enable agent debug to collect more information by (1) entering the command "tell amgr debug" on the server console, or (2) entering the parameter DEBUG_AMGR=* in the for the server. The debug output shows the name of the agent being run, in which database it resides, and the agent signer name.