welsh_gje

Sounds like a permissions issue or an architecture issue. If you look at the permissions for the image group that contains the captured image, does the user (or a group the user belongs in) have rights to read the image file? If not, the user will not see it (and if it's the only image in the image group, the user will get this error). Second, make sure you are using an x86 boot.wim as the boot image if you plan on deploying any x86 captured WIM files - x64 boot.wim cannot see x86 WIM files, so if you're using an x64 boot.wim and this is an x86 XP WIM image, you will also not see the image in the list (and again, if it's the only image in the image group, you'll get this error).As to your second issue, I've never before experienced that problem, although it could be a DNS issue. Are you doing this directly on a domain controller, or are you doing this from a remote workstation using AD or RSAT tools? First Issue - Yes I've checked all of them. I thought it may be a HAL issue but even when I try and push the image back to the machine where it came from I get the same issue. I'll check the permissions tomorrow. I've checked the permissions on the 'Image' folder in and added some permissions. I also added Everyone as 'Read' - I saw this on another forum somewhere so I did it. I've not added any permissions from within WDS. The second issue - the Active Directory is seeing the WDS server when pre-staging or else I assume it would't list it with the others. Our WDS is not on the domain controller. The domain controllers for the Local Education network are held elsewhere. Our WDS is a member server held in our branch of the AD. DNS has been checked and nslookup has been run. Regards and thanks for the reply, Gareth

Hi, When our RIS server died over the school summer holidays I decided to look at implementing WDS and using images to deploy one of two universal XPSP3 images. One image would include Adobe Creative Suite CS3 and the other wouldn't. All other software on the images would be the same. So I've set up a WDS server and it seemed to go quite smoothly. I followed various instructions to get the pxe files in there and the boot.wim file from a Vista Corporate disk. I captured the image of my basic machine (to practice) before going on to capture a proper full image. For the image, I put drivers in a C:\Drivers directory and pointed the sysprep config file to the new directory (Using a tool mentioned on the web - cannot remember the name). Resealed and captured. When I go to deploy the image I manage to get into the Vista style deployment screen, I am prompted for a domain username and password which I enter. I am then told no images are available. That is the first issue. The second issue comes when I try and pre-stage machines. I create the machine in the AD. I add the GUID and then search for WDS servers. There are around 5 on the LEA domain in certain schools. I can see mine and I choose it. Clicking apply gives me the following error: Server Object Not Found The server cannot be found on the network because the server is not a Remote Installation server, the server is not on the network or you are experiencing network problems. Do you still want to use the server name? Yes | No I originally used Server 2003(SP2) + WDS and then pulled my hair out and rebuilt the whole server to Server2003R2(SP2) + WDS. Still the same problem. DHCP is on another machine and is set up correctly (as is the WDS). The WDS server is also authorised in DHCP. Options 66 and 67 are set correctly in DHCP. Machines can PXE boot and capturing an image isn't a problem. I'm not sure what else I can describe to ask for help. If anyone can advise that would be great. Gareth