Windows XP/2003 IPv6 ISATAP tunnel Server stop forwarding after re

Assume LAN NIC nickname is 'Campus'.
There is only one LAN NIC in the Server.
The LAN NIC is in IPv4/IPv6 dual stack enviroment.
ISATAP Client connect to the tunnel server's IPv4 address.
Server IPv4 address: 10.10.10.1
Isatap tunnel prefix: 2001:250:2::/64
Server Isatap tunnel address: 2001:250:2::1
LAN NIC IPv6 default gateway address and prefix: 2001:250:1::1/64
Server LAN NIC IPv6 address and prefix: 2001:250:1::100/64


Windows XP SP2, patch to 4/18/2008
Windows Server 2003 x64 SP2, patch to 4/18/2008
Configuration example:
netsh
int ipv6
add address "Campus" 2001:250:1::100
add route ::/0 "Campus" 2001:250:1::1 publish=yes
set interface "Campus" forwarding=enable

isatap
set state enabled
set router 10.10.10.1 state=enable
...
add address "Automatic Tunneling Pseudo-Interface" 2001:250:2::1
add route 2001:250:2::/64 "Automatic Tunneling Pseudo-Interface" publish=yes
set interface "Automatic Tunneling Pseudo-Interface" advertise=enable
forwarding=enable

exit



By now, client can connect to this isatap server. But by every reboot,
Client can not get address and gateway.
We can find configuration in [netsh int ipv6] is not changed.
But in this COMMAND :
netsh int ipv6 show interface "Automatic Tunneling Pseudo-Interface"

it Returns:
Sends Router Advertisements : No
Forwards Packets : No
after reboot.
But LAN forwarding is OK after reboot:
netsh int ipv6 show interface "Campus"
Forwards Packets : Yes

FIX COMMAND:
netsh int ipv6 set interface "Automatic Tunneling Pseudo-Interface"
advertise=enable forwarding=enable
Everything OK again,

Check COMMAND:
netsh int ipv6 show interface "Automatic Tunneling Pseudo-Interface"
Sends Router Advertisements : Yes
Forwards Packets : Yes

By design, should windows 2003 admin manually enable tunnel forwarding every
time isatap server reboot?

ps.
Server 2008 isatap tunnel forwarding is enabled after reboot.