Alex L's questions

My test network setup is as follows.

A Windows 2008 R2 Server acting as a DC (AD, DNS, DHCP) it is on its own vlan (10.20.99.0/24). I then Have two XP test computers each on there own vlan (10.20.98.0/24 and 10.20.97.0/24).

For the vlans with the test computers I have the IP helper-address set to 10.20.99.255, they are able to obtain an IP correctly and logon to the domain.

At the moment I am testing all my GPO by using the default domain policy (I know this isn't the best idea but once I have them working there i will move them before going live).

Normal stuff like disabling start menu items and desktop setting are working fine but no matter how hard I try I cant get any login/startup script to work, I have tested the script on all the computers (it copy's the winexit screensaver from a share on the server to the computers sys32 directory) and it works fine when i manually run it but it doesn't work when I have it set as a login/startup script.

Am I doing something total wrong or have I just missed something?

Currently I have a network separated into two vlans and all the IP addressing is done statically; we are planning to put into place a domain controller and DHCP.

My questions are Does the domain controller have to have one physical network connection for each VLAN? Same question for the DHCP server? If not how would this be done? If they don’t need to have separate individual connections to each vlan, what vlan would it be best to put it on? One of the two existing vlans or its own separate one? (the domain controller will have a backup)

To my knowledge the DHCP can be done using the IP Helper settings on our Cisco router but I’m unsure as to where the DHCP server need to be located (what vlan) for this to work.