Search the Community

Hello, I've just created a RIS image from RISetup. Deployed it to a VM no problem. Now, I've just tried to deploy the same image to an old machine and the image I've created does not appear in the list on the 'OS choices' screen in setup. My VM running on VMWare Server sees a choice of 32-bit or 64-bit XP, then it sees the full list of all the images on the RIS server. My old machine doesn't get the choice of 32/64 bit and doesn't get the choice of all images. Does RIS decide which machines can see which images? How does it do it?

Please help We run WDS Native, We deploy XP As legacy images. I know that in the options on the client after F12 you can select Maintenance And Troubleshooting, microsoft say you can add tools to here like BIOS flash, Anti-virus scanning and memory scanning etc. This would really be usefull on our network if only i knew how to add these tools and set them up especiallythe bios flash, due to a known fault some motherboards we have. I have looked everywhere on the internet but to on avail, Does anyone know how this can be done your help would be greatly appreciated.

We have been running RIS since I started here a good number of years ago, but after upgrading my domain controllers to windows server 2008 ent, we have been receiving the following error on RIS down; "The user you have specified is not permitted to join the machine to the domain. Would you like to proceed for now and try and join the domain later" If you click no, and then re-enter the same username and password that you used to start the RIS session it will join fine. I have tried the following: New images Blank Windows Image Different Accounts e.g. domain Administrator New RIS server Google All to no help, the RIS server is still running 2003 server as we are still using RIS image and don’t want to use the new style images. Any help would be great,

Right, my lovely RIS server has been updated with the latest service pack and now runs WDS in mixed mode. I'm trying to deploy an image for a HP DC7700 and need the flexibility to be prompted for a machine name on setup. OSChooser in RIS allowed that under custom mode, but WDS either wants a list of machines whilst being prestaged or makes a psudo random name, neither of which are good enough solutions. Any idea how to get WDS to prompt me for a machine name? Burnsy

I've been cleaning up my GPOs and I found that the RIS Client Installation Services, Custom, Restart and Tools are Disabled. I tried to configure them to "Not Configured" as I was wondering if this might have been the cause of my WDS deployment never working. I set the options with no errors close the GPO but when I run a Refresh the settings are back to "Disabled" I've done this 3 times now. Am I missing something?

Is it possible to have RIS and WDS on the same network? How do the clients select which one to use? I'm asking because I've got my old RIS server set up very well with XP images. I leapfrogged Vista and and am now dabbling with 7, so am a bit out of touch. I want to start using WDS but not at the expense of my RIS server. Last time I upgraded a RIS server to WDS, it broke it.

Morning everyone, Having a little problem with a new RIS server I am building. The previous techician build one the other year and since the server started playing up I decided to rebuild it. Everything seems to be working. I have my flat CD image on the server. I have made sure the AD/DHCP is aware of everything. The machine starts up - F12 blah blah - type in the the username for building (on the Custom option), give the machine name and away it goes. The machine connects to the server and starts installing Windows XP. All the drivers go on (set this up fine). The whole thing then stops and tells me that it cannot connect to the Domain and I am not sure why. It has already connected to the domain and has been put in the correct part of the school OU. I'm thinking I must have missed something somewhere but cannot see what. Any ideas? Many thanks Gareth

Hi All Im having a problem at the moment where I can not seem to image new computers using RIS. Any computer that i purchsae which is an i5 with the intel DQ57TM motherboard will not work. I can PXE boot the computer, start RIS and start to initiate the installation but on the blue screen where files copy from the RIS server to the client nothing happens. Ive tried many solutions but nothing seems to work. Has anyone got any ideas?

We have a large number of Dell Optiplex 360 machines to install over several sites. Machine has a Broadcom Gigabit Ethernet adapter. When trying to create a RIS image the dreaded "The operating system image you selected does not contain the necessary drivers for your network adapter. Try selecting a different operating system image. If the problem persists, contact your administrator. Setup cannot continue. Press any key to exit." message appeared. No matter which driver files (From Dell 0r Broadcom) were put into the $OEM$ or i386 folder and tweaks to inf files as per Broadcom Ethernet FAQs, could not get RIS to work. Eventualy tracked down; Broadcom.com - NetXtreme II 1 Gigabit Drivers Go down the page to "Windows Remote Installation Service (RIS) Drivers" and download the appropriate Windows 2000 / 2003 Ris zip file. (zip file for Server 2003 attached) There is a readme for Server 2000. Unzip the 2 files and put them in the i386 folder. Run - net stop / start binlsvc. Voila - RIS deploys OS. win_xp_2k3_32-11.7.2.zip

Hi, Currently we use Ghost to gather and deploy our images. Each model is loaded with the required software and gathered. I've wanted to improve our current setup for a while but don't know what to move to. What do you reccomend that I look into to make our lives easier here, as there seem to be so many ways of deployment. WDS, RIS, MDT, SCCM, FOG or just stick with Ghost??? Thanks, Michael

Hi, We are currently running RIS to build our machines and it works a treat. When the machines boot up we press F12 and it looks to the network to boot and build. All nice - no issues there. We now want to implement a thin client solution for older machines. We have the server, we have the machines and we have a few licences to play with. However we cannot find a way of getting the machines to boot into thin client - it wants to load into the RIS build. It seems we cannot boot a thin client solution over the network if we have something else to boot into (RIS) - is this making sense? Therefore we are considering running something called ThinStation to boot into the XP image. Is this the right way to go or can we set it so that it boots straight into the XP image and not affect the other machines that will need to boot into RIS. It makes sense in my head what I am asking LOL. Cheers GJE

Hi, All I have just finished a remote installation after create a new image for a staff Laptop. On boot of Laptop it will start booting & get a blue error screen flash & restart it self over & over again. I don't even get to read the error as it is too fast. The Laptop is a Lenovo 3000 N200 0769-ECG with Windows XP Pro On a normal occasion I would search for the error via google but I can't seem to read the error message. Also is there a way of holding the screen. I was wondering if any one could help as I have to meet a deadline & am quite close to it. Thanks JAW$

Hello, We are using RIS (remote installation service) that now became WDS, to deploy OS to client computers. The problem is the drivers, I really need the all drivers to be "open" I mean not in executable format but rather .inf and .sys file and so on, that way RIS can automatically deploy them when installing the OS. If anyone know about a manufacturer that have all it drivers like that or any other recommendation how to resolve the problem I'll be grateful. So far I could find that HP and Dell can't guarantee open drivers. Many thanks Z. Shadar System admin St. Dominic's School, Surrey.