amorouspxy

I currently have it set up with a domain controller running RIS. I have a boot disk that can auto detect the NIC and will use the appropriate driver for each card since our network is comprised largely of older machines pieced together as we go along. This works out great with our networks...nearly seamless. Here's a great step by step guide as to how to set it up including where i found the amazing boot disk. http://www.highwaycsl.com/IT/Ghost/Deploying%20Ghost%20Images%20With%20RIS.pdf The only issue that I have right now is that with windows 2003 sp2 we get WDS instead of RIS. I have my great boot disk that works perfectly for us, but without risme I don't know how to convert it to a WIM for use as my boot file. Perhaps I'm going about this the wrong way but I've only just discovered WDS and haven't had time to do a great deal of reading on it. If anyone's got any ideas on this one I'd greatly appreciate them. Thanks.

Isn't there an option in Outlook where your email is internet based. That way you can check it anywhere much like with yahoo, etc. You have to set up the account again, I believe. I don't think it's something you can simply change on an existing account. Also, I believe for that you have to click the box to leave a copy on the server. Hmmm......now I have to go play with Outlook because it's been a while since I set it up that way. Since we have our own mail servers I found it was much easier to just set up the accounts on each machine where they leave a copy on the server for the roaming staff.

***Update*** I never did get the boot disk to go through without prompting for a password, but I used it anyway. I can update that at any time once I get the batch file working right. I did, however, manage to PXE into RIS and then boot on into ghost as planned to create and restore images today. More than a day and a half early based on the goals I set for this project. Aside from having to learn to edit script this was a rather easy project.

Thanks for the prompt reply. It's when the boot disk is running. It maps the drive to the ghost server and then gives me an error that the password is incorrect. Then it prompts me for the password. I type it in and then it boots into ghost. This is my first experience with working with any of this aside from ghosting across a non AD network with a server that was built for us so I'm in over my head a little bit. I set up ghost to multicast before I try to boot in so I really don't think that is the problem. It might be something with the script in the boot disk, but honestly I don't know. I found it online and it auto detects the nic and uses the correct driver. I have yet to find a computer on this campus that it will not boot and that's a blessing because on the other ghost server that was built for us we have to create a boot file for each computer type or a boot disk depending on the nic.

I'm working on a server using RIS to PXE into Ghost. I'm building it on a test domain because we're not setting up our campuses on a domain until summer so it has no GPO's but I have configured DHCP, AD, and most or RIS. I have a second server that I have installed Ghost on. I am working on my boot disk. I found a great one that I have edited with my domain logon information and then a batch to map a drive to the ghost server and run the ghost.exe. The problem I'm having is that when it comes to the end it asks for the password before it will launch ghost. Is there something I need to do to my ghost server so that it won't require the password to run ghost.exe? Or do I need to write something to make it log on with the username and password in the boot disk? I've never done anything like this before and I'm really kind of stuck. Any advice or insight would be great. Thanks.