Рулит  http://vietdev.sourceforge.net

• легкая интеграция
• достаточно правильно сделана работа с изображениями и аплодами файлов.
• поддержка IE, Mozzila, в Opera наблюдались некоторые глюки.
  

Но хит сезона 2002-2005, безусловно, eDX XML WYSWYG Editor.
Поставляется как сампл в MSDN.
www.xopus.com рулит по очень похожему принципу. Лучший.

 

Thanks Gary for the tip, I managed ok with the codepage (by changing the registry entry ACP under HKLM\system\CurrentControlSet\Control\NLS\CodePage . God knows why...) and now it's working.
--------------------------------------------------------------------------------
guide I get the messae "The specified MSProjectServerRole account is not in the MSProjectServerRole role." I checked for 100 times that the user is in the required role, and tried to recreate the logins and roles - nothing helps. ANYBODY ???.

В нашем случае изменение ACP на 1252
фиксит проблему :) 

SQL Server scalability casestudies for IT managers:

http://www.microsoft.com/sql/64bit/productinfo/casestudies.asp

other
http://www.enertia-software.com/item.asp?item=622
http://www.intel.com/business/casestudies/raymond_james.pdf
http://www.intel.com/business/bss/products/server/itanium2/testimonials.htm
http://www.intel.com/business/casestudies/koehler.pdf
http://www.intel.com/business/bss/swapps/server2003/testimonials.htm?showAll=true&selected=0
http://www.intel.com/business/bss/swapps/server2003/testimonials.htm?showAll=true&selected=1
http://www.intel.com/business/bss/swapps/server2003/testimonials.htm?showAll=true&selected=2
http://www.intel.com/business/bss/swapps/server2003/testimonials.htm?showAll=true&selected=3
http://www.intel.com/business/bss/swapps/server2003/testimonials.htm?showAll=true&selected=6
http://www.intel.com/business/bss/swapps/server2003/testimonials.htm?showAll=true&selected=8
http://www.intel.com/business/bss/swapps/server2003/testimonials.htm?showAll=true&selected=9
http://www.intel.com/business/bss/swapps/server2003/testimonials.htm?showAll=true&selected=11

http://www.unisys.com/products/es7000__servers/news_a_events/all__news/01218375.htm

http://www.hp.com/products1/itanium/testimonials/banca.html
http://www.hp.com/products1/itanium/testimonials/comp_usa.html
http://www.hp.com/products1/itanium/testimonials/finnish.html
http://www.hp.com/products1/itanium/testimonials/denizbank.html

some posts:

http://blogs.msdn.com/brada/archive/2004/03/10/87635.aspx
http://weblogs.asp.net/rwlodarc/archive/2003/04/24/6006.aspx
http://stupidevilbastard.com/archives/2004/02/18/intel_admits_64_bit_is_next_big_thing.php
http://weblogs.asp.net/jdennany/posts/31691.aspx
http://weblogs.asp.net/volkerw/archive/2004/02/25/80175.aspx
http://weblogs.asp.net/oldnewthing/archive/2003/11/19/55757.aspx
http://weblogs.asp.net/frankarr/archive/2004/03/25/95564.aspx
http://weblogs.asp.net/mdavey/archive/2004/03/19/92568.aspx
http://weblogs.asp.net/wallym/archive/2004/01/29/64749.aspx
http://weblogs.asp.net/pleloup/archive/2003/10/29/34389.aspx
http://weblogs.asp.net/volkerw/archive/2004/04/12/111860.aspx
http://sqljunkies.com/WebLog/jt_kane/archive/2003/09/29/247.aspx
 

A. Exchange Server is effectively a service to a back-end database--the Extensible Storage Engine (ESE); thus, disk performance is a major factor in the performance of your Exchange Server implementation. It's therefore vital that you segregate your OS, transaction logs, and database in an optimal configuration, as follows:

OS (includes the Exchange Server binaries): RAID 1 (mirrored)
Storage group (SG) transaction logs: RAID 1 (mirrored)--Each SG has its own transaction logs and should have separate physical disks. The disks that comprise the RAID 1 drive should be o­n separate controllers to avoid bottlenecks during write operations. RAID 1 is used instead RAID 5 because RAID 1 performs better for write operations.
Databases: RAID 5 (striped with parity)--RAID 5 performs better for multiple-read environments, such as databases. An alternative to using RAID 5 for database storage is to use RAID 0+1, which is a stripe set without parity. The disks that comprise the stripe set are mirrored. However, sites typically don't choose to use RAID 0+1 for databases because of their high cost (i.e., half of the disk space isn't usable). 

6565792;5296992;3325596;4965437;4526017


Службы терминалов являются дополнительным компонентом систем семейства Microsoft Windows Server 2003, а также Windows 2000 server. Службы терминалов позволяют использовать графический интерфейс Windows на удаленных устройствах, подключенных к локальной сети, глобальной сети или Интернету.

Службы терминалов могут работать в двух режимах

