M
Mark [Remove the \dot\'s]
1. It doesn't let me select more than one rule at a time to
delete/enable/disable
2. When working on a firewall policy inside a GPO it takes FOREVER to import
settings. It creates HUNDREDS of TCP connections to the Domain Controller
3. When working on a firewall policy inside a GPO it will only connect to
the DC with the PDC Emulator FSMO role even if there is a perfectly good DC
on the same LAN... that's dumb because the PDC emulator could be at the end
of a slow WAN link.
4. When using the predefined templates I can't choose only to have the
settings that relate to Domain or Public or Private so I have to then edit
the new rules manually... which takes ages because of points 1 and 3 above.
Windows Vista Firewall...
10/10 for effort
9/10 for design
3/10 for UI implementation
There... that's my rant for the day... I feel much better now
delete/enable/disable
2. When working on a firewall policy inside a GPO it takes FOREVER to import
settings. It creates HUNDREDS of TCP connections to the Domain Controller
3. When working on a firewall policy inside a GPO it will only connect to
the DC with the PDC Emulator FSMO role even if there is a perfectly good DC
on the same LAN... that's dumb because the PDC emulator could be at the end
of a slow WAN link.
4. When using the predefined templates I can't choose only to have the
settings that relate to Domain or Public or Private so I have to then edit
the new rules manually... which takes ages because of points 1 and 3 above.
Windows Vista Firewall...
10/10 for effort
9/10 for design
3/10 for UI implementation
There... that's my rant for the day... I feel much better now