I have set up a testing environment using RIS and RISME to serve ghost images of combinations of windows and office to a couple of test
clients. The problem is that RIS asks for a username and password at
the blue client installation screen and some of my less IT savvy users
"can't cope" with the challenge that this presents. Is there any way
that I can automate the login process so that their poor little brains
don't burn out before they start testing! No users no job!
Round Robin RIS ... I want to increase the available bandwidth for our RIS... specified a multiple IP host name but the clients only go to one ... find out who resolves the hostname i.e. the DHCP server or the PXE ... RIS to use multiple NICs simultaneously? ... (microsoft.public.win2000.setup_deployment)
Re: Why wont RIS work anymore? ... Do you see where the PXE clients get an IP, but just no reponse from RIS?... Or do they not even get an IP from the DHCP server?... To verify and/or "authorize" a server, utilize the network's DHCP Manager... (microsoft.public.win2000.general)
Re: Why wont RIS work anymore? ... Do you see where the PXE clients get an IP, but just no reponse from RIS?... Or do they not even get an IP from the DHCP server?... To verify and/or "authorize" a server, utilize the network's DHCP Manager... (microsoft.public.win2000.setup_deployment)
Re: Why wont RIS work anymore? ... Do you see where the PXE clients get an IP, but just no reponse from RIS?... Or do they not even get an IP from the DHCP server?... To verify and/or "authorize" a server, utilize the network's DHCP Manager... (microsoft.public.win2000.setup)
Re: Why wont RIS work anymore? ... Do you see where the PXE clients get an IP, but just no reponse from RIS?... Or do they not even get an IP from the DHCP server?... To verify and/or "authorize" a server, utilize the network's DHCP Manager... (microsoft.public.win2000.networking)