A. Remote Desktop for Administration (ранее известный как Terminal Services in Remote Administration mode)
Этот режим предназначен для предоставления операторам и администраторам возможности удаленного доступа к серверам и контроллерам доменов. Сервер, настроенный для удаленного администрирования, не требует дополнительного лицензирования. В этом режиме возможно только два одновременных подключения.

B. Terminal Server mode
Этот режим не имеет ограничений по количеству подключений, но требует дополнительного лицензирования. Решению проблемы активизации (то есть добавлению необходимых лицензий) и посвещена эта статья. В неактивированном состоянии сервер проработает 120 дней (в Windows 2000 - 90 дней).

Прежде всего нужно включить режим Terminal Server mode, это делается через компонент Панели управления (Control Panel) «Add or Remove Programs» — «Add/Remove Windows Components». Так же нам небходима установленная служба Terminal Server Licensing.

Далее можно непосредственно приступать к активации небходимых лицензий. Эта задача состоит из двух частей. Первая — активизация лицензии для самого Terminal Server-а, а вторая — установка Client Access Licenses (CALs), лицензий, определяющих количество одновременно подключенных пользователей.

1) Запускаем Terminal Server Licensing (Start -> Control Panel -> Administrative Tools-> Terminal Server Licensing).

2) Выбираем сервер терминалов, который мы хотим активировать, далее right-click и Properties. На вкладке Installataion Method выбираем метод установки Web Browser (в Windows 2000 — WorldWideWeb).


3) Переходим на вкладку Required Information, заполняем поля различной лабудой и жмем OK.


4) На терминал-сервере, который мы активируем, right-click и Activate Server, запустится Terminal Server License Server Activation Wizard. Знакомимся с описанием и жмем Next.


5) Выбираем метод активации Web Browser (в Windows 2000 — WorldWideWeb), жмем Next.


6) На этом шаге нам небходимо обратится на сайт M$ https://activate.microsoft.com/ для получения License Server ID.


7) На веб-сайте Terminal Server Licensing выбираем опцию Activate a License Server и жмем Next.


8) На этом шаге нам нужно заполнить поля, помеченные (*). Product ID берем из Terminal Server License Server Activation Wizard (см. шаг 6), остальные поля заполяем той же лабудой, что и на шаге 3. После того жмем Next, далее проверяем введенную инфу и опять жмем Next.


9) Если все правильно, то мы получим необходимый License Server ID. Сайт https://activate.microsoft.com/ закрывать не нужно, он нам прегодится в дальнейшем для получения Client Access Licenses (CALs).


Вводим полученный License Server ID в Terminal Server License Server Activation Wizard (см. шаг 6), а так же желательно распечатать страничку или сохранить где-нибуть License Server ID, он может потом потребоватся. Жмем Next.


На этом, первая часть, активизация самого сервера терминалов, завершина.


10) Для установки Client Access Licenses (CALs) (вторая часть), нужно провериь, что галочка Start Terminal Server Client Licensing Wizard установлена, и нажать Next. Мы увидим превтствие мастера установки клиентских лицензий. Знакомимся и ифой и жмем Next.


11) На этом шаге нам опять нужно будет обратится на сайт https://activate.microsoft.com/, а точнее, на ту страницу, которая упоминалась на шаге 9 (она должна быть открыта). На вопрос «Do you wish to install license tokens at this time?» отвечаем Yes (см. шаг 9).


12) На этом шаге нам нужно заполнить поля, помеченные (*). License Server ID берем из Terminal Server CAL Installation Wizard (см. шаг 11), в качестве License Program выбираем Enterprise agreement (обязательно, иначе не прокатит!), остальные поля заполяем той же лабудой, что и на шаге 3. После этого жмем Next.


13) Самый главый шаг! Тут необходимо выбрать:
Product Type — Windows Server 2003 Terminal Server Per Device Client Access License
(в Windows 2000 — Windows 2000 Server Terminal Services Client Access License (per-device))
Quantity — количество лицензий необходимых вам
Agreement Number — можно взять в топике Активация служб терминалов / Terminal Services в Варезнике или найти любой другой.
Далее жмем Next, проверяем введенную инфу и опять жмем Next.


14) Если все правильно, то мы получим необходимый License Key Pack ID, который вводим в Terminal Server CAL Installation Wizard (см. шаг 11), жмем Next, а потом Finish.


Вот, собственно, и все. :)

Взято с форума ru-board.
 

Q. Why are some Microsoft Remote Installation Services (RIS) images not displayed o­n my RIS OS selection menu?

John Savill
InstantDoc #42475
John Savill's FAQ for Windows




A. When a RIS client computer boots so it can install an OS from the RIS server, the client displays a list of OS images that are applicable to it. A problem occurs when the image's hardware abstraction layer (HAL) differs from the HAL that the local machine should use (e.g., single-processor HAL versus multiprocessor HAL). I experienced this problem recently when I used the Remote Installation Preparation (RIPrep) utility to create an image from a client workstation. When I booted another computer so it could install an OS from the RIS server, the computer didn't display the image. The problem was that the computer I used to create the image had hyperthreading enabled, which means the HAL is a multiprocessor version (although the machine actually has o­nly o­ne CPU), whereas the destination machine didn't have hyperthreading and required a single-CPU HAL. If the HAL is the same o­n both the imaged and local systems, compare the NTFS permissions o­n the RIS server's image folder with the permissions o­n an image that you know works. If the permissions aren't the same, adjust them o­n the image folder so they match the permissions o­n the folder of the working image

 

