Hola penya,

si voleu tenir llicència de KIS durant 90 dies només fa falta que activeu el producte utilitzant aquesta clau:

 WKHR6-BAMZT-HQAMZ-912HR

Apa, vagi bé.

 

 

Ja hi ha disponible la nova versió en anglés del Kaspersky 2009 v8. A continuació us passo unes petites instruccions de com posar-lo en castellà:

1. Descarregar la traducció dels productes Kaspersky 2009 v8.

2. Pausar la protecció en timps real Kaspersky 2009 v8.

3. Desactivar l'Autoprotección.

4. Tancar completament Kaspersky 2009 v8.

5. Anar a la carpeta Skin de Kaspersky 2009 v8.

             C:\Archivos de programa\Kaspersky Lab\Kaspersky Anti-Virus 2009\Skin

6. Un cop allí, descomprimim el contingut del fitxer .zip descarregat, que és una carpeta anomenada loc, i la copiem en la carpeta Skin, substituint la carpeta loc existent.

7. Un cop fet tot això, podem arrancar de nou Kaspersky 2009 v8 (activant de nou totes les proteccions) i ja podrem veure la interfície d'usuari en castellà

just upgraded my Windows Vista machine to Vista SP1 RTM and found the changes while I was terminal-servicing to my server machines.

I used console terminal service a lot to get the physical console control to do things. after upgraded to Vista SP1, found that it would no longer be able to use /console to connect to console terminal of remote machines anymore.

later found this post from Terminal Service Team Blog that states the changes after RDC 6.1, which was installed while Vista SP1 installation, that /console had depreciated and for backward compatibility, use /admin in RDC 6.1 to connect to console terminal of Windows Server 2003.

so, have to change my RDC shortcut for console connections from using /console switch to /admin .

I was browsing through the utilities at www.sysinternals.com, and I came across this neat little utility: BGInfo.exe

What does it do? It writes a bunch of current system stats such as memory, CPU, IP address, hostname, etc to the desktop bitmap.



This can be a huge time saver when you are working on lots of servers during the day. Many times they all start looking the same, with KVMs and Remote Desktop you can easily forget what system you are on.

Instead of the need to drop to a command line or open the control panel - you can see what system you are working on with a quick glance.

The program does not run in the background. It simply re-creates the current desktop image with the current system settings.

When you launch it, you are shown a screen that lets you modify how the settings are displayed.



Once you get it the way you want, save it. Then you can have it update each time you login by adding this to a startup script:

bginfo.exe /silent /timer:0

That tells it to re-write the desktop without any prompts.

Bonus Feature: You can tell it to display on the Remote Desktop logon window, and the console login window. If you click on the Desktop button in the settings, you will be able to tell it to write to these:



I don't recommend it if the machines are not in a secure environment. Why? Because it gives away info about the system without any login credentials. With that said it can be great if you have many machines buried behind a firewall and need to know which one you are on right away.

To make it more clear, if I have the Remote Desktop feature turned on, I can see info about the system before I even login:



The same is true for the console logon screen option



This tiny program is loaded with features. I have only touched the surface of what it can do. Check out its home page at Microsoft for more info.

Com fer que el Vista no et demani les credencials de login abans de connectar-se al servidor de Terminal Server: 

 

Remote Desktop Connection client 6.0 introduces new authentication features to improve security for Windows Vista and Windows Longhorn Server, which makes it mandatory for the user to enter logon credentials before RDP client can establish connection to the remote server (" Enter your credentials for <server>. These credentials will be used when you connect to the remote computer" ). But if the remote machine is configured to show logon warning message or if the remote system happens to be Windows 2000 or XP, you’ll need to enter the credentials again at remote machine’s logon screen.

There is however a workaround to skip the credentials screen that RDP 6.0 client shows by choosing “Do not attempt authentication” under Authentication options on the Advanced tab, but this option is not set permanently. To permanently skip the additional credential screen of RDP 6.0 client, edit the Default.RDP file in notepad to include enablecredsspsupport:i:0 . The Default.RDP is located in each user’s My Documents folder. Including enablecredsspsupport:i:0 disables the Credentials Security Service Provider for the connection. If you use separate .RDP files for different server, modify each of those .RDP files. Below is the content section of the default.rdp file with enablecredsspsupport:i:0 option included.

redirectposdevices:i:0
authentication level:i:0
enablecredsspsupport:i:0
prompt for credentials:i:0
negotiate security layer:i:1

Note that this workaround is suggested only if you connect Windows 2000/2003/XP systems because according to Terminal Services Team blog post – “This option does disable the new credential prompting behavior, but it also disables support for Network Level Authentication for Vista (and Longhorn Server) RDP connections; Network Level Authentication requires credentials to be provided by the client before a session is created on the server side.” So if you do connect to Vista/Longhorn over RDP, you’ll not be able to use this option.

References: http://blogs.msdn.com/ts/archive/2007/01/22/vista-remote-desktop-connection-authentication-faq.aspx

Continue reading...