Windows Small Business Server 2003 R2 Premium edition
http://www.microsoft.com/rus/Windows...s/default.mspx
все в одном пакете найди поставь перетащи домен роли отдай. потом все назад когда с машинами разберёшься. а так если по отдельности то видал пару раз такое чудо когда на винде 2003 ee sp 1 и isa 2004 крутилось.. мануал невидел, по гугли.
вот нашол тут не подолёку
В общем рабочим методом считается снос контроллера, подъем ISA и подъем контроллера
кроме того, советуют:
- Make sure that "Authenticated Users" is a member of the "Pre-Windows 2000
Compatible Access Properties" (check in Administrative Tools-"Active
Directory Users and Computers")
- Verify that the user has permissions to change the "Network Configuration
Operators" local domain group. You can do that with adsiedit.msc, or by
running dsacls.exe "CN=Network Configuration
Operators,CN=Builtin,DC=jonb,DC=local" (both adsiedit.msc and dsacls.exe are
part of Windows 2003 Resource Kit).
и это
IF YOU RUN ISA2004 on a Domain Controller Windows 2003 Server:
1. If you get RED X near Microsoft Firewall service in a Monitoring ->
Services tab of ISA 2004 manager then:
You must add rights for NETWORK SERVICE to login as service in the Domain
Controller Security Settings:
Click Start -> Programs -> Administrative Tools -> Domain Controller
Security Policy.
Expand Local Policies -> User Rights Assignment -> click on Log on as
service.
Click "Add User or Group" button -> enter "NETWORK SERVICE" -> Click OK.
You may also need to add NETWORK SERVICE to "Adjust memory quotas for a
process", "Generate Security Audits" and "Replace a process level token"
policies.
Reboot server.
2. If you can't reinstall, uninstall or repair ISA2004 installation on a DC
and get messages like:
"Setup failed while creating the services configuration" or/and "Setup
failed while restoring the services configuration" then:
You must transfer FSMO roles to DC running ISA2004 and reboot server.
ничего из этого сам не пробовал
