appunti semiseri di un presunto tecnico

    Article ID: 187614 Last Review: October 11, 2007 Revision: 6.4 This article was previously published under Q187614 SUMMARY If an unlicensed client connects to a Terminal Server for the first time, the Terminal Server issues the client a temporary Terminal Server Client Access License (CAL) token. After the user has logged into the session, the Terminal Server instructs the License Server to mark the issued temporary Terminal Server CAL token as being validated. The next time the client connects, an attempt is made to upgrade the validated temporary Terminal Server CAL token to a full Terminal Server CAL token. If no license tokens are available, the temporary Terminal Server CAL token will continue to function for 90 days. The license is stored in the client's registry. Thirty-two bit RDP clients store their license under the key HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing. Important This section, method, or task contains steps that tell you how to mo

  Solution ID: 127604 Product: Client Server Messaging Security for SMB - 3.0, Client Server Messaging Security for SMB - 3.5, Client Server Messaging Security for SMB - 3.6 Operating System: Windows 2000 Server, Windows XP Published: 10/24/07 7:46 PM Problem: Set roaming mode VPN clients' updates Roaming clients updates Mobile clients Remote Security Agents lacking the required privileges cannot get updates from the Security Server. You would like remote Security Agents to get updates automatically from the Internet (ActiveUpdate server) without having to uninstall and reinstall the agents with the client package. Environment: Client Server Messaging Security for SMB 3.0, 3.5, 3.6 Windows XP / 2000 Solution: Do one of the following to fix the issue: Option I: Enable ActiveUpdate server updates through the Security Dashboard 1. Open the Security Dashboard and then click the Security Settings tab 2. Choose the domain or group of the re

MBS Navision with MS SQL Option and Vista™ Because I am testing Microsoft Vista™ RC1 and I was curious to see Navision on Vista™, I tried to install it. Installation is not a problem. Native client is working without problems too. But biggest problem is a so small part of Navision as MDAC version detection is. This is biggest problem when you want connect Navision to some MS SQL server. You will got error about wrong MDAC version. Source of problem is the unified versioning of all DLL which are part of the Vista™. Navision is detecting MDAC version through File version of SQL ODBC driver – sqlsrv32.dll. On Windows XP you can see version like 2000.85.1117.0 etc. But under Vista™, the file has version 6.0.5600.16384 and this is "less" than requested version. Changing MDAC detection in Navision is no way. But after some "hacking" you can succeed. There is the workaround: Prepare the modified DLL: 1. You need some resource editor tool, for example the Resource Hacker ap

Creazione del package di installazione del client: http://esupport.trendmicro.com/support/viewxml.do?ContentID=EN-1033804&id=EN-1033804 Impostazione aggiornamento remoto: http://esupport.trendmicro.com/support/viewxml.do?ContentID=EN-127604&id=EN-127604 -- _____________________________________ Stefano Mazgon