Как подружить Vista и Samba

Установив Microsoft Vista обнаружил, что с компьютера невозможно получить доступ к сетевым ресурсам на сервере Samba под Linux. Быстрый поиск показал, что причиной является отсутствие поддержки NTLMv2 на нашем Samba сервере. В Microsoft Vista по умолчанию отключены более старые протоколы аутентификации. 

Исправить эту ситуацию можно так:

1. Открыть окно «Run» для выполнения команд и запустить «secpol.msc»:

2. Выбрать «continue» когда Vista выведет предупреждение

3. Выбрать «Local Policies» –> «Security Options»:

4. Найти «Network Security: LAN Manager authentication level» и открыть. 

5. Изменить значение по-умолчанию «NTVLM2 responses only» на «LM and NTLM – use NTLMV2 session security if negotiated»:

Теперь Vista сможет работать с Samba нормально. Однако лучшим вариантом, пожалуй, является обновление Samba до 3-ей версии, где уже реализована поддержка NTVLM2. 

Нас ведь интересует безопасная работа

Original

Полезные ресурсы по Windows Server 2008

Документация от Microsoft на русском языке:

http://www.microsoft.com/rus/windowsserver2008/tutorials/default.mspx

Как продлить работу пробной версии Vista/Server 2008 до 120 или 240 дней

Windows Vista and Windows Server 2008 has free activation grace period which allows user to install and use the operating system for 120 days and 240 days without product key or product activation completed. The initial grace period given is 30 days and 60 days respectively for Windows Vista and Server 2008, and user has to “rearm” the system when the expiration of grace period is nearly ending in order to reset and extend the trial evaluation period, and hence activation grace period again.

1. Open an elevated privilege command prompt.
2. Type the slmgr.vbs -rearm, and then press Enter to reset the activation grace period to 60 days.
3. Restart the computer.

Windows Essential Business Server 2008

Стала доступна Public Preview версия Windows Essential Business Server 2008. Я давно ждал этого продукта, поскольку для многих организаций ограничение на количество пользователей для Small Business Server делают невозможным его использование.

Windows Essential Business Server 2008 is designed for the needs of midsize organizations with up to 250 desktops, helping IT professionals take control of their systems, reduce time spent “fighting fires” and focus more on strategic efforts to drive business growth. The solution includes built-in IT best practices and provides a unified console for management of key workloads and product licensing, which makes IT budgeting and purchase simpler and more predictable.

Windows Essential Business Server combines the technologies of Windows Server 2008, Exchange Server 2007, Forefront Security for Exchange Server, System Center Essentials 2007, the next version of Internet Security and Acceleration Server and, in the Premium Edition, SQL Server 2008 technology. The product will be demonstrated on IBM BladeCenter S and HP BladeSystem c-Class c3000 hardware at the “Heroes Happen Here” launch on Feb. 27 in Los Angeles, and is slated for availability in the second half of 2008.

Значительно изменился состав поставляемых в комплекте продуктов, а, соответственно, и цена:

· Windows Essential Business Server 2008 Standard Edition software, including five CALs, $5,472 (U.S.); additional CALs $81 each (U.S.)

· Windows Essential Business Server 2008 Premium Edition software, including five CALs, $7,163 (U.S.); additional CALs $195 each (U.S.)

Дороговато, хотя и в комплекте идет немало.

HOW-TO start VMWARE Server on Windows Vista or Windows 2008 Server

It presents you with that dialog (as opposed to the «Local»/Remote» radio selection) because the VMWare services aren’t running on the host.

I haven’t specifically tried VMWare Server on 2008 yet, but it sounds like the driver signature enforcement might be killing the services on startup. The same exact thing happens on Vista 64-bit, which I have been able to get working.

Do this:

Completely uninstall VMWare Server…tell it to remove the license. Go through and delete all its crap that it leaves behind (mostly C:ProgramDataVMWare). I’d even go so far as regedit, search «vmware» and delete anything there too.

Then reboot with Driver Signature Enforcement disabled (as Windows boots up, press F8, select «Disable Driver Signature Enforcement»).

Then install VMWare clean. Reboot and again select to disable Driver Signature Enforcement.

See if VMWare works now.

You must disable Driver Signature Enforcement every time you boot up.