Hi guys,
I've recently caused an issue with my RIS server. We are in the middle of a virtualisation project, and overnight I ran the VMWare converter agent on our RIS server to bring it up on the VMWare ESX4 Host. The conversion went fine, and WDS (running in legacy compatibility with RIS as the functional part - as of yet we don't deploy vista/7 images) appears to be running fine, all services start, etc etc.
Now the fun part is that the machine has now moved from our old 192.168.x.x single subnetted LAN to our new VLAN'd network, and is currently residing in 10.1.0.x (10.1.0.19 to be exact). So the IP has been changed (statically), and the server has been re-authorised in DHCP and AD (by running the RISetup.exe -verify command). The services were then stopped and started.
Now I can't get any clients to boot from it at all, and I'm not sure what to try next given that I've done everything that I can think of.
Any ideas?
I've recently caused an issue with my RIS server. We are in the middle of a virtualisation project, and overnight I ran the VMWare converter agent on our RIS server to bring it up on the VMWare ESX4 Host. The conversion went fine, and WDS (running in legacy compatibility with RIS as the functional part - as of yet we don't deploy vista/7 images) appears to be running fine, all services start, etc etc.
Now the fun part is that the machine has now moved from our old 192.168.x.x single subnetted LAN to our new VLAN'd network, and is currently residing in 10.1.0.x (10.1.0.19 to be exact). So the IP has been changed (statically), and the server has been re-authorised in DHCP and AD (by running the RISetup.exe -verify command). The services were then stopped and started.
Now I can't get any clients to boot from it at all, and I'm not sure what to try next given that I've done everything that I can think of.
Any ideas?