O outro dia eu afixei uma ponta em como a permita o cliente da proteção do acesso de rede em XP SP3.  O cliente também é construído em Vista (RTM e SP1) e é um pouco mais fácil de configurar.  Embora a mesma linha de comando dos config de XP SP3 possa ser usada, há um console do MMC também.

Outra vez antes que nós configuremos o cliente que nós devemos ajustar o serviço do agente da proteção do acesso de rede para começar automaticamente, a seguir comece-o.

Então nós podemos lançar o console do MMC com o seguinte comando

napclcfg.msc

Uma vez que este ascendente aberto estala sobre clientes e então simplesmente direito-clique do Enforcement o agente você deseja usar-se e para escolher permita!

Se você for uma linha de comando junkie ou desejo ao certificado isto você pode também funcionar o seguinte comanda:

o enforcement ajustado do cliente da sesta do netsh ID = “#####” Admin = “PERMITE”

Substitua apenas o ###### com o enforcement ID.  Uma última sugestão, você pode ver o enforcement ID circundado também se você se esquecer e se necessitar de permitir do cliente que usa Netsh.

Com o lançamento recente do usuário 2008 de Windows você não é nenhuma dúvida que gasta toda sua hora livre que joga ao redor com o tudo novo. Uma coisa que você pôde jogar ao redor com é proteção do acesso de rede. Há um grande o original em começar um DHCP baseou o laboratório da SESTA ajustado acima mas uma coisa que o original falta é como configurar o cliente da SESTA em XP SP3. Em Windows Vista você começa simplesmente o serviço então permitir o cliente com a configuração MMC do cliente da SESTA (napclcfg.msc) mas XP SP3 não inclui o MMC. Assim como se configura o cliente da SESTA sem uma ferramenta da configuração do cliente da sesta? Netsh, aquele é como!

Para permitir o cliente da SESTA em XP SP3 que você necessita fazer o seguinte:

1. Começo -> Funcionamento -> Services.msc
2. Mude o serviço do agente da proteção do acesso de rede para começar automaticamente
3. Comece o serviço do agente da proteção do acesso de rede
4. Começo -> Funcionamento -> CMD.exe
5. O tipo enforcement ajustado do cliente da sesta do netsh ID = ##### 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”

…