El otro día fijé una extremidad en cómo a permita a cliente de la protección del acceso de red en XP SP3.  Construyen en Vista (RTM y SP1) y es un poco más fácil al cliente también de configurar.  Aunque la misma línea de comando de los config de XP SP3 puede ser utilizada, hay una consola del MMC también.

Otra vez antes de que configuremos a cliente que debemos fijar el servicio del agente de la protección del acceso de red para comenzar automáticamente, después comiéncelo.

Entonces podemos lanzar la consola del MMC con el comando siguiente

napclcfg.msc

¡Una vez que esto se abra chasque encendido a clientes de la aplicación y entonces simplemente derecho-tecleo el agente que usted desea utilizar y elegir permita!

Si usted es una línea de comando drogadicto o deseo a la escritura esto usted puede también funcionar el siguiente ordena:

la aplicación determinada del cliente de la siesta del netsh identificación = “#####” Admin = “PERMITE”

Apenas substituya el ###### por la identificación de la aplicación  Una indirecta pasada, usted puede ver la identificación de la aplicación circundada también si usted se olvida y necesita para permitir al cliente que usa Netsh.

Con el lanzamiento reciente del servidor 2008 de Windows usted no es ninguna duda que pasa toda su hora libre que juega alrededor con todo nuevo. Una cosa que usted puede ser que juegue alrededor con es protección del acceso de red. Hay un grande el documento en conseguir un DHCP basó el laboratorio de la SIESTA instalado pero una cosa que el documento falta es cómo configurar al cliente de la SIESTA en XP SP3. En Windows Vista usted comienza simplemente el servicio entonces para permitir al cliente con la configuración MMC (napclcfg.msc) del cliente de la SIESTA pero XP SP3 no incluye el MMC. ¿Tan cómo uno configura a cliente de la SIESTA sin una herramienta de la configuración del cliente de la siesta? ¡Netsh, de que es cómo!

Para permitir al cliente de la SIESTA en XP SP3 que usted necesita hacer el siguiente:

1. Comienzo -> Funcionamiento -> Services.msc
2. Cambie el servicio del agente de la protección del acceso de red para comenzar automáticamente
3. Comience el servicio del agente de la protección del acceso de red
4. Comienzo -> Funcionamiento -> CMD.exe
5. El tipo aplicación determinada del cliente de la siesta del netsh identificación = ##### Admin = “permite”

You will need to replace the ##### with the ID based on whichever enforcement method you are using. You can use the following IDs for the various enforcement methods:

• DHCP = 79617
• RAS = 79618
• IPSec = 79619
• TS Gateway = 79621
• EAP = 79623

For more labs

…

You have probably heard this bit of news already but in case you haven’t we thought we’d share it with you. Vista SP1 and Server 2008 were both released to manufacturing today and will become available in the near future. That is unless you have a TechNet or MSDN subscription in which case you can start downloading now :) Below is the official press release with links for more information.

What: Windows Vista Service Pack 1 (SP1) was released to manufacturing today and will start being available to customers in March, starting with Microsoft Volume Licensing customers. Windows Server 2008 was also released to manufacturing today and will be available for purchase to new customers on March 1. Microsoft Volume Licensing customers with active Microsoft Software Assurance coverage or an Enterprise Agreement will be able to download the server software toward the end of February as part of the joint Microsoft SQL Server 2008 and Visual Studio 2008 “Heroes Happen Here” launch event.

Where: http://windowsvistablog.com/blogs/windowsvista/default.aspx

http://blogs.technet.com/windowsserver

http://www.microsoft.com/presspass/features/2008/feb08/02-04WS2008.mspx

How: Windows Vista SP1 includes quality improvements that help enhance reliability, security and performance. Windows Server 2008 builds on the success and strengths of past server solutions and helps

…

Windows Vista has had everything but an easy ride since it hit the shelves in January 2007. The operating system was plagued by a luxuriant variety of problems from hardware and software incompatibilities to lack of support and poor performance and reliability. And in this context, Vista has also taken the users out for a ride, making every speed bump count, as Microsoft was applauding the evolved user experience delivered by its latest Windows client. Well, one of the most overlooked aspects among the vast volume of problems associated with Vista are the issues faced by end users when attempting to activate the operating system.

“Activation, also known as Microsoft Product Activation or Windows Product Activation, is an anti-piracy technology designed to verify that Microsoft software products are legitimately licensed. Activation works by verifying that the product key the 25-character code located on your Certificate of Authenticity (usually affixed to your computer) or proof of license label (usually affixed to the installation disc case) is authentic and is not in use on more personal computers than are permitted by the software license”, reads a fragment of the Windows Vista Activation FAQ. (more…)

activation,

Microsoft is well on its way to delivering the first service pack for Windows Vista. Currently, the exact availability date for Windows Vista Service Pack 1 is up in the air, Microsoft having offered only a general timetable that points to the first quarter of 2008. And with Vista SP1 intimately connected with Windows Server 2008, formerly codenamed Longhorn, at kernel level, the first service pack for latest Windows client from Microsoft is synchronized with the company’s last 32-bit server operating system. The official launch of Windows Server 2008 has been set for
February 28, next year, and Vista SP1 is bound to keep up the pace wit the server platform.

In mid July, Microsoft debuted the testing of Vista SP1 outside of Redmond. A preview of the first beta of Vista SP1 shipped to a select pool of testers at that time. (more…)

concomitantly, installed updates, kernel level, release candidate, server operating system, server platform, service pack 1, task menu, time microsoft, vista, Windows, windows client, windows server, windows update,…

As you may know, BitLocker Drive Encryption only encrypts the C:\ drive. If you have additional drives in your PC, or use an external USB hard drive with your notebook, you can’t encrypt that drive with BDE. Officially that is :)

While Vista SP1 will bring support for encrypting the other volumes in your system you can do it today using the command line tool manage-bde.wsf. Now before we get started I must inform you that this is in now way supported by Microsoft. I’ve tried it, it worked for me, but I highly recommend taking a backup of the data before proceeding!

With that out of the way launch the Command Prompt as Administrator and run the following command to encrypt additional drives:

cscript manage-bde.wsf -on X: -recoverykey Y:\ -recoverypassword

In this example X: is the drive you wish to recover and Y: is the drive the recovery key will be saved to. Remember to backup the recovery key and store it in a secure location. You can store this key on the C: drive (which is encrypted) and it will make things easier when you need to unlock the drive.

Once that is complete you will need to run a command to “unlock”

…