Q. How can I add a new adapter to the list of supported Microsoft Remote Installation Services (RIS) adapters?

John Savill
InstantDoc #42476
John Savill's FAQ for Windows




A. To add a new adapter, perform the following steps o­n the RIS server:

If the driver isn't digitally signed, you must configure the installation to ignore the driver-signing policy. To do so, open the RIS image's .sif file (e.g. Ristndrd.sif) and add the following line to the file's [Unattended] section:
DriverSigningPolicy = Ignore
Expand the NIC driver and copy the .inf and .sys files to the RemoteInstall\Setup\\Images\image\i386 folder. (Image represents the name of the image file.)
Within the image's \i386 folder, create the folder structure $oem$\$1\Drivers\Nic. For example, create the folder
RemoteInstall\Setup\\Images\image\i386\$oem$\$1\Drivers\Nic
Copy the .inf and .sys files that you copied earlier to the new folder.
Open the .sif file for the RIS image, and add the following lines in the [Unattended] section. (If the OemPreinstall line already exists, edit the line to say yes instead of no.)
OemPreinstall = yes
OemPnpDriversPath = Drivers\Nic
Restart the Boot Information Negotiation Layer (BINL) service by entering
net stop binlsvc
net start binlsvc

 

Q: How can I create an OS deployment package by using the Microsoft Systems Management Server (SMS) OS Deployment Feature Pack?

John Savill
InstantDoc #45128
John Savill's FAQ for Windows




A. You can now use the .wim file to create an OS deployment package, by following these steps:

Within the SMS Management Console, select New, Operating System Image Package from the context menu of the Image Packages leaf item.
Click Next to launch the New Operating System Package Wizard.
At the screen that the figure shows, enter a name for the package, the location of the .wim file, and a location to create the source for the new package, which will contain the .wim file to be deployed. The destination for the package source files should be a Universal Naming Convention (UNC) path. You should use an empty or new folder for the destination because all existing files in the location will be deleted. Click Next.
A copy progress dialog box will be displayed. After the process is done, click Finish.
Now that the image package exists, you need to deploy it to client machines via deployment points. From the SMS Management Console, select Image Package, then select the name of the image package you want to deploy. Right-click the package's Distribution Point, and select New, Distribution Points from the context menu. Then select the distribution points from which you want to distribute the OS package.

Next, you need to create a program to install the package, as follows:

Right-click the Programs leaf of the new package and select New, Operating System Program.
Click Next to launch the New Operating System Program Wizard.
Enter a name for the program (e.g., WindowsXPSP2Install) and accept the default "Create a new Operating System Program with default settings," as the figureshows. (You can change the settings later.) Click Next.
At the next screen, enter the product key to use for all installations (This feature is designed for customers with a select agreement that don't have to activate their Windows installations and that use o­ne product key for all OS installations.) Enter the key and click Next, as the figureshows. You'll notice an option to use an encrypted product key; you can find more information about this option at http://support.microsoft.com/?kbid=328356.
The wizard then prompts you to enter a workgroup or domain for the new OS to join. If you select a domain, the wizard prompts you to enter the name and password of an account with sufficient privileges to join multiple accounts to the domain, as the figureshows. You'll also notice an option to create a random local administrator password for the machine. This password won't be known, meaning the account can't be used by intruders. You must use domain accounts to log o­n to the newly built box. Click Next.
Click Finish.
Now that you've created a new program for the package, you need to update the distribution points. To do so, right-click Distribution Points and select All Tasks, Update Distribution Points from within the SMS Administrator Console.

You now have an OS ready to deploy. You might want to perform more changes, such as setting User State Migration Tool (USMT) to capture the state of user profiles if you're refreshing machines. You can also create a CD-ROM to deploy this image to new machines. From the SMS Management Console, select Image Packages, then All Tasks, then click "Create Operating System Image Installation CD." The process creates an International Organization for Standardization (ISO) file, which you can then burn to a CD-ROM (remember, you need to burn the entire contents of the ISO file). Insert the newly created CD-ROM into a new machine, and the OS will deploy, as the figureshows. You can also use the CD-ROM in an existing installation to initiate an SMS-based upgrade.

 

Have you tried adding recurring schedules to the Advertisement? You can also
rerun the package at a particular time, if you add o­nLY time-based schedules
(like run
at 10PM o­n 01/01/01). If your first schedule was not a time-based schedule
(Eg: ASAP) then a time-based schedule o­n top of it will not rerun it.

Sathish
This posting is provided "AS IS" with no warranties, and confers no rights. 

$result[^body.match[(.{50,400}[\.|\?|\!]).*][gi]{$match.1}]Что даст обрезку текста не менее 50 и не более 400 знаков до знака препинания, что, конечно, гораздо эффективнее нежели обрезка текста на полуслове, как приктикуется на многих напраснорожденных сайтах.